If you run a headless storefront, "push" can mean two different things: pushing data from your commerce backend to your custom frontend, or pushing a notification to a shopper's lock screen. This guide covers the second one. A headless build gives you full control over the experience, but it doesn't solve what happens when a shopper adds to cart and walks away. On iOS you can reach many of those shoppers with a lock screen notification, without collecting an email, a phone number or an app install, by using native App Clips.
Below: what headless commerce changes for re-engagement, why traditional follow-up tools struggle, how App Clip push works under the hood, and how to decide whether it fits your stack.
TL;DR
- Headless commerce separates your storefront (the "head") from the commerce backend, which gives you design freedom but also removes the plug-and-play apps that standard themes rely on.
- Cart recovery still matters: Baymard-based research puts average global cart abandonment at 70.22%, and most of those shoppers never gave you an email.
- Apple App Clips can send push notifications for up to 8 hours after a shopper's interaction, with no app download.
- StorePush connects to Shopify, WooCommerce, BigCommerce and custom storefronts, so a headless build is not a blocker.
- Headless itself is not a requirement for success. Go headless for real business reasons, not for push.
Table of Contents
- What "headless commerce" means for your marketing stack
- Do you actually need headless?
- Why cart abandonment follows you onto a headless site
- Why email and SMS leave most shoppers unreachable
- How App Clip push reaches anonymous shoppers
- Where push fits in a headless, multi-channel setup
- Setting up push on a headless storefront
- Our perspective: headless is the frontend, not the strategy
- What StorePush costs
- FAQ
- Sources
What "headless commerce" means for your marketing stack
In a headless setup, the backend keeps the catalog, inventory, customers, payments and orders. You build the storefront yourself and connect it through APIs. Shopify describes it as building the frontend while its APIs handle the commerce underneath, and that frontend can be a website, a mobile app or something more unusual.
On Shopify, that usually means the Storefront API, often with the Hydrogen framework. Open-source platforms such as nopCommerce, an ASP.NET Core platform, can play the same role for teams on that stack.
You may also hear "composable commerce." The two terms get used interchangeably, but there is a distinction. According to one agency guide, headless is the separation of frontend and backend, while composable is the modular assembly of best-of-breed services. Headless is the mechanism, composable is the goal.
The marketing catch
On a standard theme, you install an app and it injects a script, a popup or a tracking pixel. On a custom frontend, nothing is injected for you. Every tracking event, every popup and every follow-up trigger has to be wired in by your developers or supported by a tool that works with custom storefronts.
That is why re-engagement is often an afterthought on headless builds. The team spends months on performance and design, launches, and then discovers the abandoned cart flow was never connected.
Do you actually need headless?
Be honest about this first, because it changes the budget conversation. Shopify's own documentation says headless adds cost, complexity and maintenance compared with themes and apps, and recommends it only when your requirements exceed what standard sales channels can do. For many small and mid-market stores, a good theme and well-chosen apps will outperform a custom frontend that nobody has time to maintain.
Headless tends to make sense when:
- You sell across several surfaces (web, native app, kiosks, social) from one catalog.
- Your brand experience needs layouts or interactions that themes can't deliver.
- You have in-house developers, or a long-term agency relationship, to maintain the frontend.
If you're already there, keep reading. If you're not, the push approach below works on standard platforms too.
Why cart abandonment follows you onto a headless site
A faster, prettier storefront reduces some friction, but shoppers still leave for reasons no frontend framework fixes. The research cited earlier lists the top ones: 48% of shoppers cite unexpected extra costs such as shipping and tax, 26% cite forced account creation, and 22% cite a complicated checkout.
You can fix some of that with design. Showing total cost early and offering guest checkout helps, and guest checkout means collecting only what fulfillment requires. A headless build makes those changes easier to ship.
But even a flawless checkout loses most visitors, because most visitors are browsing, comparing or interrupted. With an average abandonment rate around 70%, the question is not how to stop everyone from leaving. It's how to reach them after they've gone.
Why email and SMS leave most shoppers unreachable
The usual answer is an email or text sequence. It works, with one big condition: you need the shopper's address or number before they leave.
Think about the shopper who drops a jacket in the cart on their phone, sees a shipping fee, and closes the tab. They never reached the email field. There's nothing to follow up on. The cart sat in your analytics and nowhere else.
For the ones you do capture, your message competes with everything else in the inbox: it may land in spam or get buried in a Gmail tab. SMS adds consent requirements and per-message costs.
That leaves a large group of anonymous shoppers, often the majority, who are invisible to your lifecycle marketing. A headless storefront doesn't change that. If anything, it makes it more visible, because you control every pixel and still can't reach them.
How App Clip push reaches anonymous shoppers
App Clips are lightweight pieces of a native iOS app that open without a full install. Apple's documentation describes a feature that matters here: an App Clip can schedule and receive notifications for a limited window. Per Apple's developer documentation, notifications are valid for 8 hours after launch, and the user can opt out from the App Clip card.
The ephemeral notification permission is enabled by adding the NSAppClipRequestEphemeralUserNotification key to the App Clip's Info.plist. In practical terms, that means:
- No email or phone number. The notification goes to the device, not to an address you collected.
- No app install. The shopper never visits the App Store or downloads anything.
- No separate sign-up. The shopper gets a standard lock screen notification, and Apple's own opt-out remains available.
The 8-hour window is short, and that's a feature. It matches the period when purchase intent is still warm: an hour later, a few hours later, that evening. If you want the timing detail, our guide to re-engaging anonymous shoppers in 1 to 4 hours walks through it, and this post on recovering carts within 8 hours covers the merchant side.
The multi-merchant routing detail
If you're building this yourself for more than one store, there's a trap. Apple's documentation says a multi-merchant platform must include a target-content-id in the notification payload URL, and that URL matching must be configured in App Store Connect. Otherwise the system can't route the push to the right merchant's App Clip on the device.
This is the sort of plumbing that eats weeks of developer time. It's also why many teams prefer to use a product built on top of it rather than build their own. For the developer view, see our App Clips guide.
Where push fits in a headless, multi-channel setup
Headless storefronts are usually built because the brand sells in more than one place. Push shouldn't be a silo. The goal is consistent messaging, whether a shopper meets you on your site, in an app, in email or on the lock screen. If you want a broader frame for that, this overview of omnichannel marketing and unified customer experience is a useful companion read.
A practical way to split the roles:
| Channel | Needs from the shopper | Best for |
|---|---|---|
| Address collected before exit | Known customers, newsletters, post-purchase | |
| SMS | Phone number and consent | High-urgency, opted-in segments |
| App Clip push | Nothing collected | Anonymous cart and browse abandoners on iOS |
| On-site messaging | Shopper still on the page | Exit-intent offers, shipping clarity |
They don't compete. Push picks up the shoppers the others never had a chance to touch.
Setting up push on a headless storefront
The exact steps depend on your frontend, but the pattern is consistent. StorePush lists Shopify, WooCommerce, BigCommerce and custom storefronts as integrations, so a headless build on any of them can be connected.
- Decide which events matter. Add to cart, checkout started and product viewed are the usual triggers. Cart and browse abandonment are the two use cases StorePush targets.
- Make sure your frontend emits those events. On a custom frontend, your developers need to send cart and product events from the storefront. This is the step teams skip, so put it on the launch checklist.
- Connect the store. Link your storefront and backend so purchases can be tied back to the notifications that drove them.
- Write the messages. Keep them short, specific and useful. A reminder that names the product beats a generic nudge. Our post on iOS lock screen notifications has examples of what works.
- Measure attributed revenue. Track funnel steps, click-through and recovered revenue, not just sends.
StorePush's dashboard covers revenue attribution, funnel tracking, CTR heatmaps and event-based triggers, so you can see which messages recovered orders.
Message ideas that don't rely on discounts
Discounts train shoppers to abandon on purpose. Try these first:
- A plain reminder that the cart is saved.
- A low-stock or back-in-stock note, when it's true.
- A price drop alert on an item they viewed.
- Shipping or delivery clarity, given how many shoppers leave over extra costs.
More on this in our post on recovering carts without discounts, and on the psychology behind drop-off.
Our perspective: headless is the frontend, not the strategy
We talk to a lot of store owners and marketers, and a pattern keeps showing up. Teams invest heavily in the storefront and then treat re-engagement as a plugin question. On headless, there is no plugin to lean on, so the gap gets noticed late.
Here's how we see it. The majority of visitors leave without buying, and the majority of those never gave you contact details. A tool that needs an email or phone number to start working has already excluded most of your traffic. That's why we built StorePush around native iOS App Clips: the shopper doesn't have to sign up, install anything or hand over data for a reminder to reach their lock screen.
We'd also say this plainly: don't go headless just to use us. Shopify's own guidance is that headless is for stores whose requirements outgrow standard channels. If you're on a theme, we work there. If you're on a custom frontend, we work there too. The push layer should follow your architecture, not dictate it.
One limit to keep in mind: App Clips are an Apple technology, so this approach targets iOS shoppers. Treat it as one channel in the mix, not the whole recovery program.
— Lucas
What StorePush costs
There are two plans. Free is $0 per month. Pro is $50 per month. A usage commission of 5% applies to revenue recovered through push-triggered purchases. You can start on the free plan and see whether anonymous push recovers carts on your store before you commit to anything.
See the current plans on the StorePush site.
FAQ
What does headless mean on Shopify?
It means you build your own storefront and use Shopify's APIs for the commerce backend, such as products, carts and checkout. Shopify's documentation covers the Storefront API and headless approach. It adds flexibility, but also cost and maintenance, so it suits stores that have outgrown themes.
What is the difference between headless and composable commerce?
Headless means the frontend is separated from the backend. Composable means assembling the stack from modular, best-of-breed services. Headless is typically the mechanism that makes composable possible, which is why people mix the terms up.
Can I send push notifications to shoppers who never gave me their email?
On iOS, yes, through App Clips. Apple lets an App Clip request ephemeral notification permission, which allows notifications for up to 8 hours after launch with no full app install. Shoppers can opt out from the App Clip card.
Does StorePush work with a custom headless storefront?
Yes. StorePush integrates with Shopify, WooCommerce, BigCommerce and custom storefronts. On a custom build, your frontend needs to send the cart and product events that trigger notifications.
Is nopCommerce free?
nopCommerce describes itself as a free and open-source eCommerce solution built on ASP.NET Core. Hosting, development and extensions are separate costs you'll need to plan for.
Sources
- Enabling notifications in App Clips, Apple Developer Documentation
- About headless commerce, Shopify Developers
- The CTO's Guide to Composable Commerce and Headless Technologies on Shopify
- What percentage of online shoppers abandon their cart?
- Checkout Optimization: How to Design a Frictionless Ecommerce Checkout
- nopCommerce on GitHub