Shopware Migration

Appearance

Executive Summary ​

  • SXSW Core Platform: +21 stories completed this week (275/708, 39%). Velocity slightly lower than prior weeks (3% vs. 4.5%), but 85 tickets in review suggest a burst is imminent. Infrastructure initiative needs attention at 48% done.
  • Arrow Graph & Frontend: Ticket boards show no movement, but this is misleading — significant work is happening on untracked boards and in active PRs/merges. Supergraph has 83 commits from 7 authors this week. We expect these to close out as merges land in the coming days.
  • Tracking Gap: Arrow work is spread across boards not currently in our tracking scope. Recommend adding these boards to get an accurate picture next week.
  • BU Progress: Peirce Phelps leads frontend advancement (7/8 areas done). Other BUs remain early-stage. Data migration tracking shows 0% but Peirce Phelps Customers is now WIP.

1. Shopware Platform - SXSW Initiatives ​

Current State: 275/708 stories complete (39%)

Week-over-Week: +21 stories (+3% vs. +4.5% previous weeks)

The core platform continues to advance. Initiative 4 (Cart & Checkout) at 39/135 (29%) is the area most needing acceleration to unblock downstream frontend work.

In Review Pipeline: 85 SXSW tickets in review state represent 12% of total scope — if these clear (and they should given normal review cadence), we'll see a meaningful velocity jump next week. 14 in Active Development with 240 still in Discovery means the funnel needs continued attention.

Action Item: The 9 blocked tickets and unassigned testing work (SXSW-91) need coordination attention to prevent compounding as more BUs attempt parallel deployment.

2. Arrow Domain API / Graph ​

Current State: 51/63 stories complete (81%)

Week-over-Week: No ticket movement on tracked boards — but active development is happening elsewhere.

The supergraph shows 83 commits from 7 active developers this week. Commit activity reveals substantial work on:

  • Catalog flow bug fixes (CESW-433)
  • Scope creation for ECMD (ARROW-2460/2461)
  • Operating company migrations (W1DA-217)
  • Cart/checkout mutations (W1DA-210)

What's Happening: Much of this work lives on boards we aren't currently tracking (CESW, W1DA, etc.) and in open pull requests. The team is actively working through the supply sync graph merge/rework — once those PRs land, we expect a batch of ticket closures in the coming days.

Recommendation: Add the CESW and W1DA boards to our tracking scope so next week's report reflects the actual state of work.

Remaining Work: 12 stories outstanding include AHRI data integration, company user data layer, and permissions checks — important items but the team is actively working toward them.

3. Arrow Frontend / Open Components ​

Current State: 376/426 stories complete (88%)

Week-over-Week: No ticket movement on tracked boards, but active PR work in progress.

Frontend repository shows 32 commits (2 authors, Pablo Romero dominant) with work focused on:

Analysis: Current work is infrastructure/tooling improvements that enable faster feature delivery. These are in PRs and expected to merge shortly, which will close associated tickets. The 50 remaining stories include customer-facing features (AHRI PDP, Order Approvals, Compare, Quote flow) — but with the foundation work landing now, the team is positioned to move through these.

Tracking Note: Some frontend feature work may also be tracked on boards outside our current scope. Worth confirming with the team which boards carry their remaining work items.

4. Arrow Infrastructure / Cross-cutting ​

Current State: 78/101 stories complete (77%)

Week-over-Week: No movement on tracked boards.

Key remaining items:

  • Homans-to-Arrow migration: 0/8 started (ARROW-2404)
  • Performance tuning: 12/18 done but paused
  • Gemaire support: 4/6 done

CI/CD Blocker: The 6 deployment tickets (SXSW-484–489, assigned to Chris Nitchie) remain the key bottleneck for Arrow Shopware BU environments. This is a legitimate blocker that needs resolution — either additional resources or redistribution of work.

5. BU Environment Deployment ​

Arrow Magento Environments: All 7 BUs have Local done, all in Ordin WIP, only Gemaire reached Staging. Production is NYS across the board.

Arrow Shopware Environments: 6 of 7 BUs show "CI/CD Blocked" — only Gemaire in "Active Development" status. This ties directly to the SXSW-484–489 cluster above.

Shopware Core Environments: All 7 BUs paused at Local/Ordin Done, none progressing to Staging.

Assessment: Environment provisioning is a real bottleneck. Resolving the CI/CD blocker is the single highest-leverage action to unblock multiple BUs simultaneously.

6. BU Frontend Implementation ​

Peirce Phelps: Most advanced with 7/8 areas complete, only Account in WIP.

Gemaire & Carrier Enterprise: All 8 areas marked WIP — active exploration underway, likely dependent on Arrow Frontend PR merges landing.

All Other BUs (Homans, ECMD, Baker, LATAM): NYS — expected to sequence after lead BUs validate the approach.

Note: BU frontend work depends on the Open Components work currently in PRs. As those merge, expect BU-level progress to accelerate.

7. Data Migration Status ​

Status: Largely not started across BUs, with Peirce Phelps Customers now in WIP — the first sign of migration work beginning.

Context: Data migration is a long-lead effort and starting it now (even in parallel with ongoing platform work) is the right call. The team should consider synthetic data approaches to validate migration tooling while waiting for complete environment availability.

Recommendation: Begin migration tooling development and validation in parallel rather than waiting for full environment readiness.

8. Repository Activity Analysis ​

ecommerce-supergraph: Strong commit velocity (83 commits, 7 authors) with active branches (182). Work is in flight and expected to land as PRs merge in the coming days.

peirce-frontend: Focused commits (Pablo Romero) on technical debt/refactoring — necessary foundation work for upcoming feature delivery.

peirce-shopware & watsco-ui-watsco: Clone timeouts suggest large repos impacting tooling — worth investigating repo configuration.

Key Insight: The gap between commit activity and ticket closure is primarily a tracking visibility issue, not a productivity issue. Work is happening on boards outside our current scope and in open PRs awaiting merge.

Blockers & Dependencies ​

Critical Path Blocker: SXSW-86 (Domain Schema Design) blocking 3 downstream tickets, assigned to Paul Briscoe — needs a status check.

CI/CD Blocker: 6 deployment tickets (SXSW-484–489) assigned to Chris Nitchie, blocking all Arrow Shopware BU progress. This is the single biggest leverage point to unblock.

Pipeline Note: ARROW project has 246 tickets in "Open" state vs. 8 "In Progress" — likely reflects work tracked on other boards rather than a true funnel constraint.

Recommendations ​

  1. Expand tracking scope — Add CESW, W1DA, and other Arrow-adjacent boards to our weekly tracking so the report reflects actual work in progress
  2. Unblock CI/CD deployment — Redistribute SXSW-484–489 tickets or add resources to Chris Nitchie; this is the single highest-leverage action
  3. Confirm Arrow PR timeline — Get explicit ETA on the supply sync graph merge and associated ticket closures expected this week
  4. Begin data migration tooling — Start parallel development with synthetic data rather than waiting for full environment readiness