Organisation Subscription · Stripe

Context

EzOM used to charge a flat monthly fee from each organisation's wallet (LEGACY). The new model sells plans with feature sets and limits on users and warehouses, paid by card through Stripe.

Billing has a lot of states that look alike but mean different things. A payment Stripe has accepted isn't the same as a plan EzOM has applied. A downgrade shouldn't cut access mid-period. A $0 trial invoice marked paid shouldn't flip a trial to ACTIVE. If any of these get mixed up, a customer gets charged twice or loses features they paid for.

1. 01Built the plan picker and review screen: current → target plan, effective date, amount due now, credit, tax, and the next renewal amount.
2. 02Implemented change timing: upgrades and monthly → annual apply immediately; downgrades and annual → monthly are scheduled for period end; a mixed change runs in two phases.
3. 03Added 14-day trials for new BASIC/STANDARD signups, Buy Now to skip or end a trial, and resuming the confirmation after the user adds a card.
4. 04Checked usage against the target plan's limits (users, warehouses) and blocked confirmation with a clear ‘reduce by N’ message.
5. 05Moved feature access to plan entitlements: PAST_DUE keeps the plan, while UNPAID, INCOMPLETE, EXPIRED, and CANCELED fall back to FREE.
6. 06Used our AI requirement workflow to write the as-is spec of the whole feature for BA/PO sign-off: 22 functional requirements, 71 acceptance criteria, and a list of open questions.