Understanding plan features and locked capabilities

Sooner or later, while you are setting up your store or trying to launch a campaign before a busy weekend, you will click into a feature and find it greyed out, marked read-only, or sitting behind a small lock icon. That moment feels like something is broken or like your money was wasted, but in almost every case it is simply your plan drawing a line between what your current tier includes and what a higher tier unlocks. Understanding that line calmly, instead of panicking the night before a Ramadan push, is what separates merchants who keep selling from merchants who freeze.

The most important thing to know first is that a locked capability is almost never a deleted one. When a feature is restricted by your plan, your existing data and settings are preserved untouched in the background; the feature simply waits in a view-only state until your tier allows it, and it switches back on the moment you upgrade. That means you can run your whole business today on what you have, decide on an upgrade deliberately rather than under pressure, and never fear that opening a locked screen will damage live orders or lose information you already entered.

Why a feature looks locked: three different reasons

A greyed-out button has more than one possible cause, and treating them all as "I need to pay more" is a common and expensive mistake. Before you reach for the upgrade page, work out which of these you are actually looking at.

• Your plan tier. The capability exists on the platform but is bundled into a higher tier than the one you pay for today. This is the only case an upgrade actually solves. Storix shows these as available-but-locked rather than hiding them, precisely so you can see what the next tier would give you.
• Your team role or permission. If a teammate sees a screen as read-only but the store owner sees it fully, the limit is the staff member's permission level, not the plan. No upgrade fixes this — the owner adjusts the role. If a teammate sees read-only but you do not, that is a role question, not your plan; the team roles and permissions lesson covers how to set those.
• It needs an app, integration, or a request. Some needs are not a plan tier at all — they are met by installing an app, connecting an external service, or asking the Storix team to enable something. When the capability you want is really an add-on rather than a built-in tier feature, the right move is to browse the app store or request the app instead of upgrading blindly.

How to decide whether an upgrade is worth it

Upgrading should be a business decision tied to a real bottleneck, not a reflex to clear every lock icon. Work through it like this:

1. Name the bottleneck the feature solves. Be specific: "I cannot add a second staff account to confirm COD orders during the rush," or "I cannot schedule the discount I need for the first three days of Ramadan." A lock with no real pain behind it is not worth a piastre.
2. Weigh the monthly EGP price difference against that pain. If the higher tier costs a few hundred pounds more per month and unlocks the automation that recovers even a handful of abandoned carts a week, the maths is usually obvious. If you would not actually use what it unlocks, skip it.
3. Time the upgrade around cash flow and seasonal peaks. Unlock extra staff seats, cart automation, or higher limits just before a known COD-volume spike — paydays, Ramadan, Black Friday, Back to School — so you pay for the capability exactly when it earns its keep, not months in advance.

Upgrade without ever stopping operations

The goal is to expand what you can do without interrupting the orders already flowing. Keep confirming COD orders by phone and WhatsApp exactly as you do now while you evaluate; the upgrade unlocks the new capability in place without touching your live catalogue, customers, or in-flight orders. Before you commit, also understand the downgrade direction: if you ever move to a lower tier, capabilities above that tier return to read-only and your data stays safe but paused, so you are never trapped by an upgrade. Plan the change for a quiet hour rather than mid-rush, confirm the specific feature you needed is now active, and only then build the workflow that depends on it.

Related lessons

• App store and requesting a new app — when a locked need is really an add-on rather than a higher plan tier.
• Support and feature requests from the admin — how to ask the Storix team when you are unsure whether something is a plan limit at all.
• Team roles and permissions — the other reason a screen shows read-only, and how to set what each teammate can do.

This Storix Academy lesson is published as "Understanding plan features and locked capabilities". Every step below is written for merchants selling online in Egypt, so apply one change at a time and measure the result before moving on.