manufacturing stabilization

This commit is contained in:
2026-03-15 11:30:10 -05:00
parent 0596970b99
commit e2254d020e
15 changed files with 492 additions and 60 deletions

View File

@@ -19,6 +19,7 @@ Current foundation scope includes:
- purchase orders with searchable vendor and SKU entry, restricted to purchasable inventory items
- purchase receiving with warehouse/location posting and receipt history against purchase orders
- branded quote, sales-order, and purchase-order PDFs through the shared backend document pipeline
- purchase-order supporting documents for vendor invoices, acknowledgements, certifications, and backup files
- shipping shipments linked to sales orders with packing slips, shipping labels, bills of lading, and logistics attachments
- projects with customer/commercial/shipment linkage, owners, due dates, notes, and attachments
- manufacturing work orders with project linkage, material issue posting, completion posting, and work-order attachments
@@ -43,11 +44,11 @@ Planned cross-module execution areas:
Near-term priorities:
1. Vendor invoice/supporting-document attachments and broader vendor-facing operational depth
2. Sales approvals and revision history
3. Planning and gantt scheduling with live project/manufacturing data
4. Inventory transfers, reservations, and deeper stock controls
5. Broader audit-trail coverage and operational diagnostics
1. Sales approvals and revision history
2. Planning and gantt scheduling with live project/manufacturing data
3. Inventory transfers, reservations, and deeper stock controls
4. Broader audit-trail coverage and operational diagnostics
5. Code-splitting and bundle-size reduction
Revisit / deferred items:
@@ -246,8 +247,8 @@ The current purchasing foundation supports:
QOL direction:
- vendor invoice/supporting-document attachments
- richer dashboard widgets for vendor queues and inbound material exceptions
- vendor-side exception tracking around acknowledgements, invoice matching, and receipt discrepancies
This module introduces `purchasing.read` and `purchasing.write` permissions. After updating the code, restart the server against the migrated database so bootstrap can upsert the new permissions onto the default administrator role.