3641b78a66
Collapses the flat ~36-entry Configuration list into 7 navigable
folders + Settings (sibling, stays at top of Configuration). Existing
menu IDs unchanged so bookmarks + cross-module data refs still work
— only parent-id moves.
New folder menus (defined in fusion_plating core):
menu_fp_config_shop_setup Shop Setup
menu_fp_config_recipes_steps Recipes & Steps
menu_fp_config_materials_tanks Materials & Tanks
menu_fp_config_workforce Workforce
menu_fp_config_quality_docs Quality & Documents
menu_fp_config_pricing_billing Pricing & Billing
menu_fp_config_reference_data Reference Data
Routing per item (sources updated in their owning module):
Shop Setup Facilities, Work Centers, Work Centres, Process
Categories, Process Types, Bake Ovens, Shopfloor
Stations, Vehicles
Recipes & Steps Step Library, QC Checklist Templates, Quality Points
Materials & Tanks Bath Parameters, Replenishment Rules, Chemicals,
Rack Tags, Calibration Equipment, Calibration Events
Workforce Operator Certifications, Shop Roles, Training Types,
Quality Teams
Quality & Documents Customer Specs, Approved Vendor List, Quality
Tags, Quality Reasons, Quality Stages, N299
Levels, Notification Templates, Notification Log
Pricing & Billing Invoice Strategy Defaults, Account Holds
Reference Data Value Sets, Value Rotations
(Settings remains as a sibling at top of Configuration, manager-gated)
Versions bumped: fusion_plating, fusion_plating_quality, _safety,
_shopfloor, _logistics, _culture, _invoicing, _notifications, _nuclear.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Fusion Plating — Logistics
Part of the Fusion Plating product family by Nexa Systems Inc.
Adds pickup & delivery management on top of the fusion_plating core:
- Vehicle master — insurance, registration, service, TDG status, home facility, current driver
- Driver tracking — extends
hr.employeewith licence class, licence expiry, TDG certification and expiry (x_fc_*fields) - Pickup requests — customer-initiated pickup of parts to be processed, with full state machine (new → scheduled → en_route → picked_up → received)
- Deliveries — scheduled delivery of finished parts back to the customer (draft → scheduled → en_route → delivered / refused / returned)
- Routes — combine pickups and deliveries into a single run for one driver and vehicle, with drag-to-reorder stops, calendar view, and total km tracking
- Chain of custody — append-only audit trail written automatically as pickups and deliveries move through their lifecycle
- Proof of delivery — recipient signature, photos, GPS, delivery timestamp
Dependencies
fusion_plating(core)hrmail
Works on both Odoo Community and Enterprise. The Enterprise fleet module
is not required — the vehicle master is a lightweight CE-compatible
model sized to what a plating shop needs.
Security
Reuses the core fusion_plating groups (Operator / Supervisor / Manager /
Administrator) via the res.groups.privilege mechanism. No new groups are
defined by this module.
- Operators: read-only on all logistics records
- Supervisors: read / write / create on routes, deliveries, pickup requests, vehicles, route stops, custody events, PODs
- Managers: full CRUD (adds unlink)
Multi-company isolation is enforced by global ir.rule records on every
new model.
Menu
Adds a Logistics section under the Plating app menu with:
- Pickup Requests
- Deliveries
- Routes
- Chain of Custody
- Proof of Delivery
Adds Vehicles under Plating → Configuration.
Field naming
- New dedicated models use the
fusion.plating.*namespace consistent with the core module. - Extensions of base Odoo models (
hr.employee) use thex_fc_prefix per the Fusion Central convention.
Odoo 19 compliance
res.groups.privilegeis reused from the core module — nocategory_idonres.groups.- No
usersfield on groups. - All models inherit
mail.thread/mail.activity.mixinvia the_inheritlist. <chatter/>tag used in form views.- SCSS is theme-aware — no hardcoded colours, only CSS custom properties
from Odoo / Bootstrap, and
color-mix()for semantic tints.
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.