How do I keep ShipStation from receiving or picking an order before the customer finishes editing?
Revize lists ShipStation as compatible and offers assisted, stack-specific setup. First establish what imports an order and what starts picking. Then use a Shopify hold that your system respects, a paid-status gate if appropriate, or a release-tag filter. Compatibility alone does not prove that your current connection waits for edits.
ShipStation’s “Minimum order age in minutes before order imports” setting supports up to 120 minutes. Match it to a shorter edit window; a window over two hours needs another verified gate. Removed items can appear as zero-quantity lines on packing slips: enable “Hide 0 quantity items” in printing settings.
Configuration-discovery checklist
- Which connection or middleware imports Shopify orders, and does it copy a snapshot or fetch later updates?
- Does import happen at order creation, payment capture, a release tag or on a schedule? What event actually starts picking?
- Does this connection respect Shopify fulfillment holds? Can it filter on paid status or an exact order tag?
- Who writes the picking stop tag to Shopify, and how soon? Does Revize list that same tag under order restrictions?
- Who owns exceptions, unpaid balances and missed imports? Record the edit deadline, release schedule and warehouse timezone.
Choose and prove the coordination method
| Your verified import behavior | Configuration to agree | Proof before going live |
|---|---|---|
| Respects Shopify holds | Choose Hold orders for a timed editing window. | Order stays unpickable while editable; final data is used after release. |
| Ignores holds but imports only paid orders | Discuss manual capture with Revize: payment stays Authorized during editing, then is captured at close. | Authorized orders do not enter picking; capture admits the final order. Do not assume every connection filters this way. |
| Can filter by order tag | Under Skip hold, enable Add release tag. Make the downstream system process only revize:order_released orders. | An untagged order is excluded; the tagged order carries the final data. Skip hold alone stops nothing. |
Read the documentation · Source
A release tag opens fulfillment; a stop tag closes editing
revize:order_released means editing has finished. A separate tag such as picked or wms:processing means warehouse work has started. Arrange for your WMS or Shopify Flow to write that stop tag and add it to Settings → Order editing → Editing restrictions → Order tags. It closes editing immediately, even when time remains. The timer is not proof that the warehouse is still waiting.
Until fulfillment does not itself hold an order, and its hold and release-tag options are disabled. Scheduled release can delay dispatch after editing closes. If your stack ignores holds and cannot enforce a paid-status or tag gate, resolve that gap before offering the editing window.
Read the documentation · Source
Get the Revize team to configure your stack
Share your connection path, import trigger, desired edit window and warehouse picking signal with Revize. The team supports selecting and configuring the hold, manual-capture or tag method for your stack. Confirm plan and custom setup requirements with the team; custom integrations and dedicated onboarding are Pro capabilities.
Discuss your fulfillment setup · Source
Prove the workflow with a test order
- Place a new test order containing a size variant and another removable item. Record its order ID and initial warehouse state.
- While editing is open, change size, quantity and shipping address; for ShipStation also remove an item. Confirm any payment difference is settled.
- Verify the order cannot enter picking before the agreed hold, payment or tag gate permits it. An early import must not become an early pick.
- Close the window and observe release. Compare final SKU, quantity and full address in Shopify, ShipStation and the packing output. Check that removed items cannot be picked.
- On a separate test order, write the chosen stop tag while time remains. Refresh the portal and verify edits are closed. Record results before enabling the workflow for customers.
Failure symptoms → checks
| Symptom | Check |
|---|---|
| Warehouse sees or picks the original order early | Check import trigger, hold awareness, paid-status mapping and release-tag filter. Stop picking while reconciling the order. |
| Final SKU, quantity or address differs | Compare timestamps and connection update behavior. Confirm the warehouse reads the final Shopify order, not only its creation snapshot. |
| Editing remains open after picking starts | Check that the WMS/Flow writes the stop tag to this order and that its spelling matches the Revize restriction. |
| Order stays held after the deadline | Check outstanding additional payment and the configured release schedule before releasing anything. |
| ShipStation prints removed items | Check “Hide 0 quantity items” and inspect a fresh packing slip. A zero-quantity line must not be picked. |
Picking has already started
Ask the warehouse to pause and confirm whether the pick can still be changed. Reconcile the final SKU, quantity and address before permitting dispatch. A Shopify cancellation of a fulfillment request does not automatically stop a third party already working on it. Fulfilled orders are outside Revize’s editing scope.
Shopify: cancelling fulfillment requests · Read the documentation