Check Shopify fulfilment by following the items, assigned location and delivery method through the actual dispatch record and customer update. Review split orders as separate fulfilments where applicable. Use the worksheet below to connect routing decisions with the quantities shipped and the tracking information the support team will need when a customer asks what has happened.
Which location is expected to fulfil the order?
Start with a representative order and identify the items, quantities and intended delivery method. Ask which location should prepare each part and why. Keep a reference to the selected order and the configuration used so the explanation can be checked against the actual arrangement.
Shopify order routing assigns orders to fulfilment locations using configured rules. Documentation. Shopify order routing applies its rules in sequence. Documentation. Shopify order routing requires at least two active locations. Documentation. Review the configured rule order with the operational owner. A sensible rule in isolation can still produce a different outcome when another rule takes priority. Give the evaluator examples that expose the intended preference rather than only an order every location could handle.
The default routing strategy seeks to minimise split fulfilments. Documentation. Shopify supports advanced routing rules based on location metafields. Documentation. Record which criteria the business actually wants to use and which data supplies them. If a custom field influences routing, assign an owner to keep it meaningful. Keep proposed location priorities distinct from a claim that a particular carrier or local service is available.
How should a split order be interpreted?
Shopify permits individual order fulfilment through the admin. Documentation. Each fulfilment within a split order is handled separately. Documentation. Shopify groups fulfilment items by location and delivery method. Documentation. Ask the reviewer to identify the items belonging to each fulfilment and the delivery method applying to them. Keep the customer order reference connected to the separate operational records so support can explain progress without assuming that one action covers everything.
Compare the intended item quantities with the proposed dispatch quantities. Include a partial-quantity example and a case with different delivery methods where relevant to the actual store. Record what remains outstanding and who is responsible for the next action.
Decide how an unavailable item or a changed source location should be handled. The operator needs a clear business decision and an approved route through the actual configuration. Keep the exception visible instead of changing an order solely to make the displayed status appear complete.
An original location-to-dispatch worksheet
Use this practical checklist for a representative order, including a split case. Fill it with actual references when evaluating the workflow. It connects the routing decision with the evidence needed by the packing and customer-support teams.
| Handover point | Information to record | Question before closing |
|---|---|---|
| Order scope | Order reference, items and quantities | What must the customer receive? |
| Routing decision | Assigned location and relevant rule | Why is this location responsible? |
| Fulfilment split | Items and method for each separate fulfilment | Which part is being processed now? |
| Preparation | Picked quantity and intended package | Does it match the current instruction? |
| Dispatch record | Relevant fulfilment and carrier reference | Which items does this record cover? |
| Customer update | Contact route and stated progress | Is the message supported by the operational record? |
| Outstanding work | Remaining quantity or exception | Who owns the next action? |
Add the configuration version or change reference to the working copy. If routing priorities are changed during evaluation, retain the earlier result and identify which later observations used the new arrangement. This avoids explaining an old dispatch with a rule that was introduced afterwards.
Keep the physical handover evidence appropriate to the business’s actual process. Ask the team what establishes that a package was prepared, handed over and subsequently tracked. The worksheet should make each stage’s evidence identifiable instead of treating a software label as the answer to every operational question.
What should be checked in a tracking update?
Shopify allows tracking numbers during fulfilment or afterwards. Documentation. Match the tracking reference to the intended fulfilment and package. Ask the operator to identify which items it covers before sending an update. A correct-looking reference attached to the wrong part of a split order can still leave the customer confused.
Shopify requires an available customer email address for the described shipping notification. Documentation. Review the contact details and proposed notification route in the controlled acceptance exercise. Keep the message aligned with the dispatch record and the remaining items. If the customer cannot receive the selected notification, define the appropriate support process rather than assuming the update has reached them.
Include a correction case in the evaluation. Ask what the actual configuration permits when a tracking reference is entered incorrectly and which evidence support should retain. Document the supported route and its observed result so the next operator does not have to improvise a customer-facing explanation.
Hypothetical example: one order leaves two locations
Imagine an order contains items assigned to separate fulfilment locations. One part is dispatched while the other is still awaiting preparation. This hypothetical example tests whether the team can explain the order’s progress accurately.
Put both fulfilment references on the worksheet and associate their items, quantities and delivery methods. Record the dispatch and tracking information for the part that has moved, then identify the remaining work. Ask a support colleague to explain the current state using those records alone.
Next, introduce a proposed location change for the outstanding part. Review the business decision, the actual supported change route and the resulting item assignment. Keep the already-dispatched part separate so a correction to the remaining work does not rewrite the interpretation of the earlier handover.
When the controlled exercise is performed, retain observations from both the operator and support view. A useful acceptance record should make it clear which items have evidence of dispatch, which tracking reference applies and what remains to be done.
What should the implementation handover contain?
Retain the routing rules, location responsibilities, split-order examples and tracking-correction instructions together. Assign an owner to relevant location data and a support route for unresolved dispatch questions. Include the next review trigger when the business adds a location, delivery method or integration.
Keep wider stock movements with inventory control. Use Shopify in Zambia for broader platform constraints. Discuss the store brief through online stores and get started with a representative split order and the handover questions you need to resolve.
Ask a colleague from the dispatch location to review the instruction using only the retained records. Record any clarification they need before preparing the intended package. Use that feedback to improve the handover fields rather than relying on informal knowledge held by one operator.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.