Store Settings
Route: /org/ecom/storesettings · Permission: Menu Listing of Store Front settings
Module: org_ecomstore_setings · Header gear: Show Store Settings in the header settings menu.
1. What Store Settings is
Everything about how one project's store behaves — how it looks, how customers reach it, where it delivers, how it takes money, how it prints, and what it automates.
It is not where products live, and it is no longer where the storefront's navigation is designed. Both moved elsewhere, and knowing that saves a long search:
| Store Settings | Inventory | Experience Manager | |
|---|---|---|---|
| Owns | Store behaviour | The products sold | The pages and navigation |
| Scope | One project | Organization | Organization + project |
| Example | Delivery radius, COD, coupons | A product and its price | The storefront menu, header and footer |
2. How settings spread across the storefront
3. The screen — step by step
Step 1 · Select a project
Store Settings is per project, not per organization. A tenant with two projects has two independent stores.
Step 2 · Pick a section
Nine sections are visible:
| # | Section | ?tab= | Page |
|---|---|---|---|
| 1 | Branding | branding | Branding |
| 2 | Contact | contact | Contact |
| 3 | Location & delivery | location | Location & delivery |
| 4 | Social | social | Social & SEO |
| 5 | SEO | seo | Social & SEO |
| 6 | Payment gateways | payments | Payment gateways |
| 7 | Order printing | printing | Order printing |
| 8 | Discount coupons | coupons | Discount coupons |
| 9 | Operation Automation | automation | Operation Automation |
?tab=payments works. Internally the sections are numbered, and the names are mapped onto those
numbers — so the URL stays readable even though the component thinks in indices.
Step 3 · Save
Save Changes appears twice — pinned top-right and floating at the bottom of long sections. There is one save for the whole screen: it writes the settings for every section at once, not just the one you are looking at.
Step 4 · Leave
Exit Store Settings in the rail.
4. The two retired sections
Two sections still exist in the code and are hidden from the rail:
| Retired section | Where it went |
|---|---|
| Storefront menu | Experience Manager → Project → Storefront → Menu |
| Header & Footer | Experience Manager → Project → Storefront → Header & Footer |
?tab=menu and ?tab=global are still accepted, but they resolve to Branding — not to the
Experience Manager, and not to an error.
So a bookmark or a doc that predates the move appears to work and quietly shows the wrong screen. If someone reports that "the menu editor disappeared", this is why.
5. Permissions — five, and two of them hide sections
| Permission | Gates |
|---|---|
| Menu Listing of Store Front settings | The page, and all loading. Without it nothing fetches |
| Manage Store Settings | Managing settings |
| Manage Story Front Coupon Codes | The Discount coupons section |
| Manage Automation of StoreSetings | The Operation Automation section |
| Show Store Settings in the header settings menu. | The header settings-gear entry |
Unlike Task Configuration — which shows every section and refuses to let you edit — this hub removes Operation Automation and Discount coupons from the rail when the permission is missing.
A user without them sees a seven-section rail and no indication the other two exist.
6. Downstream
| Section | Reaches |
|---|---|
| Branding | Storefront chrome, browser tab, invoices, brochure PDF, link previews |
| Contact | The storefront's contact surfaces, and transactional alert routing |
| Location & delivery | Checkout — which fulfilment methods appear and what they cost |
| Social · SEO | Storefront metadata, analytics tags |
| Payment gateways | Checkout payment options, COD emails |
| Order printing | Receipts and job orders |
| Discount coupons | Checkout |
| Operation Automation | Preorder scheduling |
7. Don't confuse this with…
| Thing | Where | Why it is different |
|---|---|---|
| Store Settings (this page) | /org/ecom/storesettings | One project's store behaviour |
| Organization Settings | /org/settings | Organization-wide; has no storefront section |
| Experience Manager | /org/experience | The pages, menu, header and footer |
| Inventory | /org/inventory/* | The products themselves |
| Project settings | /org/projects/:id | The project — budget, team, billing |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Nothing loads | Missing Menu Listing of Store Front settings — the fetch itself is gated |
| Only seven sections in the rail | Missing the coupons and/or automation permission |
?tab=menu shows Branding | The section is retired; it moved to Experience Manager |
| A change did not reach the storefront | Save writes all sections at once — check the save succeeded |
| Settings differ between two stores | They are per project |
| No entry in the header gear | Missing Show Store Settings in the header settings menu. |
Related
- Branding · Location & delivery · Payment gateways
- Launch health check — what to verify before going live
- Orbit Storefront overview