Skip to content
All articles

Order management systems: order states, exceptions and fulfilment handoff

Person checking paperwork while preparing a parcel beside a laptop
Photo by Kampus Production on Pexels

Choose an order management system by following one order through acceptance, fulfilment, exceptions and the next person’s handoff. Define what each status means, which record it describes and who may change it. A useful assessment explains the unfinished work behind an order as clearly as the completed work.

Where does the order begin?

WooCommerce usually creates an order when a customer completes checkout. WooCommerce also permits manual order creation in the WordPress administration dashboard. The WooCommerce merchant guide therefore gives two entry routes to consider when designing your order register.

Create an origin field in the assessment worksheet. Ask whether an order came from checkout, a member of staff or an integration, and retain the originating reference. Decide how the team should identify a repeated submission before it creates a second piece of work.

Keep the order identity distinct from the customer identity. One customer may place several orders; a familiar name should not be the only way staff decide which goods to prepare. Ask the evaluator to retrieve a specific order using its reference and then confirm the relevant customer and delivery details.

Use a hypothetical training order containing two different products. Give it a synthetic customer and address, then write down the intended quantities and delivery method. All exercises below refer to that training record. Record observations when the exercise is performed rather than presenting this proposed sequence as a completed software test.

Which status belongs to which record?

Ask the business owner to describe the difference between accepting an order, confirming its payment position, preparing goods and completing delivery. Keep those meanings in a small status dictionary. Identify the evidence needed for each transition and the person who can correct a mistaken transition.

Shopify fulfils each fulfilment within an order separately. The Shopify fulfilment guide makes that distinction particularly useful: an order-level conversation can include several separate packages or fulfilment actions.

For the training order, propose sending one product now while the second remains unresolved. Ask the operator to identify the outstanding quantity and the next action. The customer-facing view should then be inspected against what actually happened in the exercise, including any notification selected by the operator.

Avoid using a single green badge as the acceptance criterion. Instead, require the reviewer to state which part is complete, which part remains open and where the supporting evidence lives. A clear status vocabulary gives staff a way to discuss exceptions without quietly changing the meaning of “done”.

Who can move the work forward?

WooCommerce makes orders visible to Admin and Shop Manager roles. Use that documented starting point to ask which actual users should view, amend and prepare orders. Assess the deployed roles and any extensions rather than assuming that a job title gives the correct access automatically.

Give each handoff a named operational owner. The person who answers a customer’s question may need to see fulfilment progress without being the person authorised to change it. Write down the requested separation and ask the implementer to demonstrate how the chosen configuration supports it.

When an order is assigned to a third-party fulfilment service, Shopify gives that service control of its fulfilment status. If an external service is involved, record the point where responsibility passes to that service and the information expected back. Agree how an unanswered request will be followed up. The worksheet should identify who investigates the exception instead of leaving it between two teams.

Document the correction route as well. If staff select the wrong order, who can stop further work and reconstruct what changed? Use a synthetic mistake in the evaluation, with an agreed observer, before deciding whether the proposed process is understandable.

How should exceptions be assessed?

Shopify requires holds to be released before a held fulfilment can be marked fulfilled or in progress. Include a held fulfilment in the proposed assessment and ask the operator to explain why it is held. Record the authority needed to release it and the next allowed action. A hold should remain a decision with an owner, rather than a label everyone expects someone else to clear.

Shopify permits a tracking number to be added after fulfilment. This supports a separate late-tracking exercise: prepare the training record first, then assess how the later reference is entered and what notification options are presented. Verify the selected order and carrier information before treating the entry as useful evidence.

Shopify’s mobile app cannot split or merge fulfilments. If staff work mainly on phones, include their actual intended interface in the evaluation. Ask them to perform the required handoff using the supported route and record any device change needed. A desktop demonstration alone does not answer whether the proposed daily work is practical.

Ask what should happen when an address is incomplete, a quantity is unavailable or an external service has not accepted the request. For each case, specify the outstanding question, the person responsible and the condition that permits work to continue.

What belongs in an order handoff register?

Use this original transition-and-exception matrix to prepare an assessment. It is a proposed operational worksheet, not a claim that every platform supplies these fields without configuration.

Boundary Record to inspect Question before handoff
Order entry Origin and order reference Is this the intended request or a duplicate?
Preparation Product quantities and assigned owner What is ready and what remains unresolved?
Split work Individual fulfilment references Which package or quantity does this action cover?
Hold Reason and release decision Who can authorise the next step?
External service Request reference and response Has responsibility actually been accepted?
Tracking Carrier reference and selected order Is the reference attached to the correct work?
Customer update Chosen message and recipient Does the update reflect the observed position?

The WooCommerce orders overview supports filtering and finding orders. Ask a second member of staff to find the training order from the register and explain its outstanding work. The observer should keep their actual steps and any ambiguity found. That is a more useful acceptance record than simply recording that the order screen opened.

WooCommerce documents order notes as a way to communicate with customers from the administration dashboard. Before sending a real update, inspect which information the customer will receive and who selected it. Keep operational notes clear enough for the next colleague to understand the decision, while checking the intended audience for each communication action.

At the end of the assessment, retain the status dictionary, exception register and unresolved configuration questions. Use them to decide whether the workflow is ready for a controlled introduction and which owner needs to resolve the remaining gaps.

For the surrounding storefront scope, see online stores. For an integration requirement, see web development or send Spout your order workflow with the handoff that currently needs attention.

By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.

Make your next move.

A website, a store or a clearer digital plan. Let’s start with your business.

Start your brief