GenX Battery — Product Status Report

Readiness Signal: 🟠 In Progress — Core markets live, Nordic launch blocked on multiple fronts.

The GenX Battery 3P product has completed its primary launch wave across DACH, Benelux, and France. ANZ is live. The open work represents a second wave targeting Nordic markets and ongoing app maturity improvements.

• DOC (34 tickets, 82%): The outstanding blocker is DOC-4290 — Finnish and Estonian QIG translations stale for 142 days. No active authoring is visible. If Nordic markets are a near-term target, this is a hard content gate. DOC-4821 (Nordic System Planning Guide) is also blocked, suggesting the Nordic documentation wave has stalled across multiple document types simultaneously.
• WEBP (12 tickets, 67%): WEBP-812 (product comparison page) has been in Internal QA for 125 days with no forward movement. Nordic product pages (WEBP-901) are in active development but will arrive before supporting documentation — a sequencing risk.
• CLOUD (31 tickets, 71%): CLOUD-1988 (GDPR data residency) has been in Legal Review for 107 days. EU data residency compliance is a regulatory hard gate for Nordic markets — Finland, Sweden, Denmark and Norway all fall under GDPR jurisdiction. Until this is resolved, GenX telemetry cannot be confirmed as compliant for those markets.
• APP (26 tickets, 54%): The lowest completion rate across all four projects. Five blocked tickets suggest systematic issues rather than isolated bugs. The commissioning wizard crash on iPhone 14 Pro (APP-1580, 87 days stale) is the most concerning — if installers cannot complete commissioning on a common device, it directly affects field adoption.

Conclusion: Core markets are live and stable. Nordic launch is blocked on at least three independent fronts: documentation (DOC-4290), GDPR compliance (CLOUD-1988), and app localisation (APP-1720). These need to be treated as a coordinated launch gate rather than individual ticket items.

Analysis of ticket age, assignee load, and status patterns across DOC, WEBP, CLOUD, and APP:

• Nordic documentation cluster — 3 tickets, same root cause: DOC-4290, DOC-4821, and APP-1720 are all blocked on Nordic-language content or routing. These were likely created as part of the same Nordic launch planning exercise but have since stalled independently. No single owner appears to be tracking them as a cluster. A dedicated Nordic readiness ticket or sub-project would help.
• CLOUD-1988 (GDPR) — 107 days in Legal Review: This is the longest-running active blocker in the snapshot. Legal review cycles at this length typically indicate either deprioritisation or a genuinely complex legal question. Given that CLOUD-2241 (Nordic telemetry routing) is also blocked, and APP-1720 (Nordic app strings) is blocked, the GDPR ticket is the root blocker for the entire Nordic wave. It needs immediate escalation.
• APP blocked ticket pattern — 5 tickets across 3 engineers: The distribution of blocked APP tickets across Colleague 10 and Colleague 11 suggests a shared upstream dependency (likely CLOUD-2198, the firmware v2.4 compatibility layer) rather than individual engineering capacity issues. Resolving CLOUD-2198 is likely to unblock multiple APP tickets simultaneously.
• WEBP-812 (comparison page) — 125 days in QA: Internal QA completion does not guarantee deployment. This ticket has been QA-complete for over four months with no deployment signal. This is a commercial gap — buyers comparing GenX to competitors have no dedicated comparison resource on the live site.

Key upstream-downstream dependency gaps identified across the DOC → WEBP → CLOUD → APP pipeline:

• CLOUD-2198 blocking APP — no resolution timeline visible: The firmware v2.4 compatibility layer has been on hold for 47 days. At least APP-1790 (TOU UI sync) and APP-1650 (Android 14 push notifications) are downstream of this. No comment thread indicates a target resolution date.
• GDPR blocking Nordic telemetry and app simultaneously: CLOUD-1988, CLOUD-2241, and APP-1720 all share a root dependency on EU data residency compliance being confirmed. These are tracked as separate tickets with no visible parent epic linking them. Risk of one being resolved without the others being updated.
• DOC Nordic gap has no downstream WEBP ticket staged: WEBP-901 (Nordic product pages) is in active development, but DOC-4290 (Finnish/Estonian QIG) has been stale for 142 days. If WEBP-901 goes live before the documentation is ready, users arriving from Nordic product pages will find no localised documentation in the doc centre.
• APP-1855 (homeowner onboarding redesign) in Design Review: This ticket is assigned to Achinthya Hemachandra and is in active review. It has dependencies on the updated app welcome screens being aligned with the revised onboarding content in DOC-5091 (homeowner guide update, also in review). These two tickets should be confirmed as aligned before either progresses to production.

Comment thread analysis across 103 tickets in DOC, WEBP, CLOUD, and APP:

• DOC-4290 (Finnish/Estonian QIG) — urgency expressed, still unresolved: A comment from Colleague 3 in November 2025 notes "translation vendor confirmed, awaiting source file sign-off." The source file sign-off has not been completed 142 days later. This is the strongest urgency signal in the snapshot — a commitment was made and not followed up.
• APP-1580 (iPhone 14 Pro commissioning crash) — installer impact signal: Comment from field team: "Two installers reporting this in DACH. Commissioning taking 2x longer as workaround." At 87 days without a fix, this is directly impacting installer experience in live markets. The bug severity appears to have been underestimated at triage.
• CLOUD-1988 (GDPR) — legal team engaged, no timeline: The last comment from Colleague 9: "Legal have reviewed and have follow-up questions — awaiting response." No date. Legal review cycles without a defined response SLA tend to expand indefinitely. Recommend setting a formal response deadline.
• APP-1855 and DOC-5091 (Achinthya Hemachandra) — both in active review, well-coordinated: Comment threads on both tickets show active cross-referencing between the homeowner guide update and the app onboarding redesign. This is a positive signal — the PM is actively managing the dependency rather than treating them as independent deliverables.
• Overall tone: The product is in a healthy state for its primary markets. The most concerning pattern is the Nordic launch cluster — three independent workstreams (docs, compliance, app) all stalled without a visible co-ordinating owner. Recommend a dedicated Nordic launch readiness sync to unblock these as a group.