Skip to content

2 · Architecture design

Patterns by 20 November; designs by 4 December; each to the architecture review when ready, loyalty first as at 16 November 2026

6%

Four steps. The first two set the patterns: one front door for every surface (the Experience API pattern) and a domain service pattern that splits by complexity, so each service takes the lightest shape that holds it. The third applies the patterns to every Release 1 domain service, loyalty first. The fourth gets them approved: the two patterns to the architecture review with loyalty as the worked case, each domain service design when ready, then the enterprise architecture group and the review board.

In the POC each domain service is loaded into commercetools, mocked behind its contract, built thin or left out; the design is still owed for every one.

ItemStatusProgressOwnerDueMoved
The Experience API integration pattern In progress
50%
Sean with the integration architect 20 Nov 3 Nov
The domain service integration pattern In progress
50%
Sean with the integration architect 20 Nov 3 Nov
Loyalty foundation design Not started
0%
Pat with the integration architect 4 Dec 3 Nov
Order engine design Not started Moved this week
0%
Pat 4 Dec 16 Nov
Retailer settlement and reconciliation design Not started
0%
Sean 4 Dec 3 Nov
Product contract and PIM mapping design Not started
0%
Sean 4 Dec 3 Nov
Display price design Not started
0%
Sean 4 Dec 3 Nov
Weight and GST calculation design Not started
0%
Sean 4 Dec 3 Nov
Availability design Not started
0%
Sean 4 Dec 3 Nov
Store and location master design Not started Moved this week
0%
Pat, with DW 4 Dec 16 Nov
Promotion and offers mapping design Not started
0%
Sean 4 Dec 3 Nov
Payment adapter design Not started Moved this week
0%
Pat 4 Dec 16 Nov
Fulfilment integration design Not started
0%
Sean 4 Dec 3 Nov
Order history and invoice generation design Not started Moved this week
0%
Pat, with Brendan 4 Dec 16 Nov
Scheduled jobs design Not started
0%
Sean 4 Dec 3 Nov
Architecture approval Not started
0%
Sean 4 Dec 3 Nov
  • The Experience API pattern and the domain service pattern are approved, with the complex-service shape decided.
  • The loyalty foundation’s design is approved by early December, when loyalty release one’s build weeks start.
  • Every Release 1 domain service has a design on the pattern, approved or with its open items named.
  • Every decision the patterns forced is recorded as an architecture decision record.