Skip to content

Plan & billing page

The admin page where a shop owner manages their Badger Commerce plan (/admin/settings/billing), its confirmation step for plan changes, and the billing banner across admin. What it does is in Plan & billing. This page records the design decisions.

Decisions

  • One page, in the order an owner asks. What am I on and what will I pay (the plan card with the next invoice), what do I use (meters), what could I move to (plan cards), extras (add-ons, extra locations), then leaving (cancel) at the bottom. Launching the shop sits second while the shop is in demo mode, because it's the next thing to do.
  • "+ VAT" beside every price. Plans are priced without VAT, as on the pricing page, so every amount says so. The next invoice is the exception: it's what will be charged, so it shows the total with the VAT in it named.
  • A confirmation page, not a dialog, for plan changes. A plan change has consequences to read (what's charged now, when a downgrade starts, a founding price lost, add-ons that don't fit, limits that are over), and Stripe has to be asked for the amount. A page with the preview is clearer than a dialog, works without script and can be linked to. Smaller changes (add-ons, cancel, start paying now, launch) are POST forms with the data-bx-confirm dialog.
  • Over a limit is shown before you click. Each cheaper plan card already lists what the shop's usage is over, from the last count, so a refusal is never a surprise. The confirmation counts again; the card only warns.
  • The same over-limit lines as the banner. The meters reuse the admin.plan-limits.* messages, so an owner reads one wording for one problem wherever it appears.
  • The monthly customer limit is advice. It's marked "warning only" and nearing it shows a suggestion to compare plans, never a red state that implies something is blocked.
  • One billing banner at a time, the most urgent: ended, payment failed, cancelling, trial ending. Trial ending starts seven days out as a note and turns into a warning on the last day.
  • Owners' words for refusals. Stripe and the billing service refuse with English meant for staff; the owner gets their own message (admin.billing.error.*), so nothing technical reaches the page.
  • Read-only for finance. Finance staff see the page and can open the card and invoices, with no change buttons, rather than not seeing it at all.
  • bx- components only. Cards, bx-kv, bx-meter, bx-pricelist, callouts and badges; the plan cards are a small bx-plans / bx-plan addition in admin-ui.css. No inline styles except the meter widths, which come from data.

Rules a later change must keep

  • No Stripe ids, card details or owner details on the page, in the banner or in the MCP answer.
  • Every owner-facing string is a message key (admin.billing.*, admin.setup.billing.*, admin.setup.launch.*).
  • Changes go through OwnerBillingService, which records each one as an owner.* billing event, so System sees who in the shop did what.
  • The plans offered are the public ones of the shop's family plus self-serve Enterprise; sales-led plans are never offered for self-serve.