Executive summary
- What: Shopify POS v11.15 replaces the mobile Cart tab with a persistent cart button that keeps recently added items, item count, and the running total visible from Home, Products, Orders, and Search.
- Why: Staff confirm the state of a sale without leaving the screen they are working from, which removes the navigation round trips that produce mis-scans and missed discounts during peak hours.
- Who: Retailers running POS on phones, especially floor selling, clienteling, and pop-up teams. Tablet layouts are unchanged.
What changed
Until v11.15, the mobile POS cart lived behind a Cart tab in the bottom navigation, supported by a "Go to cart" bar that appeared once a sale was in progress. Both are gone. In their place is a persistent cart button that stays on screen while staff move through the app.
The button surfaces the items most recently added, the item count, and the running total. It also confirms changes that are easy to lose track of, including discounts, an attached customer, the staff member on the sale, custom sales, and fees. Tapping it opens the full cart from any main screen, and closing the cart returns staff to where they were rather than to Home.
Why it matters
Phone-based selling trades screen real estate for mobility, and the cost has always been verification. Staff who cannot see the cart check it, and every check is a trip out of the task at hand. On a busy floor that produces two recurring failures: items scanned twice because the first scan was never confirmed, and a missing discount or customer attachment found at the payment screen, when the fix is slowest.
Keeping cart state in view catches both at the point where the error is cheap. For enterprise retailers the value is less about seconds saved per sale and more about variance across a fleet: newer staff behave more like experienced staff when the system shows them what they would otherwise have to remember. Treat it as a change-management item rather than a silent upgrade, because staff trained on the old bottom navigation will look for a tab that no longer exists. Teams still standardizing device setup across doors will find the groundwork in our
Shopify POS setup guide for physical retailers.
Role-specific impact
- Marketers: Promotion and clienteling attach are now visible in line rather than confirmed at the end. Expect cleaner attribution on staff-attached sales and fewer "was the code applied" corrections at the till.
- Developers: No POS extension API was removed, but any UI extension, tile placement, or deep link that assumed the Cart tab position should be re-tested on phones under v11.15. Layout assumptions break quietly.
- Store admins: Version the fleet, pilot before a full rollout, and update the training material and till SOPs that reference the Cart tab. Mixed phone and tablet fleets will run two navigation patterns at once.
Use-case example
Real-world scenario
A 40-door apparel retailer sells from the floor on phones, with an average basket of 3.4 items. In one store, staff opened the cart roughly six times per transaction, mostly to confirm what had been scanned. At about four seconds per round trip and 300 transactions a day, removing two of those checks returns close to 40 minutes of selling time per store per day. The more durable gain is second-order: fewer voids and price adjustments at payment, where staff time and customer patience cost most. Measure void and adjustment rates for two weeks before rollout so the comparison afterward is real.
Implementation checklist
- Confirm which POS app version each device is running, starting with the oldest hardware in the fleet, and update to v11.15 or later.
- Pilot in one or two stores for a full week, including a weekend, before rolling out fleet-wide.
- Re-test any POS UI extensions, custom tiles, and deep links on phones specifically.
- Update training decks and till SOPs that reference the Cart tab or the "Go to cart" bar.
- Brief store managers on the confirmation states so they can tell staff what a correctly attached discount or customer looks like.
- Track void, price adjustment, and mis-scan rates before and after to verify the change earned its training cost.
FAQ
Q: Do we need to enable the persistent cart button?
A: No. It ships with POS v11.15 on phones and replaces the Cart tab and the "Go to cart" bar, so it arrives with the app update rather than as a configurable setting. Plan for it in a release window, not a project.
Q: Does this change anything for tablet-based POS?
A: The persistent cart button is a phone behaviour. Tablets keep their existing cart presentation, so a mixed fleet will show two navigation patterns until your training accounts for both.
Resources
Need guidance? Talk to Makro.