Build a subscription box builder: pick items, size and frequency, see the total
A build-your-own box turns a product list into a small act of choosing: three coffees out of eight, a size, how often. Done well, it sells better than a fixed bundle because customers feel the box is theirs. Anticode can build a subscription box builder with a live total, like its Ember & Oak coffee template, and then hand the customer to a payment link or send their choice to you as an enquiry. It doesn't run the subscription billing itself.
The choices, in order
Build-your-own flows work best as a few short steps with the running total always visible:
- Size. How many items or how much ("3 bags", "6 bars", "a large box"). Choosing size first sets the number of slots to fill.
- Contents. Pick items to fill the slots, with a clear count ("2 of 3 chosen"). Show what each item is like in a line, with filters if the range is large. Allow the same item twice if that makes sense for the product.
- Frequency. Weekly, fortnightly, monthly. Show the cost per delivery and, if it helps, per month.
- Extras. One or two add-ons, not a second shop.
- Summary. Everything chosen, the total, and the next step.
Pricing rules to settle first
The live total is only as good as the rules behind it. Decide them before you describe the app:
- Flat price per size, whatever's inside. Simple to explain and to take payment for.
- Price per item, with premium items costing more. Fairer, but means many possible totals.
- Frequency discount, such as a lower price per delivery for weekly.
- Delivery: included, or a fixed charge per box. Remember the total in the app is an estimate unless your checkout charges exactly the same.
The pricing rule decides how you take payment, below. A flat price per size and frequency maps cleanly to a plan list at your payment provider; per-item pricing usually doesn't.
Starting from Ember & Oak
Anticode's template gallery includes Ember & Oak Roasters, a coffee subscription builder in a warm editorial style. Using a template copies it into your project with no model call and nothing off your limits. Then reshape it with change requests: your products, sizes and frequencies, your colours, your copy. That's often quicker than describing a builder from nothing, even if you don't sell coffee.
To build from a description instead: "A build-your-own snack box. Sizes: 6, 12 or 20 snacks, flat price each. Choose snacks from 18, each with a dietary tag, filters for vegan and gluten-free, and the same snack allowed twice. Frequency: fortnightly or monthly, monthly 10% cheaper per box. A sticky summary with the count and total. Then: a Subscribe button going to my payment link, or a Send my box button that emails me the choice."
Getting from choice to payment
An Anticode app can't take a payment or create a subscription itself; payments on sites are made through payment links from your own provider, such as Stripe Payment Links, PayPal, Gumroad, Lemon Squeezy, Shopify or Whop. Two patterns work:
| Pattern | How it works | Suits |
|---|---|---|
| Payment link | Your account has one payment link, used by every buy button. Point it at a page at your provider that lists each size and frequency (6 plans for 3 sizes and 2 frequencies), and the customer picks the one they built. If your provider supports recurring checkout, it handles the subscription. | Flat price per size |
| Enquiry first | The app sends the customer's name, email and full box contents to you through Anticode's form pipeline, by email and in your dashboard. You confirm and send an invoice or a link. | Per-item pricing, small volumes, a personal touch |
With a payment link, the box contents aren't passed to the checkout automatically. Ask the customer to send the contents too (an enquiry alongside the payment), or check whether your provider's checkout can collect a note. Test the whole route with a real link before launch.
What it doesn't do
- No subscription management. Pausing, skipping a delivery or changing items happens in your payment provider or by email, not in the app.
- No customer accounts. Customers can't log in to see their box; the builder only remembers a choice in their own browser.
- No stock levels. It can't know an item has sold out unless you edit it. If the range changes often, ask whether the products can be a CMS collection you edit in the dashboard, which the app reads but can't change.
- No shipping or tax calculation beyond the simple rules you give it.
For one product with options rather than a box of many, see the product configurator. The full selling side is covered in selling a subscription on your website.
Questions people ask
Can a subscription box builder built with Anticode charge customers monthly?
Not by itself. Point its Subscribe button, through your payment link, at a recurring checkout from your payment provider, which handles the billing.
How do I receive the box contents?
Send them as an enquiry. It needs the customer's name and email, and the contents arrive in the message.
Can I change products without rebuilding?
Ask for a change in words, or use a CMS collection for products you edit yourself.