Manhattan Active Omni integration for ecommerce order management

The OMS applies routing rules that you define in advance. These rules can prioritize by warehouse cost, distance to customer, current inventory, delivery SLA, and customer segment. iWeb works with you to document the rules and test them against real order patterns before go-live.

The OMS can allocate available stock and create a backorder for the rest, hold the entire order pending replenishment, or reject the order and prompt the storefront to show the item as out of stock. Which behaviour applies depends on the routing rule and your business policy. iWeb defines these policies upfront so the OMS acts predictably.

The ERP feeds current stock levels to the OMS on a schedule you define—typically every 15 minutes to an hour during normal trading. The OMS reads the ERP count, subtracts reservations from other orders, and calculates available-to-promise. iWeb sets the sync frequency and handles reconciliation if counts drift.

Yes. If an order is split across warehouses, the OMS sends pick lists to each location, tracks each shipment separately, and waits for all legs to dispatch before it publishes full tracking to the customer. iWeb tests split-order scenarios so the OMS and storefronts stay synchronized.

The OMS flags the order as held and places it in an exception queue. A member of your credit or operations team reviews the hold, decides to release or cancel it, and the OMS resumes processing. iWeb configures the exception queue and defines who owns each type of hold.

When a customer returns goods to a warehouse or branch, the WMS receives them and updates stock. The OMS is notified of the return, applies your refund rules—which locations can accept returns, when the refund is authorized—and the ERP records the credit note and inventory receipt.

The OMS sees orders from your storefronts, marketplaces, call centre and branches at the same time. It applies allocation rules that you define—for example, holding stock for marketplace orders first, or rotating which channel gets priority each day. iWeb documents the allocation policy and tests it during peak demand scenarios.

Orders queue in the OMS while the WMS is unavailable. When the WMS comes back online, the OMS can send queued orders or the fulfilment team can manually trigger pick lists. iWeb configures fallback behaviour and ensures you have visibility into the queue so you can decide whether to hold orders or offer extended delivery times.

Yes. The OMS can route orders to a supplier, send them a purchase order or EDI message, and track when they ship. iWeb configures dropship routing and handles the communication with your suppliers so dropship orders are visible in the same order-management dashboard as warehouse orders.

The OMS publishes order status back to the storefront—allocated, ready to pick, dispatched, in transit, delivered. The storefront displays this status to the customer and triggers confirmation emails. iWeb defines the status-update schedule and ensures the storefront receives updates reliably.

The OMS can hold the order, flag it as an exception and notify the customer service team. Service staff can correct the address in the storefront or call the customer, the OMS resumes processing once the address is valid. iWeb sets up these data-quality checks and routes exceptions to the right team.

iWeb sets up dashboards and alerts that track order throughput, allocation success rate, exception volume, and sync delays between the OMS and ERP or WMS. If allocation fails, holds spike or sync lags, the right team is alerted so issues are caught within minutes, not hours.

Yes. Routing rules are configured in the OMS, not hard-coded. You can adjust thresholds, add new rules or disable old ones without an integration rebuild. iWeb trains your operations team to make these changes safely and provides a testing environment so you can validate new rules before they hit live traffic.

The OMS reserves stock for specific orders—this order gets units A through C from warehouse 1. The ERP tracks inventory balance across the whole business and records stock movements for accounting. iWeb ensures both systems see the same physical count but own different aspects of the record.