Dynamics 365 freight automation: test the handoff from order to tender

Key Takeaways

A Dynamics 365 order-to-tender handoff has six points to test: trigger, order package, field translation, approval gate, first tender and record.
Test on the intake path the environment supports (ERP feed, scheduled file, spreadsheet, email or API), not an assumed native connector.
Most failures happen in field translation: a sales order holds items and quantities, while a tender needs pallets, weight, pickup hours and accessorials.
Wilson, by Cartage, takes the order from the company's existing data flow, checks it, applies the approval rules and tenders first to approved carriers.
Run the script with four real orders: one complete, one missing weight, one above the approval limit and one sent twice.
Write-back to Dynamics 365 is a separate, scoped decision.

What does a Dynamics 365 order-to-tender handoff test need to prove?

It needs to prove that a ship-ready Dynamics 365 order reaches the freight workflow once, carries the fields a carrier needs, passes any required approval and becomes a first tender to an approved carrier, with a record that ties the tender back to the order number. If any of those breaks, a coordinator ends up retyping the order into an email.

Dynamics 365 environments differ in how an order becomes freight work. Some teams treat order confirmation as the signal, others wait for a warehouse release or a coordinator's manual flag. Some export orders on a schedule, others email a report, and some have an API connection available. Build the test around the environment the team runs today.

The scope is deliberately narrow. The full sequence through documents and pickup confirmation is covered in the steps from ERP order to booked load. This test stops at the first tender, where the ERP's job ends and freight execution starts.

The six handoff points between the order and the first tender

Test each handoff point on its own, so a failure traces to one place instead of being reported as the integration not working.

Trigger. The event that says the order is ready: a status, a release, a scheduled export or a manual flag. It should fire once per ready order, never for orders still being edited or on credit hold.
Order package. Sales order number, customer, ship-to, requested date, lines and notes. Free-text delivery instructions are the first thing to go missing.
Field translation. Items and quantities become pallets, weight, dimensions and, for LTL, the freight class the company supplies. Check where each tender field comes from and what happens when one is blank.
Approval gate. Rules decide whether the shipment can be tendered directly or needs a person: a rate above the limit, a lane with no routing rule, a customer that requires sign-off.
First tender. The approved carrier named first for the lane receives the load on its own channel. Check the carrier, content and send time.
Record. The shipment links the sales order number to the tender, rate, approval and carrier response.

What the carrier needs that the sales order often doesn't carry

The gap between a Dynamics 365 sales order and a usable tender is mostly a gap in freight fields, not a connection problem. A sales order is built to bill a customer and pick inventory. A tender is built to put a truck at a dock.

An order line says what was sold. Item weights may sit in the product master, useful only if maintained. Pallet count often isn't decided until the warehouse builds the shipment, and dimensions may not exist in the ERP at all. For LTL, freight class is an input the company provides, so confirm the class on the tender matches what shipping expects.

Other tender fields rarely live on the order: pickup hours and dock contact, a ready date that differs from the requested date, delivery appointment requirements, accessorials such as liftgate, and the reference numbers the consignee will ask for.

For each field, record whether it came from the order, a standing rule (every shipment from one plant uses the same pickup hours) or a person. A field a person fills in every time is a manual step that will survive go-live.

The intake path matters too. Wilson can take orders from an ERP feed, a scheduled file drop, a spreadsheet, email or an API, depending on what the environment supports; which connection moves the freight compares the options. Test on the path the company will actually use, because a file export and an API call fail differently.

When should the handoff stop for a person, and when should it keep going?

The handoff should keep going when the order is complete and inside the rules, and stop with a specific question when it isn't.

Agree on these rules before the test:

Missing weight or pallet count: stop before any tender and ask the named owner, usually the shipping lead.
Order edited after handover: hold the tender and use the latest version. After the tender goes out, it is a different workflow.
Same order received twice: recognize the sales order number and don't create a second shipment; re-exported files make this common.
Rate above the approval limit: send the approver the order number, lane, rate and target, then wait.
Lane with no routing rule: don't default to a carrier; ask who gets the first tender.
Decline or no response: move to the next approved carrier the rules allow, and escalate when none accepts.

A good stop names what is missing, who was asked and what happens once it is answered.

Write-back is separate. Whether carrier, rate and tender status return to Dynamics 365, and how (an updated file, a shared table, or an API connection where available), depends on the company's data flow and scope.

A handoff test script for four Dynamics 365 orders

Run the script with four real orders from recent weeks, sent through the intake path the company will use in production. The order types are illustrative.

Step	Order	Action	Pass if
1	A: complete, regular lane	Release it as usual	One shipment is created with order number, ship-to and requested date intact
2	A	Compare shipment and order	Pallets, weight, pickup hours and accessorials are filled, each with a clear source
3	A	Let it reach tender	The approved carrier named first for the lane receives the tender on its channel
4	B: weight missing	Release it unchanged	No tender goes out; the named owner is asked for the weight
5	B	Supply the weight	The workflow resumes without re-entering the order
6	C: rate likely above the limit	Release it	The approver sees order, lane, rate and target before any tender
7	D: already handed over	Send it again	No second shipment or tender appears
8	All four	Open each record	Order number, fields, approval, tender and carrier reply sit in one place

Score each step pass or fail. A failure at step 2 or 4 points to item data or field mapping, step 7 to order identification, and step 3 to routing rules, each with a different owner.

How Wilson, by Cartage, runs the Dynamics 365 handoff

Wilson, by Cartage, is an AI logistics agent that replaces the TMS for freight execution and connects to the company's ERP, so the order-to-tender handoff runs in the same workflow that later tracks, audits and pays the load. 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. No native connector is assumed: orders arrive through the feed, file, spreadsheet, email or API the company already has.

Wilson creates the shipment from the order data. How an order with a missing field is handled depends on the rules the company sets, so include one in the test. It tenders first to the company's approved carriers by email, API, EDI where supported or phone where configured, and negotiates against rate targets under configured rules and approval limits. On a decline, it moves to the next approved carrier and escalates if none accepts.

Wilson starts with assisted execution, and the scope expands step by step as the team gains confidence; see how configurable approvals work. Messages, confirmations and changes are recorded in shipment history. The Cartage team helps map the first workflow during discovery.

Bring four Dynamics 365 orders from last week, including the one your team had to fix before it could go to a carrier, and watch Wilson take each one from the order to the first tender.