Without leaving the refund screen, you can add, update, or remove discounts on eligible items. The balance recalculates on the spot, so you can refund the discounted amount. No more bouncing back and forth to the order editing page.
Want to discount before refunding → go to the order editing page and apply the discount → return to the refund page and issue the refund. Extra steps get in the way.
Add, update, or remove discounts on eligible items without leaving the refund page. The balance recalculates instantly, so you can refund the discounted amount right away.
| Item | Before | Now (discounts applied on the refund page) |
|---|---|---|
| Where to apply the discount | Order editing page navigate there to apply | Within the refund page apply directly |
| Screen transitions | Round trips required Editing page ↔ refund page | No round trips Completed on a single screen |
| Discount actions | Done on the editing page | Add, update, and delete available on the refund page |
| Reflecting the balance (outstanding amount) | Check after navigating back | Instant The page updates in place |
| Sales and tax reports | Can be inaccurate if the discount isn't reflected | Accurate You can issue refunds with the discount reflected |
| Scope | — | eligible items. The definition of the conditions isnot specified |
From the article's "Why it matters": Previously, applying a discount before a refund required navigating to the order editing page, adding unnecessary steps. Now you can apply it directly from the refund page.
As stated in the article: by applying the discount in advance, when the refund is issued the Sales and tax reports become accurate.
To avoid speculation, we separate the facts explicitly stated in the original article from the points it doesn't address.
Rather than a new feature, this is a UI improvement that "brings discount controls into the refund page." There's no mention of a new backend API.
As discounts are added, updated, or removed, the outstanding balance is recalculated within the page, and the refund is issued against that amount.
Refunds are recorded with discounts applied → sales and tax reports stay accurate. This is the benefit the article explicitly states.
It's described only as eligible items, with no criteria specified. Design your operations on the assumption that some products may not be eligible.
There's no mention of how this action is represented around refund / discount in the Admin GraphQL, or how it affects existing refund automation or reporting integrations.Stores with automation flows should verify the behavior in a sandboxbefore rolling it out to production.