Shopware Migration

Appearance

Executive Summary ​

  • SXSW platform steady at 56%: +45 completions week-over-week (511/906) with only +3 scope growth—recovery from SupplySync launch stabilization, velocity returning to ~6 stories/day sustainable pace
  • CESW board reaches 79% completion: +30 stories (324/410) with +25 scope—tracking volatility persists but real work evident (Blake: 32 commits, Emil: 58, Scott: 36 commits week)
  • Review pipeline crisis deepening: 81 items in review states (down from 125 but still critical), 19 stale tickets >30 days with P90 at 89 days—"Development Complete" median holding at 5 days but tail stretching to 92 days
  • Data migration shows false progress: All 6 BUs now "WIP" on Customers but only Peirce Phelps actually "Done"—WIP inflation masks real stagnation with 5 weeks to production and 35 categories still NYS
  • Repository velocity remains strong: 408 commits across 16 repos from 20+ contributors, but scattered effort pattern continues—no concentrated push on critical path items
SXSW  [████████████████░░░░░░░░] 56% (511/906)
CESW  [███████████████████░░░░░] 79% (324/410)
W1DA  [████████████████░░░░░░░░] 65% (110/168)
ECMD  [██░░░░░░░░░░░░░░░░░░░░░░]  8% (25/323)
GSHOP [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/33)
BSWM  [██████░░░░░░░░░░░░░░░░░░] 10% (23/234)

1. Shopware Platform - SXSW Initiatives ​

Current State: 511/906 stories complete (56%)

Week-over-Week (vs. 2026-06-30): +45 completed, +3 scope—velocity recovered to 6.4 stories/day from prior 1.2/day post-launch dip

Analysis: SXSW shows healthy recovery from SupplySync.com stabilization period. The +45 completions with only +3 scope growth is the best ratio we've seen in weeks, suggesting requirements are finally stabilizing and team is burning down backlog faster than discovering new work.

Pipeline Analysis:

  • 51 in review (down from 64)—review throughput improving
  • 16 in active dev (up from 15)—capacity slightly expanding
  • 37 development complete (unchanged)—steady handoff rate
  • 14 in review (down from prior)—clearing aged items
  • 273 in Discovery (unchanged)—funnel still stalled

By Initiative (showing meaningful deltas vs. last week):

  • Infrastructure & Architecture: 100/227 (44%)—+1 story, still lagging foundational work at 44%
  • Authentication: 33/34 (97%)—+1 story, essentially complete
  • Cart & Checkout: 81/143 (57%)—+10 stories, critical path advancing
  • Account Management: 82/130 (63%)—+13 stories, strong progress
  • Integrations: 74/118 (63%)—+19 stories, most active area
  • Specialized Features: 21/71 (30%)—+1 story, lowest completion %

Blocker Status:

  • 17 blocked items (unchanged)—Punchout plugin epic still blocking 11 items
  • No progress on clearing blockers despite 45 completions elsewhere

Key Observations:

  • Account Management jumped 13 stories—Blake Saunders' work on user permissions and multi-super-user support shipping
  • Integrations +19 stories is largest single-initiative gain—Emil Stewart's PlaceOrder and checkout integrations landing
  • Infrastructure still at 44%—this foundational gap will impact all BU deployments

Velocity Projection: At 6.4 stories/day sustained, SXSW will complete in ~62 days (early September 2026). This aligns with production cutover timeline but leaves zero buffer for slippage.

2. CE Shopware (CESW) - Tracking Volatility Continues ​

Current State: 324/410 stories complete (79%)

Week-over-Week (vs. 2026-06-30): +30 completed, +25 scope—tracking still unstable but forward progress evident

Analysis: CESW continues to show wild swings (294→324 stories, 385→410 scope) but underlying work is real. The +30/-25 net suggests board consolidation events are settling and we're seeing actual delivery velocity.

Repository Activity (2026-06-30 to 2026-07-07):

Active Epics (closed this week based on commits):

  • Checkout/Cart (CESW-44): 35/35 (100%)—COMPLETE, Emil's major milestone
  • Bectran (CESW-34): 2/2 (100%)—COMPLETE, Scott finished
  • CommercialCurbAdapter (CESW-45): 4/4 (100%)—COMPLETE, Emil wrapped
  • PlaceOrder (CESW-85): 9/17 (53%)—Emil in review, major work landing
  • Lists (CESW-72): 2/10 (20%)—Blake actively developing
  • Avalara (CESW-713): 3/5 (60%)—Scott in review

Pipeline Health:

  • 39 items in progress (consistent for 5+ weeks)—team at capacity ceiling
  • 14 in code review—healthy handoff rate
  • 6 blocked—down from 8 last analysis

Key Achievement: Three major epics shipped this week (Checkout/Cart, Bectran, CommercialCurbAdapter)—real delivery happening despite board chaos.

Recommendation: Continue tracking via repository activity and epic closure rather than story counts. Team is delivering despite Jira instability.

3. W1DA (Domain API) - Board Still Unreliable ​

Current State: 110/168 stories complete (65%)

Week-over-Week (vs. 2026-06-30): +14 completed, no scope change—first stable week in month

Analysis: W1DA finally shows a clean week with +14 completions and zero scope churn. This may indicate board consolidation events are complete and we're back to tracking real work.

Repository Activity:

  • ecommerce-supergraph: 63 commits (Mitchell Cowie: 8, Gabriel Guzmán: 23, Sebastian Poblete: 8, Robert Dumitru: 15)
  • Key work: Offer-backed pricing/inventory (DOMAIN-321–DOMAIN-330), Cart mutations (DOMAIN-360), Context propagation (DOMAIN-253)

Active Epics:

Status: Board appears stabilized. Real velocity: ~9 commits/day Domain API work.

4. ECMD Shopware (ECMDSW) - Full Scope Onboarded ​

Current State: 25/323 stories complete (8%)

Week-over-Week (vs. 2026-06-30): +3 completed, +259 scope—full project scope added to board

What Happened: ECMD added the full scope of their BU migration to the board. This is a planning maturity step — not a crisis. The new stories represent the complete feature set required for the ECMD migration, most of which map to platform infrastructure and frontend boilerplate work that is already in place.

Key Context: Much of the Shopware/Domain infrastructure is shared and already built. The frontend has been largely developed in the boilerplate (watsco-frontend-boilerplate). Most of these 259 new tasks will be "check the box" verification/configuration tasks. Expectation: majority marked complete within 2 weeks as teams validate existing capabilities against ECMD-specific requirements.

New Epics Added:

  • Cart & Checkout (0/40), Account Management (0/63), Specialized Features (0/76)
  • Integrations (0/11), Branch Management (0/7), Content Management (0/10)

Repository Activity:

  • ecm-supergraph: 9 commits (Lucian Miculescu, Sebastian Poblete)
  • Work: Customer migration, Offer integration

Assessment: Track over the next 2 weeks to validate the "check the box" hypothesis. If completion rate doesn't accelerate dramatically, then resourcing needs revisiting.

5. Gemaire Shopware (GSHOP) - Still Zero After 6 Weeks ​

Current State: 0/33 stories complete (0%)

Week-over-Week: +1 scope, 0 completed—unchanged for 6+ weeks

Repository Activity:

  • gem-headless: 4 commits (dbogdanowicz)—Arrow connector for cart API
  • gem-shopware: 4 commits (girish.assudani)—Customer migration import, permissions import

Critical Finding: Repository shows active work on customer migration and cart integration, but GSHOP board shows 0 completions for 6+ weeks. This is a complete tracking disconnect.

Evidence of Real Work:

  • Customer import script written and committed (girish.assudani)
  • Checkout preferences migration implemented (girish.assudani)
  • Arrow cart API connector built (dbogdanowicz)

Root Cause Analysis: Commits reference different project codes:

  • Commits: No GSHOP ticket references
  • Work happening in separate tracking system (likely legacy Gemaire project)
  • GSHOP board may be newly created but not yet adopted by team

Recommendation:

  1. Immediate meeting with Gemaire team lead to audit tracking
  2. Either migrate work to GSHOP board or retire board as "not started"
  3. If work is real, GSHOP is actually ~15-20% complete based on commit patterns (customer migration, cart API, imports)

6. Baker Shopware (BSWM) - Full Scope Onboarded ​

Current State: 23/234 stories complete (10%)

Week-over-Week (vs. 2026-06-30): +2 completed, +202 scope—full project scope added to board

What Happened: Same pattern as ECMD — Baker added the full BU migration scope to their board. The new 202 stories represent the complete Baker feature set. Like ECMD, most of these map to shared infrastructure and boilerplate frontend work that already exists.

Key Context: Baker Headless App epic (the original active work) went from 19/25 to 21/24 — real progress. The 28 new epics (AHRI, Warranty, Parts Lookup, StockPro, Order Approvals, etc.) are feature verification tasks against the shared platform. Expectation: majority marked complete within 2 weeks.

Repository Activity: baker-shopware showing Nick Rolando's setup work from prior weeks.

Assessment: Healthy sign that Baker is formalizing their full scope. Watch for rapid completion over next 2 weeks as shared capabilities are validated.

7. Arrow - Frontend / Open Components ​

Current State: 380/426 stories complete (89%)

Week-over-Week: No change (frozen for 3+ weeks)

Analysis: Arrow Frontend board remains frozen despite 60 commits this week in watsco-frontend-boilerplate (Lino Rallo, Gabriel Guzmán, Tyler Hawkins). Work is happening but not tracked in this board.

Repository Activity:

Status: Board deprecated. Frontend work now tracked in BU-specific boards (CESW, BSWM, GSHOP).

8. Arrow - Infrastructure / Cross-cutting ​

Current State: 84/106 stories complete (79%)

Week-over-Week (vs. 2026-06-30): +3 completed, +5 scope

Analysis: Arrow Infrastructure shows modest progress in-board, but significant work is happening outside tracked tickets:

  • CIDR block allocation underway for new environments
  • Infrastructure architecture diagrams being produced for the target state
  • CE Staging site has started — first BU to reach staging environment

Active Epics:

  • Demo Environment Bugs: 23/28 (82%)—unchanged
  • Performance Tuning: 12/18 (67%)—unchanged
  • Homans to Arrow migration (ARROW-2404): 4/13 (31%)—+3 stories this week, accelerating

CI/CD Status: CE staging environment work has begun. Mid-July target for broader staging access remains on track.

Concern: Homans migration showing progress but other infrastructure work stalled. Staging restart plan status unclear with 1 week to target date.

9. BU Environment Deployment - No Change ​

Arrow Shopware Environments:

  • 5 BUs still "CI/CD Blocked" (SXSW-484–SXSW-489)—unchanged for 8+ weeks
  • Gemaire: "Active Development"—only BU progressing
  • LATAM: "CI/CD Blocked" (SXSW-486)

Shopware Core Environments: All 7 BUs remain "Paused" at Local/Ordin Done—unchanged for 7+ weeks.

Arrow Magento Environments:

  • Gemaire: Staging Done—most advanced
  • Carrier Enterprise: Staging WIP—only other BU progressing
  • All others: Ordin WIP

Timeline Check:

  • Mid-July staging restart: 7 days away
  • Mid-August production cutover: 5 weeks away

Risk Assessment - CRITICAL:

  • 8-week pause on staging environments means zero integration validation for 8 weeks of dev work
  • 5-week runway to production is insufficient for:
    • Staging environment smoke tests (1 week)
    • Integration issue discovery and fixes (2-3 weeks)
    • UAT and business validation (1-2 weeks)
    • Production deployment rehearsal (1 week)

Minimum timeline: 5-7 weeks needed, but only 5 weeks available. Production cutover will slip to late August or early September.

Recommendation:

  1. Confirm staging restart happens this week (July 8-14)
  2. Pre-stage rollback procedures and smoke test plans NOW
  3. Communicate production date risk to stakeholders immediately
  4. Consider parallel staging tracks (BU-by-BU) to compress timeline

10. BU Frontend Implementation - Minimal Movement ​

Peirce Phelps: 7/8 complete (Account WIP)—unchanged for 7+ weeks

Gemaire & Carrier Enterprise: All 8 areas WIP—unchanged for 4+ weeks

All Others: Not started

Repository Activity:

  • peirce-frontend: 13 commits (Lino Rallo)—Peirce sync with boilerplate
  • watsco-frontend-boilerplate: 60 commits (multiple contributors)—Homans clone, Apollo refactor
  • baker-headless: 60 commits (Tyler Hawkins, Gabriel Guzmán, German Berselli)—Domain API migration
  • homans-next-frontend: 16 commits (Lino Rallo)—new repo, Homans initial clone
  • homans-shopware: 3 commits (Josh L)—newly tracked, SwagPayPal setup and module alignment with Peirce environment

Key Finding: Homans frontend launched this week—new homans-next-frontend repo created with initial styling and home page. This is the first new BU frontend to start since Peirce.

Analysis: Frontend work is happening (Homans, Baker Apollo migration) but most BUs remain stalled. The 7+ week freeze on Peirce Account suggests a persistent blocker.

Recommendation:

  1. Audit Peirce Account blocker—7+ weeks is too long for single epic
  2. Accelerate Homans, Baker, ECMD frontend starts—5 weeks to production insufficient for new builds
  3. Consider reducing frontend scope to core flows only (browse → cart → checkout)

11. Data Migration - False Progress Alarm ​

Current State:

  • Only 1 of 42 categories actually Done: Peirce Phelps Customers
  • 6 of 7 BUs show Customers "WIP": Homans, ECMD, Gemaire, Baker, CE (only LATAM still NYS)
  • All other categories (35 of 42) remain NYS: Companies, Products, Orders, CMS Content, Lists

Week-over-Week Changes:

  • Homans Customers: NYS → WIP—NEW
  • ECMD Customers: NYS → WIP—NEW
  • Gemaire Customers: NYS → WIP—NEW
  • Baker Customers: NYS → WIP—NEW
  • CE Customers: NYS → WIP—NEW

Critical Analysis - DATA QUALITY ISSUE:

Someone mass-updated 5 BU customer migrations from NYS → WIP this week without corresponding repository evidence. Let's audit the claims:

Repository Evidence (2026-06-30 to 2026-07-07):

  • Peirce: Joshua LaRose committed customer sync (SXSW-909)—LEGIT
  • Homans: No commits visible in captured data—UNVERIFIED
  • ECMD: Lucian Miculescu committed customer migration work (ecm-supergraph, sw-plugin-account-structure)—LEGIT
  • Gemaire: girish.assudani committed customer import scripts (gem-shopware)—LEGIT
  • Baker: No commits captured (baker repos timed out)—UNVERIFIED
  • CE: Blake Saunders committed account/customer work (cesw)—LEGIT

Verdict: 3 of 5 new "WIP" statuses are backed by repository evidence (ECMD, Gemaire, CE). 2 are unverified (Homans, Baker) but repos may have timed out.

However, the real problem is definition of "WIP":

  • WIP should mean: Migration script written, tested, and in active data transfer
  • WIP actually means: Someone started thinking about it

Velocity Reality Check:

  • Week-over-week: 0 → 5 BUs moved to WIP, but 0 → 1 moved to Done
  • Required velocity: 35 categories in 5 weeks = 7 categories/week
  • Actual velocity: 0.14 categories/week (1 Done in 7 weeks)
  • Gap: 50x current velocity needed

What This Means:

  • At current pace (1 Done / 7 weeks), migrations will complete in 245 weeks (September 2031)
  • Even if all 6 "WIP" categories complete next week (optimistic), still need 36 categories in 4 weeks = 9/week sustained
  • Mid-August production cutover is impossible without immediate emergency intervention

Emergency Recommendations:

  1. THIS WEEK: Audit all "WIP" customer migrations—require evidence of working script + test data transfer
  2. FREEZE scope: Deprioritize Companies, Orders, CMS, Lists—focus only on Customers + Products (minimum viable)
  3. Parallel execution: Spin up dedicated migration team per BU, work in parallel not sequential
  4. Accept partial launch: Go live with Customers + Products only, backfill other categories post-launch
  5. Communicate production date slip: Mid-August is not achievable, need to push to late September minimum

12. Review Pipeline Aging - Critical Bottleneck Persists ​

Current State: 81 items in review states (down from 125 last week but still critical)

Aging Analysis:

  • Development Complete: 37 items, median 5 days, P90 35 days, max 92 days
  • In Review: 24 items, median 34 days, P90 89 days, max 90 days
  • Ready for Review: 4 items, median 27 days, P90 31 days, max 31 days
  • Under Code Review: 16 items, median 0 days, P90 5 days, max 5 days

Stale Tickets (>30 days in review):

  • SXSW-391: Domain Resolver - 92 days (Mitchell Cowie)
  • SXSW-595: Cross-BU Feature Analysis - 90 days (Cleo Hister)
  • SXSW-649, SXSW-625: Cross-BU Feature Analysis - 89 days (Cleo Hister)
  • SXSW-744: Parts List Analysis - 84 days (Cleo Hister)
  • 10 Domain API tickets: 31-56 days (Mitchell Cowie, Gabriel Guzmán)

Analysis:

  • "In Review" is where tickets die: Median 34 days, max 90 days—this is unacceptable
  • Development Complete moves reasonably: Median 5 days suggests handoff works
  • Review capacity is the bottleneck: 24 items stuck with P90 at 89 days

Root Cause:

  • Cleo Hister has 10 stale feature analysis tickets (56-90 days)—needs review capacity or tickets should close
  • Mitchell Cowie has domain resolver at 92 days—single blocker holding up downstream work
  • Domain API tickets (31-56 days) suggest review backlog on API contract changes

Immediate Actions:

  1. Cleo's tickets: Batch-close feature analysis items or assign second reviewer
  2. Mitchell's SXSW-391: Escalate to tech lead for forced closure or emergency review
  3. Domain API backlog: Assign dedicated API reviewer (Mitchell or Gabriel) for Domain tickets

Process Fix: Implement SLA:

  • Development Complete → In Review: 7 days max
  • In Review → Done: 14 days max
  • Any ticket >21 days auto-escalates to tech lead

13. Repository Activity & Team Velocity ​

Week Summary (2026-06-30 to 2026-07-07): 408 commits across 16 repos, 20+ contributors

Top Contributors:

  • Emil Stewart: 58 commits (cesw, supergraph, sw-plugin-authorize-net)—Order placement, Authnet, tax
  • Lino Rallo: 60 commits (boilerplate, peirce, homans, baker)—Homans launch, Apollo refactor
  • Blake Saunders: 56 commits (cesw, supergraph, sw-plugin-lists)—Lists, permissions, price restrictions
  • Scott Kovach: 36 commits (cesw, supergraph)—Avalara, quotes, lead conversion
  • Gabriel Guzmán: 57 commits (supergraph, boilerplate, baker, homans)—Domain API, frontend migrations
  • German Berselli: 20 commits (supergraph, boilerplate, baker, homans)—Frontend work

Repository Breakdown:

  • cesw: 126 commits (Emil: 36, Blake: 32, Scott: 27)—most active repo
  • ecommerce-supergraph: 138 commits (Gabriel: 23, Robert: 15, Emil: 11)—Domain API + integrations
  • watsco-frontend-boilerplate: 34 commits (Lino: 17, Gabriel: 11)—Homans clone, refactors
  • peirce-frontend: 13 commits (Lino)—Boilerplate sync
  • homans-next-frontend: 16 commits (Lino)—Initial clone
  • baker-headless: 34 commits (Gabriel: 10, German: 9)—Apollo migration
  • peirce-shopware: 13 commits (Rob Simmons, Htun Htun Htet, Cristian)—Delivery, fees, employee import

Velocity Analysis:

  • Sustained pace: 408 commits / 7 days = 58 commits/day—healthy, stable velocity
  • Broad distribution: 20+ contributors shows team is engaged, not bottlenecked on 2-3 people
  • But scattered effort: No repo shows >140 commits—suggests team is context-switching across many priorities

Repository Coverage:

  • Active: cesw, ecommerce-supergraph, watsco-frontend-boilerplate, peirce-shopware, homans-next-frontend, baker-headless (6)
  • Inactive: gem-headless (4 commits), gem-shopware (4), ecm-supergraph (9), sw-plugin-* (13 total)—6 more repos with light activity
  • Timed out: dev-shopware, peirce-magento—couldn't capture data

Concern: Only 2 repos show >100 commits/week (cesw, supergraph). This suggests:

  1. Work is fragmented across too many codebases
  2. OR repos have been split too granularly (microservices tax)
  3. OR team size doesn't support parallel work across 16+ repos

Recommendation:

  • Consolidate effort: Pick 3-4 critical repos per sprint, ignore the rest
  • Track by epic, not repo: Many epics span multiple repos—track epic closure, not commit distribution
  • Accept repo sprawl: With 7 BUs + platform + frontend + plugins, 16