The business problem
A kit can contain several components and nested kits. Keeping its cost current should not require opening every parent product or losing an entire run because one kit fails.
Pro-A-Motors / Purchasing & pricing
Keep a kit connected to its component costs.
A scheduled and manually requested process recalculates eligible kit costs in batches, with progress and individual failures recorded.
Explore the workflow ↓Queue eligible kits→Process in batches→Review the run
What improved
Keep parent-kit costs connected to their components.
What we changed
Cost updates can work through parent and nested kits while preserving run progress and individual failures.
What the team can do now
Manufacturing administrators can follow a cost-update run and investigate failed kits while the other eligible kits continue through processing.
The implemented workflow
Keep parent-kit costs connected to their components.
A kit can contain several components and nested kits. Keeping its cost current should not require opening every parent product or losing an entire run because one kit fails.
How it works
Cost updates can work through parent and nested kits while preserving run progress and individual failures.
What the team does next
Use the native BoM calculation, including nested kits, and record individual errors.
What the next team receives
Manufacturing administrators can follow a cost-update run and investigate failed kits while the other eligible kits continue through processing.
How the work moves01 02 03
Follow the work from one decision to the next.
Queue eligible kits
Collect active, non-service variants covered by active kit BoMs for the company.
Process in batches
Use the native BoM calculation, including nested kits, and record individual errors.
Review the run
Inspect completion, processed count, failed count and the error log.
Build notes and background
Inventory logicWorkflow automation
Make the exceptions part of the workflow.
The queue does not replace BoM costing
Eligible kits delegate their calculation to Odoo’s BoM rules.
Completion can contain failures
Run status and per-kit errors must be interpreted together.
Cost is separate from selling price
Refreshing a kit cost does not itself authorize a customer-price update.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
The custom Pro-A-Motors contribution is scheduling, batching, concurrency control and run visibility. Odoo Manufacturing and mrp_account provide the underlying BoM cost calculation.
Where this work helps
Business areas supported.
- Purchasing & Pricing
Rebuilds kit cost from its components and records the update result for review.
- Accounting & Finance
Makes component-based kit cost updates traceable; this is cost maintenance, not an accounting-posting workflow.
Related work