Billing & Grace Period

Pricing model

Every period is priced the same way: full monthly base price, any discount applied, then VAT — flat, regardless of how many washes actually get scheduled inside the 30-day window. There’s no proration.

Price (top row) and washes granted (bottom row) are calculated independently. The plan’s nominal wash count (e.g. “12 washes/month”) is a target, not a hard cap in either direction: a longer cycle (a 5-week span on a weekly-ish schedule) can grant more washes than nominal, a shorter one can grant fewer — every preferred-day occurrence that actually falls in the period gets a wash, full stop. Price never changes either way — see Known Gaps for the one open question this still leaves (fewer washes than nominal, same price).

Grace period — why it’s measured in days, not washes

A grace period is a payment-collection clock, not a usage clock — it answers “how long do we let someone use the service before they’ve paid,” which is inherently about elapsed time. A wash-count-based grace period would actually reward slow usage: a customer who skips washes would never trip it. Every comparable business model (rent, gym dues, subscription dunning) ties this to calendar time for the same reason.

A customized grace period (an admin extending it for a specific customer) carries forward automatically on every future auto-renewal — it isn’t a one-time override.

Turning overdue into a pause is now a deliberate admin action, not an automatic one. Going overdue no longer pauses service by itself — the subscription keeps running and the customer keeps getting washed. The admin gets a notification listing everyone who just went overdue and decides, subscription by subscription, whether pausing makes sense (a one-click action from the Payments screen). This exists so a customer who’s a day late paying doesn’t lose service before anyone’s actually looked at their situation.