Order management systems

An order management system (OMS) keeps the customer order and its outstanding fulfilment obligations coherent as work passes between sales channels, warehouses and partners. To assess one, ask who can release, allocate, change and close each order line, and where staff see an unresolved exception.

Decide what the OMS owns

Keep a stable reference to the original order, its lines, quantities, delivery choices and source channel. Define which system may change each decision.

A storefront may accept payment and display updates; an OMS may hold and allocate lines; a warehouse system may report a short pick. If two systems can independently release or cancel the same work, establish which decision prevails and how the other system is corrected.

For each line, staff should find the quantity assigned to each fulfilment source, the quantity completed, what remains outstanding and who owns the next action. Keep payment and delivery progress distinct from fulfilment state. Shopify documents separate order, payment, fulfilment and return statuses.

OMS Ownership and Control Across Systems

Set acceptance criteria for ownership

Assess whether the proposed setup gives staff one place to view orders and their fulfilment state across the relevant order sources.

For configured orchestration, check that provider communications create events that move an order through its journey, and that the flows reflect the business process rather than an assumed default.

Use a representative order to check that an incoming order and fulfilment information can pass between the platforms involved, and that the resulting order state remains visible. Record which flows and provider connections must be configured for this behaviour; the documented platform capability alone does not confirm that a particular connection is covered.

Configuring OMS for Multi-Channel Fulfilment

Trace the order lifecycle

Preserve the original order quantity when an allocation changes so a revised assignment does not conceal what is still owed.

Order Lifecycle: Key Decisions and Exception Points

Check line-level traceability

For partial fulfilment, verify that staff can follow updates from the original order product through the relevant fulfilment instruction and tracking records. Dynamics 365 models an order as having multiple fulfilment orders, an order product as capable of multiple fulfilment paths, and tracking records with line-level updates.

Use that structure as a test for whether the OMS can show which quantities are complete and which remain owed, without losing the relationship to the original order line. Check that changes and progress can be reconciled back to the order and product lines, rather than relying only on an order-level completion indicator.

Examine relevant starting points

Shopify order routing can be a starting point for a Shopify store assigning orders among fulfilment locations. Shopify documents sequential routing rules, with a default preference for fewer split fulfilments, and requires at least two active locations.

Check the store's configured rules, eligible locations and connected fulfilment services. These routing features alone do not establish a complete workflow across other sales channels or detailed warehouse work.

Microsoft Dynamics 365 Intelligent Order Management documents provider-based exchange of order and fulfilment information, configurable orchestration and fulfilment optimisation. Its data model can relate one customer order to multiple fulfilment orders and line-level tracking records.

That range of functions requires configured source lists and inventory inputs. Microsoft's optimisation documentation says a source with Use real inventory switched off is treated as having unlimited inventory. Ask which setting and stock data the proposed route uses.

Shopify's default routing rules also try to stay within the destination market where possible and choose the closest location to reduce delivery times. Custom rules can use location metafields such as capacity or fulfilment speed, or prioritise warehouses, balance inventory or optimise fulfilment costs. Check which of these objectives the proposed configuration actually applies.

Top OMS Considerations for Australian E-commerce

Check the optimisation inputs

For an optimisation-based setup, inspect the business constraints and strategies that influence source selection, not just the resulting allocation. Dynamics 365 Intelligent Fulfillment Optimization reads configuration including fulfilment sources, source lists, constraints and strategies; it can also use Azure Maps to geocode addresses and calculate distances between orders and sources.

Confirm that each configured source represents a real place or provider that can supply products, and that its address and location details are maintained. The source configuration can determine whether inventory is checked through Inventory Visibility or assumed unlimited, so the setting should match the stock data the operation intends to use.

Key OMS Performance Indicators (Australia Context)

Assess changes and exceptions

Agree what happens when a line is unavailable: wait for stock, use another eligible source, split the order or seek a customer decision. Keep the affected quantity and next action visible. Once warehouse work has been released, an address change or cancellation needs an acknowledged hand-off; a channel's cancellation label does not prove picking stopped.

Give each candidate setup the same ordinary order, mixed basket, shortage, split fulfilment and post-release change. Add marketplace or collection cases if they occur in the operation.

Inspect the allocation, warehouse instruction, exception record, line-level completion and update returned to the originating channel. Record required configuration and manual work as well as what cannot be shown.

Treat payment and cancellation states as work signals, not proof that every obligation is settled. Shopify describes a pending payment order as having reserved inventory even though payment is not guaranteed; a cancelled order that has not been fully refunded can still have work remaining. Check that the OMS keeps such outstanding actions visible.

Shopify also distinguishes an authorised payment from a captured payment: authorisation is a cue to capture before it expires, and an Expiring badge appears two days before the capture deadline. Test whether payment holds and remaining work are visible to the staff member deciding whether to release or close an order.