Branding
Route: /org/ecom/storesettings?tab=branding · Permission: Manage Store Settings
1. What Branding covers
The store's visual identity — "Control your brand's visual identity across the storefront." One name, four images and two colours, each landing somewhere specific.
| Store branding | Organization branding | |
|---|---|---|
| Scope | One project's store | The organization |
| Reaches | Storefront, invoices, brochure, link previews | Every surface |
| Set in | Store Settings | Experience Manager |
2. Where each asset is used
3. The form — step by step
Step 1 · Name the store
Store Name is the only required field on the section — "Displayed on the storefront, browser tabs, and invoices."
Step 2 · Upload the images
| Image | Constraint | Empty behaviour |
|---|---|---|
| Logo | PNG or JPG · max 500 KB | — |
| Favicon | PNG or JPG · 32×32 · max 100 KB | — |
| Brochure Cover Image | Upload PNG/JPG · A4 portrait · max 800 KB | "Leave empty for an auto-branded title page" |
| Social Share Image | Wide 1200×630 banner | "Falls back to your Logo if left empty" |
The last two accept either an upload or Pick from Assets — any image from the Digital Assets library, with no size cap, "already optimised on S3".
The screen says why: it "stores a direct image link that link-preview crawlers can always load". An uploaded image can end up behind a path a crawler will not follow, and the failure only shows up when someone shares the link and gets no preview.
Step 3 · Set the colours
Primary color and Secondary color each take a hex value — shown as CURRENT HEX — with a row
of preset swatches beside them. Unlike the Ops configuration screens, the hex field here is
editable, so any brand colour can be used.
Step 4 · Check the preview
A Storefront Preview card sits top-right showing the store name and a SHOP NOW button in the current branding — a live read of what the shopper will see.
4. Field reference
| Field | Control | Required | Notes |
|---|---|---|---|
| Store Name | Text | ✅ | Storefront, browser tab, invoices |
| Logo | Upload | — | PNG/JPG, max 500 KB. Change Logo when one exists |
| Favicon | Upload | — | PNG/JPG, 32×32, max 100 KB |
| Brochure Cover Image | Upload or Pick from Assets | — | A4 portrait, max 800 KB on upload |
| Social Share Image | Upload or Pick from Assets | — | 1200×630; falls back to the logo |
| Primary color | Hex + swatches | — | |
| Secondary color | Hex + swatches | — |
Where "Pick from Assets" reads from
The organization's Digital Assets library. The size cap applies only to direct uploads — an asset already in the library is served from S3 and is not re-checked.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| Menu Listing of Store Front settings | No access |
| Manage Store Settings | Read-only |
| A selected project | Branding is per project |
| Digital Assets library | Pick from Assets has nothing to offer |
6. Downstream
Branding is the most widely consumed section — storefront chrome, the browser tab, invoices, the product brochure PDF and link previews all read it. A change here is visible to customers as soon as it is saved.
7. Don't confuse this with…
| Thing | Where | Why |
|---|---|---|
| Store branding (this page) | Store Settings | One project's store |
| Brand Identity | Experience Manager | Organization-wide identity |
| Storefront theme colours | Here | Primary/secondary drive the storefront palette |
| Brochure cover | Here | The product brochure PDF, not a storefront page |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| A shared link shows no image | No social share image, and the logo fallback is not crawler-reachable — use Pick from Assets |
| Upload rejected | Over the per-image size cap |
| The brochure has a plain title page | No cover image — that is the documented fallback |
| Colours did not change the storefront | The save covers every section; confirm it succeeded |
| Favicon looks wrong | It must be 32×32 |