To rebuild a cart across devices, you have to tie the cart to something that survives the device switch: a logged-in account, a buyer token passed to the cart, or a platform-level identity like Shop. By default, none of that exists. A cart lives in a browser session, so the moment a shopper moves from phone to laptop, the cart stays behind. Below, we cover what each major platform gives you, where the gaps are, and how to reach the shoppers who never log in at all.
TL;DR
- Carts are tied to a browser or device session by default, so a cart started on a phone does not appear on a laptop unless the shopper is identified.
- Shopify (via Shop), BigCommerce (Persistent Cart) and headless builds (buyer identity on the cart object) can all carry carts across devices, but only for logged-in or identified shoppers.
- Anonymous visitors, who are most of your traffic, never trigger any of that. You need a re-engagement channel that does not depend on an email or phone number.
- Whatever you send must land on a cart that is actually waiting. A notification that opens an empty cart is worse than no notification.
- Apple App Clip notifications can reach the lock screen without an install or signup, but the default window is 8 hours, so timing matters.
Table of Contents
- Why carts disappear when shoppers switch devices
- What each platform gives you out of the box
- The problem none of these solve: anonymous shoppers
- A practical setup in five steps
- Reaching shoppers you cannot identify: App Clip notifications
- Our perspective
- Where StorePush fits
- Common mistakes to avoid
- FAQ
- Sources
Why carts disappear when shoppers switch devices
Picture the usual path. Someone finds your product on Instagram, taps through on their phone, adds a jacket to the cart, then gets pulled away. That evening they open a laptop, search your brand, and find an empty cart. Most of them will not rebuild it. They walk away.
The reason is plain engineering. Shopify's own community guidance says that Shopify carts do not automatically carry over when a customer logs in from a different browser or device, because the cart is tied to the browser or device session. The developer documentation for custom storefronts points the same direction: you must explicitly pass a buyer identity or customer token to the cart for it to persist across contexts.
Device hopping is also routinely ignored in abandonment research. A DeviceAtlas review of more than 200 articles found that fewer than 2% drew any link between cart abandonment and the user's device, beyond the usual mobile versus desktop split. Most advice is about copy and discounts. The plumbing gets skipped.

What each platform gives you out of the box
Before buying anything, check what your platform already does. Here is where the main ones stand.
| Platform | What carries a cart across devices | Who it works for | Main limit |
|---|---|---|---|
| Shopify | Shop app cart sync, announced in the October 2026 changelog | Shop users | Shopper must use Shop |
| Shopify (logged-in checkout) | Continuous authentication from cart to checkout | Authenticated customers | Does not create a login for anonymous visitors |
| BigCommerce | Persistent Cart | Logged-in customers on Growth, Scale or Performance plans | Needs an account and a qualifying plan |
| Headless / custom | Buyer identity or customer token on the cart | Authenticated buyers | You build and maintain it |
| WooCommerce | Persistent cart for logged-in users, depending on your setup and plugins | Logged-in customers | Guests get nothing |
Shopify and the Shop app
This is the biggest recent change. Shopify's October 5, 2026 changelog says that for Shop users, carts sync across devices, and carts started in the Shop app carry over to your storefront and the other way round. It also says browsing activity syncs to the shopper's Shop account, so Shop can resurface viewed items and abandoned carts. If a meaningful share of your buyers already use Shop, you get this without lifting a finger.
The catch is in the phrase "for Shop users." A first-time visitor from a paid social ad is not necessarily in that ecosystem.
BigCommerce Persistent Cart
By default, BigCommerce saves a cart in the browser's cache for 7 days, accessible only from the same device and browser. With Persistent Cart switched on under Settings, then Checkout, logged-in customers can reach their cart from any device and browser for 30 days, and carts created before login convert once the shopper signs in. It requires a Growth, Scale or Performance plan.
Note the pattern again: the shopper has to log in.
Headless and custom storefronts
If you built your own storefront on the Shopify Storefront API, cart persistence is your job. Shopify's documentation covers attaching buyer identity to the cart. A common miss on custom builds is the checkout URL: it needs to be requested again or updated when the buyer's authentication status changes, or the contents may not follow them between an app and the web storefront.
The problem none of these solve: anonymous shoppers
Every option above has the same precondition. The shopper has to be identified, whether through Shop, a store account or a token. Yet most visitors leave without buying and without handing over anything. No email, no phone number, no account.
For those shoppers, "rebuild the cart across devices" is the wrong goal. You cannot sync a cart to an identity you do not have. The practical goal is different: get them back to a cart that is waiting, on the device they are holding right now.
That is why we think of cart abandonment as a browsing problem, not only a checkout problem. Most people leave long before checkout, and a form asking for their email at that point does not rescue them.
A practical setup in five steps
Here is the order we would work in if we were setting this up for a store today.
- Turn on what your platform already offers. On BigCommerce, enable Persistent Cart if your plan allows. On Shopify, make sure customer accounts and Shop Pay are active so authenticated and Shop users keep their carts.
- Make login cheap, not mandatory. One-tap sign-in options reduce the cost of identifying a shopper. Do not gate the cart behind an account. Guest checkout stays on.
- Fix the technical side of the return trip. Slow loads and crashes on older mobile operating systems quietly kill returns. As the DeviceAtlas piece argues, re-engagement should be as much about the technical experience, such as a cart being ready when the shopper taps the message, as about the wording. Test your cart page on an older iPhone before you blame your copy.
- Add a channel for anonymous visitors. Choose one that does not need personal data collected up front. See the next section.
- Measure by attributed revenue, not by sends. Track which recovered orders came from which trigger, so you can tell whether the cart waiting on the other end actually converted.
For a deeper look at the mobile side of that audit, our mobile checkout fixes and five-point audit walks through it step by step.
Reaching shoppers you cannot identify: App Clip notifications
Apple App Clips are lightweight pieces of a native app that launch without installation. Apple's documentation explains that App Clips can schedule or receive notifications when they provide value, for example to update a user on a delivery. For a store, that same mechanism puts a message on the shopper's lock screen with no app download and no personal data handed over.
Two technical facts matter for you:
- The window is short. Ephemeral notifications are active for 8 hours after the App Clip launches by default. Developers can request standard push permission inside the App Clip to extend that to a week or more.
- It takes setup. An App Clip needs its own bundle identifier and push configuration in the Apple Developer Portal, and the ephemeral notification capability has to be enabled in the App Clip's Info.plist.
That is exactly why most stores do not build this themselves. And because of the 8-hour default, the message has to go out while the shopper still has the original intent. Waiting for a next-day email sequence misses it. We go deeper on timing in reengaging anonymous shoppers in the first 1 to 4 hours and on the permission side in iOS push notifications and the quiet alerts before the one ask.
A notification does not need a discount to work either. If margin matters to you, see how to recover carts without discounts.
How this fits with cross-device sync
The two approaches complement each other. Platform sync handles identified shoppers who switch devices. Lock screen re-engagement handles the anonymous shopper who left on their phone and is still carrying it. Treat them as layers inside broader cross-channel strategies, where each channel covers the audience the others cannot reach.

Our perspective
We built StorePush around one observation: the shoppers you most want back are the ones who gave you nothing. They did not sign up, they did not leave an email, and a cart synced to an account that does not exist helps no one.
So we do not try to rebuild the cart in a database keyed to an identity. We bring the shopper back to the cart through their lock screen, using native iOS App Clips, with no email, no phone number and no app install. That is the gap Shopify's Shop sync, BigCommerce's Persistent Cart and custom token logic leave open, and it is the one our product is designed for.
We also think stores over-invest in message copy and under-invest in the landing moment. A well-timed notification that opens a slow or empty cart wastes the one tap you earned. Fix the destination first, then the message. Our iOS lock screen notifications guide explains how we approach both.
— Lucas
Where StorePush fits
StorePush sends cart and browse abandonment push notifications to the lock screen using native iOS App Clips, and it integrates with Shopify, WooCommerce, BigCommerce and custom storefronts. The dashboard includes revenue attribution, funnel tracking, CTR heatmaps and event-based triggers.
Pricing is simple: the Free plan is $0 per month, Pro is $50 per month, and there is a 5% usage commission on attributed recovered revenue. You can see the plans and start on the StorePush site.
Common mistakes to avoid
- Assuming sync equals recovery. Cart sync only helps shoppers who are already identified. Measure how many of your abandoners are actually logged in. For most stores that is a small slice.
- Forcing accounts to unlock persistence. Gating the cart behind registration adds the very friction you are trying to remove.
- Ignoring the 8-hour window. If you use App Clip notifications, send quickly, and design a path to request longer-term permission once the shopper has shown interest.
- Skipping the checkout URL on custom builds. If the buyer's authentication state changes and the checkout URL does not, contents may not persist between app and web.
- Testing only on a new phone. Older operating systems and slower devices are where silent failures hide.
FAQ
Why does my cart disappear when I switch from my phone to my laptop?
Because the cart is stored against a browser or device session, not against you. Unless you are logged in or using a service that syncs identity, such as Shop, the second device has no way to know about the first.
How do I make carts persist across devices on BigCommerce?
Go to Settings, then Checkout, and enable Persistent carts, then save. It is available on Growth, Scale and Performance plans, and logged-in customers can reach their cart from any device for 30 days. Shoppers who never log in still only have the browser cart, which BigCommerce saves for 7 days by default.
Does Shopify sync carts across devices now?
Yes, for Shop users. Shopify's October 2026 changelog says carts sync across a shopper's devices and carry over between the Shop app and your storefront. Shoppers outside the Shop ecosystem do not get this automatically.
How can I bring back shoppers who never logged in?
You need a channel that does not depend on stored contact details. Lock screen notifications through iOS App Clips are one option, since they require no install and no email or phone number. Remember that the default notification window is 8 hours, so speed matters.
Sources
- Faster checkout, carts synced across devices via Shop (Shopify Changelog)
- Continuous cart authentication to checkout (Shopify Changelog)
- How can I keep items in my cart after logging in on a different browser? (Shopify Community)
- Cart (Shopify Storefront API documentation)
- Persistent Cart (BigCommerce Support)
- Enabling notifications in App Clips (Apple Developer Documentation)
- 5 Cart Abandonment Questions about User Devices that are Never Asked (DeviceAtlas)
