Subscription Box Hosting

Subscription box hosting for the same date every month.

A box business is not recurring billing spread across the month. Everyone renews on the same day, everyone ships in the same week, and the cut-off decides both.

One renewal dateCut-off decides the pick listSkips honoured in time
Cycle billingCut-off handlingSkip and swapDaily backupsFree SSL24/7 support
Built for the monthly cycle

One date decides the month.

Everything about a box business is arranged around a cut-off, and every failure is a discrepancy between what was billed and what was packed.

Renewals as one run, not a trickle

A shared billing date turns the month's revenue into a single batch. That run gets its own limits, because a timeout half way through means some subscribers are charged and others are not.

One batch

A cut-off that is honoured exactly

Skips, swaps and address changes made before the deadline must be reflected in what ships, and changes after it must not be. That boundary is a scheduled moment, not an approximate one.

Hard boundary

A pick list that matches what was billed

The warehouse export is generated from the same state the billing run used. Generating it separately is how somebody pays for a box they did not receive.

Signup surges before the cut-off

Marketing pushes hardest in the days before the deadline, so new subscribers arrive in a concentrated burst rather than evenly across the month.

Failed payments handled before shipping

A card that declines needs retrying before the box is packed, not after. Dunning runs inside the window rather than trailing it.

The cycle

Billed and packed must agree.

Every expensive mistake in a box business is a mismatch: a skipped subscriber who received a box, a charged subscriber who did not, or an address change applied a day late.

  • Renewal run batched with its own limits
  • Cut-off applied as a scheduled boundary
  • Pick list generated from the billed state
  • Dunning completed before packing
Subscribers
Active
6,400
Cut-off
Applied
exactly
Pick list
Matches billing
yes
Renewal run
This cycle
running
Renewal day

Six thousand charges in one window.

The load that matters arrives once a month on a date you chose, which makes it the easiest spike to prepare for and the most damaging to get wrong.

Batched
monthly renewal run
Exact
cut-off boundary
Matched
pick list to billing
MagicWP145 ms
Typical shared host1560 ms
Untuned VPS590 ms

Illustrative comparison of a subscriber account page during a renewal run. Your numbers depend on subscriber count and plan complexity.

Configuration

What we change for subscription boxes

A shared billing date and a hard cut-off drive all of it, and both are decisions the business already made.

SettingWhat we doWhy
Renewal batchingWhole cycle run with limits sized for the subscriber baseA shared billing date means the month's charges happen together, so a run that times out leaves part of the base billed and part not.
Cut-off enforcementApplied as a precise scheduled boundaryA skip requested before the deadline that still ships, or an address change applied after it, both produce a wrong box and a refund.
Pick list generationDerived from the same state the billing run usedGenerating the warehouse export independently lets it diverge from what was charged, which is how somebody pays for a box nobody packed.
Dunning windowRetries completed before packing beginsA declined card discovered after the box has shipped is an unrecoverable cost rather than a payment to chase.
Pre-cut-off signup capacityPlanned for a concentrated burstAcquisition is pushed hardest in the days before the deadline, so new subscribers arrive together rather than spread across the month.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Is this different from ordinary recurring billing?
Yes. Ordinary subscriptions renew on each customer's own anniversary, spreading load across the month. A box business renews everybody on one date, which makes it a single batch.
What happens if a subscriber skips after the cut-off?
The box ships, because the cut-off is a hard boundary. Treating it loosely is how a skipped subscriber receives a box and asks for a refund on something already dispatched.
How do I make sure the warehouse packs what I billed?
By generating the pick list from the same state the billing run used. Produced independently the two diverge, and somebody pays for a box that was never packed.
When should failed payments be retried?
Inside the window, before packing. A decline found after the box has shipped is a cost you absorb rather than a payment you can still collect.

Bill and pack the same list.

Move the box business across — migration is free, subscribers included.