Keeping commerce truth outside the channel that reads it

← Architectures

Reference structure · Commerce · Technology × Organisations

One ecommerce architecture in which storefront, marketplace and media surfaces read a shared commerce reading rather than each maintaining their own.

This is one possible structure, not a target state and not a record of a system observed in a specific environment. It is useful while its assumptions hold, and it says where a different arrangement would fit better.

The structural question

Should each channel hold its own version of catalogue, price and performance truth, or read from a shared reading held outside them?

Components

Each part is here for a reason: what it owns, and what it depends on.

• Catalogue and price source

  Owns: Source of record for product identity and price rules.

  Depends on: Depends on channel-specific overrides being explicit rather than emergent.

• Commerce platform (e.g. Shopify, Magento)

  Owns: Source of record for storefront sessions and its own orders.

  Depends on: Depends on app and customisation choices that accumulate into platform-specific behaviour.

• Marketplace channels

  Owns: Their own listing state and order flow.

  Depends on: Depend on identifier mapping; unmapped listings become invisible to the shared reading.

• Media and creative performance

  Owns: Spend and creative results.

  Depends on: Depends on attribution windows that rarely agree across channels.

• Shared commerce reading

  Owns: Source of record for the reconciled view — not for orders or inventory.

  Depends on: Depends on agreed definitions of margin, availability and return rate.

Ownership and source of record

Catalogue and price rules sit outside the storefront; each channel remains source of record for its own orders. Whoever can approve a channel-specific override determines how long the shared reading stays credible — usually a commercial decision, not a technical one.

Movement through the structure

1. 01

   Catalogue and price source

2. 02

   Channels (storefront, marketplace, media)

3. 03

   Shared commerce reading

4. 04

   Channel decisions

5. 05

   Read-out

The dependency to watch is override drift: each channel's local exception, individually reasonable, eventually makes the shared reading a fourth version of truth.

Dependencies

The question is whether the dependency matches what the organisation needs.

Intentional coupling

Price rules and channel presentation benefit from moving together within a channel; separating them entirely creates latency where customers notice it.

Costly coupling

Letting the storefront platform own catalogue truth couples every other channel to that platform's data model and to its app ecosystem.

What is hard to reverse

Holding catalogue and price rules outside the storefront preserves the ability to change storefront. Deep app-level customisation inside a hosted platform is the least reversible part of most commerce estates.

When something fails

If the shared reading fails, channels continue selling on their last known state — acceptable briefly, and dangerous during promotions or thin stock. If the catalogue source fails, channels should hold rather than fall back to stale overrides.

Assumptions

A reference structure is only reusable when its assumptions travel with it.

What must hold

If these are not true in a given environment, the structure is the wrong starting point.

• More than one channel sells the same catalogue.
• Near-real-time synchronisation is required for stock and price, but not for performance reading.
• Identifier mapping across channels is achievable and maintained.
• Overrides can be governed rather than left to each channel team.

Trade-offs

Each improves something and costs something. Neither side is universally preferable.

• Portability of catalogue truth against the convenience of the storefront platform owning it.
• A shared reading against local channel autonomy and speed.
• Consistency across channels against the failure surface that synchronisation introduces.

What this makes possible

Pricing, inventory and creative decisions can be taken against one reading, and channel exceptions become visible as exceptions.

What it constrains

It adds mapping and governance work, and makes fast unilateral channel changes harder.

How you would know whether it helped

Whether channels stop reconciling by hand, and whether stock and price discrepancies between channels reduce.

What informed this

Platform constraints in hosted commerce and marketplace APIs, technical reasoning about synchronisation requirements, and observed situations in multi-channel D2C environments.

Another structure may fit when

Another structure may fit when one channel dominates revenue — letting that platform own catalogue truth is simpler until a second channel matters commercially.

Where this stops fitting

Stops fitting single-channel D2C businesses, catalogues small enough to reconcile manually, or organisations without an owner for override governance.

Related

Related reading

Industry

• Retail
• D2C
• Consumer Brands

Knowledge · Playbook

• Turning Weekly Retail Signals Into Decisions Someone Owns
• Operating a Marketplace That Keeps Moving Underneath You
• When Every Team Holds a Different Version of the Customer

Evidence · Observed Situation

• When growth outpaced the organisation's ability to read itself
• When every team had a dashboard and no team had a decision

The situations linked above informed this representation. They do not establish that this structure is right for another environment — that remains a question about the specific organisation, its ownership and its constraints.

Architecture, as a question →Work with Cralgo →