One Demo, Six Freight Modes. Which Workflows Actually Hold?
Key Takeaways
- A multimodal claim holds only when each mode’s workflow survives that mode’s most common failure on a real lane. Six happy paths prove six screens, not six workflows.
- Choose the failure that actually breaks each mode: a reclassified LTL invoice, an FTL truck that doesn’t show, a rolled ocean booking, a container not ready for drayage, a parcel that stops scanning, a document the broker sends back.
- Grade every cell as holds, holds with approval, partial or narrated, and record the lane along with the mode.
- Coverage depends on the lane: the approved carriers, the tracking sources and the partners on that lane decide what can be executed.
- Wilson, by Cartage, supports LTL, FTL, ocean, drayage, parcel and cross-border freight. In cross-border, it coordinates documents and follow-up with the customer’s broker, carriers and forwarders; it does not clear customs.
When does a multimodal workflow actually hold?
A workflow holds when the system takes a real order in that mode to a recorded end state, and still reaches a correct end state after the mode’s typical failure is introduced. Anything less is coverage on paper.
Most multimodal demos run one mode in depth, usually truckload or LTL, and narrate the rest. The six modes share a lifecycle but break in different places, and a demo that never touches those points can’t show whether the workflow survives them.
Use three conditions for a pass:
The next action happens without a coordinator reassembling information from inboxes or portals.
The failure is handled inside the configured rules, or escalated with what happened, what was tried and the decision needed.
The outcome is recorded on the shipment.
What each mode involves day to day is covered in Six freight modes, one coordination layer, and the capabilities to check in each mode are listed in Six freight modes, one operation. What must the software cover?. This guide is the test plan: which failure to inject in each mode, how to grade the result and how to read it lane by lane.
How do you run a six-mode test in one session?
Run the modes one after another, in order of your volume, with one real order and one named failure each, and grade each mode before moving to the next.
Drop modes you don’t ship. Testing a mode you only plan to add is fine; label it as such.
Pick one real lane per mode. Use a lane you actually run, with the carriers you actually use on it.
Bring the order as your system produces it. An ERP export, a spreadsheet row or an emailed order, not a cleaned-up sample.
Name the failure in advance, not the timing. The vendor knows a missed pickup is coming, but not when.
Hold the controls constant. Same approved carrier list, same approval limits, same notification recipients in every mode.
Grade before moving on. Write down the grade, the lane and where the evidence sits on the shipment while it’s in front of you.
What changes by mode that the test has to catch?
Each mode has a weak point that a generic demo skips. The test should put pressure exactly there.
- LTL. Class comes from item weights and dimensions, and accessorials show up on the invoice that weren’t on the quote. Watch whether a reclassification is caught when the invoice is checked against what was booked.
- FTL. The risk is a tendered truck that doesn’t arrive. Watch whether the system confirms the pickup ahead of time, notices the miss and rebooks from approved carriers within the rules or with approval.
- Ocean. A rolled booking moves the departure, which moves arrival, drayage and the consignee’s plans. Watch whether the downstream parties hear about it, not just whether the milestone changes.
- Drayage. The container may not be available when the truck is booked. Watch the follow-up with the drayage carrier and whether the team knows the new pickup plan.
- Parcel. Volume is the issue. Watch rating, labels, pickup and tracking, then a package that stops scanning, handled as an exception rather than lost in a list of hundreds.
- Cross-border. The carrier may accept the load while the shipment waits on paperwork. Watch whether the system follows up with the customer’s broker and the shipper when a document comes back, and records each exchange. Customs clearance itself stays with the broker.
How should a buyer grade the results and read them by lane?
Grade each mode on four levels, then read every grade as a statement about one lane, not about the whole mode.
- Holds: order to end state, failure included, inside the rules.
- Holds with approval: the same, with a person approving a step the rules route to them. A pass, if the request carried enough context to decide.
- Partial: the steps ran until the failure, then a coordinator had to rebuild the situation.
- Narrated: the vendor described the workflow instead of running it. Treat it as unsupported until shown.
Lane matters because what can be executed depends on what exists on that lane. A carrier with an API gives a different tracking source than one that only answers the phone. One lane may have three approved carriers to rebook with; another may have one. A cross-border lane involves a broker and possibly a forwarder whose responsiveness the software doesn’t control. A “holds” on one LTL lane is good evidence, not proof, for the next.
Two more rules. Weight grades by volume, but don’t ignore a “partial” on a low-volume mode carrying high-value or time-critical freight. And keep adjacent jobs, such as customs clearance or dock scheduling, out of the grade; if a vendor claims them, verify them separately.
The six-mode test matrix
Use this matrix as the session agenda. Each row is one order, one failure and one pass condition. Add a grade and a lane for each row as you go.
| Mode | Bring this order | Inject this failure | It holds when | A person should appear when |
|---|---|---|---|---|
| LTL | Mixed-SKU order with real weights and dimensions | Invoice arrives with a higher class than quoted | The mismatch is flagged against the booking and payment waits | The carrier’s reclassification needs a dispute decision |
| FTL | Full truckload with a set pickup window | Truck doesn’t show; carrier goes quiet | Miss detected, carrier chased, rebooking started from approved carriers | The replacement rate is above the approval limit |
| Ocean | Container booking with a downstream delivery | Booking is rolled to a later vessel | New ETA reaches the team, the drayage side and the consignee | The new date breaks a customer commitment |
| Drayage | Import container pickup from port or rail | Container isn’t available at the booked time | Drayage carrier followed up; new pickup plan recorded and shared | Extra charges need approval |
| Parcel | A batch of parcel orders from one day | One package stops scanning after pickup | Exception raised for that package; carrier contacted; customer updated if configured | A claim or reship decision is needed |
| Cross-border | Order shipping to Mexico or Canada | Broker returns a document for correction | Broker and shipper followed up; corrected document tracked to the shipment | The company must decide on content the broker needs |
Grade sheet per row: mode, lane, grade, where the evidence sits on the shipment, and anything that needed lane-specific setup.
How does Wilson, by Cartage, handle a six-mode test?
Wilson, by Cartage, is an AI logistics agent that supports LTL, FTL, ocean, drayage, parcel and cross-border freight, with the same control model in every mode. For the broader category, see what an AI logistics agent is.
In every mode, Wilson works from the customer’s order data (ERP feed, scheduled file drop, spreadsheet, email or API) and tenders the customer’s approved carriers first. Cartage can introduce additional capacity, but the customer approves any carrier before Wilson uses it; if no approved carrier accepts, Wilson escalates. Wilson tracks each load with the best available source: carrier API, GPS/ELD where available, the carrier website by PRO number, and email or calls when those don’t answer. For parcel, Wilson rates, labels, schedules pickups, tracks and audits shipments with FedEx and UPS. Carrier invoices are audited against what was booked before payment under approval rules.
Cross-border needs a plain statement: Wilson is not a customs broker and does not clear customs. It coordinates freight documents and follows up with the customer’s broker, carriers and forwarders, and what it can execute depends on the lane and the partners on it.
Messages, confirmations and changes are recorded in each shipment’s history, which is where the matrix evidence lives. Wilson starts with assisted execution, and the customer sets the approval boundaries. Most teams start on a few lanes and expand mode by mode.
Pick the two modes where your team loses the most time, bring one real order from each and the failure you want to see, and grade what Wilson does lane by lane.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai