Operations

OMS

Order Management System. The system of record for what was ordered, from where, and against which inventory (Manhattan, Fluent, Shopify, NetSuite). An OMS decides which store, warehouse, or node sources an order; orchestration decides how it physically reaches the customer once sourced. The two meet at the promise: the OMS commits a date, dispatch is what keeps it.

Where this fits

The day-to-day vocabulary of running deliveries. Routes, waves, drops, manifests, ETAs, SLAs. These are the units operators reason in, and the inputs every downstream model needs.

Related terms

TMS: Transportation Management System. The system of record for shipments and freight movements. Older TMS platforms model shipments; Nash sits above them and orchestrates the live decisions a TMS records after the fact.
WMS: Warehouse Management System. The system of record inside the four walls: receiving, put-away, inventory locations, picking, packing. A WMS knows a parcel is ready to leave the building. It does not decide who carries it, when it goes, or what happens when that carrier fails. Nash reads the ready signal and takes the order from there.
BOPIS: Buy Online, Pickup In Store. The retail order pattern where a customer buys online and collects in person. On the operations side, it consumes pick-and-pack labor at the store rather than carrier capacity.
ERP: Enterprise Resource Planning. The system of record for finances, inventory, procurement, and HR at a larger business (SAP, Oracle, NetSuite, Microsoft Dynamics). Logistics decisions Nash makes show up in the ERP as completed transactions; the ERP rarely makes them.
Cross-dock: A facility where inbound freight is unloaded and reloaded onto outbound vehicles directly, without sitting in storage. Used to consolidate or reshuffle loads in transit.