Trigger an outbound shipment confirmation from a WMS via API after pack completion and sync the tracking number back to the OMS
domain: manh.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
After pack completion in the WMS, query the outbound shipment endpoint for the completed carton or pallet; retrieve the generated carrier tracking number, carrier SCAC, service level, label ZPL or PDF, and actual shipment weight and dimensions.
POST an order shipment confirmation to the Order Management System (OMS) or marketplace API: include the order ID, line-item quantities shipped, carrier SCAC, service level, tracking number, and estimated delivery date.
Publish a shipment notification event to downstream consumers (customer notification service, analytics, ERP inventory deduction) via an event bus or message queue, including the full shipment payload.
Update the WMS outbound shipment record to 'shipped' status to close the wave task and release the allocated inventory from the outbound hold zone.
Handle partial shipments (not all ordered lines shipped in one carton) by sending a partial shipment confirmation for shipped lines and leaving unshipped lines in a back-order or hold status in both WMS and OMS.
Known gotchas
Tracking numbers are assigned by the carrier at label generation time; if the WMS generates labels in advance (pre-manifesting), the tracking number may exist before the physical shipment — downstream systems that trigger customer notifications on tracking number receipt must wait for actual ship confirmation, not label generation.
WMS and OMS can disagree on shipment quantity due to pick shorts resolved after the wave was cut; always use the WMS-confirmed shipped quantity as the authoritative quantity for the shipment confirmation, not the originally ordered quantity.
Carrier manifest cutoffs mean that cartons labeled after a certain time may not be inducted until the next business day; the estimated delivery date in the shipment confirmation should account for the manifest cutoff to avoid promising delivery dates the carrier cannot meet.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?