Known Gaps & Roadmap
Honest list of what’s identified but not yet resolved — kept here rather than buried, so partners see the same picture the team is working from.
1. Wash-quota-vs-calendar mismatch
Covered in detail in Wash Job Generation. When a customer’s preferred days produce more occurrences than their plan grants in a 30-day window, the last occurrence silently gets no wash — looking like a missed one. Proposed fix: surface the cutoff in the customer app (show that date as “next cycle” instead of leaving it blank). UI-only, no change to pricing or period length.
2. Pricing fairness when occurrences fall short of the plan quota
The mirror-image case: if a customer’s preferred days yield fewer occurrences than their plan’s nominal wash count in a given period (short month, a day excluded, holidays), they’re still charged the full flat price for fewer washes than the plan name implies. This is a business decision, not a technical one — keep flat pricing regardless of delivered count (current behavior), or adjust. Not yet decided.
3. Admin card grouping — the all-future edge case
The vehicle-grouping fix (see Admin Experience) assumes there’s usually a period currently in force to anchor the main card on. In the narrow window where a vehicle has no period in force yet (e.g. right after an admin bulk-renews ahead of time, before the new period’s start date), the “primary” card falls back to that future period and still shows the pre-activation grace/washes display quirks. Rare in practice, not eliminated.
Recently resolved (for reference)
- Admin dashboard cards now group by vehicle instead of listing every period flat.
- Grace-period urgency in the admin UI now matches the 7-day customer reminder window instead of showing alarm styling from day one.
- Subscription activation/renewal/pause/expiry no longer waits for the 3 PM Cairo operational-sweep gate — split into an independently-timed lifecycle sweep.