Store configuration

The dashboard and storefront read the first Store record (stores(take: 1)) as shared application settings. The operator page is /dashboard/platform/store.

One deployment is one store. Products, carts, orders and regions are not linked to a Store record, so extra Store rows do not create separate shops.

Dashboard-managed settings

The Store settings screen reads and updates:

• store name;
• logo SVG (logoIcon);
• logo color (logoColor);
• homepage title;
• homepage description.

The server sanitizes the logo SVG against an allowlist of SVG elements and attributes, both in the server action and in a field hook on the model. An SVG that does not survive sanitizing is rejected. Creating, updating and deleting Store records requires canManageSalesChannels. Anyone can read the Store.

Other Store fields

The Store model also has:

• defaultCurrencyCode;
• related currencies;
• paymentLinkTemplate, swapLinkTemplate and inviteLinkTemplate;
• metadata (JSON);
• a computed paymentProviders field. It lists installed Stripe or PayPal providers whose environment variables are set, with their publishable key.

These fields are not on the settings screen. Edit them on the generic /dashboard/stores page or through GraphQL. /dashboard/platform/system also has a Stores tab.

Markets

The Store is not the market model. Regions, countries, currencies, prices, tax rates, payment providers and shipping options have their own records, managed under /dashboard/platform/regions and the related pages. Changing defaultCurrencyCode does not convert prices.

Before you publish changes

1. Preview branding on the storefront at desktop and mobile sizes.
2. Check each region's currency, prices, countries, tax rate, payment providers and shipping options.
3. Keep provider secrets out of Store metadata and out of NEXT_PUBLIC_ variables.