Two core tracks, one optional
B2C Store and B2B Stores are the core commerce tracks, across two tranches. Club Portal is a third, optional track — priced separately, not yet confirmed. Analytics runs as part of implementation across every track, detailed out separately.
B2C Store
Tranche 1padi.com/store — Frontastic → React/Next.js on the modernized padi.com decoupled architecture. CommerceTools B2C engine, checkout, catalog, and pricing stay unchanged.
B2B Stores — NA-US+CA / EMEA / APAC
T1 + T2Birddog replaced by BigCommerce (hosted), integrated to NetSuite via the Patchworks iPaaS layer. Americas + Canada in Tranche 1; EMEA and APAC follow in Tranche 2.
Club Portal
Optionalpadi.com/club, if confirmed. Vue.js → React/Next.js onto the padi.com architecture, plus a Drupal 10 → 11 upgrade on the instance shared with Pro. Not yet approved.
Anchored to the ERP sunset
Tranche 1 assumes a mid-September 2026 start with the 1 February 2027 go-live held fixed. Tranche 2 is sequenced behind Tranche 1's go-live, not the original programme start.
Six items, none blocking build start
The platform and architecture decisions are resolved. What's left is commercial and administrative — pricing confirmations, sign-offs, and a couple of scope calls.
B2C ERP sync model
Patchworks is being evaluated as the iPaaS layer for CommerceTools ↔ NetSuite too, not just BigCommerce. Needed pre-build start.
B2C SOW sign-off
Needed to kick off CommerceTools discovery for the B2C Store track. Owner: PADI.
Japan scope
Separate Oracle ERP system — can't be a simple regional add-on. Unresolved; candidate for a future phase.
Club Cloudflare routing
Bundled with the Club Portal go/no-go, not an independent decision — follows automatically if Club is confirmed.
Pro Cloudflare routing
To be confirmed during discovery — not committed for November 2026 in this proposal.
Unified Cart & Payments
Not a November 2026 deliverable. Picked up during this workstream's discovery phase — see Unification below.
Unification topics
Two parallel efforts PADI is driving that touch the systems this workstream builds — tracked as open decisions, not assumed or estimated as specific requirements yet.
PADI's product team is developing platform-agnostic requirements for a single cart (anonymous + authenticated, multi-currency) and unified payments across B2C and B2B. Still pending current-state mapping and feasibility analysis. We pick up their findings during this workstream's discovery phase and assess what's feasible for the Feb/May 2027 go-lives — a contingency budget is carried per track to cover them once scoped.
Beyond cart and payments: Localization, Device Fingerprinting, Search, Security, and similar continuity topics carrying forward from the Nov 2026 padi.com go-live. They apply to B2C Store, B2B Stores, and potentially Club Portal. Initially analysed, then scoped during this workstream's discovery — a contingency budget is carried per track to cover them once scoped.
Club & Pro
Both share the same Drupal 10 instance today. Only Club is being considered for modernization in this workstream, and only if confirmed.
Club Portal
Optional · pending confirmationNot yet approved as part of this workstream's scope. If confirmed: Vue.js → React/Next.js onto the padi.com decoupled architecture, plus the shared Drupal 10 → 11 upgrade — Club's IA/content changes stay isolated to Club, and the upgrade itself is tested against Pro before go-live. padi.com/club routing is bundled with this decision, not independent of it. If not confirmed, nothing changes — Club stays exactly as it is today.
We recently learned from the PADI Technology team that the Piccolo API also needs to be considered for Club entitlements as part of the Club Portal backend — we'll analyse and understand this further during discovery.
Pro Portal
On hold · out of scopePlaced on hold for a future modernization, based on recent developments. padi.com/pro Cloudflare routing is not committed either — to be confirmed during discovery. Pro's existing functionality and IA are protected regardless of what happens with Club — the shared Drupal 11 upgrade (if it happens) is tested against Pro too, but no new Pro features or design work are in scope here.
Architecture
The same two diagrams from the full proposal — toggle between them to talk through what actually changes.
Macola feeds both platforms manually — no automated sync. Birddog has no NetSuite path, so B2B becomes non-functional the moment Macola retires unless replaced first.
NetSuite becomes the single source of truth for both platforms. BigCommerce replaces Birddog, hosted and native for Phase 1 — not headless. B2B stays on independent subdomains; only B2C (and Club, if confirmed) join the padi.com namespace.