Everything you need to correct an order—without guesswork.

Edit quantities and unit prices on real orders

Work from a filterable order list inside the embedded app. When you open an order, adjust line quantities and unit prices with guardrails that match your store’s configuration—and, when Shopify allows in-place edits on that order, shipping fee and cart / order-level discount in the totals band.

• Filter by status, payment, fulfillment, delivery method, tags, and date range.
• Sort presets tuned for common “find my problem order” workflows.

Upward price changes, handled the way your store chooses

When a unit price goes up—or your settings require it—the app follows a configured method (for example void and recreate, or an adjustment line strategy where applicable). You’re not limited to “discounts only” thinking.

• Store‑level policy for how upward changes are applied.
• Explicit confirmations when the path affects how the order is represented in Shopify.

Fix billing and shipping addresses before they hit finance

Edit shipping and billing addresses in the same guided flow as line edits. Billing corrections can trigger the same careful paths as upward repricing—so finance sees a clean story, not a patchwork of notes.

Pull from the customer’s saved addresses

When an order has a linked customer, use their address book to apply the right mailing fields faster—with fewer copy‑paste errors.

Custom surcharge lines when the order needs an extra line

Add structured adjustment lines where your workflow allows—so exceptions are still represented as order lines, not side spreadsheets.

Preview the diff, then commit

Changes are summarized before commit. You decide when the update syncs—after you’ve read line, shipping and order-level discount, totals, and address deltas.

Operational controls merchants expect

• Optional timeline comment for internal context.
• Choose whether to notify the customer when it’s appropriate.
• Restock options where void‑related paths apply—so inventory stays honest.

Activity history you can defend

See runs with status, source and result order references, void/recreate flags, errors, soft‑risk acknowledgements, and trace IDs—so support and finance can answer “what happened to order #…?” with evidence.