mrp/ROADMAP.md

Roadmap

Product direction

MRP Codex is being built as a streamlined, modular manufacturing resource planning platform with strong branding controls, fast operational workflows, and a single-container deployment model that is simple to back up and upgrade.

Current status

Completed: Foundation release

• Monorepo-style workspace with client, server, and shared
• React + Vite + Tailwind frontend shell
• Express + TypeScript backend shell
• Prisma + SQLite schema foundation with committed initial migration
• Local authentication with JWT-based session flow
• RBAC permission model and protected routes
• Central Company Settings with runtime branding controls
• Light and dark mode theme system
• Local file attachment storage under /app/data/uploads
• Puppeteer PDF service foundation with branded company-profile preview
• CRM reference entities for customers and vendors
• CRM customer and vendor create/edit/detail workflows
• CRM search, filters, and persisted status tagging
• CRM contact-history timeline with authored notes, calls, emails, and meetings
• CRM shared file attachments on customer and vendor records, including delete support
• CRM reseller hierarchy, parent-child customer structure, and reseller discount support
• CRM multi-contact records, commercial terms, lifecycle stages, operational flags, and activity rollups
• Inventory item master, BOM, warehouse, and stock-location foundation
• SKU-searchable BOM component selection for inventory-scale datasets
• Theme persistence fixes and denser responsive workspace layouts
• Full-site density normalization pass across active CRM, inventory, settings, dashboard, and login screens
• SVAR Gantt integration wrapper with demo planning data
• Multi-stage Docker packaging and migration-aware entrypoint
• Docker image validated locally with successful app startup and login flow
• Core project documentation in README.md, INSTRUCTIONS.md, and STRUCTURE.md

Current known gaps in the foundation

• Prisma migration execution is committed and documented, but local Windows Node 24 schema-engine behavior remains inconsistent; use Node 22 or Docker for migration execution
• The frontend bundle is functional but should be code-split later, especially around the gantt module
• CRM reporting is now functional, but broader account-role depth and downstream document rollups can still evolve later
• Shipping is not yet linked to sales orders
• Purchasing documents are not yet implemented
• The current sales foundation does not yet include approvals, revisions, or branded transactional PDFs

Planned feature phases

Phase 1: CRM and master data hardening

• Better seed/bootstrap strategy for non-development environments
• Additional CRM account-role depth if later sales/purchasing workflows need it
• More derived CRM rollups once quotes, orders, and purchasing documents exist

Phase 2: Inventory and manufacturing core

• Item master and SKU structure
• Warehouse and stock location modeling
• Inventory transactions and on-hand tracking
• Bills of materials and custom assemblies
• Project records tied to manufacturing work
• File attachments for BOM drawings and manufacturing support docs

Phase 3: Sales and purchasing documents

• Quotes, sales orders, and purchase orders
• Reusable line-item and totals model
• Document states, approvals, and revision history
• Branded PDF templates rendered through Puppeteer
• Attachments for vendor invoices and supporting documents

Phase 4: Shipping and logistics

• Shipment records linked to sales orders
• Bills of lading, packing slips, and shipping BOM PDFs
• Carrier, package, and tracking data
• Outbound shipment status workflow
• Scanned logistics-document attachment handling

Phase 5: Manufacturing planning and scheduling

• Live project-backed SVAR gantt timelines
• Task dependencies, milestones, and progress updates
• Manufacturing calendar views and bottleneck visibility
• Labor and machine scheduling support
• Theme-compliant gantt customization for light/dark mode

Phase 6: Security, audit, and operations maturity

• Expanded role management UI
• Permission assignment administration
• Audit trail coverage across critical records
• Backup/restore workflow documentation and scripts
• Health checks, startup diagnostics, and production readiness cleanup

Cross-cutting improvements

• Stronger validation and error reporting across all APIs
• More automated tests for auth, settings, files, PDFs, and workflow modules
• Better mobile behavior in module-level pages
• Ongoing responsive-density tuning for module-level layouts and data-entry screens
• Consistent document-template system shared by sales, purchasing, and shipping
• Clear upgrade path for future module additions without refactoring the app shell

Near-term priority order

1. Shipping module tied to sales orders
2. Purchase orders and vendor-facing document flow
3. Sales and purchasing PDF templates
4. Live manufacturing gantt scheduling
5. Broader audit and operations maturity