Plans and what they unlock

How to see which plan you are on

Your plan is shown on the Home screen, in the greeting card at the top, alongside your company and the shop you are working in. There is also a plan usage panel further down Home showing how much of your allowance you have used.

How to change plan, or pay your bill

Not possible inside the app — contact your provider

Every billing screen in the menu — Billing Dashboard, Plans, Invoices, Payments, My Subscription, My Orders, My Services, Credit Ledger and Payment Plans — opens a placeholder. None of them is built.

You cannot view your bill, pay it, or change plan from inside SaleSprint. To upgrade, downgrade, or settle an invoice, contact whoever sells you SaleSprint directly.

Do not ignore an overdue bill on the assumption you can settle it in the app later — an unpaid account is eventually suspended, and a suspended workspace refuses sign-in with “This workspace is suspended for non-payment.”

The tiers

SaleSprint ships five subscription tiers. Each one includes everything below it, so moving up never takes a feature away.

Tier	On your bill
Basic	Essential
Standard	Standard
Growth	Growth
Professional	Professional
Enterprise	Enterprise

The entry tier has two names

The plan you buy is called Essential, but inside the app the same tier is labelled Basic. They are the same thing. Every tier above it uses one name in both places.

Alongside the tier, a plan carries its own pricing, trial length and a monthly credit allowance. Separately from the tiers there is an add-on catalogue — credit packs, licence add-ons and service packs — which can be bought on top of any plan, and whose price can be negotiated for an individual account.

The four things a plan controls

Everything a plan unlocks falls into one of four groups, and they behave differently enough that it is worth knowing which one you are hitting.

Capacity limits cap how many of something you can have: companies, branches, warehouses and users, plus per-product ceilings on variants, attributes, prices, images and discount exclusions. Essential allows one company, one branch, no warehouses and two users; Enterprise allows seven companies, fifteen branches, ten warehouses and forty-five users, with most per-product ceilings removed entirely.

Modules are whole functional areas, each off by default and bought in: manufacturing, e-commerce, van sales, delivery aggregation, payroll, the payment API, predictive analytics and disaster recovery.

Industry packs tailor the product to a trade — restaurant, salon, pharmacy, hospitality, rental, automotive, optical, veterinary and others. An account opts into the packs it wants, and a plan caps how many can be active at once.

Capabilities are smaller cross-cutting switches: custom receipt layouts, removing the “powered by” marks, multi-currency, multi-jurisdiction tax, inline and automatic discounting, backdating a sale, multi-level categories, product images, combos, and read or write access to the public API.

Note what “backdating a sale” covers: the till sale only. Every other dated document is governed by your own settings rather than your plan, and even a sale needs both — see Document dates and how far they can move.

Hitting a limit

Plan limits are enforced on the server, at the moment you try to write. The client cannot talk its way past one, which also means you will meet a limit at save time rather than when you open the screen.

What you get back depends on which kind of limit it was:

• A capacity limit — “Your plan allows 5 branches and you have 5. Upgrade or remove one to add more.”
• A capacity of zero — the thing is not in your plan at all: “Your current plan does not include warehouses. Upgrade to add them.”
• A module, pack or capability that is off — “Manufacturing is not included in your current plan. Upgrade to enable it.”

A limit of unlimited is exactly that. A limit of zero blocks even the first one, which is the case worth watching: it reads as a missing feature rather than a quota.

Note

If the entitlement service itself cannot be reached, checks allow the action rather than block it. A platform problem will never lock you out of your own data.

Locked, or simply gone

The menu treats an unavailable feature in one of two ways, and the difference is deliberate.

Locked — the item stays visible with an upgrade badge. This is what you get when your plan is too low, or when a module or capability is not enabled. The feature exists and is worth knowing about, so the menu keeps it in front of you.

Hidden — the item is not rendered at all. This happens when:

• You lack the permission for it. Plan has nothing to do with this, and no amount of upgrading will reveal it — see Roles and permissions.
• It belongs to an industry pack the account has not enabled. A veterinary screen in a hardware shop is clutter, not a sales opportunity.
• It is an opt-in flow switched off in settings, such as the layaway and backorder options in POS.

A locked parent collapses to a single locked row rather than expanding, and a parent whose children are all hidden disappears along with them.

Changes take effect without an update

Which tier unlocks which permission is held in a matrix an operator can edit directly, rather than being fixed in a released build. Re-tiering a feature therefore reaches customers without anyone shipping a new version of the app.

A change applies immediately on the server handling it, and within a minute everywhere else.

Related

• Roles and permissions — the other half of what you can reach
• Settings and how they resolve