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 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.
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.
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.
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
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.
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.
| Setting | What we do | Why |
|---|---|---|
| Renewal batching | Whole cycle run with limits sized for the subscriber base | A 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 enforcement | Applied as a precise scheduled boundary | A 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 generation | Derived from the same state the billing run used | Generating the warehouse export independently lets it diverge from what was charged, which is how somebody pays for a box nobody packed. |
| Dunning window | Retries completed before packing begins | A declined card discovered after the box has shipped is an unrecoverable cost rather than a payment to chase. |
| Pre-cut-off signup capacity | Planned for a concentrated burst | Acquisition is pushed hardest in the days before the deadline, so new subscribers arrive together rather than spread across the month. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Is this different from ordinary recurring billing?
What happens if a subscriber skips after the cut-off?
How do I make sure the warehouse packs what I billed?
When should failed payments be retried?
Bill and pack the same list.
Move the box business across - migration is free, subscribers included.