The POC on a page
as at 16 November 2026
The POC gets the Release 1 build ready to start. It does three things, in order: it gets the team into every system the build needs; it sets the integration patterns for the Experience API and for the domain services and designs each Release 1 domain service with them, through architecture approval; and it builds one working slice that proves an order flowing end to end across the systems, on services in Azure, deployed by CI/CD. A fourth part runs across all three: the AI-native way the work is planned and built, proven on the POC’s own work so the Release 1 team inherits a method with numbers behind it. It proves what is new to Metcash. It is not a production build.
- Delivers: a developer desktop for each builder, then access to every system the build touches.
- When: now to 13 November; the developer desktop when the image lands.
- Done when: each builder works with the full toolchain, and each system is reached by working evidence or a stand-in is named and accepted.
- Delivers: the Experience API integration pattern; the domain service integration pattern; a design for each Release 1 domain service; architecture approval.
- When: patterns by 20 November; designs by 4 December; each to the architecture review when ready, loyalty first.
- Done when: both patterns and the designs are approved, with every decision recorded.
- Delivers: one order end to end across the systems, on services in Azure, deployed by CI/CD, with every external service on its sandbox and the domain services mocked first.
- When: 9 November to the demo on 18 December; the store leg 18 to 29 January.
- Done when: the flow runs live on the demo day with no manual step, and the sandbox is torn down and rebuilt from code.
- Delivers: the delivery workflow on every POC repository; the plan from requirement to agent-ready task brief in Azure DevOps; a measured baseline.
- When: across all three parts: the plan ready before 9 November, the read-out in late January.
- Done when: every Part 2 and Part 3 item is delivered from a planned, traced task brief through the gated workflow, and the read-out carries the baseline.
How the parts fit. Parts 1 to 3 run in order but overlap, and Part 4 runs under all of them. The build starts in the sandbox on the draft patterns as soon as access lands, because the sandbox is disposable and nothing in it is production. What the build learns goes back into the designs before they are approved. Approval gates the Release 1 build, not the POC.
The banner. Thirsty Camel, the confirmed first Liquor banner. The storefront is a replica of today’s Thirsty Camel website from the user’s point of view: the public site is crawled, read-only, for its pages, navigation, layout and content, and the replica is rebuilt on the new stack. The data behind it is synthetic. Porters is a second skin from configuration, to prove one codebase serves many banners.
Who. Sean and Pat build the POC themselves, alongside the Part 2 designs. The integration architect works with them on the two patterns, and the enterprise test practice and security join from Part 1. Two builders is why the build spends its time on the flow across the systems and starts every domain service as a mock.
What is real and what stands in. Every external SaaS is real, on its sandbox or a test account: the commercetools development project, the CyberSource sandbox, Auth0 and Coveo on free accounts, Vercel, and the Talon.One test tenant once the loyalty foundation reaches it. Each domain service starts as a mock behind its contract and becomes real only where time allows; the same contract tests run against the mock and the real service. Data for commercetools is loaded directly. What this leaves unproven is mapping Metcash’s real product and price data into commercetools, which the read-out names.
Out of scope
Section titled “Out of scope”Real customer data and real money; the mapping of real Metcash product and price data; production readiness (performance at scale, penetration testing, PCI assessment, SIT and UAT); a full order manager, delivery and the fulfilment platform; content management, merchandising and full search; B2B journeys; further banners beyond the second skin; the Food and hardware storefronts; migration and cutover. Each is in the Release 1 scope or decided elsewhere.
What leaves the POC
Section titled “What leaves the POC”The Shopper developer image and its standard; the two approved patterns with their deployment and CI/CD templates; the delivery method proven on real work, with its plan template in Azure DevOps and the measured baseline; a design for every Release 1 domain service; standards version 0 as the input to version 1; the working slice and its Bicep, pipelines and repositories as the start of the Release 1 build; the acceptance record; the stand-in register with the swap for each; and the estimating basis for the Release 1 build.
Additions since v0.6
Section titled “Additions since v0.6”On 16 November Sean accepted four items from Pat’s next steps into Part 3: staff access management, store pick device enrolment, mobile app lifecycle management, and geo-polygon mapping and delivery boundaries. They are marked “Added 16 Nov” in their scope reference until the scope note is re-cut.
Source: the Shopper POC scope, v0.6 of 3 November 2026 (approved version 0.5), re-expressed for this site.