Cross docking system: from the mixed trailer to the load sorted by delivery sector
The trailer arrives packed with volumes from dozens of invoices, all mixed. The WMS cross-dock mode receives it blind, by volume; builds one labeled pallet per invoice; stores it in a dedicated cross-dock area; shows the floor grouped by delivery sector and only lets the pallets on that load onto the truck — with a PDF load sheet.
The cross dock screens
From the mixed trailer to the load sheet, no paper in between
All in the browser, with a USB or Bluetooth barcode reader — or the handheld in keyboard mode. Every scan is recorded with who did it and when.
Cross docking is the operation where cargo crosses the warehouse without becoming stock: it arrives at one dock, is checked, sorted by destination and leaves on another vehicle. In BrainCargo’s WMS cross-dock mode, the load’s NF-e (electronic goods invoice, XML) invoices are linked to the vehicle before unloading; the team performs a blind count by volume (volume = an individual package) — the expected quantities only appear at closing —; shortage, overage and damage are entered in a supervisor approval queue, with an optional photo; the pallet is built guided, one per invoice, with its own label, and addressed to a cross-dock area separate from storage; and the load is built per delivery sector from the floor view and checked by scan — a pallet not on the load is refused — with a PDF load sheet. The “where is the invoice” search shows the stage, address and days in the warehouse by invoice number, key or pallet label.
It’s the routine of anyone running less-than-truckload: the trailer arrives “mixed”, with volumes from dozens of invoices jumbled together, and needs to leave sorted by destination. Without a system, checking becomes counting on paper, the missing volume only shows up at the customer, and the question “where’s that invoice?” stops the dock. Cross-dock mode was built for carriers and logistics operators who work this way every day — and it lives in the same WMS that stores depositors’ inventory.
Everything runs in the browser, with a USB or Bluetooth barcode reader on the dock’s computer or tablet — you can start without a dedicated handheld. And it doesn’t replace what already works: the TMS you use (SSW, a widely used Brazilian TMS, for instance) keeps issuing the CT-e (the electronic freight bill of lading); the WMS handles what happens inside the warehouse, from inbound dock to outbound dock.
For management, the gain is visibility: the day’s dashboard shows vehicles, receiving sessions, pending approvals and open loads; every discrepancy has an owner and can carry a photo; and each invoice’s history answers where it is and for how many days. See also the WMS for logistics operators.
What you can achieve
Blind
receiving counted by volume
The team counts what arrived without seeing the expected quantities; the difference against the NF-e invoices appears when the receiving session closes.
Photo
optional, on a discrepancy
Shortage, overage and damage are recorded at the dock — a photo can be attached — and wait in a queue for the supervisor’s decision.
1 pallet
per invoice, labeled
Guided building: the system suggests the next invoice, counts built × expected and prints the pallet label.
Scan
load checked on scan
A pallet that is not on the load is refused on the spot; on closing the load, the load sheet comes out as a PDF for the driver.
Why this module
Fewer lost volumes
Every volume is scan-counted on arrival, every pallet carries the invoice on its label, and the load only accepts the pallet that belongs to it. The missing volume shows up at the dock, not in the customer’s complaint.
Evidence for damage
A photo can be attached at the dock, at unloading time, and stays with the discrepancy — which only proceeds with the supervisor’s decision. The conversation with the shipper starts with evidence, not memory.
“Where is the invoice?” in seconds
By number, key, DANFE scan or pallet label: stage, address and days in the warehouse — without anyone going to look on the floor.
Dwell time visible, per invoice
Each invoice’s days in the warehouse are recorded from arrival: the baseline to discuss dwell-time limits with each customer without a parallel spreadsheet.
Sector load, checked by scan
The floor view by delivery sector shows what’s ready for each sector; the load is built from it and checked by scan — a pallet outside the load is refused. Closed means the load sheet is printed.
The whole dock on one dashboard
The day’s vehicles, receiving in progress, pending approvals and open loads on one screen — for the supervisor and for management.
How cross docking works in BrainCargo’s WMS, in 6 steps
From the invoice’s XML to the load closed by delivery sector, everything recorded by scan.
-
Link the NF-e invoices to the vehicle
The invoices’ XMLs arrive before the trailer and are linked to the vehicle: the dock knows what to expect without typing anything.
-
Receive blind, by volume
The team scans volumes without seeing the expected quantities. On closing the receiving session, the system compares against the NF-e invoices.
-
Record the discrepancy
Shortage, overage or damage go into the supervisor’s approval queue — a photo can be attached.
-
Build one pallet per invoice
Building is guided: the system suggests the next invoice, counts built × expected and prints the pallet label on the Zebra (via the print hub or by downloading the ZPL).
-
Address it to the cross-dock area
The pallet goes to the cross-dock area, separate from storage; the floor view by delivery sector shows what’s ready for each sector.
-
Build the load by delivery sector and close
The load is built from the delivery-sector floor view and checked by scan: a pallet not on it is refused. On closing, the load sheet comes out as a PDF.
What's included
- NF-e (XML) invoices pre-linked to the vehicle before unloading
- Blind receiving counted by volume — expected quantities only appear at closing
- Shortage, overage and damage discrepancies — a photo can be attached
- Supervisor approval queue for every discrepancy
- Guided pallet building per invoice, with built × expected counts
- Pallet label with invoice, delivery sector and volumes (Zebra printer; ZPL, the Zebra label language, via the print hub or download)
- Addressing in the cross-dock area, separate from storage
- “Where is the invoice” by number, key, DANFE scan or pallet label — with stage and days in the warehouse
- Floor view by delivery sector: stored invoices grouped by delivery sector, with volumes, kg, m³ and days
- Load building per delivery sector, checked by scan — a pallet outside the load is refused
- Load closing with a PDF load sheet
- Day dashboard: vehicles, receiving sessions, pending approvals and open loads
- Runs in the browser, with a USB or Bluetooth barcode reader (or a handheld in keyboard mode)
- Lives alongside your TMS or ERP: the CT-e keeps coming from wherever it comes today
- In the same WMS as 3PL storage: depositors, labels, reports and, for those who store, the monthly billing
Cross docking in the WMS, on a spreadsheet or TMS-only: what changes at the dock
| Criterion | BrainCargo (WMS with cross dock) | Spreadsheet and paper | TMS only |
|---|---|---|---|
| Trailer check | Blind, by volume, on the scanner | Paper count against the invoice | Out of scope |
| Discrepancy | In the supervisor’s queue, photo optional | A note and a photo on a personal phone | An incident logged afterwards |
| Pallet | One per invoice, with a label | Hand-written ID | Not tracked |
| “Where is the invoice” | Search by number, key or pallet label | Asked over the radio | Only the document status |
| Load by delivery sector | Checked by scan; refuses pallets outside the load | Visual check | Load sheet without physical check |
Process criteria, not brands. The TMS keeps issuing the CT-e; the WMS handles what happens inside the warehouse.
WMS family
Warehouse, cross dock and client in one system
The same WMS stores depositors’ inventory and runs cross-dock cargo — with role-based access; the storage depositor checks their stock and closing in the portal.
- WMS for 3PL warehouses Receiving via the NF-e XML, scan-based addressing, checked FEFO picking and cycle counting, with inventory segregated per depositor.
- you are here Cross docking system Mixed trailer → blind receiving by volume → one pallet per invoice → load checked by scan, with a PDF load sheet.
- Blind receiving The team counts what arrived without seeing the invoice; the difference appears at closing, and shortage, overage and damage go to the supervisor’s queue — a photo can be attached to damage.
- Depositor portal The warehouse’s client checks balance, movement statement and the month’s closing on its own, under your warehouse’s brand.
- Storage billing The month’s inventory becomes a per-contract closing for each depositor — no parallel spreadsheet.
- WMS for logistics operators Several clients in the same warehouse, role-based access, Zebra labels and reports under the warehouse’s brand.
Frequently asked questions
What is cross docking?
It is the operation where cargo crosses the warehouse without becoming stock: it arrives at one dock, is checked, sorted by destination and leaves on another vehicle, usually the same or the next day. The name comes from “crossing the dock”.
What is the difference between cross docking and warehousing?
In warehousing, goods sit in a stock position, controlled by SKU, batch and expiry, and billed by dwell time. In cross docking they just pass through: control is by invoice, volume and destination, and the goal is to leave fast. In BrainCargo’s WMS the two coexist, with the cross-dock area separate from storage.
Is cross docking the same as transshipment?
No. Transshipment is just moving the load from one vehicle to another. Cross docking is the complete dock process: receive, check, sort by destination, build and dispatch — with a record of every volume.
What are the types of cross docking?
In direct (pre-distribution), the load already arrives sorted by destination and just changes vehicles. In indirect (post-distribution or consolidated), the load arrives mixed and is broken down and rebuilt at the dock — the case of the LTL “mixed” trailer, which is the focus of the WMS cross-dock mode.
What is blind receiving?
It is counting what arrived without seeing the invoice’s quantities. The receiver scans the volumes; only at closing does the system compare against the NF-e invoices and point out shortage or overage. It avoids “eyes-on-the-invoice” checking, which confirms the paper instead of what’s on the dock.
Do I need a WMS to do cross docking?
With a few invoices a day, paper works. When the trailer brings dozens of mixed invoices and the outbound leaves by delivery sector, the system is what ties each volume to its invoice and destination — and what answers “where is the invoice” without anyone walking the floor.
Does it work for less-than-truckload?
It is the carrier’s typical use: the trailer arrives with volumes from many invoices and shippers, the team checks by volume, builds one pallet per invoice and the load leaves by delivery sector.
Do I need to replace my TMS or CT-e issuer?
No. The WMS handles what happens inside the warehouse; the CT-e keeps being issued by the TMS you already use (SSW, for instance). If you want, BrainCargo’s CT-e issuer is also available on the same account.
Do I need a handheld data collector?
Not to start: cross dock runs in the browser, with a USB or Bluetooth barcode reader on the dock’s computer or tablet. Anyone who already has a handheld uses its reader in keyboard mode.
How does management follow the operation?
Through the day dashboard: vehicles that arrived, receiving in progress, pending discrepancy approvals and open loads. Every discrepancy has who recorded it, the photo, if one was attached, and who approved it, and every invoice shows its stage and days in the warehouse.
Your mixed trailer, sorted by delivery sector
Talk to us on WhatsApp and book a cross-dock demo with your dock’s own flow.
Modular pricing, sized to your operation: you only pay for the modules you use, and the plan scales with your volume. Ask for a quote on WhatsApp.