Skip to content

Since mid-August: what moved

Week 37 · 2026·11 September 2026

Three weeks of movement across the commerce architecture: loyalty consolidation endorsed and sequenced, a contracted payments direction, the experience layer contested, settlement joining the backbone, and the analytics estate heading to Fabric.

This first edition catches up the three weeks since mid-August. The through-line: the programme moved from requirements to concrete design — three detailed architectures shipped — while three big directions firmed: one loyalty platform for every pillar, one contracted payments stack, and one analytics platform. Each item links onward to the capability page involved.

Loyalty: one platform, every pillar — endorsed and sequenced

Section titled “Loyalty: one platform, every pillar — endorsed and sequenced”
  • Endorsed at GLT: every pillar’s loyalty migrates to the one enterprise platform — and the hardware programme (Mitre 10 / Home Timber & Hardware) is confirmed in scope as the fourth move: members and balances only, the simplest of the four, with today’s agency-run arrangement concluding once migration completes.
  • The sequence is Liquor first, then Total Tools, then the Food re-shape. The Liquor call now on the clock is ledger shape — one balance across banners or a balance per banner — which must be settled before the programme is created, expected this quarter.
  • The loyalty detailed architecture (proposed) keeps the platform at arm’s length: one engine API layer as the only route in and out, a member registry keeping till lookups off the engine, and the transaction rail as the switch — a pillar migration is a repoint, and rollback is the repoint back.
  • One vendor-side change to watch: Talon.One has been acquired by Adyen since the enterprise agreement was signed; roadmap and renewal posture are being tracked.

Payments: a contracted direction for money-in

Section titled “Payments: a contracted direction for money-in”

The corporate payments function has contracted a CyberSource gateway over Fiserv acquiring as the group’s go-forward stack — signed, not yet implemented anywhere. Standing guidance to the new commerce build: integrate to CyberSource, not the incumbent gateway. The case is architectural: network tokens give durable, cross-brand payment continuity, and centralised decisioning cuts checkout friction before it reaches step-up authentication — one platform, B2B and B2C. Detail lands under payment orchestration.

The experience layer: one seam, a working shape

Section titled “The experience layer: one seam, a working shape”

Three answers to “who builds the experience layer” were on the table — the enterprise Experience API, a pillar-sponsored thin-BFF model, and a shape that couples the layer to the commerce engine the platform mandate says must stay swappable. The design sessions since have landed a working shape: channels, then a thin and optional BFF, then one shared, enterprise-owned orchestration layer, then pillar domain services for bespoke logic only — with the formal operating-model decision deferred until technology leadership is in the room. REST is firming as the channel-facing standard, and the ownership question is real: there is no Experience API team today, now an open entry in the decisions register.

Working the money-out leg end to end found the store-disbursement calculation living in the current retail-transaction platform — not the ERP, which accepts prepared journals only and pays stores on its supplier rail. Retailer settlement is now the ninth component of the commerce backbone, with a current-state read and future-platform requirements written. One mandated fix stands out for its leverage: mint a unique transaction reference when the transaction is created and carry it end to end — most of the reconciliation problem collapses. Home page for the detail: billing & settlement.

The analytics platform is migrating to Microsoft Fabric and OneLake — a re-engineering, not a lift-and-shift — with retail media as the first slice and an enhancement freeze while it runs. The sequencing rule that matters most for shopper work: enterprise loyalty and campaign data consolidate on Fabric, not before — interim builds on the old platform are technical debt. See analytics & AI.

The availability-service question widened from Food to Food, Liquor and Hardware together — one cross-estate service, with a decision paper due within weeks and a dual track under assessment: build on shared foundations, or buy. See inventory.

Work packages: from requirements to design

Section titled “Work packages: from requirements to design”
  • The endorsed pull-forward set is five: Identity · Loyalty back end · POS Adapter · OMS · Experience API. See delivery.
  • The POS adapter is one package in three parts — modernise the current retail-transaction estate, upgrade the vendor interface, integrate the TTHG POS estate. Industry research backs the boundary: store-initiated sync is the default, and almost nothing in POS is a testable standard.
  • Detailed architectures shipped for the Experience API, the POS adapter and loyalty; each go-live ask now prices the build and the run separately.
  • An ownership and operating-model framework now sits under the stack — who builds · runs · changes · sets the standard · pays, asked layer by layer. The first open cell: the customer master’s build-and-run owner.

Inspection of the Thirsty Camel estate showed a live national platform — published stores, banded price lists, live payments — so the banner programme is a replatform intended as the blueprint for the next banner, and its scope is being reconciled with what already runs. Context: the Liquor pillar.

Also moving: the enterprise ecommerce platform evaluation completed mid-August, with the outcome moving through release. On the clock next: the inventory decision paper, the Liquor ledger call this quarter — and this digest going weekly from Friday. The capability pages above pick up the full detail as the catch-up absorption lands.