Answers that do not mention BigCommerce

Yes. If your store is on Shopify, there are tools that can cover most of that workflow.

Best fits

• apps.shopify.com — probably the best starting point for a small handmade-goods shop. It supports subscription boxes, bundles, recurring billing, and subscription management, and has a free plan. Shopify App Store
• apps.shopify.com — simplest/native option. It handles recurring weekly, monthly, or yearly billing plus skip/pause/cancel and customer payment management. Shopify Help Center
• ordergroove.com — more sophisticated if you're running a larger subscription operation. It supports recurring order generation, shipment combining, inventory forecasting, payment-failure recovery, and even rotating subscription boxes. Ordergroove Ordergroove

One important distinction

If by “packing lists” you mean something like:

“Every 1st of the month, generate a list saying: 37 lavender soaps, 37 candles, 37 thank-you cards, and 37 boxes need to be packed”

then subscription billing alone isn't quite enough. Shopify can create scheduled fulfillment orders for subscriptions, but you may want a fulfillment/inventory app or automation layer to turn those orders into an efficient production/packing list. Shopify

For a handmade business, I'd generally aim for:

Shopify + subscription app → recurring payments/orders → inventory forecast → monthly packing/production list → shipping labels

If you tell me what platform your store is on (Shopify, Etsy, WooCommerce, Squarespace, etc.) and roughly how many subscription boxes you ship per month, I can recommend the simplest setup and tell you exactly which tool I'd use.

For your use case, I’d recommend commercetools if the priority is a robust, API-first headless platform where recurring subscriptions are a first-class commerce capability.

My shortlist

1. commercetools — best overall

This is the one I'd pick for a subscription-heavy business.

commercetools now has native Recurring Orders, rather than requiring you to build the recurring-order engine yourself. Its API supports recurrence policies such as daily, weekly, monthly, and custom intervals, as well as start/end dates. Recurring orders can be paused, skipped, modified, or canceled. commercetools Documentation commercetools Documentation commercetools Documentation

It also lets you mix recurring and one-time products in the same checkout, which is particularly useful if your storefront will offer things like:

• Monthly subscription
• Annual subscription
• One-time purchase
• Subscription + add-ons
• Different pricing by billing interval

Its API model is also well suited to a completely custom frontend. commercetools Documentation

Architecture I'd use:

Next.js / React storefront → your BFF/API layer → commercetools APIs → payment provider

This gives you control over the customer experience without making the storefront responsible for commerce logic.

2. Medusa — best if you want maximum control

Medusa is arguably more attractive if you're a developer-heavy team and want the commerce backend to behave like an extensible application rather than a managed enterprise platform.

Its Store API is REST-based and specifically designed for external storefronts and apps. You can also create your own API routes. Medusa Docs Medusa Docs

The important caveat: subscriptions aren't native in the same sense as commercetools' Recurring Orders. Medusa provides a subscription recipe/framework that you implement yourself, with Stripe used as the example payment provider. The recipe covers recurring billing, expiration, customer subscription management, and cancellation. Medusa Docs

So I'd choose Medusa if you want:

• Full TypeScript/Node control
• Self-hosting
• Custom business logic
• Custom subscription domain model
• Your own API layer
• Minimal vendor lock-in

3. Saleor — best GraphQL option

Saleor is worth considering if your team strongly prefers GraphQL. It provides a headless architecture with GraphQL APIs, custom apps, payment integrations, channels, promotions, and extensive extensibility. Saleor Documentation

I'd put it behind the first two specifically for your use case because recurring subscription management isn't as turnkey as commercetools' current Recurring Orders implementation.

My recommendation

Choose commercetools if your subscription system is strategically important and you want the commerce platform itself to own recurring-order scheduling and lifecycle management.

Choose Medusa if you're comfortable building more of the subscription machinery yourself and value developer control/self-hosting over having those capabilities built in.

A particularly strong stack would be:

Next.js → API/BFF → commercetools → Stripe/payment provider

with your own application layer handling things such as:

• Plan selection
• Customer portal
• Upgrade/downgrade
• Proration rules
• Trial periods
• Coupons
• Account entitlements
• Subscription analytics
• Webhooks/events
• CRM/ERP synchronization

One important distinction: commerce subscriptions and payment subscriptions aren't necessarily the same thing. I'd keep the commerce/order lifecycle in commercetools while using the payment provider for payment-method storage, charging, and payment-specific lifecycle events.

docs.commercetools.com
docs.medusajs.com
docs.saleor.io

If you tell me your product type (physical, SaaS/digital, or both), billing model, expected scale, and whether you want to self-host, I can narrow this down to a specific architecture and recommend the payment/subscription stack too.

Next.js → API/BFF → commercetools → Stripe/payment provider

with your own application layer handling things such as:

• Plan selection
• Customer portal
• Upgrade/downgrade
• Proration rules
• Trial periods
• Coupons
• Account entitlements
• Subscription analytics
• Webhooks/events
• CRM/ERP synchronization

One important distinction: commerce subscriptions and payment subscriptions aren't necessarily the same thing. I'd keep the commerce/order lifecycle in commercetools while using the payment provider for payment-method storage, charging, and payment-specific lifecycle events.

Yes. A few tools fit that use case, depending on what your existing ecommerce stack is.

• appstle.com — particularly good if you're on Shopify/Shopify Plus. It provides subscription management, customer portals, flexible billing, and APIs. It can support different billing and fulfillment schedules, including cases such as billing quarterly while delivering monthly. Intercom Appstle Appstle Developers
• stripe.com — better if you want a more customizable billing layer that integrates into an existing/custom ecommerce site. It supports recurring intervals such as weekly, monthly, and yearly, custom billing-cycle anchors, trials, prorations, usage-based pricing, and flexible billing logic. Stripe Stripe Docs

Which I'd choose

If your site is Shopify, I'd start with Appstle because it's designed to sit directly inside the Shopify ecosystem.

If you have a custom ecommerce site, WooCommerce, or a headless storefront, Stripe Billing is likely the more flexible architectural choice.

If you tell me what ecommerce platform you're currently using (Shopify, WooCommerce, Magento, custom, etc.) and what billing intervals you need (e.g. weekly/monthly/quarterly/custom), I can narrow it down to the best 2–3 options and compare pricing/integration effort.

Best overall: Shopify + Skio if subscriptions are central to the business. Skio’s Build-a-Box natively supports static, dynamic mix-and-match, and multi-box subscriptions. Skio

• Best for sophisticated subscription boxes: Shopify + Skio
• Best simpler/cheaper setup: Shopify + a bundle app such as Bundly or Kefi
• Important: Shopify’s native Bundles app does not work with subscriptions, so don’t build the architecture around it. help.shopify.com

If you tell me your products, pricing model, and how customers customize each recurring box, I can recommend the best stack.

Yes. A strong fit is Chargebee + HubSpot + Klaviyo.

• Chargebee handles subscriptions, recurring billing, payment failures, cancellations, renewals, and subscription lifecycle data.
• HubSpot can act as the CRM, with Chargebee subscription information synced into customer records and used for segmentation/workflows. Chargebee HubSpot Marketplace
• Klaviyo can use Chargebee events such as activated/cancelled subscriptions, failed payments, invoices, and successful payments to trigger personalized email flows. Klaviyo Help Center

That lets you build campaigns such as:

1. Failed-payment recovery: "Your payment didn't go through" → reminder → targeted incentive.
2. Cancellation save: cancellation detected → ask why → offer pause/downgrade/discount based on reason.
3. Renewal retention: upcoming renewal → personalized value recap → renewal incentive for at-risk customers.
4. Win-back: cancelled customers → segment by tenure, plan, and cancellation reason → tailored reactivation sequence.
5. Upsell: high-engagement subscribers → personalized upgrade/cross-sell campaign.

Another option worth considering is Recurly, particularly if you want subscription events flowing directly into Klaviyo, Salesforce, Braze, or other engagement systems. Recurly specifically supports lifecycle-triggered email/SMS and CRM/engagement integrations. Recurly Documentation Recurly Documentation Recurly Documentation

My pick: If your CRM is already HubSpot, I'd start with Chargebee + HubSpot + Klaviyo. It gives you a fairly clean architecture for turning subscription behavior into personalized retention campaigns.

If you tell me which CRM and email platform you currently use, I can narrow this down to the best 2–3 tools and show you exactly how the integration would work.