For the calls with the Shopify agency + Helmuth (Tue 2 Jun) and Helmuth (Wed 3 Jun). Fill as you go — notes autosave in this browser. At the end, hit “Build notes → copy” and paste into an email to yourself.
Firm Intex switch-off date?
Only signal so far is “June–July 2026 / ~1–2 months.” Need a hard date — it sets everything.
Cutover style?
POS pilot store + date? Rollout order across the ~27 stores?
The most important slide — make sure nothing falls between you and the agency. Tick one per row; use the last column for the owner’s name / notes.
| Workstream | Agency | SJ | Gössl/Helmuth | Shared | TBD | Owner / notes |
|---|
What owns ORDERS, FULFILMENT & INVOICING post-Intex?
Biggest single decision — Shopify is commerce, not a full ERP. Swings ~6 backend components.
What does Intex do today that Shopify can’t — and where does it go?
Procurement, manufacturing/production, financial accounting, supplier orders, wholesale invoicing?
⚠️ INVOICING — who issues invoices after Intex? (Shopify? accounting package? the new ERP?)
Business-critical + BAO compliance. The e-commerce cutover can be perfect and still fail if invoicing has no home.
Definitive Location list + roles
Today Shopify has ONE Location (hardcoded “Graz”, gid …516046, in 8 places in my Worker code — must change). Need: central DC(s) + each store.
Ship-from-store for online orders — yes/no?
⚠️ PÖ & WDA warehouses — become Shopify Locations (not in online channel), or stay out entirely?
Today these are excluded from online stock via custom code. If they never enter Shopify, confirm their stock truly never needs to sell online (pop-up/event?).
How are opening inventory counts migrated into Shopify per Location?
One-time export from Intex per-warehouse → Shopify. Who does it, when, how reconciled?
⚠️ DPD label / fulfilment path in Shopify? (HARD blocker — orders can’t cut over without it)
Today labels run through Intex.
DDP / international duties (CH, UK, US) — preserved post-cutover?
Where are products (masters, variants, German descriptions) authored post-Intex?
⚠️ Product IMAGES — what’s the upload path once the Intex/Citrix/FTP pipeline dies?
Today images flow Intex FTP → Citrix → Mac → Xano. Photo studio needs a non-Intex path (Shopify Files / direct upload at product creation).
Price authority moves to Shopify (Admin/POS, incl. sale/compare-at)?
B2B / wholesale destination?
No Shopify B2B config exists today — “continuity” may be a greenfield build. Affects the tb.one feed + price tiers.
⚠️ Confirm tb.one will be sourced from SHOPIFY, not Intex.
It must read product/stock/price/orders from Shopify (the new source of truth). Wiring it to a dying Intex = throwaway.
Who builds the tb.one connection — me, the agency, a Tradebyte connector/app, or Tradebyte themselves?
Order / customer HISTORY — keep in Shopify, or archive + go-forward only?
Recommend: archive Intex history to durable storage for lookup + let Shopify own go-forward (bulk import is lossy; merging retail+online by email is a data-protection call).
⚠️ BAO 7-year retention — who exports ALL Intex order/invoice/customer financial history (incl. in-store) before Intex goes dark, and to where?
⚠️ MY data-loss gate — the Shopify-only enrichment that lives only in my Xano (not in Intex) must be in Shopify or archived BEFORE any of my cache tables are deleted.
German descriptions/SEO, sketch images, colour metaobject IDs, care symbols, collection rules, AI recommendations, wishlists/outfits. I own this extraction — flag it so the cutover doesn’t delete it out from under me. Confirm the sequencing with the agency.
Does Reever fully own returns post-cutover (retiring the Intex returns path)? Go-live before or after the order cutover?
Tick once the agency’s plan demonstrably respects each — these prevent oversell / double-pick / data loss.
What does the cutover need from me, and when?
My Intex-coupled crons (Task#1, stock sync, reconcilers, price sweeps) retire at cutover; storefront crons (recs, search, configurator, sale-tags, curator hub) repoint Xano→Shopify. The single hardcoded ‘Graz’ Location in my code must become multi-location.
Coordination cadence — how do we sync during the ~6-week cutover? (shared doc, weekly call, Slack/email?)