Product Roadmap & Known Fixes
Source: the PM's Roadmap sheet. This is the planned direction; each item should be validated against the actual repo state before being treated as done. Status values are the PM's (Planned / Picked / In Progress / Merged / Live / Pending / Upcoming).
All modules are being migrated to Next.js; fundamentally similar modules are being merged. Every migrated screen requires full data validation (see Data Validation Protocol below).
Completed merges
| ID |
Merge |
Result |
| A1.1 |
Customer Marketing + CRM Stats |
Unified marketing performance module (Merged) |
| A1.2 |
Customer 360 + Customer Insight |
Customer Intelligence module — RFM, 37 filters, profiles in one place (Merged) |
Pending merges
| ID |
Merge |
Priority |
Notes |
| A2.1 |
Campaigns + Journeys → Central Marketing Hub |
P0 |
One hub for manual + automated outreach |
| A2.2 |
Loyalty + Fraud → Loyalty & Trust |
P1 |
Fraud controls become native to loyalty config |
| A2.3 |
Reviews & Ratings + NPS → Customer Feedback & Sentiment |
P1 |
Unified sentiment layer |
Standalone migrations
| ID |
Module |
Priority |
| A3.1 |
Order 360 → Next.js |
P1 |
| A3.2 |
Digital Bills → Next.js |
P1 |
| A3.3 |
WhatsApp Chat → Next.js |
P1 |
| A3.4 |
WhatsApp Config → Next.js |
P1 |
Data Validation Protocol (MANDATORY per migration — all P0)
| ID |
Check |
What it enforces |
| A4.1 |
Data Point Logic Validation |
Every metric computes per the Product Logic Spec |
| A4.2 |
Data Composition Validation |
Breakdowns sum correctly (Customers = Transacting + Non-Transacting, etc.) |
| A4.3 |
Data Sync Time Validation |
Orders <5min, profiles <5min, points real-time, campaign stats <15min, RFM nightly |
| A4.4 |
Cross-Widget Integrity |
Same metric matches across widgets |
| A4.5 |
Regression Testing on Merges |
No feature silently dropped when merging modules |
| A4.6 |
Period Filter Consistency (P1) |
All widgets share default period + outlet filter (known inconsistency today) |
B. New Feature Requirements
Campaign & Segmentation (P0 headline items)
| ID |
Feature |
Priority |
Status |
| B1.1 |
Partial audience send on direct upload (%/n subset) |
P0 |
Planned |
| B1.2 |
Plug campaign layer into segmentation tab (filter→send on one screen) |
P0 |
Planned |
| B1.3 |
Customer Cohorts — check & deploy |
P0 |
Planned |
| B1.4 |
Cumulative campaign metrics widget (4 channel blocks) |
P0 |
Planned |
| B1.5 |
Filtration logics in Journeys (audience filters on automations) |
P0 |
Planned |
| B2.1 |
New-customer repeat-ordering funnel widget |
P0 |
Planned |
Previously identified enhancements (selected)
| ID |
Item |
Priority |
Status |
| B3.1 |
WhatsApp Partner API integration |
P0 |
Picked |
| B3.2 |
Wallet-balance campaign category |
P0 |
Picked |
| B3.3 |
Customer-ratings campaign category |
P0 |
Picked |
| B3.4 |
Enhanced media (video/doc/location) in WhatsApp |
P0 |
Picked |
| B3.5 |
Notification delivery & revenue reports |
P0 |
Picked |
| B3.6 |
Rename "Auto Campaigns" → "Journeys" (V1) |
P0 |
Picked |
| B3.7 |
Dynamic per-campaign ROI attribution window |
P0 |
Picked |
| B3.8 |
Click-rate tracking for WhatsApp |
P0 |
Picked |
| B3.9 |
Promo-code generation inside auto campaigns |
P0 |
Picked |
| B3.13 |
Meta TSP integration |
P1 |
In Progress |
| B3.15 |
Drip campaign sequences (multi-step multi-channel) |
P2 |
Planned |
| B3.16 |
Emailer automation drip |
P2 |
Planned |
| B3.18 |
Truecaller integration |
P2 |
Planned |
C. Membership V2 (phased)
| Phase |
Items |
| Phase 1 (P1) |
In-place plan versioning, menu-level member pricing, menu/cart toggle, menu+cart stacking |
| Phase 2 |
Promo+membership stacking modes, grace period after expiry, one-tap renewal |
| Phase 3 |
Virtual wallet benefit, loyalty multiplier (2x–10x) |
| Phase 4 |
Member-price teaser for non-members, child-outlet dashboard |
D. Loyalty Enhancements (recently shipped — Live)
| ID |
Item |
| D1.1 |
Tier downgrade logic (inactivity → downgrade, progress resets) |
| D1.2 |
Point expiration on downgrade (forfeit unredeemed) |
| D1.3 |
Per-order-type earning/burning rates |
| D1.4 |
Welcome points via KYC completion |
| D1.5 |
Refer & Earn program |
These map to shipped code: crons/loyalty_milestone_downgrade.js, commonFunctions/handleWalletPointsFlow.js, handleMilestoneUpgrade.js, rewardHelper.js. Validate in ../03-Modules/Loyalty/README.md.
E. Data Reliability & Known Fixes (open bugs)
These are real, PM-acknowledged production issues. New joiners should read them so dashboard discrepancies are understood, not "discovered" as surprises. Full engineering triage in ../13-CommonIssues/Known-Bugs-From-Roadmap.md.
| ID |
Bug |
Priority |
| E1.1 |
ROI calculation rectification |
P0 |
| E1.2 |
Loyalty metrics rectification |
P0 |
| E1.3 |
WhatsApp volume reports inaccurate |
P0 |
| E1.4 |
Various CRM statistics incorrect |
P0 |
| E1.5 |
Campaign builder budgeting & scheduling issues |
P0 |
| E1.6 |
Loyalty flow & automation issues |
P0 |
| E1.7 |
All 8 automated journey logics need verification |
P0 |
| E1.8 |
Digital bills report logic |
P1 |
| E1.9 |
AOV shows ₹0 in "Your Effective Offers" (should be Revenue/Redemptions) |
P1 |
| E1.10 |
Loyalty points 2-point discrepancy (Total ≠ Used+Available+Expired) |
P1 |
| E1.11 |
Loyalty microsite redemption flow issues |
P1 |
| E1.12 |
Layered filters: SKU/promo/audience intelligence in reports |
P2 |
How to use this roadmap
- New joiners: understand where the product is going (Next.js + merges) so today's monolith structure makes sense as a transitional state.
- Engineers: the "E" bugs and "A4" validation protocol are the acceptance bar for any dashboard/analytics work.
- QA: A4.5 (regression on merges) + the cross-widget integrity rules are your primary test charter.