2026-10, affected cart mutations reject unless POS confirms the write. Wrap every write in try/catch, distinguish a refused update from an unknown outcome, and read the actual cart before retrying an ambiguous write.On this page
Why this is suddenly visible
Before POS UI extensions API 2026-10, several cart mutation methods could resolve even when POS did not apply the requested change. That created a dangerous illusion: the app could display “Discount applied” or “Customer selected” because the promise resolved, while the cashier’s cart remained unchanged.
Shopify changed this contract on October 7, 2026. In API version 2026-10, affected mutations reject if POS cannot confirm the write. This is an improvement for correctness, but it is also a breaking change for extensions that assume every awaited call resolves. Unhandled rejections can skip cleanup code, leave spinners running, or suppress a staff-facing error.
The behavior is controlled by the POS UI extension’s declared API version, not a store-wide switch. Extensions on 2026-07 and earlier keep their old behavior until they upgrade.
Which cart operations need attention?
Audit calls to bulkCartUpdate, removeLineItem, applyCartDiscount, addCartCodeDiscount, removeAllDiscounts, setCustomer, removeCustomer, line-item property and discount mutations, and selling-plan mutations. Shopify’s October 7 changelog lists the complete set. The new updateLineItemQuantity method also rejects on unconfirmed writes from its first release.
Do not assume that only discounts are affected. A loyalty app can apply a discount and assign a customer in sequence. If the first write is unconfirmed and your code continues optimistically, the second step can create a mismatched cart or staff interface.
Fix the promise handling before upgrading
Shopify documents this straightforward pattern for a cart-level discount. The method and argument shape below are from the POS Cart API; the UI helpers are placeholders for your app’s own state management:
async function applyStaffDiscount() {
setLoading(true);
try {
await shopify.cart.applyCartDiscount(
'FixedAmount',
'Staff discount',
'5.00'
);
setDiscountApplied(true);
} catch (error) {
setDiscountApplied(false);
showToast('Could not update the POS cart.');
console.error('POS cart discount failed', error);
} finally {
setLoading(false);
}
}
Only set a success state after the promise confirms the write. Always reset loading state in finally. In a real extension, inspect the cart state after the mutation when subsequent actions depend on the precise discount, customer, or quantity.
Two error messages require different responses
Shopify identifies two specific unconfirmed-write messages:
POS refused the cart update. The cart was not changed.
POS could not confirm the cart update.
Refused means POS declined the update and the cart is unchanged. A common example is a cashier already moving into payment, where cart editing is unavailable. Tell staff what happened and let them retry when the cart is editable.
Could not confirm means the outcome is unknown and a partial write is possible. Do not blindly retry a discount, customer assignment, or bulk mutation. Read the current cart, reconcile it with the intended change, and only then decide whether another write is needed. Blind retries can duplicate discounts or create inconsistent state.
Other failures, including invalid discount values or missing customers, can also reject. Don’t classify every rejection as one of these two conditions. Log the operation name, API version, and safe diagnostic information without storing customer personal data in logs.
Make bulk operations and staff UX safe
For a bulk update, consider the whole operation’s intended final state. If POS cannot confirm it, refresh the cart and compare each relevant field. Do not mark the whole workflow complete based on your app’s local state. Disable duplicate action buttons while a write is pending, but always restore them on error.
When upgrading, inventory every POS extension cart mutation rather than fixing only the first error you see. Update the declared api_version to 2026-10 only after all call sites have rejection handling. If a release cannot be made safely yet, a supported earlier API version can buy migration time; it does not fix the old silent-write ambiguity.
This is different from an online-store cart drawer failing to repaint. For that issue, see why a Shopify cart drawer updates only after refresh. POS has its own cart mutation contract and cashier workflow.
How to test this
- Inventory every cart mutation called by your POS UI extension and note its declared API version.
- On a test POS cart, apply a valid discount and verify the promise resolves, the visible cart changes, and your success UI appears.
- Attempt a cart change when POS is no longer accepting edits, such as during the transition to payment, and verify the refusal is caught.
- Simulate an unknown or failed response in a controlled test and verify the app reads current cart state before any retry.
- Test a two-step workflow such as customer selection followed by a discount; verify a failure cannot leave the UI falsely completed.
- Check that spinners, disabled buttons, and error messages recover after each failure.
- Upgrade the extension to
2026-10in a test environment, repeat all cases, and inspect logs for unhandled rejections.
Sources and further reading
- Shopify changelog: POS cart mutations reject unconfirmed writes, October 7, 2026
- Shopify POS UI extensions Cart API reference
- Shopify Admin API 2026-10 release notes
Documentation reviewed October 31, 2026.

