36 lines
3.0 KiB
Markdown
36 lines
3.0 KiB
Markdown
# Delivery roadmap
|
|
|
|
Source: Mani Candles Commerce Platform specification and project pack created in the earlier project discussion. Stack: modular NestJS/TypeScript application, PostgreSQL/Prisma, with Redis workers and private object storage introduced when needed. Provider adapters isolate external integrations.
|
|
|
|
## Phase 1: Foundation and core commerce
|
|
|
|
- 1A (implemented): service bootstrap, configuration, database lifecycle, initial organization migration, health API, test/build baseline, team workflow.
|
|
- 1B (implemented; native CI and deployment configuration pending): authentication, sessions, recovery, users, configurable RBAC, organization access, approval status, audit events. Test denied access and cross-organization access.
|
|
- 1C (implemented; native concurrency CI pending): catalog, variants, collections, addresses, inventory ledger and reservations. Test concurrent reservation and stock reconciliation.
|
|
- 1D (core implemented; tax/shipping rules, payment enablement and native CI pending): cart, checkout, orders, coupons and pricing snapshots. Test money precision, discount eligibility, retries and transaction rollback.
|
|
- 1E: verified payments/refunds, shipping/tracking, returns, notifications and operational dashboard. Test signatures, replay, partial fulfillment and reconciliation.
|
|
|
|
## Phase 2: Internal operations
|
|
|
|
Suppliers, material/urli classification and compatibility, procurement, purchase orders, partial goods receipts, QC, invoices, supplier payments, private versioned documents and validation, BOM, production batches, consumption, wastage, packaging BOM and costing.
|
|
|
|
## Phase 3: B2B and white label
|
|
|
|
Business verification, price lists, MOQ, quotations, credit policies, samples, branding/artwork approvals, partner purchase orders, partial payments, custom candle requests and partner reporting.
|
|
|
|
## Phase 4: Growth channels
|
|
|
|
Wishlist, verified reviews/moderation, seasonal campaigns, discounts, cart recovery, consent-aware messaging, Instagram, Etsy, WhatsApp, blogs/SEO and segmentation.
|
|
|
|
## Phase 5: Community and optimization
|
|
|
|
Moderated forums, advanced analytics, forecasts, accounting adapters, profitability and workflow automation. SaaS tenancy/billing requires a separate architecture decision before implementation; an organization table alone does not provide tenant isolation.
|
|
|
|
## Definition of done for every feature
|
|
|
|
Small cohesive files; no duplicated business rules; unit tests for success, failure and boundaries; HTTP/integration tests where behavior crosses boundaries; schema migration and upgrade validation when persistence changes; documented API and permission contract; passing checks; focused Conventional Commit; reviewed pull request. Do not mark an entire phase complete until its end-to-end acceptance criteria pass.
|
|
|
|
## Decisions still needed
|
|
|
|
Provider accounts; deployment target and PostgreSQL service; tax/invoice and retention rules; stock location model; approval thresholds; Etsy sync direction; launch feature cut. Resolve each before its dependent milestone.
|