78 lines
2.7 KiB
Markdown
78 lines
2.7 KiB
Markdown
# 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.employee` with 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)
|
|
- `hr`
|
|
- `mail`
|
|
|
|
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 the `x_fc_` prefix per
|
|
the Fusion Central convention.
|
|
|
|
## Odoo 19 compliance
|
|
|
|
- `res.groups.privilege` is reused from the core module — no
|
|
`category_id` on `res.groups`.
|
|
- No `users` field on groups.
|
|
- All models inherit `mail.thread` / `mail.activity.mixin` via the
|
|
`_inherit` list.
|
|
- `<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.
|