next slice

ROADMAP.md

@@ -1,5 +1,10 @@
 # Roadmap
 
+## Documentation maintenance
+
+- Keep [CHANGELOG.md](D:/CODING/mrp-codex/CHANGELOG.md) updated alongside roadmap-driving feature completion, priority shifts, and notable delivery milestones.
+- When roadmap changes affect implementation guidance or deployment expectations, update the companion docs in [README.md](D:/CODING/mrp-codex/README.md), [INSTRUCTIONS.md](D:/CODING/mrp-codex/INSTRUCTIONS.md), [STRUCTURE.md](D:/CODING/mrp-codex/STRUCTURE.md), and [UNRAID.md](D:/CODING/mrp-codex/UNRAID.md) in the same change set.
+
 ## 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.
@@ -31,6 +36,7 @@ MRP Codex is being built as a streamlined, modular manufacturing resource planni
 - Purchase orders with vendor lookup, item lines, totals, and quick status actions
 - Purchase-order line selection restricted to inventory items flagged as purchasable
 - Purchase receiving foundation with warehouse/location posting, receipt history, and per-line received quantity tracking
+- Branded sales quote, sales order, and purchase-order PDF templates through the shared Puppeteer pipeline
 - Shipping shipment records linked to sales orders
 - Packing-slip PDF rendering for shipments
 - SKU-searchable BOM component selection for inventory-scale datasets
@@ -46,7 +52,7 @@ MRP Codex is being built as a streamlined, modular manufacturing resource planni
 - 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
-- The current sales/purchasing/shipping foundation still does not include approvals, revisions, shipment labels, vendor-side attachment handling, or broader branded transactional PDF coverage beyond packing slips
+- The current sales/purchasing/shipping foundation still does not include approvals, revisions, shipment labels, or vendor-side attachment handling
 - The dashboard is now live-data driven, but still needs richer KPI widgets, alerts, recent-activity queues, and exception reporting as more transactional depth is added
 
 ## Dashboard Plan
@@ -224,8 +230,7 @@ QOL subfeatures:
 - Local Windows Prisma migration reliability still needs a cleaner documented workflow or tooling wrapper
 - Frontend bundle splitting is still deferred; the Vite chunk-size warning remains
 - Sales approvals and document revision history were planned but not yet built
-- Broader branded PDFs for quotes and sales orders still need to be added
-- Purchasing PDFs and vendor invoice/supporting-document attachments still need to be added
+- Vendor invoice/supporting-document attachments still need to be added
 - Shipping is now linked to sales orders, but labels, bills of lading, and logistics attachments are still pending
 - Inventory transactions exist, but transfers, reservations, and more advanced stock controls still need follow-up
 - CRM document rollups and broader account-role depth were deferred until more downstream modules exist
@@ -246,8 +251,8 @@ QOL subfeatures:
 
 ## Near-term priority order
 
-1. Sales and purchasing PDF templates
-2. Shipping labels, bills of lading, and logistics attachments
-3. Projects and program management
-4. Manufacturing execution
-5. Vendor invoice/supporting-document attachments and broader vendor-side operational depth
+1. Shipping labels, bills of lading, and logistics attachments
+2. Projects and program management
+3. Manufacturing execution
+4. Vendor invoice/supporting-document attachments and broader vendor-side operational depth
+5. Sales approvals and document revision history