100 lines
4.0 KiB
Markdown
100 lines
4.0 KiB
Markdown
# 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
|
|
- 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 contact history, shared attachments, and deeper operational metadata are not built yet
|
|
|
|
## Planned feature phases
|
|
|
|
### Phase 1: CRM and master data hardening
|
|
|
|
- Contact history and internal notes
|
|
- Shared attachment support on CRM entities
|
|
- Better seed/bootstrap strategy for non-development environments
|
|
- Deeper CRM operational fields and lifecycle reporting
|
|
|
|
### 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
|
|
- 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. CRM contact history and internal notes
|
|
2. CRM shared attachments and operational metadata
|
|
3. Inventory item and BOM data model
|
|
4. Sales order and quote foundation
|
|
5. Shipping module tied to sales orders
|