Vrida — Feature Catalog (Master Index)

Lock status + counts derive from DOCS_INDEX.md (the gated source). This catalog is the product-feature view; not in the per-lock gate — sync at phase boundaries.

Vrida is nursery-focused with dedicated Platform, Identity, Payments, Integrations, AI layers + Files and Search shared services. See individual module specs for full feature lists.

Platform & Service Layers

Module / Service	Schema	v1.0 status	Schema
Platform	platform	✅ Schema locked 2026-06-09	16 tables, 301 cols
Identity / Auth	identity	✅ Schema locked 2026-06-09	11 tables, 140 cols
Payments	payments	✅ Schema locked 2026-06-10	8 tables, 112 cols
Integrations	integrations	✅ Schema locked 2026-06-11	9 tables, 127 cols
AI / Intelligence	ai	🔧 Spec pending	—
Files (shared service)	files	✅ Schema locked 2026-06-11	3 tables, 43 cols
Search (shared service)	search	🔧 Spec pending	—

Note: the prior "Core / Platform" combined entry is retired. There is no core schema. Platform stands alone as Vrida's control plane.

Schema-Only Modules (no feature-spec file — schema is the spec)

Module	Schema	v1.0 status	Schema	Notes
Pricing	pricing	✅ Schema locked 2026-06-09	4 tables, 56 cols	Carved out of Inventory scope. Price lists, per-variant rules, customer/group assignments, quantity breaks. PricingService owns resolution.
Shared	shared	✅ Schema locked 2026-06-09	7 tables, 57 cols	Non-tenant global reference data. Seed-managed.

Nursery-Facing Modules

#	Module	Schema	v1.0 status	Schema	Feature count
1	Inventory	inventory	✅ Schema locked 2026-06-09	21 tables, 236 cols	94
2	Point of Sale	pos	✅ Schema locked 2026-06-10	19 tables, 279 cols	204
3	Customer Orders	orders	✅ Schema locked 2026-06-10	7 tables, 132 cols	149
4	Purchasing & Suppliers	purchasing	✅ Schema locked 2026-06-10	16 tables, 340 cols	134
5	Customer Management (CRM)	crm	✅ Schema locked 2026-06-09	8 tables, 107 cols	158
6	Reporting & Analytics	reporting	🔧 Spec pending (schema not yet locked)	—	146 features specced
7	Production / Propagation	production	✅ Feature-spec locked (schema pending, v1.2)	—	41
8	Customer-facing App	customer_app	✅ Feature-spec locked (superseded in direction — see Consumer Layer)	—	145
9	Multi-location	multi_loc	✅ Schema locked 2026-06-09	1 table, 21 cols	107 features specced
10	Settings & Admin	admin	✅ Schema locked 2026-06-10	11 tables, 145 cols	~99 (config-scope; HR/labor permanently out of scope)
11	Billing	billing	✅ Schema locked 2026-06-10 (merchant A/R + A/P)	8 tables, 113 cols	No feature-spec file — schema designed from seams. docs/modules/11_billing.md is the historical SaaS-subscription spec (Platform's now); retained for Platform subscription UX reference.
12	Audit & Compliance	audit	✅ Schema locked 2026-06-10	7 tables, 118 cols	108
13	Notifications	notifications	✅ Schema locked 2026-06-10	11 tables, 166 cols	128
14	Delivery & Logistics	delivery	⏸ Deferred (v1.5)	—	TBD
15	Services & Jobs	services	⏸ Deferred (v2.0)	—	TBD

Pre-redesign feature baseline (13 nursery-facing modules with feature specs): ~1,694 features. Feature count excludes platform/service layers (not counted as features) and the 3 schema-only modules (pricing, shared, billing).

Consumer Layer (post-v1.0 — direction only)

Direction agreed 2026-06-09. No module spec files exist or should be created until the merchant core is built.

Future module	Schema	Notes
Consumer	consumer	Platform-level Vrida consumer identity; social-login auth.
Rewards	rewards	Per-business loyalty: points, earning rules, tiers, expiry, redemptions.
Offers	offers	Business-issued or Vrida-issued discount/promo offers.
Consumer App	consumer_app	Consumer app experience. Supersedes the nursery-only 08_customer_app.md direction.

Module Spec Process

Each module spec follows this format:

1. Overview & target customer
2. Feature hierarchy (groups → features → notes)
3. Tier behavior matrix (Starter / Pro / Enterprise)
4. Database schema for the module
5. API contract (what other modules can call)
6. Events emitted and consumed
7. AI features in this module
8. Deferred items (for the module's future versions)
9. Explicitly out of scope