Subscription box billing.
The part nobody puts on the unboxing video.

Pick your billing model before you pick your software.

Every subscription box runs on two calendars — a billing cycle (when the card is charged) and a ship cycle (when the box goes out). The billing model is just the rule that connects them, and everything downstream — dunning, skips, proration, customer emails — inherits from that rule.

• Monthly recurring. The default: one charge, one box, every month. Simplest to explain, but it maximizes the number of renewal charges — and every renewal charge is a fresh chance to fail.
• Quarterly (or other multi-month) recurring. One charge covers a quarter of boxes, or one bigger seasonal box. Fewer renewal events means fewer decline opportunities, at the cost of a bigger sticker price per charge.
• Prepay with renewal. The customer pays up front for a fixed term — 3, 6, or 12 boxes — and the plan renews at the end of the term (into another prepay term, or rolling monthly). Great for cash flow and gifting; the trap is the renewal charge at the end, which is large, often months after the last time the customer thought about you, and must be clearly disclosed up front (see section 04).
• Bill-on-cycle. Renewals fire on a fixed date — the signup anniversary, or one shared date like "the 1st" for the whole subscriber base. Predictable revenue, simple dunning math, and a single cutoff to align fulfillment against. The trade-off: the charge can land weeks before the box does, which generates "I paid, where is it?" tickets.
• Bill-on-ship. The charge fires when the box actually ships. The charge and the delivery line up, which customers intuitively understand — but now a failed payment doesn't just miss a renewal, it blocks a shipment that's already picked and packed, and your dunning window compresses to however long the box can sit on the dock.

There is no winner in that table — but there is a rule: your billing calendar must resolve before your shipping calendar acts. Charges, retries, and skips all need to be settled by the ship cutoff. Hold that rule and most of section 02 gets easier.

The operational seams where boxes go wrong.

These are the five situations that separate a billing setup that survives contact with real subscribers from one that generates support tickets and chargebacks. None of them are exotic — they happen every single cycle.

Proration and mid-cycle changes

A subscriber upgrades from the standard box to the premium box on day 11 of a 30-day cycle. Do you charge the difference now, prorated? Charge the full new price at the next renewal? Ship the new tier this cycle or next? There's no universally right answer — but you need one answer, applied consistently, that your billing platform can actually execute and your help docs can state in one sentence. Ad-hoc proration handled by manual refunds is how billing records and fulfillment records drift apart.

Skips and pauses

A skip ("no July box") and a pause ("stop until I say otherwise") are retention features — a subscriber who can skip a month often doesn't cancel. But each one is a billing and a fulfillment instruction: the renewal charge must not fire, and the box must not ship, and both must resume correctly afterward. The classic failure is the skip that stops the box but not the charge — which turns a retention feature into a refund and, sometimes, a chargeback. Skips also need a cutoff of their own: a skip requested after the billing run has fired is next month's skip, and the interface should say so.

Address changes mid-cycle

Subscribers move, and they update their address the day they think of it — which is rarely the day you ship. Your system needs one unambiguous rule for which address a given box uses: typically, the address on file at the ship cutoff. If the change lands after labels are printed, the box goes to the old address and the subscriber should be told that at the moment they save the change, not discover it from a tracking page.

Failed payments before the ship cutoff

This is the seam that costs real money. A renewal fails on the 1st; boxes ship on the 10th. Does the box ship anyway? If it ships and the payment is never recovered, you've donated product and postage. If it silently doesn't ship, a subscriber whose card simply expired loses a box they wanted and you lose them. The workable pattern is a defined window: failed renewals go into retries and dunning immediately, anything recovered by the cutoff ships on time, and anything still unpaid at the cutoff is held — with the subscriber clearly told how to fix payment and what happens to their box if they do.

Dunning windows aligned to ship dates

Dunning — the sequence of retries and "please update your card" messages after a failed charge — is usually configured in the abstract: retry after 3 days, again after 5, and so on. For a subscription box, an abstract schedule is wrong by construction. The whole sequence has to fit between the billing date and the ship cutoff, which is exactly why bill-on-cycle operators bill several days to a couple of weeks before shipping: that gap is the dunning window. If you bill on the 1st and ship on the 10th, you get roughly nine days of retries and emails; design the sequence to that number, not to a generic template.

Decline recovery: the churn your subscribers didn't choose.

Subscription churn comes in two kinds. Voluntary churn is a decision — the subscriber cancels. Involuntary churn is an accident — the renewal charge fails (expired card, reissued card, insufficient funds, a bank's fraud model getting twitchy) and the subscription lapses even though the subscriber never wanted to leave. For a box business, involuntary churn is uniquely painful because the person was, by definition, still willing to pay.

We're deliberately not quoting industry-average recovery percentages here — the numbers floating around content marketing are mostly unsourced and vary wildly by vertical, price point, and card mix. Measure your own: failed renewals, recovered renewals, and time-to-recovery are three numbers your billing platform should hand you. What is general and reliable is the toolkit:

• Scheduled retries. Many declines are temporary — insufficient funds on the 1st can clear on the 3rd. A spaced retry schedule (fitted to your ship cutoff, per section 02) recovers a meaningful share of soft declines with zero customer effort. Retry the soft declines; don't hammer hard declines like "stolen card," which only irritates issuers.
• Card account updaters. The card networks operate account-updater services — Visa Account Updater and Mastercard's Automatic Billing Updater — that let participating billers receive updated card numbers and expiry dates when a stored card is reissued. Ask whether your gateway or platform enrolls you; for a business built on stored cards, this quietly prevents a whole category of failures. Network tokens serve a similar keep-the-credential-fresh role where supported.
• Grace periods. Rather than canceling on the first failure, keep the subscription in a "past due" state for a defined window while retries and dunning run. The subscriber keeps their slot; you keep the relationship; the state is honest in your reporting.
• Dunning messages that respect the reader. A failed renewal email should say what happened, what happens to their box, and give a one-tap way to update the card. This is also where a clear pause option earns its keep — someone dodging a charge this month may take a skip instead of a cancellation.
• Processing redundancy. Serious recurring-billing operations run more than one gateway or merchant account for redundancy — if a processor has an outage or starts declining unusually, renewals can fail over to a healthy route instead of piling into the dunning queue. Platforms with intelligent routing use decline and approval data per card BIN for approval-rate optimization: sending each renewal to the route where it's statistically most likely to be approved.

The compliance floor: disclose clearly, cancel easily.

Subscription boxes are negative-option businesses — the customer is charged repeatedly unless they act — and that structure is specifically regulated. The floor, stated generally:

• Clear disclosure before the charge. Under ROSCA — the Restore Online Shoppers' Confidence Act, the U.S. federal law covering online negative-option sales — you must clearly and conspicuously disclose all material terms of the deal before obtaining billing information: that it renews, how often, at what price, and (critically for prepay plans) what the renewal charge will be.¹
• Express informed consent. ROSCA also requires the consumer's express informed consent before the charge — no pre-checked boxes doing the heavy lifting, no burying the renewal in the fine print.¹
• A simple way to stop the charges. The same statute requires "simple mechanisms" for a consumer to stop recurring charges. If a subscriber signed up online in two minutes, cancellation should not require a phone call placed during business hours and a retention gauntlet.¹

Where the FTC's "click-to-cancel" rule stands (checked on ftc.gov, September 3, 2026): the FTC finalized an amended Negative Option Rule in October 2024 that would have imposed detailed click-to-cancel requirements, but the Eighth Circuit vacated it on July 8, 2025, days before full compliance was due — so that specific rule never took effect. In 2026 the FTC restarted the rulemaking: it issued an advance notice of proposed rulemaking on negative-option marketing and took public comment through April 13, 2026.^2,3 Translation for operators: the detailed 2024 rule is off the books for now, a successor is in the works — and none of that repealed ROSCA, Section 5 of the FTC Act, or the state auto-renewal laws (California's being the best known) that impose their own disclosure and easy-cancellation requirements. The FTC has continued bringing negative-option cases under the existing statutes.

What to demand from a billing platform.

Every platform demo shows you the happy path: signup, charge, ship. Sections 01–04 are the questions that actually sort platforms. Before you commit, make the vendor show you — in the product, not the deck:

1. Your billing model, natively. Monthly, quarterly, prepay-with-renewal, anniversary vs. fixed-date billing — configured, not "handled with a workaround."
2. Ship-aware dunning. Retry schedules and dunning sequences you can fit to your billing-to-cutoff window, with a defined hold state for boxes whose payment hasn't recovered.
3. Self-service skips, pauses, and cancellation. Subscribers manage their own subscription — skip a month, pause, change address, update the card, cancel — without emailing support. That's retention tooling and your compliance posture in one feature.
4. Decline recovery built in. Automatic retries, account-updater/network-token support through your gateway, grace periods, and dunning emails — with reporting on failed vs. recovered renewals so you can see your own numbers.
5. Processor flexibility and redundancy. Your own merchant account rather than a forced processor, support for more than one gateway for failover, and visibility into approval rates and decline reasons.
6. One source of truth for billing and fulfillment. Charges, skips, addresses, and shipments in one system (or a real-time sync), so the box list for a given ship date is generated from settled billing state — not exported and reconciled by hand.
7. A checkout you control. The signup page is where disclosure, consent, and conversion all happen at once. You want control over its layout and copy — and the ability to run it on your own domain.
8. Honest reporting. Renewal revenue vs. new revenue, refunds, approval rates, and decline reasons broken out — not one blended "sales" number.

Choosing the payments layer underneath all this is its own decision — we've written a separate guide to choosing a subscription payment gateway that covers the gateway-specific questions.

Where Admoji fits for box operators.

Admoji is a CRM-plus-checkout platform, and subscriptions are one of its named verticals.⁴ Against the checklist above, here's what it publishes:

• A custom checkout on your own domain. A Shopify-style checkout running at your own subdomain — like checkout.yourdomain.com — that syncs products, orders, and customers with your Shopify store in real time. Your signup page, your layout, your disclosure copy.⁴
• Recurring billing with recovery logic in the flow. The checkout is built with smart routing and retry logic baked in, and the platform's billing reports break out every recurring charge and every refund. Its conversion reporting surfaces true approval rates and decline reasons — the numbers section 03 told you to measure.⁴
• Approval-rate optimization. Admoji ships a native DataPunch BIN-routing integration for routing transactions across your merchant accounts by real-time BIN intelligence; Admoji publishes a +19.6% average approval lift figure for it (admoji.com, observed September 3, 2026).⁴
• Your own merchant account. Stripe, Authorize.net, NMI, or any processor you want — with redundancy across the accounts you run, rather than a single forced processor.⁴
• A full CRM underneath. Customer data, order history, and funnel reporting live in your account — Admoji states plainly that you own your customer list — and the platform is PCI-DSS compliant and SOC 2 aligned.⁴

Pricing is published and simple: $79/mo + 0.35% of volume on the Launch plan, no long-term contracts, with a 14-day free trial and no credit card required.⁴ If you're comparing subscription-billing platforms head to head, see how Admoji stacks up against Sticky.io.

Common questions.