To support warehouse operators in their daily workflows, we’ve built a specific cross dock module into our mobile application

Configuration

When using scanning via the Mobile App, there are some functions that require setup in the Qargo software.

Navigate to CONFIGURATION > 'Integrations'
From the side menu, select 'Mobile app / Subco portal'
Under the Configuration panel there are 2 options that can be toggled on/off:
- Location scan required.
- Default keep pallet on trunk when unloading

Location scan required.

When toggled on, this will add the requirement for a location to be scanned before the pallet is scanned. There are 3 options when scanning locations:

Store in depot: Depot location scan
To delivery vehicle: Delivery vehicle scan
Keep on Trunk: Remain on trunk (Location scan bypassed)

Default keep pallet on truck when unloading.

With this option toggled ON, the default option there is no location or action option, it will immediately default to scanning pallets.

Permissions

The module is available for the following roles: Admin, Super Admin, Qargo Admin and Warehouse operator. It’s not visible for drivers.

Navigate to CONFIGURATION > Organisation settings
Scroll down and click on 'Add user' and give that user Warehouse operator as Role.

Once enabled, you’ll see an additional tab in the mobile app, i.e.

Modes

The cross dock app has 2 modes (pallet per pallet / Bulk pallets) that can be used to control the behaviour of the built in flows.

Location scanning

Scan the location pallets are put down (eg: bay in the cross dock or a delivery vehicle), which is then shown in the pallet tracking history.

Keep pallets on truck while unloading

Where depots do not have space to offload and store freight, it may stay on the trailer and is loaded directly from there to the outbound vehicle

Bulk Scanning workflow

Select scanning mode 'Pallets in Bulk'
Select option for Location or Action. (Based on configuration)
Scan location / action barcodes
Scan all pallets that are to be placed in that location / require that action

When processing multiple pallets, there is the option to switch between options for each pallet as needed. For instance, an incoming vehicle has multiple pallets, some that are to be loaded to the delivery vehicle and others that will be held pending delivery. Use the 'Choose new action' option to change the action.

It is not possible to switch between scanning options for a single pallet and bulk pallets.

Use cases

We’ve identified 3 major use cases which we’ve built into the app:

Use case 1: unloading an inbound vehicle
Use case 2: loading an outbound vehicle
Use case 3: free scanning

Use case 1: unloading an inbound vehicle

This use case fits in the “unloading” and “store” events of Cross dock events.

The unloading action will:

tell warehouse operators what to do with a pallet they’re unloading. This is the digital equivalent of the pallet label. All relevant routing information is visualised in the app, which allows them to put the pallet onto the correct outbound vehicle, or tells them to store it in the cross dock when the outbound truck has not been assigned yet.
register following scans:
- “scanned in” when the pallet is scanned, as from that point we know the pallet was brought into the depot
- “scanned out” when the outbound vehicle is known at the moment in time the scan takes place (doesn’t happen when Keep pallets on truck while unloading is enabled)
- “stored” when the outbound vehicle is not yet known at the moment in time the scan takes place (doesn’t happen when Keep pallets on truck while unloading is enabled)

Use case 2: loading an outbound vehicle

This use case fits in the “loading” event of Cross dock events.

The loading action will:

support the warehouse operator with an extra verification that all pallets that should be on that trip are also present on the truck
- this functionality is only relevant when the trips are also planned in the TMS. For outbound trunks that are not planned in the TMS the verification doesn’t happen.
register the “scanned out” scan for each scanned pallet
- note that this already may have happened if the “unloading” and “free scanning” flows were executed for the pallets, since those also may generate a “scanned out” scan when a pallet is moved from the inbound vehicle or from the cross dock (only happens when Keep pallets on truck while unloading is enabled).

Pallet barcode reference.
Scan action status. In this case the pallet was scanned loaded onto the vehicle.
Trip details for the scan activity. Depending on the activity this may also show a vehicle ID or location. Also includes the user details (email).

Use case 3: free scanning

This use case fits in the “loading” and “store” events of Cross dock events.

The free scan action will:

support the warehouse operator to handle a pallet that is present in their cross dock
- they can verify if routing information is available, and load the pallet if that is the case
- it also allows them to move a pallet from one location in the cross dock to another
register following scans:
- the “scanned out” scan for each pallet that is loaded on an outbound truck
- the “stored” scan for each pallet that is moved inside the cross dock

💡PRO TIP: It is possible to free scan pallets to a location.

Use a 3rd party website like THIS to produce in-house barcode labels that can be used to identify pallet locations.