One load, five reference numbers, no clear answer.

Key Takeaways

One load typically carries 5 or more reference numbers: the order number, the customer's PO, the BOL number, the carrier's PRO number and the carrier's invoice number.
Each team searches by a different one. Sales knows the PO, the warehouse knows the BOL, the carrier knows the PRO and accounts payable knows the invoice number.
The fix is one shipment record per load that holds every number and document as it's created, not a cross-reference built after a question comes in.
Wilson, by Cartage, is an AI logistics agent that creates the shipment from the order and keeps every document, message and change on it from quote to payment.
Wilson replaces the TMS as the system of record for shipments and connects to the ERP, where order data already lives.

Why do reference numbers cause so much confusion?

Reference numbers cause confusion because each team creates and uses a different one, and nothing ties them to the same load at the moment they're created. A simple question ("where is this order?" or "is this invoice right?") turns into a search across the ERP, inboxes, shared drives and carrier websites. The answer exists; it's just split across five places.

This affects any manufacturer or distributor that books freight by email and spreadsheet, with the ERP on one side and carriers on the other. It isn't unusual: in a BCI Global survey of 240 supply chain leaders, only 35% reported end-to-end visibility.

A few definitions. The BOL (bill of lading) is the document the driver signs at pickup that describes the freight. The PRO number is the tracking number a carrier assigns to an LTL shipment. The rate confirmation is the document that records the rate and terms agreed at booking, when the carrier commits to move the load.

Here is one question, with numbers given for example:

Tuesday, 9:05 a.m. A customer's buyer emails customer service: "Where is PO 7731?"
Tuesday, 9:20 a.m. Customer service finds sales order 20418 in the ERP. It shows "shipped" but no carrier, so they forward the email to logistics.
Tuesday, 9:45 a.m. The coordinator searches her inbox for 20418. The carrier's emails only mention the BOL number and the PRO number.
Tuesday, 10:30 a.m. She finds the BOL on the warehouse's shared drive, gets the PRO and checks the carrier's website: delivered Monday at 3:12 p.m.
Tuesday, 11:15 a.m. Customer service replies, two hours after the question.
Friday, 2:00 p.m. Accounts payable gets carrier invoice 88412, which shows only the PRO number. Nobody can find the rate confirmation, so the invoice is held and logistics gets another email.

Which reference numbers describe one load, and who owns each?

Usually five or six numbers describe one load, and each is created by a different party at a different moment. That’s why they drift apart: no single person sees them all being created.

Number	Created by	When	Who searches by it
Order number	Shipper’s ERP	When the order is entered	Sales, customer service
Customer PO	The customer	Before the order	The customer, sales
Shipment or load ID	Shipper’s logistics team	When the shipment is created	Logistics
BOL number	Shipper or carrier	Before pickup	Warehouse, carrier
PRO number	Carrier	At or after pickup (LTL)	Carrier, tracking
Carrier invoice number	Carrier	After delivery	Accounts payable

The mix changes by mode. FTL carriers may use their own load number instead of a PRO; parcel shipments have a tracking number per package; ocean adds booking and container numbers. The principle is the same: every new number has to land on the same record.

Timing is the real issue. The PRO number often arrives after pickup, by email or on the carrier’s website, and the invoice number arrives weeks later. If nobody attaches them when they arrive, the link has to be rebuilt by hand every time someone asks.

How do you link every number to the same load?

Make the shipment the center of the record and attach each number and document to it the moment it appears. It’s a routine, not a project, and it starts with the order.

Create one shipment per load from the order, carrying the order number and the customer’s PO.
Put the shipper’s references on the BOL. When the order and PO numbers are on the BOL, they often travel through to the carrier’s invoice.
Attach the PRO number when the carrier assigns it, not when someone needs it.
File every document on the shipment: the quote, the rate confirmation, the BOL, the POD (proof of delivery, the receipt the consignee signs) and the invoice.
Send status back to the ERP so sales and customer service can answer by order number without asking logistics.

Common mistakes

Treating the inbox as the record. Carrier replies stay with whoever received them, and the history leaves when that person is out.
Leaving the order and PO numbers off the BOL. The carrier’s invoice comes back with only its own numbers, and accounts payable can’t match it.
Filing the rate confirmation in a different place from the invoice. The audit can’t happen without both side by side. See keep the rate confirmation tied to the invoice.
Building a lookup spreadsheet after the fact. It’s out of date by the time it’s finished, and someone has to maintain it.

How does Wilson, by Cartage, keep reference numbers together?

Wilson, by Cartage, creates the shipment from the order and keeps every document, message and change on that shipment from quote to payment. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Wilson replaces the TMS: it’s both the system of record for shipments and the execution layer that does the work. Orders arrive through an ERP feed, a spreadsheet, email or a scheduled file drop, and Wilson works with SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs. Teams use Wilson’s dashboard the way they’d use a traditional TMS.

Step	Trigger	What Wilson does	When a person steps in
1. Create	Order arrives	Turns it into a shipment carrying the order details	If details are missing
2. Quote and book	Shipment is ready	Requests quotes from approved carriers, books and generates the rate confirmation and BOL	Above the approval limit
3. Track	Load is in transit	Uses the carrier’s API, GPS or ELD data, or the carrier’s website by PRO number; otherwise emails or calls	Exceptions it can’t resolve
4. POD	Load is delivered	Requests, follows up and files the POD	If missing past the set window
5. Audit and pay	Invoice arrives	Audits and reconciles it against what was booked, then pays from the company’s wallet	If the invoice doesn’t reconcile
6. Write back	Status changes	Optionally updates the ERP by CSV or Excel file, shared table or API	Not required

The controls are the company’s. Wilson starts with assisted execution, and the company sets which actions need approval, such as bookings above a cost threshold. Every message, confirmation and change on each shipment is recorded in the change history, so the record shows not just the numbers but who sent what, and when.

Write-back is optional and set up per customer, usually after order intake is working; see how shipment updates get back to the ERP. Customers can also follow shipments on a tracking link with the company’s branding, so customers can check status by themselves instead of emailing customer service.

Wilson doesn’t replace the ERP; orders and finance stay there. It works alongside a WMS through connections built per customer, with no pre-built WMS connectors today.

What changes when every number is on one record?

When every number is on one record, any team can answer a question about a load by the number it already has. The two-hour search becomes a lookup, and the invoice that was held becomes an audit.

Customer service answers by PO or order number, with the carrier, the status and the POD on the same page.
Accounts payable matches the invoice to the rate confirmation and BOL without asking logistics.
Logistics sees the full history, including carrier replies. See what happens to a carrier’s email reply.

What to ask a vendor to show in a demo

Bring in one of our orders and show the shipment record that’s created, with the order number and PO.
Show where the PRO number lands when the carrier assigns it.
Show the rate confirmation, BOL, POD and invoice on the same shipment.
Show a carrier’s email reply attached to the right shipment.
Show how status gets back to our ERP.

FAQs

How do I link order, PO, BOL, PRO and invoice numbers to one load? Create one shipment record per load and attach every number and document to it as it's created. Wilson, by Cartage, does this by creating the shipment from the order and keeping everything on it through payment.
What reference numbers does a freight shipment have? Usually an order number, the customer's PO, a shipment ID, a BOL number, a PRO number and a carrier invoice number. Parcel and ocean shipments add their own.
What is a PRO number? A tracking number the carrier assigns to an LTL shipment, typically at or after pickup.
Why doesn't the carrier's invoice show my order number? Often because the order and PO numbers weren't on the BOL. Put them there and they usually carry through.
Is Wilson a TMS? Wilson replaces the TMS: it's the system of record for shipments and the execution layer, and it connects to the ERP.
Does Wilson write updates back to the ERP? Yes, when the customer wants it, by CSV or Excel file, a shared table or API where one is available.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, covering the full shipment lifecycle.

Conclusion

Five numbers for one load isn’t the problem. Five numbers in five places is. When each number and document lands on one shipment record as it’s created, customer service, accounts payable and logistics can each answer from the number they already have.

Wilson, by Cartage, creates that record from the order and keeps it current through payment, which is what freight execution looks like in practice. Bring one load your team spent an hour tracing last week and watch Wilson build the record from the order in a demo at cartage.ai.

Sources

BCI Global, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai