Reported details
What happened
Shopify’s Developer Changelog says POS UI extensions using API version 2026-10 or later must handle rejected promises for the listed Cart API mutations; versions 2026-07 and earlier are unaffected.
A mutation succeeds only when POS confirms the cart changed. The changelog describes two unconfirmed outcomes: POS refused the update and the cart is unchanged, or POS could not confirm it and a partial write is possible.
For the uncertain outcome, the changelog says to read the cart before retrying. It also notes that mutations can reject for other reasons, including an invalid discount value or missing customer.
Business relevance
Why it matters
An app can no longer treat a resolved mutation as proof that a cart update took effect when using 2026-10; confirmation now determines whether the write is reported as successful.
Retries need different handling depending on what is known: an unchanged cart after a refusal differs from an outcome that may include a partial write.
The version boundary makes this a targeted compatibility issue for apps adopting 2026-10 or later, not a reported change for extensions that remain on 2026-07 or earlier.
Editorial perspective
Analysis & judgment
By making confirmation part of mutation success, Shopify POS changes the signal an extension can trust: a resolved operation is no longer the only meaningful state to account for. This changes implementation reviews from checking that a call completes to checking its confirmed outcome; the evidence is a single changelog claim, not an account of how every app currently handles writes.
For merchants using affected extensions, a declined discount or other cart change could leave the app’s displayed state out of step with the cart if the app does not handle rejection. That makes extension readiness relevant to checkout reliability, but the supplied evidence does not establish how many merchants or apps are affected.
Treat adoption of 2026-10 as the decision gate: if an extension uses that version or later, verify handling for every cart mutation it calls and read the cart before retrying an uncertain write; if it remains on 2026-07 or earlier, this specific change does not require a version-driven code change. The evidence does not establish when any individual app will upgrade.
Applicability
Seller impact
Merchants relying on POS extensions for discounts, fees, customer assignment, line-item changes, or selling plans should confirm whether those extensions use API version 2026-10 or later.
If an affected extension fails to handle rejected writes, its displayed cart state could differ from the state POS applied, making checkout behavior harder for staff to interpret.
The update does not affect apps on POS UI extensions API version 2026-07 or earlier, according to the changelog.
Action plan
What to do now
- 1
Check extension API versions
this-weekAsk your POS app or extension developer whether the extension uses API version 2026-10 or later. Prioritize extensions that change discounts, fees, customers, quantities, or line-item details.
- 2
Verify rejection handling before upgrading
this-weekIf your team maintains an affected extension, confirm that every Cart API mutation it calls handles a rejected promise and that the interface does not present an unconfirmed change as applied.
- 3
Review cart state before retrying uncertain writes
monitorFor an outcome that POS could not confirm, read the cart before retrying because a partial write is possible. Do not treat every rejection as the same case; the changelog also identifies validation and missing-customer errors.
What not to do yet
- Do not retry an uncertain cart write blindly: the changelog says a partial write is possible and directs apps to read the cart first.
- Do not assume this version-specific change applies to extensions on 2026-07 or earlier.
Sources & context
Evidence and sources
A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.
- 01Source link
In POS UI extensions API version 2026-10, Cart API mutations reject when Shopify POS doesn't confirm that the cart changed. In earlier versions these mutations resolve whether or not POS applied the write. This is a breaking change for apps that adopt 2026-10, and those apps need to handle a rejected promise on every cart mutation they call. Apps on 2026-07 and earlier are unaffected. What changed POS reports the outcome of every cart write. Only a success result confirms that the cart changed. Earlier API versions resolve the mutation regardless of that result, so an app can't tell an applied write from a dropped one, and an app can show a fee or a discount as applied when the cart never changed. In 2026-10, these mutations reject unless POS confirms the write: bulkCartUpdate, removeLineItem, applyCartDiscount, addCartCodeDiscount, removeAllDiscounts, setCustomer, removeCustomer, addLineItemProperties, bulkAddLineItemProperties, removeLineItemProperties, setLineItemDiscount, bulkSetLineItemDiscounts, removeLineItemDiscount, addLineItemSellingPlan, and removeLineItemSellingPlan. updateLineItemQuantity is new in 2026-10 and rejects from its first release. An unconfirmed write reject
Shopify Developer Changelog · Workflow status: single-source
Retrieved: October 7, 2026 at 06:07 p.m. UTC
Claim is bounded to the ingested title or summary; no source body or quotation is retained.