f4e1f9d218
The Phase B plan (commit 8eb2c2de) listed 12 modules to sweep, but the
codebase has 13 more modules with ACL CSVs referencing the old role
group xmlids. Backward-compat (Phase A's implied_ids chains) keeps
these working today, but the old groups will be deleted after the
30-day rollback window — so the sweep must cover ALL modules with
plating-group ACL refs to avoid post-rollback breakage.
Sweeps: batch, bridge_documents, bridge_maintenance, bridge_mrp
(uninstalled but file present), bridge_quality (planned removal),
bridge_sign, compliance, culture (retired), kpi, logistics,
notifications, portal, reports.
Pattern matches the original sweep:
group_fusion_plating_operator → group_fp_technician
group_fusion_plating_supervisor → group_fp_shop_manager_v2
group_fusion_plating_manager → group_fp_manager
group_fusion_plating_admin → group_fp_owner
group_fp_accounting → group_fp_manager
group_fp_receiving → group_fp_shop_manager_v2
group_fp_estimator → group_fp_sales_rep
group_fp_shop_manager (legacy) → group_fp_manager
cgp_officer → group_fp_quality_manager
cgp_designated_official → group_fp_owner
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.