Plans and limits

For anyone who has hit a limit or is working out which plan they need. Every organization is on a plan, and the plan sets the allowances below. Individual limits can be raised for your account without changing plan, so if one number is the only thing in your way, ask.

What a plan costs

PlanPer monthPer yearWhat it fits
Starter$49$490One store running reviews, loyalty and wishlists.
Growth$149$1,490A store past its first thousand active members a month.
EnterpriseTalk to usTalk to usSeveral storefronts, or volume past what Growth allows.

Paying for a year costs 17% less than paying monthly, which is two months free. Prices are in US dollars and are per organization: every store, every team member and all four products are inside the number.

Every organization starts on a 14-day free trial, from the day you sign up, with no card and nothing to activate. There is no permanent free plan: if the trial runs out with nothing paying, the organization goes read only rather than being charged or deleted. See Billing.

What you are sold on

Three allowances, one per product, and they are the only ones that change with the plan.

AllowanceStarterGrowthEnterprise
Review submissions per month2,00020,000From 100,000
Active loyalty members per month1,00010,000From 50,000
Active wishlist customers per month1,00010,000From 50,000

Enterprise numbers are a floor rather than a ceiling: they are where the conversation starts, and what comes out of it is written onto your account.

Going over one is billed rather than blocked, at $10 per 1,000 review submissions, $15 per 1,000 active loyalty members and $10 per 1,000 active wishlist customers, on both Starter and Growth. It is one switch on the billing page and it is on by default; turn it off and each product degrades after 14 days instead. See If you go over an allowance.

Two features are not on every plan: AI review summaries and AI review screening start on Growth, and SSO is Enterprise.

The backstops

Everything below is a fair-use backstop rather than a tier. Each one is set high enough that normal use never meets it, and it exists so that a runaway import or integration cannot quietly run up your account. Products and customers are the same on every plan for that reason.

AllowanceStarterGrowthEnterprise
Connected stores31025
Products100,000100,000100,000
Variants per product100100200
Customers1,000,0001,000,0001,000,000
Review requests sent per month20,000200,0001,000,000
Team members525250

Structure

The counts that stop you building something rather than stop you growing.

AllowanceStarterGrowthEnterprise
API keys202050
Webhook endpoints2050200
Loyalty programs31050
Rules per program50200500
Tiers per program102550
Rewards per program1005002,000
Stamp card types1050200
Survey flows1050200
Steps per survey flow2050100
Saved charts502001,000
Dashboards1050200
Saved filters502001,000
Quick filters2050200
Tags per record2550100
Wishlists per customer100100100
Items per wishlist500500500

Storage and retention

AllowanceStarterGrowthEnterprise
Brand assets per site100 MB500 MB2,048 MB
Uploaded files in total5,000 MB50,000 MB250,000 MB
One upload25 MB50 MB100 MB
Assistant attachments5 MB5 MB5 MB
Photos and videos per review101020
Webhook delivery history30 days90 days365 days
Import history180 days365 days730 days

Imports, exports and rate

AllowanceStarterGrowthEnterprise
Import jobs per day1050200
Export jobs per day1050200
Rows per import50,000250,0001,000,000
Rows per export100,000500,0002,000,000
API requests per minute6006003,000
MCP requests per minute120120600
Loyalty events per minute120120600
Loyalty stamps per minute120120600
Emails per customer per day101020

The per-minute numbers are per organization, not per key. See Rate limits.

The emails-per-customer-per-day cap is a protection rather than an allowance: it exists so that a misconfigured flow cannot mail one person forty times.

Assistant attachments is how much one message to the dashboard assistant may carry in images and PDFs. It is the same on every plan, because what a model will read in one message is a property of the model rather than of what an account pays. Ask us if you need more room.

Import history is how long a finished import job is kept, along with the CSV it ran on and the list of records it wrote. Past it the job is cleared out. The records the import created or updated are never touched by that: only the receipt goes.

What happens when you reach one

It depends on which kind of limit it is, and there are only three kinds.

The three allowances you are sold on keep working when you go over. You get a warning at 80 percent, and after that it depends on one switch: with overage billing on (the default) everything carries on and the units past the allowance are billed, and with it off everything carries on for fourteen days and then that one product stops taking new activity. Nothing is deleted either way and your storefront never changes. Billing has the rates and the whole sequence.

A backstop blocks the action and says so in one sentence naming what you reached and what to do:

You have reached the limit of 100,000 products. Upgrade your plan or ask us to raise the limit.

Only the create is refused. Reading, editing and deleting what you already have always work, so a backstop can never strand you from your own data. Over the API this is a 400 with the code BAD_REQUEST. See Errors.

Backstops are set high enough that normal use never meets one, and they are not a reason to upgrade. If you have reached one doing something reasonable, the number is wrong: tell us and we will raise it.

A feature switch reads differently, since there is nothing to delete:

AI review summaries is not available on this plan. Upgrade your plan to turn it on.

The screens for a feature your plan does not include are hidden rather than shown broken, and the API says the same sentence rather than pretending the endpoint does not exist.

The three that are metered

Three of the allowances are the ones a plan is priced on, one per product:

MeterWhat counts
Review submissionsReviews submitted in the calendar month, however they arrived.
Active loyalty membersMembers with any loyalty activity in the calendar month: points, stamps, or rewards. A member who does nothing that month is not counted.
Active wishlist customersCustomers who created a wishlist, or added or removed a wishlist item, in the calendar month. Somebody who only views a shared wishlist is not counted.

Everything else in the tables above is a backstop rather than something you are sold: it is there so a runaway integration cannot quietly run up your account, and you should never come close to one in normal use.

Watching your usage

Settings → Billing shows what you are using against what you are allowed. The three metered allowances get a bar, and the backstops read as a plain count, because a bar against a number nobody is meant to reach is not information. The reviews, loyalty and wishlists screens each carry a banner for their own allowance once it passes 80 percent.

Every monthly meter (review requests, active loyalty members, active wishlist customers, review submissions) covers the current calendar month in UTC and resets when it rolls over. The rest are running totals of what your account holds right now.

Counts are cached for a few minutes, so a number can briefly lag a big import or delete you just ran.

Raising a limit

Any single limit can be lifted for your organization without moving you up a plan, which is the right answer when one number is the only problem: a catalog that is unusually large for your order volume, a one-off migration that needs a bigger import, an integration that needs more requests a minute for a week. Ask rather than upgrading for one row of a table.