Freight coordination software for manufacturers: buy the workflow, not the dashboard

Key Takeaways

A manufacturer should buy freight coordination software for the workflows it completes, from plant order release to carrier payment, not for the screens that display them.
The test unit is one plant's real week, covering outbound finished goods and inbound raw materials.
For each of 10 workflows, the buyer separates "completes the work" from "displays it only," asks for evidence and notes when a person is still needed.
An approval step the plant chose is not a failure; a coordinator retyping or chasing to finish the step is.
Wilson, by Cartage, is an AI logistics agent that replaces the TMS for freight execution, connects to the ERP and completes these workflows under the manufacturer's carriers and rules.

What should a manufacturer pay freight coordination software to do?

A manufacturer should pay for freight work that ends finished: a carrier booked, a pickup confirmed for the dock, a POD filed, an invoice audited and paid. A dashboard showing the same load as "pending" leaves the work with the shipping office.

Manufacturing freight starts on the production schedule. A work order closes, finished goods are palletized, and the ERP releases a shipment already promised to a customer. Meanwhile, inbound raw materials have to arrive before the line runs short. Every load passes through the same ten workflows.

Most freight software can display that chain. Fewer products move a load from one link to the next without a coordinator sending the email or keying the BOL, and a status field looks identical either way. The general case for judging tools by finished tasks is in how to judge logistics automation by the work it finishes. The scorecard below applies it to a single plant, row by row.

How to build a workflow scorecard from one plant's week

The scorecard works because it is built from shipments the plant already moved, not from a vendor's sample data.

Pick one plant and one recent week. Include finished goods leaving the dock and materials arriving at receiving.
List every load and the signal that started it: an ERP release or ship-ready flag for outbound; a purchase order, supplier email or collect pickup for inbound.
Write the end state for each workflow. "Booked" means a carrier accepted and a rate confirmation is on file.
Run the same loads through each product under the plant's rules, carriers and approval limits.
Record the person-needed condition, and whether it is a rule the plant chose or a product gap.

An illustrative scoring method: 2 points when the software completes a workflow with evidence, 1 when a person finishes it, 0 when it only displays. The total matters less than where the zeros fall: a zero at pickup confirmation costs a plant more than a zero at a monthly report.

Where manufacturing freight work hides between the ERP and the dock

Most unfinished work in a plant sits at handoffs the production schedule creates.

Production-driven release. When a run finishes late, the ship date moves, and the carrier who agreed to Tuesday must be asked about Wednesday. Software that completes this goes back to the carrier; software that displays it shows a new date and waits.

The pickup window at the shipping dock. The work is getting the carrier to confirm the plant's window, reconfirming before the day and telling the dock when it changes. Assigning the door itself is a facility-side job.

Paperwork that must match the pallets. The BOL, packing slip and pallet labels need the counts and weights actually staged. When the order changes after release, all three change.

Inbound raw materials. Inbound loads often start as a supplier email or a purchase order with collect terms the plant must book. A tool that handles only outbound orders leaves receiving without a confirmed arrival.

How should a buyer tell completed work from a display?

A workflow counts as completed only when the end state exists on the shipment and nobody outside the software produced it.

A status is not evidence. Ask for the carrier's reply, the call transcript, the signed POD or the reconciled invoice on the load.
"Configurable" is not "configured." Score only what runs today on these loads.
Test carriers without APIs. Regional carriers that answer by email or phone are where coordinators spend their day.
Approval steps are not failures. Score how the product presents the decision, with options gathered, not the fact that the plant requires one.

Some decisions stay with people: which customer gets the last truck when production falls short, whether to expedite inbound material, adding a carrier, and claims. Confirm they reach the right person with context. For the steps between an ERP release and a carrier acceptance, see what happens after the order is in the ERP.

The workflow scorecard for manufacturing freight

Workflow	Completes the work	Displays it only	Evidence to ask for	A person is still needed when
Plant order release from the ERP	Creates the shipment from the release and picks up date changes	Lists imported orders	The load from last week's release, with ERP reference	Weight, pallet count or ship-to is missing
Quote requests to approved carriers	Sends requests and follows up on missing replies	Shows rates someone pasted in	Requests and replies on the load	No approved carrier serves the lane
Selection under rules	Applies rules and rate targets, negotiates within limits	Ranks quotes for a coordinator	The rule applied and quote chosen	Cost exceeds the approval limit
Booking	Tenders, follows up to acceptance, files the rate confirmation	Marks booked after a person tenders	Acceptance and rate confirmation	No approved carrier accepts
Pickup appointment confirmation at the dock	Gets the carrier to confirm the window, reconfirms, alerts the dock	Shows a requested date	Confirmation and reconfirmation	Production moves the release
Documents (BOL, packing slip, pallet labels)	Generates and sends them	Stores templates	All three for a real load	Staged pallets differ from the order
Tracking and exceptions	Contacts the carrier on a delay and starts rebooking under rules	Shows a late flag	The delay, contact and update sent	Rebooking exceeds the limit
POD	Requests, follows up, files it	Shows delivered	The filed POD	Still missing after the set window
Invoice audit	Checks the invoice against the booking, flags differences	Holds it for review	A matched and a flagged invoice	An accessorial is outside the rules
Payment	Pays approved invoices under the plant's rules	Exports a list for payables	Payment tied to the load	Amount exceeds the limit or is disputed

How Wilson, by Cartage, performs against the scorecard

Wilson, by Cartage, is an AI logistics agent built to complete the work in each row, using the manufacturer's carriers and rules. It replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica, and other ERP environments, with the exact connection depending on the customer’s data flow and scope. Orders can also arrive by file drop, spreadsheet, email or API.

Wilson requests quotes from approved carriers and tenders them first, negotiates against rate targets within approval limits, books, and produces the rate confirmation, BOL, packing slips and pallet labels. It confirms and reconfirms pickup times with carriers by email, API, EDI where supported, or phone where configured; door assignment stays with the plant. It tracks each load through the best available source (carrier API, GPS/ELD data or the carrier's website by PRO number), with emails or calls as a fallback. On a missed pickup, it contacts the carrier, notifies the team in Slack or Microsoft Teams and initiates rebooking from the approved carrier list, within the rules or with approval. It files PODs, audits and reconciles invoices, and pays carriers from the Wilson Wallet under approval rules. Messages, confirmations and changes are recorded in the shipment history, which answers the evidence column.

Wilson starts with assisted execution, and scope can expand step by step as the plant gains confidence. For the category, see what an AI logistics agent actually does.

Bring one plant's shipments from last week and score them with Wilson in a demo: row by row, see how much of each workflow Wilson completes and where your team still steps in.