Workflows, Use Cases & Edge Cases

How an edit actually affects the order

Both the admin Order Editor and customer self-service editing apply changes through Shopify’s own order-editing system — the app never maintains its own separate copy of order totals. This means:

• Price & tax: adding or swapping a line item is priced at that variant’s current live price, and Shopify recalculates tax for the change automatically, using the order’s existing tax settings (region, tax-exempt status, and so on).
• Inventory: increasing a line’s quantity, or adding a new item, decrements available inventory for that variant the same way a normal sale does. Reducing a quantity restocks it — for admin edits and the cancel-and-recreate flow this is a checkbox you control per action; for customer self-service quantity reductions, restocking always happens (this isn’t a separate toggle on the storefront side).
• Payment — the app never charges a card: applying an edit that increases the order’s total does not charge the customer automatically. It creates or increases an outstanding balance on the order, and — if you leave notifications on for that action — Shopify emails the customer an invoice they can pay from their order status page. The app has no ability to charge a saved card without the customer’s action.
• Refunds on a value-reducing edit: covered in full in Refund settings — automatic on the customer self-service side (Growth+) when enabled; on the admin side, refunding is one of the explicit checkboxes in the cancel-and-recreate flow when that path is used, and something you’d handle from Shopify’s own order page for a direct in-place edit that reduces the total.
• Existing order-level discounts: a discount already applied to the order stays as it was — editing an existing line or adding a new one doesn’t automatically extend an existing percentage-off discount to the new/changed line. If you need a discount reflected on a newly added item, apply it directly on that line where the tool you’re using supports it, or adjust manually afterward.
• Shipping: shipping lines aren’t touched by an item edit — a shipping charge already on the order stays as it was unless you specifically change it (something the admin Order Creator/Editor screen lets you do directly; customer self-service editing doesn’t expose shipping-cost changes at all, only the shipping address).

Order editing workflows

Workflow: Direct admin edit (quantity, shipping, tags, notes)

1. Merchant opens the order from the Orders list or Shopify’s own order page.
2. Changes a supported field (quantity, shipping method, tags, note, PO number, metafields).
3. Clicks Save.
4. The app applies the change through Shopify’s order-editing API directly to the existing order — no new order number, no cancellation.
5. The order’s totals, tax, and inventory update immediately; the change is visible on Shopify’s own order page right away.

Workflow: Admin edit requiring cancel-and-recreate

1. Merchant makes a change Shopify’s API can’t apply in place (e.g. changing the customer).
2. On Save, the app shows exactly which change(s) triggered this and what will happen.
3. Merchant reviews any already-fulfilled-item warning, chooses restock/refund/notify options, and confirms.
4. The original order is cancelled with an explanatory timeline note; a new order is created with every change applied, referencing the original.
5. Both orders now exist in your order history, cross-referenced — the original as cancelled, the new one active.

Full detail: Admin Guide → When an edit needs a cancel-and-recreate.

Workflow: Customer self-service item edit

1. Customer opens their order status page within the editing window.
2. Clicks Edit, makes a change (quantity, variant swap, add a product, or a mix), clicks Save changes.
3. The app validates the request against every setting on the Storefront Settings Reference (eligibility, locked items, variant scope, quantity caps, stock).
4. If valid, the change is applied through Shopify’s order-editing API — same mechanism as an admin edit.
5. If the change reduced the order’s value and automatic refunds are on, a refund is issued in the same request.
6. The merchant sees the updated order immediately, tagged (if configured) and logged in Recent activity.

Workflow: Customer self-service cancellation

1. Customer opens Cancel order, picks a reason, confirms.
2. The app cancels the real order through Shopify, restocking items and refunding any captured payment per your cancellation settings.
3. The order shows as cancelled in your admin immediately.

Real-world use cases

Use case — Customer wants to change a product’s size or colour

Turn on Item/product editing with a variant scope that fits your policy (e.g. “Same and higher value variants” to avoid unapproved downgrades). The customer uses Change option on the line in question — no support ticket needed.

Use case — Customer wants to change a quantity

Turn on Item/product editing and, if you want them able to go all the way to zero, Remove items. Otherwise they can still increase quantity or reduce down to 1.

Use case — Customer wants to cancel a single item, not the whole order

This is exactly the reduce-a-quantity-to-zero flow above, not the order-level Cancel order feature — cancellation is always whole-order. Reducing one line to zero (with Remove items on) leaves the rest of the order intact.

Use case — Merchant wants to restrict editing on certain products

Use Product tags with either mode depending on whether one restricted item should block the whole order or just itself — see that section for the tradeoff.

Use case — Merchant wants a short window for fast-moving fulfillment

Set a short editing window (15–30 minutes) and turn on fulfillment hold so nothing can ship inside that window even if your fulfillment process doesn’t check tags.

Use case — Merchant wants a single daily cutoff instead of a rolling window

Use Use daily time limit instead — every order placed before your cutoff closes at that same time; orders placed after it get the next day’s cutoff.

Use case — B2B/wholesale order needs a specific field filled in before it can be created

Use Mandatory metafield rules with a condition matching your wholesale customer tag or segment.

Use case — Repeat or recurring customer

Use Duplicate order from the Orders list rather than rebuilding the order from scratch — see Admin Guide → Orders.

Use case — Seasonal campaign needs a tag added to many orders at once

Use Bulk tag operations (Pro plan) from the Orders list.

Edge cases