Supplier routing

Supplier Coordinator prepares a routing record for a customer order and organization. The route has its own status and revision. It can retain a supplier reference, routed units, routing date and acknowledgement ID. These details identify the supplier side of the handoff without turning an acknowledgement into proof of shipment.

• Prepare. Keep a draft route linked to the order it serves.
• Decide. Submit the route for an Order Reviewer to approve or reject against the current order revision.
• Follow through. Record the supplier response and completion state after the decision.

The review record carries the source revision, reviewer, decision, reason and operation key. A returned decision can ask the coordinator to revise the route; an approved decision is the basis for the next routing action. When the order changes, the earlier decision remains in history rather than silently applying to a new version.

Keep the route organization aligned with its customer order. Before recording an acknowledgement, check the supplier reference and the routed quantity against the approved route. A response belongs to that route even when shipment arrives later through a separate source.

Choose the staff allowed to prepare routes and the independent staff allowed to decide them. Agree when a supplier reference is assigned and how routed units are checked against order lines. Decide what the acknowledgement ID identifies in the supplier system. It should be possible to trace a customer order to the exact route and reviewer reason used for the decision.

Use a confirmed customer order with two order lines. The Supplier Coordinator prepares one route and sends it for review. The Order Reviewer checks the order revision, line quantities and customer context, then approves it with a reason. The coordinator records the supplier reference and acknowledgement. Fulfillment Coordinator later records a Shipped event if shipment evidence arrives. The routing acknowledgement alone does not change a fulfillment event.

Repeat with a rejected route. The rejected status and review reason remain visible. A corrected route should receive a fresh review rather than inheriting an old approval. Check an operation receipt whose expected revision is stale and make sure the team investigates it before repeating the action.

• Routing review inbox — Submitted routes waiting for a reviewer decision.
• Approved routes — Routes that can move to supplier follow-through.
• Routing progress — Draft through completed routing work by status.

Follow order to routing and review supplier response.