Order Editing and Fulfilment & Shipping Platforms

How fulfilment integrations work

Order Editing keeps an order editable for a controlled period, then releases the final order to the warehouse or shipping platform. The correct setup depends on how that platform imports orders from Shopify.

Common patterns are:

• Delayed payment capture: the platform imports only after payment is captured.
• Order hold: Shopify fulfillment orders remain on hold until editing closes.
• Order tag: the platform or automation skips orders carrying the editing tag.
• Fulfillment request: after editing ends, Order Editing asks Shopify to send a request to the assigned fulfillment service.

The goal is the same in every pattern: the downstream platform should act on the final edited order, not a copy imported before the customer finished.

Platforms with documented setups

Start with the dedicated guide for the platform. A platform name in this list does not mean every account uses the same settings; warehouse locations, payment capture, subscriptions, bundles, split fulfillment, and other apps can change the correct design.

Pipe17's request model

Pipe17 uses a different pattern from systems that poll for newly paid orders. When enabled, Order Editing requests fulfilment through Shopify after:

• editing time has expired;
• Order Editing holds are released;
• the order is fully paid;
• an open fulfillment order is assigned to a service that supports fulfillment requests.

See Getting Started with Pipe17 before enabling the integration.

Work with a 3PL, WMS, OMS, ERP, or iPaaS

A 3PL can use its own Shopify app or an underlying warehouse management system, order management system, ERP, or integration platform. Compatibility depends on that actual connection and its import trigger.

Ask the provider:

• what event makes it import an order;
• whether it respects Shopify fulfillment holds;
• whether it can ignore an order tag;
• whether it supports Shopify fulfillment requests;
• when it locks products, shipping, addresses, and payment data;
• how it handles later Shopify order updates.

Plan the setup

Before launch, document:

1. the customer's editing-window length;
2. how the order is held or excluded downstream;
3. when payment is authorised and captured;
4. the event that releases the order;
5. which locations and fulfillment orders are included;
6. how the platform receives updated products, quantities, addresses, shipping, and totals;
7. the fallback when the release or request fails.

Contact Order Editing support before launch when the workflow uses multiple warehouses, split fulfilment, subscriptions, custom Shopify Flow automations, or more than one system that can release an order.

Test before launch

Use an existing controlled order when possible. Create a new test order only when the integration trigger or payment path cannot be verified otherwise.

Confirm:

• the order is withheld while editing is open;
• a supported customer edit reaches Shopify;
• the downstream platform does not begin fulfilment early;
• the hold, tag, payment, or request transition happens once;
• the platform receives the final products, shipping address, shipping method, and quantities;
• a failed release is visible to the operations team.

If the platform is not listed

An unlisted platform can still be compatible. Contact support with the provider name, Shopify connection method, import trigger, fulfillment locations, payment-capture setup, and whether it supports holds, tags, or fulfillment requests.

Do not copy another platform's delayed-capture or hold configuration without confirming that the new provider uses the same trigger.