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. Pricing fairness when occurrences fall short of the plan quota

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. Note this is now only a one-directional gap — see “recently resolved” below for the upper-bound side, which no longer applies.

2. 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.
• Wash-quota-vs-calendar mismatch (used to be listed here as gap #1): the plan’s wash count is no longer a hard ceiling — every preferred-day occurrence that falls inside the 30-day window now gets a wash, even when that’s more than the plan’s nominal count. The old “last occurrence silently gets no wash” behavior no longer happens.
• Auto-renewal no longer skips a customer whose ending period wasn’t paid — it always creates the next period and flags an admin to follow up instead of silently letting the schedule lapse (see Renewal Flows).
• Grace-period expiry no longer auto-pauses a subscription — it flags the subscription as overdue and hands the pause decision to an admin (see Billing & Grace Period).
• Missed-wash retries are now capped at one attempt — a wash that’s missed twice is marked Missed instead of retrying indefinitely, and an admin is notified to follow up with the customer (see Subscription Lifecycle).