Carizmo — Subscription System
This is the partner-facing reference for how Carizmo’s subscription system works end to end — the business model, the state machines behind it, and the day-to-day admin experience. It mirrors the internal engineering docs but written for a non-engineering audience, with the flows drawn out rather than described in prose.
What a subscription actually is
One subscription = one vehicle, one fixed 30-day period, one flat price. There’s no proration — a period runs for exactly 30 days from whichever date it starts, at the plan’s full monthly rate. Renewing doesn’t extend that period; it creates a brand new one, linked back to the period it renews.
The three systems that have to stay in sync
Everything downstream — the wash schedule, the payment reminders, the admin
dashboard — reads from the same two fields on every subscription: is this
period in force (status), and has it been paid for (paymentStatus).
They’re independent on purpose — a subscription is routinely “in force but
not yet paid” during its grace period, which is normal, not an error.
Where to go next
- Customer Journey — the actual path a customer takes, from signing up to renewing.
- Subscription Lifecycle — the two state machines, drawn out.
- Billing & Grace Period — how price and the payment deadline are calculated.
- Renewal Flows — the three different ways a subscription renews.
- Wash Job Generation — how preferred days turn into a real schedule, and a known rough edge.
- Admin Experience — how the admin dashboard represents all of this, and the choices made to reduce confusion.
- Scheduled Tasks — what runs automatically, and when.
- Known Gaps & Roadmap — open questions, honestly listed.