B2B Decisions and Workshop Plan
Shareable with BLACKROLL and project partners. Maintained by 22Bits. Last checked 2026-10-26. Part of Project: B2B Migration.
Every decision the B2B project needs, who decides it, by when, and in which workshop. This is the working document for the workshops: each workshop gets a pre-read from it two days before, and every outcome is written back here.
Guiding principle (Kristy, B2B weekly 2026-10-26). Every decision is cost conscious. Out-of-the-box Shopify features and platform standards come first; solutions that need a lot of development are not affordable. Each lean below is checked against this.
49 decisions in eight areas. The IDs are stable: they never change and are never reused. New decisions get the next free number in their area.
How to read it
Status. Open: no decision and no working assumption yet. Assumed: the most likely answer today, which BLACKROLL still has to confirm. Decided: confirmed by the person in the "Decides" column, with date and source.
Options and lean. Where we stand today. It goes into the pre-read as a proposal, not as a decision.
ERP. Yes = the answer depends on what MyFactory and Xaidat can do or deliver; partly = one part of it does.
Needed by. The last moment the decision can be made without rework. Store setup = before the staging and production stores are created (the one-way doors; until then the spike runs in a throwaway Plus sandbox). Spike = before the spike plan is fixed. Build = before building starts (planning runs through November). Migration = before the first dry run. Go-live = before the CH cutover.
WS. The workshop in the proposed workshop plan below.
Background for the ERP and pricing decisions is in B2B ERP, Pricing and Architecture; for content and design in B2B Content and Design in a Liquid Store; the per-epic picture in the B2B Scope Matrix; the customer groups in B2B Customer Groups.
Working assumptions to confirm
The most likely answers after the kickoff on 2026-10-19. We plan with them until BLACKROLL confirms or changes them.
Topic | Working assumption | ID | To confirm with |
|---|---|---|---|
ERP route | Option B through the Xaidat gateway for companies and locations, if Xaidat can scope and deliver it in time. Prices stay in Shopify (P2, decided). Option A stays the fallback for the CH wave. Scope, estimate and timeline for the gateway extension have to come from Xaidat | E1 | Kristy, Teoman Lam, Xaidat |
Pros and trainers | They move into the B2B store as one-person companies | S2 | Sen, Kristy |
Native B2B | Native Shopify B2B features. If Sen is unsure, we compare native B2B and a B2B app such as SparkLayer side by side against the must-have list | PL7 | Sen |
Content | Native Shopify content editing. Content from Craft CMS is only possible with a headless shop, so it is not an option for a Liquid store | T1 | Kristy, Sen |
Design | Brand 2.0 tokens and typography on Horizon's B2B blocks. Porting the D2C design system into a Liquid theme means rebuilding every component, which is a lot of work. The B2B team would like the store closer to the D2C look, with D2C content (Sen, 2026-10-21), so the direction is decided in workshop 0 | T2 | Kristy, Sen |
Product data | The D2C product data through the existing feed, plus B2B fields in Shopify; no separate PIM integration for B2B in wave 1 | E7 | Sen, Teoman Lam |
Mindmap
One card per area; the IDs match the tables below.
flowchart LR
hub(("B2B<br/>decisions")):::hub
st["STEERING FIRST<br/><br/>S1 Scope for January<br/>S2 Pros: D2C or B2B<br/>S3 Wave order<br/>S4 Sales calendar<br/>S5 Owners<br/>S6 QA engineer<br/>S7 Workstream split<br/>S8 Market strategy"]:::steer
pl["PLATFORM<br/><br/>PL1 Store type<br/>PL2 Domain<br/>PL3 Stores, markets<br/>PL4 Custom code<br/>PL5 Run model<br/>PL6 Make or n8n<br/>PL7 Native B2B or app"]:::area
erp["ERP AND GATEWAY<br/><br/>touches all areas<br/><br/>E1 Option A or B<br/>E2 System of record<br/>E3 CH dealers in ERP<br/>E4 Tag owner<br/>E5 Data back<br/>E6 Product feed<br/>E7 Product data"]:::erp
mig["MIGRATION, GO-LIVE<br/><br/>M1 Parallel run<br/>M2 Dealer comms<br/>M3 Switch-off"]:::area
ci["CUSTOMER INTAKE<br/><br/>CI1 Signup flow<br/>CI2 Login<br/>CI3 Cohort<br/>CI4 Company model<br/>CI5 VAT ID check<br/>CI6 Klaviyo for B2B"]:::area
pr["PRICING<br/><br/>P1 Price model<br/>P2 Price master<br/>P3 Price conflicts<br/>P4 Catalogs<br/>P5 Volume, minimums"]:::area
pay["PAYMENTS, CURRENCIES<br/><br/>PC1 Base currency<br/>PC2 Methods per country<br/>PC3 CembraPay<br/>PC4 Terms, credit<br/>PC5 Checkout fields<br/>PC6 Shipping, FIEGE<br/>PC7 Merchant of record<br/>PC8 Central billing"]:::area
th["THEMING, CONTENT<br/><br/>T1 Shopify or Craft<br/>T2 Design scope<br/>T3 Feature list<br/>T4 Languages<br/>T5 Analytics plan"]:::area
st --- hub
pl --- hub
erp --- hub
mig --- hub
hub --- ci
hub --- pr
hub --- pay
hub --- th
classDef hub fill:#08427b,stroke:#052e56,color:#ffffff
classDef area fill:#f4f8fd,stroke:#438dd5,color:#1f2937
classDef steer fill:#fff2cc,stroke:#d6b656,color:#1f2937
classDef erp fill:#8c8c8c,stroke:#52525b,stroke-width:2px,color:#ffffffWhy ERP and data ownership come first: almost every area needs something from MyFactory through Xaidat. The diagram is in B2B ERP, Pricing and Architecture.
Steering: decide before the workshops
Not workshop topics. If these stay open, every workshop reopens scope. T1 (content system) and the direction of T2 (design scope) belong here too and are listed under theming. Most of these are Sen's and Kristy's decisions; S1, S2 and S8 also need the sign-off of the B2B leadership team (Martin Loer, Alec Duffield, Robert Kruschke). Workshop 0 takes place on Wed 28 Oct in the afternoon with Sen, Kristy, Martin Loer and maybe Robert Kruschke; whoever is not in the room signs off in writing by Fri 30 Oct. The session is 60 minutes and decides by exception on the pre-read; S6, S7 and the content owner per market are settled by email, and DEPT names the handover receiver in December (2026-10-26). Sen leads the project internally at BLACKROLL and coordinates the BLACKROLL participants (Kristy, 2026-10-23).
ID | Decision | Options and lean | Decides | ERP | Needed by | Status |
|---|---|---|---|---|---|---|
S1 | Scope and date for 31 January: what is in wave 1, what moves after January | Lean: CH wave by January, Pro DE and Pro BNL after, order per S3. Kristy asked for a wave approach or milestones in the first week of November. Basis: a provisional estimate on the working assumptions above; a firm estimate follows the final decisions. There is no formal DEPT estimate (question 1). Option raised by Sen (2026-10-21): connect the existing flows (Pipedrive, MyFactory, Xaidat) to the new store as they are and improve them after January. That keeps CI1, P2 and PL6 small for wave 1 and fits the guiding principle. Proposed to keep out of this phase from Sen's requirements list (facts below): the affiliate program (B2B2C), co-branding, reseller product feeds through Channable, AI newsletters; EDI runs as a separate key result. Sen marks each row of the list as wave 1, later or out | Sen; sign-off B2B leadership | no | Workshop 1 | Open |
S2 | Pros and trainers: verified segment on the D2C store, or one-person companies in the B2B store | Working assumption: B2B store. Every Pro then needs a company and a location for native B2B, which the spike tests. The Pro shop has about 6,800 B2B partners, not all active (Robert at the kickoff); the D2C store already has a | Sen, Kristy ("Business & Tech decision", slide 5); input Robert Kruschke | partly | Spike, so as soon as possible | Assumed |
S3 | Wave order of the three shops: CH store, Pro DE store, Pro BNL store | Lean: CH first; order and timing of DE and BNL follow S1. The Pro BNL store is an English-language store with daily orders, so BNL is a migration, not a market launch. Sen's requirements list also names AT, the rest of the EU and international customers. Sen (2026-10-23) names France next to Benelux; whether France is a B2B market today is open (question 25) | Sen | no | Workshop 1 | Open |
S4 | Wave 1 date against the B2B sales calendar | Needs the calendar (facts below) | Sen, B2B sales | no | Workshop 1 | Open |
S5 | Names: ERP and Xaidat counterpart, Finance owner for payments, DEPT receiver for the handover, CMS contact per market, sponsor, deputy for Sen | ERP: Teoman Lam (Teo) is the main contact, Holger Welzel joins for specific ERP topics (Sen, 2026-10-23). Country contacts: Thomas Mullis (CH), Patrick Stegemann (Benelux). Sponsor: Kristy, who manages the project budget (2026-10-26). Still open: Finance owner, DEPT receiver, a content owner per market (kickoff action "Assign CMS SPOC for markets"), and a deputy who confirms decisions while Sen is out of office (13 to 23 Nov, 21 Dec to 2 Jan). Workshop 0 names the Finance owner and the deputy; the content owner per market is settled by email (2026-10-26). The DEPT receiver is not named in November: DEPT assigns the person in December, and the handover goes to whoever is assigned (Philipp, 2026-10-26) | Kristy, Sen | no | Workshop 1 | Open (ERP, country contacts and sponsor named) |
S6 | Does the project team need a QA engineer? | Kristy wants an answer within two weeks of the kickoff. Lean (Philipp, 2026-10-26): no, not needed on the current assumptions, because the work is mostly Shopify configuration, a standard Horizon theme and existing flows connected as they are; look at it again if custom development or the Xaidat connection for Pro DE grows. Settled by email with Kristy instead of in workshop 0, answer by Fri 30 Oct (2026-10-26) | Kristy | no | Build | Open |
S7 | Store setup and front-end work as separate workstreams | Suggested by Kristy at the kickoff. Lean: yes. Settled by email with Kristy and Sen instead of in workshop 0, answer by Fri 30 Oct (2026-10-26) | Kristy, Sen | no | Workshop 1 | Assumed |
S8 | Market strategy: which countries the B2B store serves next, beyond CH, DE, AT and Benelux | Raised by Sen (2026-10-23): the developers need to know the next markets to build the right structure from the start. It drives the base currency (PC1), the payment providers (PC2), the markets per wave (PL3) and the languages (T4). France needs a place (question 25). At the kickoff Kristy named Spain, Poland, the UK and the US as possible expansion markets | Sen; sign-off B2B leadership | no | Store setup | Open |
Facts to collect before the workshops
Workshops stall on unknowns. These questions have an answer somewhere; they are not decisions.
How B2B works in the CH store today: which discounts, what percentage, who gets what (Sen; requested 2026-10-20). Known since 2026-10-21: two price groups through discount codes, and the customers are mostly physios. Sen (2026-10-23): prices are set per product group, and customers are created in Shopify first and then in MyFactory. That does not match ADR-060 (no ERP record, one blanket discount) and is checked with Teoman Lam (question 26). Nothing is written down yet; Sen walks Rron through the setup.
Latest state of CembraPay on a new store, and the workaround mentioned at the kickoff (Sofia Carvalho, Finance, Kristy).
Can Xaidat feed products, stock and customers into a second store in the Plus organization, and what would Option B cost and take (Teoman Lam, Holger Welzel, Xaidat; question 8; part of the prep call with Teo). Since P2, Option B no longer includes price lists.
What the wholesale app on pro.blackroll.com has switched on beyond prices: volume rules, net terms, minimums (22Bits, admin access in place).
The signup workflows of the Pro shop and the CH store (22Bits, kickoff action). The general lead flow is known since 2026-10-21 (CI1). Sen (2026-10-23): CH creates customers in Shopify first, DE and AT in MyFactory first; Benelux and France are to be clarified.
An inventory of customer tags and metafields across the stores (22Bits, kickoff action).
The B2B sales calendar (Sen).
Collected 2026-10-23: there is no formal DEPT estimate behind the gate on slide 9. The approach is documented in the ADRs, and the sizing assumption was that the migration fits into one trimester of work. Sandor Voordes led the scoping; 22Bits asks him about his sizing (question 1).
The cost-benefit case for the platform, including the voucher blackout periods for dealers around Black Friday (Kristy, Sen, Martin Loer).
The new B2B price model ("B2B Direct Price") for the B2B shops and EDI: what changes and when it is ready. Since P2 it is built in Shopify catalogs, not in the ERP. Sen aligns it internally with Sebastian Krebs before workshop 3b and forwards the email (P1).
The open questions on scope and data that Holger Welzel raised with Sen (Sen).
The requirements baseline for ERP data: customer structures, GTINs, product data, stock and the ERP data flows. Prep call with Sen and Teoman Lam before workshop 1a, following Sen's meeting with Teo on 2026-10-22 (E2, E3, E6, E7).
Which B2B product information is needed beyond the D2C product data, and what the new PIM planned for January changes (Sen, Teoman Lam, Kristy; E7).
Benelux and France: how customers are created, how prices work, which payment providers and languages are needed (Sen with Patrick Stegemann; question 25; CI1, P1, PC2, T4).
Collected 2026-10-22: the B2B requirements list from the discovery in December 2025, which the epics were written from. Sen sent the two Confluence pages ("Input Sen - B2B Requirements" and "Input Alex - Requirements Data & AI"). Sen's page lists about 55 B2B features, 11 affiliate features (B2B2C) and one co-branding feature, with reach and impact but without a wave or must-have marking; in the discovery the commerce features were kept on a separate tab and not ranked. What it adds is in the decision rows (S1 to S3, E4 to E6, PL3, CI1, CI4 to CI6, P1, P4, PC4, PC6, T3, T5) and in the new decision PC8.
Which rows of Sen's requirements list are wave 1, which come later and which are out of this phase (Sen, before workshop 0; S1, PL7). This becomes the must-have list the spike and PL7 test against.
Decision list by area
ERP and gateway
In the room: Kristy, Teoman Lam (main ERP contact), Sen, Xaidat, and Julia Schopka for data ownership (she joins or reviews E2). Holger Welzel joins for specific ERP topics. A prep call with Sen and Teo before the workshop sets the requirements baseline. This area decides who owns which data; the others build on it.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
E1 | Integration route | A: Xaidat keeps sending tags, a translator app in Shopify. B: Xaidat creates companies and locations natively. Prices are no longer part of either option, because they stay in Shopify (P2). Working assumption: B through the gateway, if Xaidat can scope and deliver it in time; A as the fallback for the CH wave. Xaidat is a third party, so scope, estimate and timeline come from Xaidat. Kristy said at the kickoff that Xaidat would take on the gateway work. Both options are checked against the guiding principle in workshop 1a: A means custom code in Shopify, B means paid work at Xaidat | Kristy, Teoman Lam; input Holger Welzel | yes | Build | 1 | Assumed |
E2 | System of record per data object: companies and contacts, delivery addresses, prices, assortment, payment terms, credit, stock, orders | One table, ERP or Shopify per row (the data table in B2B ERP, Pricing and Architecture). Prices: Shopify, decided on 2026-10-26 (P2). Julia Schopka asked to review it, because the source-of-truth decisions affect the data platform | Kristy, Teoman Lam, Sen; input Julia Schopka | yes | Build | 1 | Open (prices decided) |
E3 | Do CH dealers get ERP records before migration? | Yes: one path for every wave (old B2B store → ERP → gateway → Shopify), ERP work first; this fits Option B. No: CH companies are created in Shopify directly (ADR-060 4.3). Sen (2026-10-23): in CH customers are created in Shopify first and then in MyFactory. If CH dealers already have ERP records, this decision is mostly answered (question 26) | Sen, Teoman Lam | yes | Migration | 1 | Open |
E4 | Who owns the customer tags and their mapping from now on | ERP team, B2B sales operations, or no tags at all with Option B. Sen's requirements list keeps the assortment exclusions ( | Teoman Lam, Sen | yes | Build | 1 | Open |
E5 | What comes back from the ERP: order status, invoice, payment status, credit limit | All four (Sen's requirements) or orders and status only for wave 1. Needs Xaidat work in both options. Sen's requirements list asks for payment status in real time, invoices in the order history, VAT lines on invoices, and Skonto shown in checkout and on invoices | Teoman Lam, Finance | yes | Build | 1 | Open |
E6 | Products and stock for the new store | The same gateway feed as for D2C; a CSV import for wave 1 if the gateway cannot feed a second store. Sen's requirements list adds live stock levels, expected restock dates from the ERP, back-in-stock notifications and preorders | Teoman Lam | yes | Build | 1 | Open |
E7 | B2B product data: D2C product data plus B2B fields, or a separate PIM integration for B2B | Raised by Sen (2026-10-23): the D2C product data is the starting point. Open which B2B-specific information is needed (for example GTIN, packaging units, logistics data and classifications from Sen's requirements list) and whether it is kept as an extra data layer in Shopify or needs its own PIM integration. Sen wants consistent product data across markets without duplicate maintenance. Lean: D2C product data through the existing feed plus B2B fields as metafields; no separate PIM integration for wave 1. A new PIM is planned for January (kickoff), so the B2B fields have to fit it | Sen, Teoman Lam | partly | Build | 1 | Assumed |
Platform
In the room: Kristy, Sen, DEPT (Sandor Voordes, Romeo Vreeken). Mostly Kristy's calls; they go into workshop 1 because they share the room.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
PL1 | Store type | A new, dedicated B2B store in the Plus organization (BLAC-6171, ADR-035) with a Liquid theme, not headless. Confirmed at the kickoff: a new store, not the existing shop as the base. Switching store type later means redoing most of the setup (Shopify) | Kristy | no | Store setup | 1 | Decided (kickoff 2026-10-19) |
PL2 | Domain | Keep pro.blackroll.com (Sen's suggestion at the kickoff), b2b.blackroll.com after the CH cutover (the legacy CH shop uses it until then), or a new host. Kristy left the choice to Sen. Cutover plan for DNS and Vercel | Sen; input Bernd Stoeckler (DNS), Mark Smits (Vercel) | no | Go-live | 1 | Open |
PL3 | Stores and markets: sandbox, staging, production; markets per wave | Lean: spike in a throwaway Plus sandbox; staging and production only after PL1, PC1 and CI2. Markets per wave follow S3 and S8: Sen's requirements list names CH, DE, AT, the rest of the EU and international customers, and Sen now also names France | Kristy, 22Bits | no | Store setup | 1 | Open |
PL4 | How much custom code DEPT will run after January: translator app, signup approval app, migration scripts | Lean: native first, custom code only where a must-have fails (BLAC-6171). Kristy (2026-10-26): out-of-the-box Shopify and platform standards first, no solutions that need a lot of development. A custom price admin UI is not needed, because prices are managed in the Shopify admin (P2) | Kristy, DEPT | partly | Build | 1 | Assumed |
PL5 | Run model after 29 January: who at DEPT owns the store, apps and integrations; Cloudflare and Datadog in front or not | Lean: DEPT names the receiver in December, and the handover plan goes to whoever is assigned then; 22Bits does not wait for a name in November (Philipp, 2026-10-26). No proxy in front of the store (Shopify advises against it, question 7) | Kristy, Romeo Vreeken | no | Build (handover plan 15 Dec) | 1 | Open |
PL6 | Integration platform for Pipedrive, Shopify, ERP and Klaviyo | Make (today) or n8n. Lean: keep Make for wave 1 (question 16) | Alexandra Schmitz | partly | Build | 3 | Open |
PL7 | Native Shopify B2B or a B2B app | Kristy at the kickoff: "let's not call them native or not native right now"; Sen decides. Working assumption: native B2B, the default unless a must-have can't be met (BLAC-6171). If Sen is unsure, compare native B2B and an app such as SparkLayer side by side against the must-have list. Sen (2026-10-21): the B2B shops run on apps today, and native B2B would save a lot if it covers the must-haves. Sen (2026-10-23): native Shopify features wherever possible. This fits the guiding principle | Sen | partly | Spike | 1 | Assumed |
Customer intake
In the room: Sen, B2B sales and back office, Michelle Chevalier (CH process), Alexandra Schmitz and Front Row (CRM), Teoman Lam for the ERP parts.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
CI1 | Signup and approval flow | Pipedrive approval creates the company in Shopify (and the ERP customer), or a signup form in Shopify with approve or decline in an app. Native company account requests do not work on a store restricted to logged-in B2B customers, so a Shopify-side flow needs a custom form or app. Today (Sen, 2026-10-21): a partner fills in a form on a landing page; Pipedrive routes the lead to the right contact, who approves or declines; at a set stage an Excel list is filled in; Customer Care enters the customer with conditions in MyFactory; Xaidat pushes the customer to Shopify, and the customer gets an activation email. This takes two to three days. Options Sen named: Pipedrive creates the Shopify account through the API and the ERP data is added later; customers are activated directly instead of by email; or the flow stays as it is and is connected to the new store (S1). Sen (2026-10-23): Pipedrive stays the central system for B2B lead management and approval. Open: which system starts the customer creation, how company data moves and how the systems stay in sync. Today the order differs by market: CH Shopify first, DE and AT MyFactory first, Benelux and France to be clarified. Sen's requirements list also asks for access by email domain, for example | Sen, Alexandra Schmitz; input Michelle Chevalier, Front Row, Teoman Lam | yes | Build | 3 | Open |
CI2 | Login method | Shopify one-time code or BLACKROLL ID through our OIDC provider. Lean: one-time code for wave 1; BLACKROLL ID needs its own spike and puts an identity service on DEPT (question 6). Open point: ADR-035 mentions Firebase as identity provider; is that decided? | Kristy | partly | Spike | 1 | Open |
CI3 | Wave 1 cohort and de-duplication | Active dealers only, everyone who ever ordered, or all segment members; a rule for dealers in several shops. Lean for CH: active dealers, 700 to 1,000 companies (ADR-060, question 9); Kristy expects over 1,000 businesses in wave 1. If the Pros come in (S2), the Pro shop adds about 6,800 B2B partners | Sen | partly | Migration | 3 | Open |
CI4 | Company model and roles | Company = ERP customer number, location = ERP delivery address (spike 2.6); may dealers add one-off delivery addresses (spike open point 5; 31% of DE customers have several); company admins manage contacts, customer service orders on behalf (BLAC-6192). Sen's requirements list adds a unique B2B company ID, several users per company with roles and departments, and a GLN per location; in the discovery Holger Welzel noted that a company identifier is missing for B2B today. Sen (2026-10-23): one long-term approach for how B2B companies are represented in MyFactory and Shopify, for all markets | Sen, Teoman Lam; input Holger Welzel (logistics) | yes | Migration | 3 | Open |
CI5 | VAT ID check | At signup or during migration; app or own service (VIES); reverse charge per location. Not native in Shopify. Sen's requirements list asks for a real-time check per delivery country in checkout and several VAT IDs per customer. Lean with the guiding principle: an existing app, not an own service | Sen, Finance | no | Build | 2 | Open |
CI6 | Klaviyo as the B2B martech tool | Kristy at the kickoff: "if we stick with Klaviyo". BLAC-6188 and Front Row assume Klaviyo. From the requirements pages: the double opt-in status shared across systems, and B2B journeys (welcome, post-purchase, winback) | Alexandra Schmitz | no | Build | 3 | Open |
Pricing
In the room: Sen, B2B sales, Sebastian Krebs for the B2B Direct price model, Finance if price lists change.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
P1 | Price model | Keep today's tiers as they are (DE EK tiers in the wholesale app, CH discount levels) or one consolidated model. CH and DE price differently today; ADR-050 reworks the ERP price model (base lists plus factors). Sen (2026-10-21): CH has two price groups through discount codes, DE has EK1, EK2, EK3, EK1-5 and many variants. Sen (2026-10-23): CH prices per product group, DE and AT use customer-specific prices and individual conditions, Benelux and France are to be clarified. A new B2B price model is being worked out at BLACKROLL: a "B2B Direct Price" for the B2B shops and EDI, close to today's prices. Since P2 it is maintained in Shopify catalogs. Sen aligns it internally with Sebastian Krebs before workshop 3b. Sen's requirements list names 12 price groups (EK1-2P, EK1-3P, EK1-5P, EK1-9P, EK1-10P, EK1-15P, EK1-20P, EK1-30P, EK1-40P, EK2, EK3, VK-10P); customer-specific prices override the group price, and single customers get discounts on single products. In Shopify a price group maps to a catalog with a percentage adjustment and fixed prices per variant, which is close to how the wholesale app works today. When a company location has several catalogs, the lowest price wins; the spike checks how that fits customer-specific prices and the assortment restrictions (P4, PL7) | Sen, B2B sales; input Sebastian Krebs | partly | Build | 3 | Open |
P2 | Where price lists and catalogs are managed | Decided in the B2B weekly on 2026-10-26 (Kristy): prices live only in Shopify for now. Price management in the ERP becomes part of the integration with the new ERP, which comes later (question 27). Prices are managed in the Shopify admin per catalog: a percentage adjustment for the whole catalog, fixed prices per variant, volume pricing (up to 10 price breaks) and quantity rules, and CSV import and export per catalog or in bulk, matched by SKU. Shopify Plus allows up to 25 catalogs per company location and 10,000 per store (Shopify). To make the later ERP integration easy, catalogs follow the ERP price group codes, fixed prices are keyed by SKU, and no price logic lives in an app, so a later integration writes the same objects through the Admin API. Today MyFactory sends no prices to Shopify; they are maintained by hand (Sen, 2026-10-21) | Kristy, Sen | partly | Build | 3 | Decided (B2B weekly 2026-10-26) |
P3 | Which price wins at migration | Where wholesale app prices and ERP price lists differ ("price truth" in B2B ERP, Pricing and Architecture). With P2 the prices dealers pay today (wholesale app on pro.blackroll.com, discount codes in CH) are the natural starting point | Sen, B2B sales | partly | Migration | 3 | Open |
P4 | Catalogs and assortment restrictions | Consolidate the 33 restriction combinations (the top six cover 94%); what customers without a tier see. Lean: top six as catalogs, untiered customers see no prices until assigned (question 12). The exclusion tags ( | Sen | partly | Migration | 3 | Open |
P5 | Volume pricing, quantity rules, minimum order values | Which special conditions carry over; depends on what the wholesale app has switched on today (facts above). Native catalogs support volume pricing and quantity rules per variant | Sen | no | Build | 3 | Open |
Payments and currencies
Includes checkout and shipping. In the room: Sen, the Finance owner, Sofia Carvalho (Shopify Payments on D2C), Kristy, Holger Welzel for logistics, and the country contacts Thomas Mullis (CH) and Patrick Stegemann (Benelux) depending on S8. Sen collects the local requirements with them beforehand.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
PC1 | Store base currency | CHF or EUR. Changing it later relabels prices without converting them; CembraPay needs CHF; CHF limits local payment methods in other markets. Lean so far: CHF if CembraPay stays (question 2). Sen prefers to replace CembraPay (PC3); then the base currency follows the market strategy (S8) | Sen, Finance | no | Store setup | 2 | Open |
PC2 | Payment methods per country and the payment provider | The list of providers for CH, DE and BNL; selling with several business entities requires Shopify Payments (ADR-001); D2C consolidates on Shopify Payments. Benelux providers and local requirements are still open (Sen, 2026-10-23) | Sen, Finance; input Sofia Carvalho, Thomas Mullis (CH), Patrick Stegemann (Benelux) | no | Store setup | 2 | Open |
PC3 | CembraPay | Keep it (48% of CH B2B orders) or replace it with payment terms on account. At the kickoff Sofia called CembraPay critical for Swiss B2B customers and said there is a way to make it work; a breakout was agreed. Kristy is not sure CembraPay is still needed for invoicing. Sen (2026-10-23) prefers native Shopify B2B payment terms and invoices instead of CembraPay, if all business-critical Swiss payment requirements are covered. Native payment terms also fit the guiding principle | Finance, Sen; input Thomas Mullis | no | Store setup | 2 | Open |
PC4 | Payment terms and credit control | Who may pay by invoice, credit limits, what happens when a payment is overdue. Today a Flow removes | Finance, Sen | yes | Build | 2 | Open |
PC5 | Checkout requirements | PO number, VAT ID display and reverse charge, minimum order value, shipping contact; the exact requirements are still needed; checkout UI extensions are Plus only | Sen | no | Build | 2 | Open |
PC6 | Shipping and fulfilment | Shipping profiles per market and the FIEGE connection for the B2B store, not described in detail yet. Sen's requirements list asks for shipping rules by country, segment and basket, carriers from DHL parcel to freight, air and sea, packaging units (VPE), and parcel count and volume shown to the customer | Holger Welzel (logistics), Sen | yes | Build | 2 | Open |
PC7 | Merchant of record and the cost of local payment methods | Raised by Kristy at the kickoff: who is merchant of record, what local payment methods cost in Shopify Payments, and what Shopify has to set up (a roadmap with Shopify) | Kristy, Finance | no | Store setup | 2 | Open |
PC8 | Central billing for buying groups (Intersport, Sport 2000) | New from Sen's requirements list: orders from members of a buying group are billed through the central organisation (Zentralregulierung). The shop shows that an order goes through the central office, the ERP handles the settlement, and the central office controls assortment and invoices, with its own EDI rules. Touches the company model (CI4), payment terms (PC4) and checkout. Likely needed from the Pro DE wave on, since the buying groups are retail dealers; to confirm with Sen. With the guiding principle: as far as possible with standard payment terms and a checkout note, the settlement stays in the ERP | Sen, Finance, Teoman Lam | yes | Build | 2 | Open |
Theming and content
In the room: Sen, Martin Loer, Robert Kruschke, the B2B content team, Tina Kopf (B2B marketing), Kristy, a designer if there is one, and the country contacts for languages. Julia Schopka (analytics) in 4b.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
T1 | Content system | Working assumption: native Shopify content editing (BLAC-6181), brand content stays on blackroll.com. Content from Craft CMS is only possible with a headless shop, which was ruled out. The kickoff deck still lists Craft CMS, so this needs clearance; a deep dive was agreed. A yes or no Kristy can give by mail; it changes the estimate. Sen (2026-10-21) would like D2C content in the B2B store; without a headless shop that means maintaining it a second time in Shopify. Sen (2026-10-23) also lists the role of Craft as still open | Kristy; Sen owns content | no | Provisional estimate | 0 | Assumed, needs clearance |
T2 | Design scope | Working assumption: Brand 2.0 tokens and typography on Horizon's B2B blocks. Porting the D2C design system means rebuilding each component in Liquid (the D2C components are Vue and do not carry over) and maintaining the design in two places; every component adds scope, so a reuse decision needs the exact component list and a designer. Kristy was open to reusing the design system at the kickoff. Sen (2026-10-21): the B2B team wants the store to look closer to D2C, with D2C content, also to serve the physios better (S2). Sen (2026-10-23) frames two options: adapt selected D2C design elements and content into a Liquid theme, or build a new B2B theme from scratch; no designer is assigned so far. The options paper shows both next to our lean. Because this drives the estimate, the direction is decided in workshop 0, and the component list follows in workshop 4. Lean for January: Horizon as the base with its own files untouched, Brand 2.0 through the theme settings and one custom stylesheet, and any later component as a separate section or block that editors place in the theme editor. That keeps Horizon updatable at a few hours per Shopify update and is the option that fits the guiding principle. The pre-read for workshop 0 compares the maintenance cost of the three options | Kristy, Sen | no | Provisional estimate (direction), build (components) | 0, 4 | Assumed, needs clearance |
T3 | Storefront feature list | Quick order, reorder, order history, invoices, public pages (login, dealer application); Horizon covers quick order (BLAC-6179). Sen's requirements list rates the quick order matrix and the order history high and adds CSV upload, a download area for dealer marketing material, campaign discounts, trainings and product recommendations, and content per segment (more than 40 segments) | Sen | partly | Build | 4 | Open |
T4 | Languages and translation | Languages per wave (CH: DE and FR; Benelux and France per S8), the tool (Translate & Adapt), who translates: probably the B2B content team. The country contacts confirm which languages their markets need; Sen collects this beforehand | Sen, B2B content team; input Thomas Mullis (CH), Patrick Stegemann (Benelux) | no | Build | 4 | Open |
T5 | Analytics and tracking plan, consent | Kristy wants an analytics workstream with a business contact for forecasting, not only GA4 tracking. GA4 through Shopify customer events; OneTrust or Shopify consent. Tracking defined before theme work, after the Liquid decision. Lean: forecasting (in Sen's requirements list) is a data-team topic, apart from store tracking. Alexandra Schmitz's requirements add a shared event taxonomy and server-side tracking | Julia Schopka | no | Build, before theme work | 4 | Open |
Migration and go-live
Mostly planning with Sen once the waves are fixed; no workshop of its own.
ID | Decision | Options and lean | Decides | ERP | Needed by | WS | Status |
|---|---|---|---|---|---|---|---|
M1 | Parallel run and delta migration | How long each old shop runs next to the new one, order freeze, delta import; the legacy syncs stay alive until each wave (ADR-060 4.2, BLAC-6185) | Sen | partly | Go-live | later | Open |
M2 | Dealer communication per wave | Who tells dealers what and when, through which channel (slide 10). For the CH wave the communication has to be ready before 21 December, because Sen is out of office until 2 January | Sen, Tina Kopf | no | Go-live | later | Open |
M3 | Switch-off and redirects | Dates and owners for the legacy CMS, the Vercel app, apps and contracts per wave; one date for BLAC-6012 and BLAC-6186; redirects from the old hosts (questions 18 and 19) | Sen, Andrea Zimmerli, Kristy | no | Go-live | later | Open |
Proposed workshop plan
Ordered by dependency and by the one-way doors, not by area.
No. | Workshop | When | Length | Decisions | Must be in the room | Needs first | Output |
|---|---|---|---|---|---|---|---|
0 | Steering | Wed 28 Oct, afternoon | 60 min, decided by exception on the pre-read | S1 to S4, S8, T1, T2 direction; from S5 the Finance owner and a deputy for Sen. S6, S7 and the other owners by email, answers by Fri 30 Oct for S6 and S7 | Sen, Kristy, Martin Loer, Robert Kruschke if he can; written sign-off on S1, S2 and S8 by Fri 30 Oct from whoever is not in the room (Alec Duffield) | The pre-read with options and proposals; Robert's view on S2, in the room or in writing; Sen's wave marking of the requirements list; a provisional estimate on the working assumptions | Scope, waves, urgent owners, Pros, content, design direction, market strategy |
1a prep | ERP requirements with Teo | Week of 26 Oct | 60 min | Input to E2, E3, E6, E7 | Sen, Teoman Lam, 22Bits | Xaidat's answer on the second store (question 8) | Requirements baseline: customer structures, GTINs, product data, stock, ERP data flows |
1a | ERP and data ownership | Mon 2 Nov | 2 h | E1 to E7 | Kristy, Teoman Lam, Sen, Xaidat; Julia Schopka or a review of E2; Holger Welzel for specific topics | The prep call with Teo; Xaidat's answer on Option B | System-of-record table, ERP route, product data approach |
1b | Platform | Tue 3 Nov | 90 min | PL2 to PL5, PL7, CI2 | Kristy, Sen, DEPT | Outcome of 1a | Go for store setup, run model, login method |
2 | Payments, currencies and checkout | Wed 4 Nov | 2 h | PC1 to PC8, CI5 | Sen, Finance owner, Sofia Carvalho, Kristy, Holger Welzel; Thomas Mullis and Patrick Stegemann depending on S8 | CembraPay state; the market strategy (S8); local requirements collected by Sen | Base currency, payment matrix per country, checkout spec |
3a | Signup and onboarding | Mon 9 Nov | 90 min | CI1, CI6, PL6 | Sen, Alexandra Schmitz, Front Row, Michelle Chevalier, Teoman Lam | The signup workflows of the Pro shop and the CH store; the onboarding process per market | Signup and approval flow, martech tool, integration platform |
3b | Customers and pricing | Tue 10 Nov | 2 h | CI3, CI4, P1, P3 to P5 | Sen, Martin Loer (retail), Robert Kruschke (physios and medical), Sebastian Krebs (pricing), B2B back office, Teoman Lam | Workshops 1 and 2, the CH setup doc, the wholesale app settings, Sen's internal alignment on the B2B Direct price model | Cohort, company model, price model, catalog plan |
4 | Theme and content | Thu 12 Nov (moved, Sen is out from 13 Nov) | 90 min | T2 components, T3, T4 | Sen, Martin Loer, Robert Kruschke, B2B content team, Tina Kopf, Kristy, designer; Thomas Mullis and Patrick Stegemann for languages | T1 and the T2 direction from workshop 0, a draft feature list, the component list | Theme scope with component list, translation plan |
4b | Analytics | Tue 17 Nov | 45 min | T5 | Julia Schopka, Kristy, a business contact for forecasting | The Liquid decision (PL1) | Analytics and tracking plan |
Workshops 1 and 3 are split so that each group only sits in on its own topics: Xaidat and DEPT don't share a session, and signup is decided apart from pricing. Workshop 3 needs the results of 1 and 2. In the decision tables, WS 1 covers 1a and 1b, WS 3 covers 3a and 3b, and T5 is decided in 4b. M1 to M3 go into a go-live planning session with Sen once the waves are fixed, proposed for Wed 25 Nov. Together that is about 14 hours of sessions. The dates are proposals and depend on who can be in the room.
Changes after the replies of 2026-10-23 and the B2B weekly of 2026-10-26.
Workshop 0 takes place on Wed 28 Oct in the afternoon for 60 minutes, with Sen, Kristy, Martin Loer and maybe Robert Kruschke (B2B weekly 2026-10-26). Whoever is not in the room signs off S1, S2 and S8 in writing by Fri 30 Oct. S6, S7 and the owners not needed before workshop 2 are settled by email.
Guiding principle from Kristy (2026-10-26): cost conscious decisions, out-of-the-box Shopify first. Prices live only in Shopify for now (P2, decided).
Sen is out of office from 13 to 23 November and from 21 December to 2 January. Workshop 4 moves to Thu 12 Nov, the go-live planning moves to Wed 25 Nov, and every decision from workshops 1 to 3 has to be confirmed by Thu 12 Nov, or by a deputy (S5). Workshop 4b does not need Sen and stays on 17 Nov.
Sen leads the project internally at BLACKROLL and coordinates the BLACKROLL participants (Kristy). Teoman Lam is the main ERP contact (Sen).
An in-person working day in November, in Cologne or near Koblenz, is being planned, and one of the workshops can move there.
Timeline
Red bars decide a one-way door (scope, ERP route, store setup, store currency). A milestone is a deadline, not a meeting. Each pre-read goes out two working days before its session, and every write-back follows within two days.
gantt
title B2B workshops, October to November 2026
dateFormat YYYY-MM-DD
axisFormat %d %b
section Inputs and milestones
Questions to Xaidat sent :milestone, 2026-10-21, 0d
Provisional estimate :est, 2026-10-21, 2026-10-26
Price master decided (P2) :milestone, 2026-10-26, 0d
Xaidat answer needed :milestone, 2026-10-27, 0d
Written sign-off S1 S2 S8 :milestone, 2026-10-30, 0d
Wave approach and milestones :milestone, 2026-11-06, 0d
All decisions of WS 1 to 3 confirmed :milestone, 2026-11-12, 0d
Sen out of office :sen, 2026-11-13, 2026-11-23
section 0 Steering
Pre-read :milestone, 2026-10-26, 0d
Workshop 0 Steering (60 min) :crit, w0, 2026-10-28, 1d
Write-back :after w0, 2d
section 1 ERP and platform
Prep call ERP requirements with Teo :p1, 2026-10-29, 1d
Pre-read for workshops 1 and 2 :milestone, 2026-10-29, 0d
1a ERP and data ownership (2 h) :crit, w1a, 2026-11-02, 1d
1b Platform (90 min) :crit, w1b, 2026-11-03, 1d
Write-back and ADR drafts :after w1b, 2d
section 2 Payments
2 Payments and checkout (2 h) :crit, w2, 2026-11-04, 1d
Write-back :after w2, 2d
section 3 Customers and pricing
Pre-read :milestone, 2026-11-05, 0d
3a Signup and onboarding (90 min) :w3a, 2026-11-09, 1d
3b Customers and pricing (2 h) :w3b, 2026-11-10, 1d
Write-back :after w3b, 2d
section 4 Theme and analytics
Pre-read :milestone, 2026-11-10, 0d
4 Theme and content (90 min) :w4, 2026-11-12, 1d
Write-back :after w4, 1d
4b Analytics (45 min) :w4b, 2026-11-17, 1d
Write-back 4b :after w4b, 2d
section Later
Go-live planning M1 to M3 (60 min) :w5, 2026-11-25, 1dAbout the estimate. There is no formal DEPT estimate (question 1). 22Bits brings a provisional estimate into workshop 0. It is built on the working assumptions above and says so line by line. A firm estimate only makes sense after the final decisions, so each workshop updates it.
Rules for every workshop: a pre-read with options and our lean two days before; one named decider per decision; an open fact is a reason to postpone that decision, not to guess; every decision is written back here with date and decider and confirmed in writing within two days. Architecture decisions (for example E1, PL1, PL7, P2, T1, CI2) also get an ADR in DEPT's ADR register (question 23).
Provisional implementation timeline
Provisional, as of 2026-10-21, checked again on 2026-10-22, 2026-10-23 and 2026-10-26 with no date changes. Built on the working assumptions above, before any workshop has taken place. It is the starting point for the wave approach Kristy asked for in the first week of November, and it is updated after every workshop.
What it assumes
The working assumptions above hold: Option B through Xaidat with Option A as the fallback for the CH wave, Pros in the B2B store, native Shopify B2B, native Shopify content, Brand 2.0 tokens on Horizon's B2B blocks, D2C product data plus B2B fields.
The guiding principle holds: out-of-the-box Shopify first, custom code only where a must-have needs it.
The workshops decide on time, and the store currency and CembraPay are settled in November. S1, S2 and S8 are signed off by 30 October.
Xaidat starts the gateway extension in early December and delivers it by the end of February. Until then the CH wave runs without it: CH companies and CHF price lists are created in Shopify, and orders, products and stock go through the existing gateway, connected to the new store (E6). Since P2 the extension covers companies and locations, not price lists.
Wave order CH, Pro DE, Pro BNL (S3). Swapping DE and BNL moves their two go-live dates, but hardly the end date. France is not part of a wave yet (question 25).
Each legacy shop runs next to the new store for about four weeks after its go-live (M1).
The 22Bits team as planned today. A bigger team shortens the build phases, but not wave 2, because Xaidat's delivery sets its pace.
The B2B sales calendar is not known yet (S4). Go-live dates move to avoid a sale window.
Prices are maintained in Shopify catalogs (P2). The new B2B price model (P1) is ready for the DE price lists by January; if not, wave 2 starts on today's prices.
The direction for T2 in workshop 0 is tokens and typography. Reusing D2C components adds theme work before the CH wave and moves its date.
Sen is out of office from 13 to 23 November and from 21 December to 2 January. A deputy confirms decisions in between, and the CH dealer communication is ready before 21 December.
The new PIM planned for January does not change the product feed for the B2B store before the CH go-live (E7). The new ERP comes after this project (question 27).
Agentic development
Implementation is done with agentic development. That shortens the work that is code: theme sections, Shopify Functions and checkout extensions, migration and mapping scripts, tracking, tests and runbooks. It does not shorten decisions, Xaidat's and Front Row's work, payment provider onboarding, configuration in the Shopify admin, data clean-up that needs a business call, acceptance testing or dealer communication. Agents also never get access to real customer data: scripts are built and tested on anonymised samples, and people run them on the real exports.
So the critical path is decisions, Xaidat and data quality, not coding. We expect agentic development to save a few weeks in the build phases, but it doesn't move the dependencies.
What it means
Milestone | Provisional date | What drives it |
|---|---|---|
Wave 1 CH live | Week of 8 Feb 2027 (best case 1 Feb) | Decisions in workshops 0 to 2, CembraPay, Xaidat connecting orders and the product feed to the new store, acceptance testing in January |
Legacy CH store and legacy CMS off | Early March 2027 | Four weeks of parallel run after the CH wave |
Wave 2 Pro DE live | Early April 2027, after Easter | Xaidat's Option B delivery, the price groups and the 33 restriction combinations as Shopify catalogs, about 6,800 Pro accounts as companies, the CRM sync |
Wave 3 Pro BNL live | End of April 2027 | Reuses the Pro DE path; the BNL payment provider and NL content |
All legacy shops off, final handover to DEPT | End of May 2027 | Parallel run after the last wave |
Measured against the target of 31 January, only the CH wave lands close to it. The full current scope takes until about the end of May 2027. Who delivers waves 2 and 3 after 31 January, and when DEPT takes over which part, belongs to S1.
Red bars are on the critical path. Milestones are dates, not meetings.
gantt
title Provisional implementation timeline, as of 2026-10-21
dateFormat YYYY-MM-DD
axisFormat %d %b
section Planning
Workshops and write-backs :plan, 2026-10-21, 2026-11-20
Spike in a Plus sandbox :spike, 2026-11-02, 2026-11-14
section Calendar
Sen out of office :senoff1, 2026-11-13, 2026-11-23
Black Friday peak :peak, 2026-11-23, 2026-12-01
Christmas (reduced capacity) :xmas, 2026-12-21, 2027-01-04
Sen out of office :senoff2, 2026-12-21, 2027-01-02
Easter :easter, 2027-03-26, 2027-03-30
section Foundation
Staging and production stores :f1, 2026-11-09, 2026-11-21
Markets payments and checkout :f2, 2026-11-16, 2026-12-12
Theme on Horizon with Brand 2.0 tokens :f3, 2026-11-23, 2026-12-19
Analytics and tracking :f4, 2026-11-30, 2026-12-19
section Wave 1 CH
CH companies and price lists :c1, 2026-11-16, 2026-12-19
Orders and product feed via Xaidat :crit, c2, 2026-11-30, 2027-01-16
Lead flow Pipedrive to Shopify :c3, 2026-11-30, 2027-01-16
Dry runs and fixes :c4, 2027-01-11, 2027-01-23
Acceptance test and go/no-go :crit, c5, 2027-01-25, 2027-02-06
CH go-live :milestone, 2027-02-08, 0d
Hypercare and parallel run :c6, 2027-02-08, 2027-03-06
section Wave 2 Pro DE
Price groups as Shopify catalogs :d1, 2026-11-16, 2026-12-19
Xaidat Option B (companies, locations) :crit, d2, 2026-12-07, 2027-02-27
Pro accounts as one-person companies :d3, 2027-01-11, 2027-02-20
CRM sync with Front Row :d4, 2027-01-11, 2027-02-27
Integration tests and dry runs :crit, d5, 2027-03-01, 2027-03-13
Acceptance test and go/no-go :crit, d6, 2027-03-15, 2027-03-26
Pro DE go-live :milestone, 2027-04-06, 0d
Hypercare and parallel run :d7, 2027-04-06, 2027-05-01
section Wave 3 Pro BNL
BNL payment provider and NL content :b1, 2027-02-15, 2027-03-27
Migration on the Pro DE path :b2, 2027-03-30, 2027-04-17
Acceptance test and go/no-go :b3, 2027-04-19, 2027-04-24
Pro BNL go-live :milestone, 2027-04-26, 0d
Hypercare and parallel run :b4, 2027-04-26, 2027-05-22
section Switch-off and handover
Handover plan agreed :milestone, 2026-12-15, 0d
Current handover target :milestone, 2027-01-29, 0d
Legacy CH store and legacy CMS off :milestone, 2027-03-08, 0d
Pro DE store off :milestone, 2027-05-03, 0d
Pro BNL store off and final handover :milestone, 2027-05-24, 0dOpen questions
Questions that are not decisions, or that feed one. Where a question is covered by a decision, the decision row holds the options and the lean.
# | Question | Ask | Default if there is no answer | Decision |
|---|---|---|---|---|
1 | How was the estimate behind the gate on slide 9 ("scope and DEPT estimate signed off") built, and who owns it? Answered by Kristy on 2026-10-23: there is no formal DEPT estimate. The approach is documented in the ADRs, and the sizing assumption was that the migration fits into one trimester of work. Sandor Voordes led the scoping; 22Bits asks him about his sizing | Sandor Voordes | 22Bits provides a provisional estimate on the working assumptions | S1 |
2 | Store currency CHF or EUR, and does CembraPay install on the new store? If not, do native payment terms replace it for approved companies? Sen prefers native payment terms instead of CembraPay (2026-10-23) | Sen, Finance, Kristy | CHF base currency, Shopify Payments for later EUR markets, CembraPay tested in the spike; if it fails, net terms on the company for wave 1 | PC1, PC3 |
3 | Is Craft CMS a B2B integration (deck slides 6 and 7) or is content native in Shopify (BLAC-6181)? Who edits B2B content, and must any D2C content appear in the B2B store? Sen would like D2C content in it (2026-10-21) | Kristy, Sen | Native Shopify content, no Craft sync, brand content stays on blackroll.com | T1 |
4 | Which order for the three shops, and where do the Pros go? | Sen | CH first; Pros into the B2B store | S2, S3, PL2 |
5 | ERP: Option A or Option B, and who speaks for Xaidat and MyFactory in this project? Sen (2026-10-23): Teoman Lam is the main ERP contact, Holger Welzel joins for specific topics | Kristy, Teoman Lam | Option B if Xaidat can deliver, A as fallback for the CH wave | E1 |
6 | Login: Shopify one-time code or BLACKROLL ID through our OIDC provider? | Kristy | One-time code for wave 1, BLACKROLL ID later | CI2 |
7 | Who at DEPT receives the B2B store, theme, custom code and integrations on 29 January, and from when are they in the project? What does "shared services" cover for a Liquid store that needs neither a Cloudflare worker nor Datadog? | Kristy, Romeo Vreeken, Sandor Voordes | Minimal custom code, everything in | PL5, S5 |
8 | Can the Xaidat gateway publish products and stock to a second store in the Plus organization, and who configures it? Expansion stores don't share data by default (Shopify). Part of the prep call with Teo | Teoman Lam, Holger Welzel, Xaidat | The gateway feeds the new store like the D2C store; if not, a CSV import for wave 1 | E6 |
9 | Which customer list is wave 1: the 23,486 CH segment members, the 1,029 who ever ordered, or the 700 active per year? Who produces it and the de-duplication rule against the DE ERP list? | Sen | Active dealers (700 to 1,000 companies), as ADR-060 4.3 says | CI3 |
10 | Is the CH bridge (ADR-060 scenario 1) built on the D2C store, or is the Vercel fallback (scenario 3) what runs? BLAC-5366 is blocked. What has to keep running until the CH wave, and who watches it? | Sen, Andrea Zimmerli | Scenario 3 is live; the old store's product, price and stock sync and the Xaidat order webhook stay until cutover | M1 |
11 | What is the B2B sales calendar (next sale window) that sets the CH go/no-go date? | Sen, B2B sales | Wave 1 before the first 2027 sale season | S4 |
12 | Who decides the consolidation of the 33 assortment restriction combinations, and the fallback for untiered customers? | Sen | Top six combinations as catalogs (94% of restricted customers), the rest consolidated; untiered customers see no prices until assigned | P4 |
13 | Translation: which tool and who translates CH French and NL content for a store that is not in Craft? | Sen; Thomas Mullis and Patrick Stegemann for the languages per market | Translate & Adapt with AI translation, reviewed by a native speaker per market (BLAC-6180) | T4 |
14 | Checkout customisations (PO number, shipping contact, VAT ID display) need checkout UI extensions, which are Plus only: is the new store on the Plus organization from day one, and who sets up the dev store? | Kristy, 22Bits | Yes, as an expansion store in the Plus organization; dev store in week 1 | PL3, PC5 |
15 | A Liquid store tracks through Shopify customer events and pixels, not GTM in Nuxt. Does the analytics team accept that, and is the consent banner OneTrust or Shopify's? | Julia Schopka, Kristy | Shopify web pixel plus GA4 through Shopify's Google channel; consent through Shopify's customer privacy API | T5 |
16 | Which integration platform carries the Pipedrive, Shopify, ERP and Klaviyo sync, Make or n8n, and who licenses and runs it? | Alexandra Schmitz | Keep Make for wave 1, re-pointed | PL6 |
17 | Is there a designer for the theme, or is Brand 2.0 limited to tokens, logo and typography on a Horizon theme? Sen (2026-10-23): no designer is assigned so far | Kristy, Phil Smith | Tokens and typography only | T2 |
18 | Who owns the legacy CMS switch-off date, BLAC-6012 or BLAC-6186, and is the Cloudflare router's legacy sitemap fallback (BLAC-3340) removed in the same change? | Andrea Zimmerli, Sen, Kristy | Switch-off right after the CH wave; the router fallback goes with it | M3 |
19 | Which apps and contracts are cancelled per wave (wholesale app, login app, payment hiding app, CembraPay on the old store, Vercel project), and who holds the list and the savings in the business case? | Sen, Kristy | 22Bits inventories them during the spike; the savings go into the business case | M3 |
21 | Is there a Pro or dealer application form on blackroll.com that must now point to the B2B store, and does the separate B2B form from ADR-043 exist anywhere? | Alexandra Schmitz, Sen | The application form lives in the B2B store and posts to Pipedrive; nothing in Craft | CI1 |
22 | What does "running in optimization mode by 31 January" (slide 1) mean if the DE wave is after January? At the kickoff Kristy described optimization mode as the phase where the platform is used to grow revenue | Kristy | CH live and handed over; DE and BNL are the next step | S1 |
23 | Confluence documentation and a decision log for this project (slide 11): which space, and do ADRs for BLAC-6171 and the content decision go into the ADR register? The B2B team works in Asana, not Jira (Sen, 2026-10-21): where are decisions and tickets tracked so the B2B team sees them? Sen checks with Kristy; topic for the steering decisions | Kristy, Sen, Ramon Nagelhout | ADR register, written by 22Bits, reviewed by Ramon Nagelhout; this document is the working log until then | all |
24 | Access list (slide 10): Plus organization admin, Pipedrive, Klaviyo B2B, MyFactory test, Xaidat, GA4, PIM. Shopify store admin access, including pro.blackroll.com, is in place. Who collects the rest and by when? | Kristy, Sen | 22Bits sends the list; access within a week | S5 |
25 | Is France a B2B market today? Which shop do French customers order in, how are they created and priced, and does France belong to a wave? Sen named Benelux and France together (2026-10-23) | Sen, Patrick Stegemann | France stays as it is today until S8 decides | S3, S8 |
26 | Do CH customers have a MyFactory record? Sen (2026-10-23): in CH customers are created in Shopify first and then in MyFactory, and prices are set per product group. ADR-060 says CH dealers have no ERP record and get one blanket discount | Teoman Lam, Sen | Checked in the prep call with Teo; until then the CH wave plans with companies created in Shopify | E3, P1 |
27 | Which ERP replaces MyFactory, and when? Kristy (2026-10-26): a new ERP comes later, and price management in the ERP becomes part of that integration (P2) | Kristy, Teoman Lam | MyFactory stays through this project; nothing in the B2B store depends on MyFactory-specific logic | P2, E1, E4 |
More open points on the individual epics are in Epic Questions.