Platform Governance
Part of Ecommerce platform scalability
Planning for more stores without duplicating every system
Decide which product, stock, order and app records to share when adding brand storefronts or separate stores.
Before adding a brand storefront or another sales experience, decide which records and operations stay shared. A new website does not necessarily need a new commerce store. A shared backend does not make every app aware of which storefront a product, order or message belongs to.
Map shared facts and deliberate differences
List what the new storefront must present differently: range, navigation, content, price, service rules and staff ownership. For each underlying fact, name the system that may change it and the systems that receive it. Keep this operating decision separate from regional currency and translation planning.
Capability / Question to settle
- Product identity
- Is one saleable SKU authoritative across storefronts?
- Stock
- Is quantity shared or allocated to a channel?
- Price and availability
- Which rule produces each storefront’s customer result?
- Order
- Can staff identify the originating storefront?
- Content
- Who approves each site’s navigation and campaign copy?
- Integration
- Does each app preserve storefront or channel context?
Use one product sold on both sites and one excluded from the new site. Trace search, direct access, basket and a staff-created order. This should expose where visibility and order rules need separate controls.
Compare structures by the work they create
A shared commerce store with several storefront channels can avoid copying the core catalogue. BigCommerce Multi-Storefront supports multiple websites and channels using a store’s catalogue.
For apps, check that product channel assignments are handled correctly and that order records include the channel ID. Confirm how each proposed connector handles the relevant storefront, especially order messages and fulfilment feeds.
A single storefront with customer segments may be sufficient when the business mainly needs different offers or presentation within one site. Shopify Markets is another option to assess; verify its documented capabilities against the distinctions you need before relying on it.
Before choosing this structure, confirm whether one storefront can meet the required brand or customer distinction and how staff will review the resulting orders.
Independent commerce stores give each operation separate settings and data. Shopify expansion stores are for organisations on the Shopify Plus plan. If a shared product or stock number is required, specify its synchronisation route and owner.
Compare storefront structures by the work they create
- Shared commerce store with several storefront channelsAvoids copying the core catalogue. BigCommerce Multi-Storefront supports multiple websites and channels using a store's catalogue.
- Single storefront with customer segmentsMay be sufficient when the business mainly needs different offers or presentation within one site. Shopify Markets is another option to assess; verify its documented capabilities against the distinctions you need.
- Independent commerce storesGives each operation separate settings and data. Shopify expansion stores are for organisations on the Shopify Plus plan. If a shared product or stock number is required, specify its synchronisation route and owner.
Check apps preserve storefront or channel context
- Product channel assignmentsConfirm they are handled correctly.
- Order recordsConfirm they include the channel ID.
- Each proposed connectorConfirm it handles the relevant storefront, especially order messages and fulfilment feeds.
Test one ordinary change across the proposed structure
Plan to publish a shared product, exclude it from one storefront, change one local price and correct its description. For each structure, record the edits, approvals, channel assignments and downstream updates. Then inspect an order, refund and customer message for the originating storefront.
If independent stores are necessary, document the continuing synchronisation jobs and app changes required to keep shared records aligned.
Test one ordinary change across the proposed structure
- 1Publish a shared product.
- 2Exclude it from one storefront.
- 3Change one local price.
- 4Correct its description.
- 5Record the edits, approvals, channel assignments and downstream updates.
- 6Inspect an order, refund and customer message for the originating storefront.
- 7If independent stores are necessary, document the continuing synchronisation jobs and app changes required to keep shared records aligned.
