Plans, Usage and Billing
A plan belongs to an organization, not to a site. One allowance covers every site inside it, which is why the usage screen totals them together. That is also where it lives: open the organization, then Billing → Subscriptions (the plan and what it allows), Usage (what this month used), Invoices or Payment details.
Plans
| Plan | Per month | Per year | Sites | Events / month | Recorded sessions / month | Recording storage / month |
|---|---|---|---|---|---|---|
| Free | — | — | 1 | 10000 | 100 | 1 GB |
| Starter | 29 EUR | 290 EUR | 1 | 500000 | 10000 | 30 GB |
| Growth | 99 EUR | 990 EUR | 5 | 1500000 | 30000 | 90 GB |
| Scale | 249 EUR | 2490 EUR | 10 | 5000000 | 100000 | 300 GB |
| Agency | 149 EUR | 1490 EUR | 25 | 2500000 | 50000 | 150 GB |
Every plan includes every feature; plans differ by sites and by how much is collected and recorded. The published allowances are in section 5 of the Terms of Service. A year costs ten months. Sessions we identify as automated traffic are credited back, so bots never use up a plan.
Only an organization's owner can choose, change or cancel a plan; everyone in it can see the plan, the usage and the invoices. An organization has one subscription: to switch plan or between monthly and yearly, open Billing → Payment details, which opens the payment provider's portal. The founding-customer code FOUNDER (50% off for life, first 20 organizations) is typed on the payment page.
The Free plan is one per person. You can own several organizations, but only one of them can hold sites on the Free plan; give the others a plan first. An organization a client owns, where you are only an admin, does not count against yours.
What is counted
Three counters, reset monthly:
- Events — one per pageview, per error occurrence, per newly captured lead, per recorded
interaction (a click, a rage click, a dead click, a scroll-depth measurement) and per custom
event sent with
StorePilot.track(). On a typical shop that is about thirty per visit, most of them clicks. Errors count per occurrence, not per unique fault: an error seen five thousand times is one row in the dashboard and five thousand against the allowance, because it cost that. - Recorded sessions — one per visit whose session is recorded.
- Recording storage — the bytes those recordings store.
Nothing is counted for a request that was not stored. A payload refused for consent, for an opt-out signal or for an excluded URL never reaches a counter — you cannot be billed for data we declined to keep, and a counter that ticked on refusals would make a site look busy for switching privacy protections on.
What happens as you approach a limit
| At | What happens |
|---|---|
| 80% | A notice on the usage screen, and a message to the organization's owners. Nothing changes. |
| 100% | A second notice. Still nothing changes. |
| 120% | Of any one of events, recorded sessions or recording storage: pageviews, interactions, recordings and page snapshots are refused until the month ends. Errors, leads, orders and survey answers are not. |
The gap between 100% and 120% is deliberate: a month that runs 5% over is not a reason to stop collecting somebody's data, and a hard stop the moment a round number is crossed is how a shop loses the week of analytics it was about to look at.
Errors and leads keep flowing past every limit, always. They are the two things that cost money to miss — an error you never saw is a checkout that is broken right now, and a lead you never received is a customer. Analytics and recordings are the ones that stop, because they are the ones you can catch up on.
Reading the usage screen
Billing → Usage shows the current month against the allowance, per counter, for the whole organization, and the same month per site. The number of sites is the one figure that is a total rather than a monthly count. The month is calendar-based and resets at the start of the next one — the screen prints that moment in your own time zone; it is not a rolling window, so a spike does not follow you for thirty days.
Invoices
Every charge produces an invoice row with its amount, currency, status and period, readable from the billing screen and included in your account export. There is no separate archive to request.
Changing or cancelling
Paid plans have no trial: the first month (or year) is charged when you choose a plan, and the Free plan is how to try StorePilot. A subscription is active, past due or cancelled, and a cancellation takes effect at the end of the period you have paid for, not immediately — then the organization returns to the Free plan. If a payment fails and is still unpaid fourteen days later, the subscription is cancelled and site settings become read-only until a plan is chosen again; errors and leads keep being collected throughout. Data collected during a paid period stays under the retention rules that applied when it was collected.
An organization that still pays for a plan cannot be deleted — cancel the subscription first, or the card would go on being charged for an organization that no longer exists.
The provider's own portal handles payment methods and receipts. It is available once there is a customer record to open it against, which means after the first checkout — before that there is nothing to show and the button says so instead of failing.