Admin / New feature

Waive outstanding order balances
Formally handle balances you won't collect, right from the admin

Waive an outstanding balance in one action from the payment card on the order page. Also included: automatic adjustments when editing, refunding, or returning, visibility for buyers, a dedicated permission, and write-off reporting.

On this page
  1. What's changing (30-second overview)
  2. 5 key components
  3. Workflow diagram
  4. Auto-adjustment rules (only the excess, oldest first)
  5. Before vs. now
  6. What's documented vs. not documented
  7. 5 key points for developers
  8. 3 practical use cases
  9. One-line summary for proposals

1What's changing

When an order still has a balance dueand you decide not to collect it,,
you can now use the order page'spayment card to waive that balance directly.Waived amounts can also be removed later.
¥?

Before: the balance stays outstanding

The ability to handle an uncollected balance as a waiver from the payment card on the order page is introduced in this post as a new feature.

Now: waive it and keep a record

Waive from the payment card. It's reflected on the buyer's side too, and can be tracked as a write-off in reports.

25 key components

New

① Waive from the payment card

Waive the outstanding balance from the payment card on the order page. Existing waivers can also be removed here.

Automatic

② Automatic adjustments

When processing order edits, refunds, or returns, Shopify adjusts existing waivers as needed.

Buyer-facing

③ Shown to buyers

The waived amount appears on relevant buyer-facing surfaces such as customer accounts, checkout, and email notifications.

Permissions

④ Dedicated staff permission

Requires the new Admin permission "Waive order balances." High-privilege roles such as Store admin have it enabled by default.

Reports

⑤ Write-off reports

Adds new write-off metrics and dimensions to track waived balances. A new default report "Write-offs by order" is available to all stores.

3Workflow diagram

Staff Has Waive permission Order page Payment card Waive balance Waived amounts can also be removed here Waived amount recorded Balance due → 0 Auto-adjusted on edits, refunds, and returns Shown on buyer-facing surfaces Customer accounts Checkout Email notifications Tracked in reports Write-off metrics / dimensions Default report "Write-offs by order"

4Auto-adjustment rules (only the excess, oldest first)

If order edits, refunds, or returns causethe order total to fall below the waived amount, Shopify reversesonly the excess. Reversals are appliedstarting with the oldest waived amount.
BEFORE: Total waived amount Waiver A (older) Waiver B (newer) Order total after refunds, returns, or edits Excess Auto-adjusted by Shopify AFTER: Only the excess is reversed Waiver A Waiver B Order total = waiver cap Rules ① Only the amount exceeding the order total is reversed ② Reversals are applied starting from the oldest waiver (the diagram above shows one example allocation; the article gives no specific calculation example)
The article explicitly names three applicable actions: order edits,refunds, andreturns. Behavior for other actions isn't specified.

5Before vs. after

ItemBefore this releaseAfter this release
Waiving balances Not specified New Waive from the payment card on the order page
Removing waivers Not specified Available Remove existing waivers from the same page
On edits, refunds, and returns Not specified Auto-adjusted Only the excess is reversed, oldest waiver first
Buyer visibility Not specified Shown Customer accounts / checkout / email notifications
Who can do it — Permission-based Only staff with the "Waive order balances" permission
Reports — All stores "Write-offs by order" + write-off metrics/dimensions

6What's specified vs. not specified

Documented

Confirmed information

Waiving balances from the payment card and removing waived amounts
Automatic adjustment rules for edits, refunds, and returns
Display on buyer-facing surfaces (customer accounts, checkout, email notifications)
Permission "Waive order balances", enabled by default for Store admin and similar roles
"Write-offs by order" is available to all stores

Not documented

Information not covered in the article

Handling in the Admin API (GraphQL) and webhooks
Accounting and tax treatment of waived amounts
Whether partial waivers are possible
Exact wording of the email notifications
Which plans and countries the feature is available in

If you handle balances through API or accounting system integrations,verify in a development store beforehandhow order data looks after a waiver.

75 key points for developers

1. A waived amount is a separate amount attached to the order

Because the changelog mentions "removing existing waived amounts" and "reversing from the oldest waived amount," waivers appear to stack on the order as individual amounts. Plan for orders with multiple waivers.

2. Refunds and returns change waived amounts automatically

If the order total drops below the waived amount, the excess is automatically reversed, starting with the oldest waiver. If you sync waived amounts to external systems,re-sync after refunds and returnsis required.

3. Review your permission design

The new "Waive order balances" permission is ON by default for high-privilege roles such as Store admin. Behavior for custom roles isn't documented, socheck who can waive balancesin your list of roles.

4. Shown on buyer-facing surfaces

Waived amounts appear in customer accounts, checkout, and email notifications.If you've customized notification templates or customer accounts, check how they display.

5. Write-offs become an analytics dimension

New write-off metrics and dimensions have been added, and the default report "Write-offs by order" is available to all stores. You canaggregate and audit waived amounts per order. Whether this data is available via the API isn't documented.

83 practical use cases

Balance ¥300
USE CASE 1

Close out small unpaid balances without collecting them

Challenge
Small balances left over from order edits and similar changes can leave an order marked as "Payment pending" even after you've decided they aren't worth collecting.
Solution
Waive the balance from the payment card on the order page. If you waive by mistake, remove the waived amount from the same page to restore it.
Impact
The decision not to collect is recorded on the order, and the waiver is also shown to the buyer.
Tech notes
Requires the "Waive order balances" permission. Decide whether to grant it to frontline staff together with your operating rules.
USE CASE 2

Limit who can waive balances to enforce internal controls

Problem
Waiving a balance directly affects revenue, so it shouldn't be something anyone can do.
Solution
Grant the new "Waive order balances" permission only to manager roles. High-privilege roles have it on by default, so review who currently has access.
Impact
Narrows down who can waive balances and enforces your approval flow through admin permissions.
Tech notes
High-privilege roles such as Store admin have it on by default. Defaults for other roles aren't documented, so check your actual roles when rolling this out.
Orders Write-off
USE CASE 3

Review and audit waived amounts monthly

Problem
Without a cross-order view of how much went uncollected on which orders, it's hard to explain to accounting and auditors.
Solution
Use the default "Write-offs by order" report and the write-off metrics/dimensions to total waived amounts per order and review them regularly.
Impact
Makes waivers visible so you can refine your operating rules and spot unusual waivers.
Tech notes
The report is available on all stores. Syncing to external accounting systems and retrieving the data via API aren't documented. Also account for waived amounts being adjusted automatically on refunds and returns when aggregating.

9One-line summary for proposals

"A new feature that lets you formally 'waive' unpaid balances you won't collect, right from the order page.
Automatically adjusted on refunds and returns, shown to buyers, restricted by a dedicated permission, and tracked in the Write-off report.
When rolling it out, you only need to settle who gets the permission and check how it appears in notifications and integrations."