$ crate features --all
not a billing tool — the whole box, handled.
Seven parts of one system: schedules, dunning, reserved stock, a portal, reports, integrations and the security under them. Each has its own screen below.
schedules
a renewal date that moves when the subscriber does.
Set a cadence per product: every two weeks, monthly, every other month. Subscribers skip, swap or pause from their own account, and the next charge and the stock reservation shift with them.
in your week
The “can you push my box back” email stops arriving. Nobody on your team edits a date by hand.
$ crate cadence set --every month --allow skip,swap,pausedunning
a failed card gets a plan, then a polite email.
Retries land on the days cards usually clear. The update-your-card email is written in your voice, and a subscription pauses only when the sequence runs out, releasing its stock back to the shelf.
in your week
Failed payments become one list that shrinks on its own, instead of a Monday spreadsheet.
$ crate dunning retry --days 1,3,6 --email update-cardinventory
stock is held before the box is due.
Every upcoming renewal reserves units against live inventory. When demand outruns the shelf, Crate holds the order and names the SKU and the gap, rather than selling what you don’t have.
in your week
You reorder on Tuesday because the screen said matcha was 22 short, not on Friday because a box couldn’t be packed.
$ crate reserve --window 7d --hold-shortportal
a portal that wears your name.
Subscribers manage their plan on your domain, in your colors: skip, swap, update a card, read order history, follow a box from reserved to delivered.
in your week
The tickets that remain are the ones that need a person.
$ crate portal publish --domain manage.yourbrand.comanalytics
churn, by cohort, by month.
See which signup month holds and which one leaks. Cohort retention sits beside renewals and recovered payments, so a fix shows up on the same screen that found the problem.
in your week
Change a retry rule on Monday; read what it did to the August cohort by the end of the month.
$ crate report cohorts --by signup-monthintegrations
renewal events go where your team already looks.
Seven integrations, each one narrow and specific. Crate sends the event; the other tool does its own job with it.
security + reliability
who changed what, and when, is always on the record.
Card details never touch your servers or ours in the clear; they live with the payment processor. Inside the workspace, every edit to a plan, a retry rule or a subscriber leaves a line in the audit log.
in your week
When a subscriber asks why a box skipped, the answer is one search away.
// the fine print, plainly
what holds the rest up.
security
- Card data stays with the payment processor
- Two-step sign-in for every teammate
- Role-based access: owner, ops, support
- Audit log on every plan and rule change
reliability
- Charges are idempotent: a retry never double-bills
- Inventory re-synced continuously, not nightly
- Webhooks retried with backoff if your endpoint is down
- Failed jobs surface in the dashboard, not a log file
your data
- Export subscribers and orders as CSV any day
- Import from your current tool as it stands
- Subscriber requests to delete are honored from the portal
- Plan limits printed on the pricing page
$ crate plans
seven parts, one annual price.
Every feature on this page is in the plans. The difference between them is subscriber count and how many stockrooms you run, from $199 a year.