Preserve the source lot identity, physical quantity, release status and approved date fields, while assigning missing or conflicting information to a responsible owner. Do not derive an unsupported expiry from an import date. Reconcile bulk, finished units, samples and held stock separately so opening availability reflects the actual product state and its documented use conditions.
Understand the decision
A hypothetical migration finds finished stock with supplier-provided dates, bulk awaiting release and retained samples stored outside the main warehouse. Older records use different date formats, and a few lots have no approved shelf-life entry. The opening records must keep those uncertainties visible rather than replace them with convenient defaults.
Work through the requirements
- Map date meanings and formats before import.
- Reconcile quantities by lot, location and status.
- Assign incomplete date or release evidence for review.
| Record or decision | Why it matters |
|---|---|
| Lot snapshot | Record identity, quantity and physical state. |
| Date mapping | Define approved meanings and source fields. |
| Data exception | Assign missing or contradictory information. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
A technically valid date can still have the wrong meaning. Have the product owner approve how manufacture, expiry and review dates are mapped, and preserve missing evidence as an exception instead of disguising it with a default.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Cosmetics manufacturing in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: manufacturing product configuration ↗Odoo 19: quality control points ↗Odoo 19: lot numbers ↗Odoo 19: expiration dates ↗