Ends in a real contract
The selection becomes a subscription through the API, not an approximation assembled at checkout.
BUNDLE BUILDERS THAT ACTUALLY SUBSCRIBE
Shopify subscriptions and Recharge integration
Subscription logic and bundle builders that hand off cleanly to Recharge. For Tayst Coffee we built a guided builder that captures coffee type, number of drinkers, roast and cup count, then passes the finished bundle straight into a Recharge subscription.
IN SHORT
- A bundle builder has to end in a valid subscription contract. The hard part is the handoff, not the quiz.
- For Tayst Coffee the flow captures coffee type, number of drinkers, roast and cup count, then passes the built bundle straight into Recharge.
- Recharge suits bundle logic, swaps and mature retention tooling; native Shopify Subscriptions suits simple offers with fewer moving parts.
- Swap, skip and pause journeys should be designed with the signup flow, not bolted on after churn becomes a problem.
- Every extra question in a builder costs completion, so each one has to earn its place by changing what the customer receives.
The part everyone underestimates
Build-your-own subscription flows look like a front-end problem. A few questions, a nice preview, an add-to-cart. Most of them are built that way, and most of them break at the same place.
The difficulty is the handoff. The customer has assembled something specific: this roast, that many cups, this frequency. It has to become a valid subscription contract that renews correctly, can be swapped, survives a price change and does not fall apart when one component goes out of stock.
When the builder and the subscription platform are treated as separate projects, that translation gets approximated at checkout. The customer receives something adjacent to what they chose, and you find out through support tickets in month two.
How we build one
Six stages. Stage four is the one that separates a working builder from a demo.
- 01
Model the offer
What is being sold: fixed bundles, build-your-own, tiered frequency, or a mix. This decides the data model, and getting it wrong is expensive to unwind once customers hold contracts.
- 02
Design the flow
Each question earns its place by changing what the customer receives. A builder that asks five things people cannot answer will lose more customers than the personalization gains.
- 03
Build the builder
State carried cleanly from first question to cart, with the selection visible and editable at every step, and a URL that can be shared or resumed.
- 04
Handoff to Recharge
The finished bundle becomes a subscription contract through the API rather than being approximated at checkout. The stage where most builders quietly break.
- 05
Lifecycle journeys
Swap, skip, pause, change frequency and cancel, designed as part of the build. Retention is decided here far more than in an email campaign.
- 06
Test the edges
Out-of-stock components, price changes on an active contract, failed payments and partial fulfillment. The states that appear at month four and are never in the demo.
What the Tayst builder does
A worked example
Tayst Coffee sells coffee subscriptions. The builder asks what kind of coffee you drink, how many drinkers there are in the household, which roast you prefer (light, medium or dark), and how many cups you get through, up to a hundred. It then lets the customer choose their cups.
The finished bundle is passed straight into Recharge as a subscription. Not reconstructed at checkout, not approximated with a note on the order. Handed over as the contract the customer built.
Recharge against native Shopify Subscriptions
| Recharge | Shopify Subscriptions | |
|---|---|---|
| Bundle logic | Strong | Basic |
| Swap and skip | Mature, customer-facing | Simpler |
| Retention tooling | Built in | Bring your own |
| Moving parts | Another platform to own | Stays inside Shopify |
| Cost | Platform fee plus transaction share | Lower |
| Best for | Build-your-own, complex cadence, retention focus | One product, one cadence, simplicity |
The states that appear at month four
- A component in an active bundle goes out of stock
- Prices change while contracts are live
- A payment fails and the retry schedule has to be right
- A customer wants to swap one item without rebuilding the bundle
- A customer pauses over a holiday and expects to resume where they left off
- Partial fulfillment when one item in the box is delayed
- A cancellation that should offer a pause rather than an exit
None of these appear in a demo. All of them appear in production. We design for them during the build rather than discovering them through churn.
What good subscription UX does
Earns every question
Each step changes what arrives in the box. Anything else is a default, because questions cost completion.
Makes changing easy
Swap, skip and pause are self-serve. The cheapest retention work is letting people adjust instead of cancel.
Survives the edges
Out of stock, price change, failed payment. Designed for during the build, not discovered later.
Who we have done this for
Clients from the roster whose work this page describes. Each links to what we built.
GANT
GANT came to Shopify with internal systems already in place. We migrated the store and connected those systems, including integrations with individual local stores.
SEE THE WORK →
Tayst Coffee
Tayst launched a new brand of compostable single-serve coffee pods. We built the Shopify store and a guided builder: shoppers say how they brew, how many drinkers there are, which roast they like and how many cups they need, get a recommended mix they can change, and the bundle becomes a Recharge subscription with a 15% discount. Tayst has grown about 20% month on month.
READ THE STORY →
Eat Cake Today
Eat Cake Today is a funded Malaysian startup that sells cakes from many local bakers and kitchens and delivers them the same day. We built the Shopify storefront and the back end behind it: each vendor's capacity and each cake's making time decide which dates and times a shopper is offered, and each order goes straight to the kitchen and a rider. The service now covers three to four cities.
READ THE STORY →
Trunki
Trunki, the UK kids' ride-on suitcase brand, moved from Magento to Shopify Plus with its design intact and a custom builder for personalized Trunkis. We also built a warranty system, connected their back-office systems and launched their US and German stores. UK revenue is up about 50%.
READ THE STORY →
Moonglow
Moonglow sells jewelry set with the moon as it looked on a date that matters to you. Shoppers were stuck on how it works, so we built a moon-phase calculator that shows the real moon for any date, and a builder that turns that date, an engraving and a metal into a piece of jewelry. Sales are up more than 25%.
READ THE STORY →Subscription questions
Can customers build a custom subscription bundle on Shopify?
Yes. The bundle is assembled in the storefront and passed to the subscription platform as a single contract, which is how the Tayst coffee builder works.
Recharge or Shopify Subscriptions?
Recharge when you need bundle logic, swaps and mature retention tooling; native Shopify Subscriptions when the offer is simple and you want fewer moving parts.
Should we use Recharge or native Shopify Subscriptions?
Recharge when you need bundle logic, swaps, complex frequency rules or mature retention tooling. Native Shopify Subscriptions when the offer is simple (one product, one cadence) and you would rather have fewer moving parts. The decision is about the offer, not the technology.
Why do subscription bundle builders fail?
Because the builder and the subscription platform were treated as separate projects. The quiz works, the cart works, and then the selection cannot be expressed as a valid subscription contract, so it gets approximated at checkout and the customer receives something they did not choose.
How many questions should a bundle builder ask?
As few as change the outcome. Each question costs completion, so anything that does not alter what arrives in the box should be a default, not a step.
Related
ERP & Internal Systems
Shopify connected to the systems a business already runs on, down to integrations with individual local stores.
Custom Apps & Back Ends
When the logic does not fit an app: vendor capacity, delivery scheduling, made-to-order queues.
Product Configurators
Build-your-own product flows, from Trunki custom designs to date-driven personalization at Moonglow.
Build-your-own flows for non-subscription products are product configurators. Moving from WooCommerce with existing subscriptions? That has its own considerations.
NEXT STEP
Scope a custom build
Vendor capacity engines, bundle builders and configurators are the work we are asked for most. Tell us the rule set.
