Usage limits and feature entitlements

Overview

• Billing Overview shows usage for active Stores, active staff users, active Products, Orders created this month, active POS slots, and active KDS slots.
• Monthly Order usage is counted from the start of the current UTC month in the current implementation.
• Daily API usage is counted in UTC-day buckets.
• Usage cards warn near/over the effective Business limit.
• Feature availability is separate from numeric usage limits. A Business can be under its Store limit but still lack a plan feature such as Integrations or API Access.
• Custom subscription overrides can change both feature flags and numeric limits without changing the displayed base plan name.

When to use this

• Check Usage before adding a Store, staff member, Product, POS/KDS device, or before a high-volume integration goes live.

Step-by-step

1. Open Billing & Plan → Overview.
2. Review each Usage card and Feature availability.
3. Investigate cards close to or above their limit.
4. Remove/deactivate obsolete resources where appropriate or upgrade the Business.
5. For API, monitor both the daily plan allowance and the separate short-window rate limit.

Common mistakes

• Do not assume deleting historical Orders is the normal way to handle a monthly order limit.
• Do not confuse inactive/deleted resources with active resources counted toward many limits.
• Do not confuse the daily API allowance with the 100 requests/minute per-key rate limit.

Troubleshooting

• If usage seems unexpected, check active/deleted status and whether the metric is Business-wide.
• If API is being rejected despite low minute-by-minute traffic, check the Business's daily API allowance.