Order Management System

Definition

An Order Management System (OMS) is the software layer that decides where an order will be fulfilled — before the warehouse receives it. The OMS captures orders from all channels, determines the optimal fulfillment node based on inventory availability, cost, and SLA, and releases the work order to the appropriate execution system (WMS, store, drop-shipper).

OMS vs WMS distinction (critical):

• OMS asks: Which node should fulfill this order?
• WMS asks: How do we pick, pack, and ship from within this node?
• OMS operates in the pre-fulfillment planning space; WMS operates in the execution space.

---

Core Functions

Order capture: Receives orders via EDI, web API, POS, call center, and marketplace integrations. Normalizes order format across channels.

Available-to-Promise (ATP): Queries real-time inventory across all nodes to confirm that the item is actually available before committing to the customer. Poor ATP accuracy → oversells → customer service failures.

Capable-to-Promise (CTP): Extends ATP by considering lead times, production schedules, and in-transit inventory — used in B2B environments.

Order routing: Determines optimal fulfillment node based on:

• Inventory availability at each node
• Shipping cost from each node to customer
• SLA (can this node deliver within the promised window?)
• Node capacity (is the DC over-capacity today?)

Order splitting: When no single node has full inventory, OMS splits the order across nodes. Must weigh split-ship cost against customer experience of receiving multiple packages.

Returns processing: Issues return authorizations; routes returns to optimal node (local store, regional returns center, or DC); assigns disposition logic.

Customer communication: Order confirmation, shipping notifications, tracking, exception alerts.

---

Omnichannel Complexity

Modern OMS platforms must handle fundamentally different fulfillment scenarios simultaneously:

Channel	OMS Challenge
BOPIS (Buy Online, Pick In Store)	Store inventory must be model-able as fulfillment capacity; store inventory accuracy is typically lower than DC
Ship-From-Store (SFS)	Store becomes a mini-DC; OMS must route orders to the store with lowest pick cost and highest stock accuracy
Drop-Ship	OMS sends PO to vendor; tracks vendor confirmation and shipment — no DC involvement
Standard DC fulfillment	Straightforward; OMS routes to regional DC with available inventory
Marketplace orders	Amazon, Walmart marketplace — OMS must normalize and route; often have strict SLA penalties

---

Vendor Landscape

Vendor	Strengths	Best For
Manhattan Active Omni	Unified OMS+WMS; omnichannel-first architecture; real-time ATP	Large omnichannel retailers
IBM Sterling OMS	Complex B2B order management; deep EDI; global	Enterprise B2B/wholesale
Kibo Commerce	Mid-market omnichannel; headless architecture; modern API	Mid-market retailers
Fluent Commerce	Cloud-native; distributed inventory; strong SFS	Omnichannel brands and retailers
Salesforce Order Management	Native Salesforce ecosystem; strong for Salesforce Commerce customers	Salesforce shops
SAP / Oracle embedded	Basic OMS functionality within ERP; limited routing logic	Simple fulfillment from single DC

---

Integration Risk Points

ATP latency: OMS must have near-real-time inventory from all nodes. Batch inventory feeds (hourly or daily) cause ATP errors. Real-time integration is required for high-volume channels.

Split-ship economics: An order split across two nodes may cost more to ship than it saves in handling. OMS routing logic must model total landed cost including carrier rates, not just inventory proximity.

Carrier rate shopping: OMS should integrate with carrier rate engines to ensure the lowest-cost service level that meets SLA is selected at order routing time.

Node capacity: OMS routing without real-time DC capacity data can flood one DC while another sits underutilized. Throughput capacity must be a routing constraint.