A quick guide to XD (cross docking)

Created by Giedre Cesnuleviciene, Modified on Tue, 23 Apr 2024 at 10:22 AM by Giedre Cesnuleviciene

Cross-Docking


In logistics cross-docking is used when there is a need to deliver the goods from the manufacturer to the end user without long-term storage in the warehouse. Thus, usually, only the ordered amount of goods arrive at the temporary warehouse (doc). The goods are usually stored for not more than 24 hours. During that time it can be sorted out and dispatched as soon as a suitable vehicle is available. As a result the number of routes is minimized.                            

            

Traditional method of transportation a) from point A to point B as opposed to b) hub&spoke model    

    

Cross-docking functionality is available for the Enterprise plan only. Enterprise accounts will have an additional Enterprise management tab in the settings.             

    



Where and how to use XD in Track-POD?


Routes tab. Add Order window



XD mark in add/ edit order window


It is actually quite a rare case when during a cross-docking route the driver will need to pick up an additional order on the way. For example if the main warehouse is in Kaunas and the cross-docking warehouse is in Vilnius, the driver will need to pick up an order in Elektrenai during a cross-docking route between those two warehouses.



For a more convenient route planning the order in Elektrenai can be marked as XD. Such an order will have an “Order” note for it in the XD column in the Unscheduled section. 

Orders with such a mark cannot be routes. They need to be manually assigned to an XD route.



Routes tab. Route creation window


While creating a route, it can also be made an XD route. 



The XD mark will also be added for such a route in the Routes section on the dashboard:




Assigning routes for XD


Other routes can be added to an XD route afterwards as shown on the example:


Step 1. Choose option Assign Routes for XD



Step 2. Select routes for XD



Result: added route(s) is duplicated into the current one and becomes an “order” within this route where address = warehouse address and order number = route number and instead of the client name there is a “cross-dock” mark.



If such an “order” is deleted from the route, it returns to the Unscheduled section with a “Route” mark in the XD column. Orders with such a mark cannot be routed. Example below:



Note: you cannot add other Routes for XD to a non-XD route:




Adding XD routes


The second option, Add XD Routes, allows the addition of other routes to an XD route. It is available for both XD and regular routes. As a result a new route is created, where added routes are now presented as orders. 


Detailed example are in the screenshots:


Step 1. Choose a date, warehouse address, and necessary routes.



Only routes that don’t have an XD mark and routes without an order marked “Route” in XD column can be selected. It should also be mentioned that the route which the Add XD Routes option is being selected for, can also be added.


As a result, we get a new route where orders = selected routes.



Directories. Vehicles


Each vehicle in the Directories can also be marked as XD when the general setting for Cross-Docking is enabled.

It does not affect anything in the system. This option can mark which vehicles are suitable for XD routes.



In the dialog window and in the general Drivers’ tab there is a separate XD column as well.



Settings. Users


User permissions can be set individually to allow or disable the ability to view XD orders and routes.


View all - regular and XD orders/routes. View only XD - only XD orders/ routes. Hide XD - only regular.



If the option View only XD is selected, Pickup&Delivery type of order will be automatically selected in the order creation window.


Settings. Custom fields.


XD option can also be selected for a custom field. 



For web-users with Hide XD option enabled such XD only field in the custom field section won’t be visible. 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article