Connection did not equal readiness
A fast-growth launch had a fixed traffic date while its order workflow was still being connected. The critical work became a full test order, stock confirmation and an overflow plan before the promotion.
Platform integrations and order workflows
A connected screen is not the same as a proven fulfilment flow. Before live volume, we verify how the exact store sends orders, how changes and cancellations are controlled, when tracking returns and which event notifies the customer.
Current workflow by platform
| Platform | Normal starting workflow | What must be tested |
|---|---|---|
| Shopify | Permissioned collaborator access and automatic order/tracking flow | SKU mapping, address visibility, hold/cancel cut-off, fulfilment event and customer notification |
| WooCommerce | Direct authorisation and automatic two-way order/tracking flow | Product mapping, statuses, tracking return and the store's email behaviour |
| TikTok Shop, Etsy, eBay and other marketplaces | Controlled CSV or Excel workflow unless a supported direct setup is confirmed for that account | Required fields, carrier recognition, dispatch deadlines, marketplace policy and who uploads tracking |
| Manual or custom workflow | Agreed file format or another documented handoff | Owner, schedule, duplicate prevention, correction path and proof of completion |
Dianxiaomi in the workflow: RyanFulfil uses Dianxiaomi as one of its internal order-management tools. It helps the team operate the order and tracking handoff, but it does not replace human ownership of product mapping, route checks, exceptions or customer communication.
What we prove before the first live order
- Receive: the correct order, SKU, variant, quantity and complete delivery data appear.
- Control: the team knows when an order can be held, edited or cancelled and who approves release.
- Fulfil: the same workflow used in the test will be used for real orders.
- Track: the carrier and number return in a format the platform recognises.
- Notify: the customer-facing shipped event occurs at the agreed physical milestone, not merely when a label exists.
- Recover: address errors, stockouts, route rejection, duplicate orders and failed tracking upload have named fallbacks.
Use the complete platform preflight checklist →
Security and access
Use each platform's supported collaborator, staff-role or authorisation flow where available. Grant only the access needed for the work and keep ownership with the seller. For platforms using a controlled file workflow, record who exports orders, who imports them, when the transfer happens and how tracking returns. Shared store passwords are not the default integration method.
Operational examples from the reviewed chats
Tracking semantics mattered
Some workflows created tracking before physical carrier handoff. The control was to agree which real event justifies marking the order fulfilled and sending a customer email.
Ownership changes needed re-authorisation
A store transfer changed who controlled the connection. Re-authorising the intended owner and testing the flow prevented an old setup from becoming a hidden dependency.
Manual steps needed an owner
Marketplace and file-based orders worked when the export, import, carrier field and tracking upload were documented. Unrecorded manual handling was the risk, not manual handling itself.