Feature toggles

Settings → Features. Four switches, one per product area, set per store environment:

Toggle	Covers
Reviews	Review collection, widgets, request emails, import/export
Rewards	The loyalty programme: earning rules, rewards catalogue, members
FAQs	Product- and page-scoped FAQs and their widget
Galleries	UGC galleries and lead capture

Turning one off hides its section of the sidebar and stops its widgets rendering. Data is not deleted — switch it back on and everything is where you left it.

Toggles are not plan limits

These two things look similar in the sidebar and are completely different in intent.

• A feature toggle is a choice you made. The feature is available to you; you decided this store does not use it. It is hidden — no menu entry, no widget, nothing to explain.
• A plan lock is a limit on your subscription. The feature exists and you cannot use it yet. It stays visible with a padlock, and clicking it explains what plan it needs.

The difference is deliberate. Hiding something you could buy is a bad experience — nobody upgrades to get a feature they have never seen. Showing something you have deliberately switched off is clutter.

If a feature is missing from your sidebar entirely, it is a toggle. If it is greyed with a padlock, it is your plan. See Billing & plans.

Per store, not per organization

Toggles are per store environment. An agency running six client stores can run reviews-only on five and the full stack on the sixth.

When to turn something off

• You are launching in stages. Reviews first, loyalty in a month. Turn loyalty off until you are ready rather than leaving half-configured screens in front of your team.
• A client does not want it. Fewer menu items, fewer questions.
• The feature does not work on your platform. Loyalty accrual does not currently fire on Shopify — if that is a dealbreaker for a given store, hiding Rewards is more honest than leaving a programme that never awards anything.

From the API

GET /features returns the current state, PUT /features sets it. Both are store-scoped like everything else, so they need an x-store-env-id.

Widgets respect toggles server-side. Turning Reviews off does not rely on you also removing the widget container — the container will simply render nothing.