Four implementation proposals are on your desk. One costs half as much as another. One promises go-live in six weeks. All four say they understand manufacturing.
So how do you choose?
The odds aren't kind to a careless pick. Gartner expects more than 70% of recently implemented ERP initiatives to fall short of their original business case goals by 2027, and up to 25% to fail outright (Gartner, 2024). For a cosmetics manufacturer, the Odoo implementation partner you sign with decides how formulations, raw materials, batches, quality checks, packaging and lot traceability will run for years.
This guide gives you 10 questions to put to every Odoo partner, what a credible answer sounds like, and the red flags worth walking away over.
Key Takeaways
- Gartner expects 70%+ of new ERP initiatives to miss their business case by 2027 (
- A partner badge proves standing with Odoo, not manufacturing depth. Ask for a comparable batch-manufacturing reference.
- Ask for a fit-gap analysis, a named functional lead and written exit terms.
- Buy a two-week paid discovery before the full project.
Still working out what your ERP needs to do? Start with our complete guide to cosmetics manufacturing software on Odoo, or talk to our Odoo team.
Why does the partner matter more than the software?
Every Odoo partner works from the same codebase, yet Gartner still expects more than 70% of ERP initiatives to miss their goals (Gartner, 2024). The software isn't what varies between proposals. The implementation approach is, and that's what decides whether Odoo fits your plant or fights it.
Picture a manufacturer making face creams, shampoos, serums and other personal care products. Its ERP has to handle:
- Formulations and Bills of Materials (BoMs)
- Raw materials, ingredients and packaging components
- Batch-wise production and actual material consumption
- Quality checks at incoming, in-process and finished-goods stages
- Lot numbers, expiry dates and traceability
- Production planning, inventory valuation and cost control
- Finished goods, dispatch and order fulfilment
Some of that is standard Odoo and configuration. Some needs workflows, integrations or custom code, depending on how much control you need. A good partner sorts those before quoting.
The stakes are higher in cosmetics than in most sectors. Cosmetics were the most-notified product category in the EU's Safety Gate system in 2025, at 36% of 4,671 alerts (European Commission, 2026). When a regulator or retailer asks which raw-material lots went into a finished batch, the answer depends on how your partner configured lot tracking on day one.
Weak implementations tend to fail in the same six ways:
- Unmapped processes. The system gets configured before anyone has watched a batch being made.
- Uncontrolled scope. Requirements surface mid-project and turn into a stream of change requests.
- Needless customisation. Standard features get rebuilt, so maintenance and upgrade costs climb.
- Poor data migration. Formulas, stock balances, lots and open transactions come across wrong.
- Weak adoption. Training is squeezed into the last week, so staff work around the system.
- No support after go-live. The team leaves just as real production starts.
None of these is a software bug. They're planning and delivery failures, which is why the partner deserves as much scrutiny as the ERP itself.
10 questions to ask an Odoo implementation partner
Each question below comes with what a good answer includes and the red flag to watch for. Ask all ten of every partner, in writing, so you can compare answers side by side.
1. Can you show us a manufacturing project like ours?
You need a partner who understands how your factory runs, not just how to click through Odoo. Ask for projects that involved batch manufacturing, formulations, raw material consumption, packaging, QC or finished-goods traceability. Cosmetics or personal care experience is the best fit. Food, pharma and chemicals are close behind.
A good answer: The partner explains the manufacturing problem, the process they built, the Odoo apps used, what was custom and what changed for the client. Then they offer a reference call.
Red flag: A slide of client logos and nobody who can explain what was actually delivered.
Hold partners, including us, to that standard. When we talk about Ruelia Professional, a haircare and skincare maker on Odoo 19 Community, we're specific: we built packaging BoMs for 14 finished SKUs and a pre-production view that flags packaging shortfalls before purchase is due. Our three custom modules there handled inter-company orders and distribution-chain rules. They weren't formulation builds, and we don't pitch them as such.
Follow-up: Can we speak to a customer whose production process is close to ours?
2. How will you handle formulations, batches and QC release in Odoo?
For a cosmetics plant, this is the question that separates partners fastest. A formula isn't just a recipe. It sets ingredient quantities and batch size, and often the production steps, quality checks and expected consumption too.
Ask for a live demo of a realistic flow: a cream made against a defined formula, ingredients issued from stock, actual consumption recorded, a lot created, and the finished product held until QC approves it.
A good answer: The partner separates standard BoM and manufacturing features, configurable quality controls and anything that needs custom work. They show how a rejected or quarantined batch is blocked from release.
Red flag: "It's all standard," with no demo to prove it.
Our guide to batch manufacturing records in Odoo shows what that flow should look like.
3. Who will map our processes and lead the functional work?
ERP projects succeed when someone understands the business before anyone touches configuration. Your functional consultant should sit with production, purchasing, stores, QC, finance and sales to see how information moves between them.
A good answer: You meet the proposed functional lead before signing. You know their relevant experience and who owns requirements, process mapping, solution design, testing and stakeholder sign-off.
Red flag: Developers are left to interpret requirements without functional analysis. Or the consultant who ran the presales demo disappears at kickoff.
Follow-up: Who's accountable if the configured workflow doesn't match the process we agreed?
4. Is your proposal fixed-scope or time-and-materials?
Neither model is better by default. What matters is whether the pricing matches how well the scope is understood. Fixed price works when scope is documented in detail. Time-and-materials suits evolving requirements or open technical questions.
A good answer: The proposal lists included processes, deliverables, assumptions, exclusions, custom development, payment terms and the change-approval process. A T&M proposal adds estimated effort, rates, reporting and budget controls.
Red flag: A low headline price with vague deliverables, no exclusions and no word on how extra work gets billed.
Odoo implementation cost is more than the partner's fee. Compare total cost: implementation, licences, integrations, data migration, training, hosting where it applies, and ongoing support.
5. How will you migrate our existing data?
Migration gets underestimated because product lists and stock sheets look simple until someone opens them. A cosmetics plant may need to move product and ingredient masters, formulas, units of measure, suppliers, opening stock, lot numbers, expiry dates, customer prices and open transactions.
A good answer: The partner covers data ownership, templates, validation rules, who cleans what, trial migrations, reconciliation and the cutover plan. They state which history moves to Odoo and which stays readable in the old system.
Red flag: The whole plan is "export to Excel, import to Odoo."
Follow-up: How will we confirm that migrated stock, lot details and financial balances match the approved opening position?
6. What support do we get after go-live?
Go-live is when real use starts. The first few weeks surface problems with production entries, stock moves, reports, user rights and month-end close.
A good answer: A defined hypercare period, support channels, response targets, an escalation path, included support hours and commercial terms for ongoing help.
Red flag: Support exists only as a verbal promise, with nothing in writing.
Ask who handles an urgent production issue at 7 a.m. on a Monday, and whether the original project team stays involved through the first month-end close.
7. What will you customise, and what will you keep standard?
Custom development is sometimes the right call. It should close a specific, documented gap. Standard Odoo Manufacturing covers BoMs, manufacturing orders and production recording. Depending on version and workflow, you may need code for percentage-based formula entry, formula approvals, complex batch-release rules or industry reports.
A good answer: A fit-gap analysis that splits standard features, configuration, third-party integrations and custom development. Custom work is documented, tested and built to survive upgrades.
Red flag: Everything is custom. Or everything is standard, with no fit-gap behind the claim.
Ask for examples where the partner talked a client out of a customisation and simplified the process instead. That answer tells you more about their judgement than any technology list.
8. Which Odoo version will we run, and how will upgrades work?
Your ERP has to outlast the first project. Ask which version and edition they propose, why it fits your requirements, and how custom modules and integrations will be maintained.
A good answer: The partner explains the version, hosting, module dependencies, testing approach and upgrade plan, including compatibility checks and regression testing for custom code.
Red flag: "Upgrades are effortless," or an assumption that custom modules will just work on the next version.
Ask how source code, technical documentation, backups and deployment steps will be kept. Those are what let you own the system long term.
9. How will you train our team and test before go-live?
An ERP only works if people follow the process inside it. User acceptance testing (UAT) should prove real business scenarios, not just that screens load.
For a cosmetics plant, that means receiving a raw-material lot, making a defined batch, recording actual consumption, handling a QC failure, releasing finished goods and tracing a finished lot back to its inputs. If your plant works to ISO 22716, the cosmetics GMP guideline, your QA team will want those scenarios to mirror your GMP records.
A good answer: Scenario-based test cases, named business users who run them, a defect log with fixes tracked, and formal sign-off before go-live. Training is built around each role.
Red flag: Testing squeezed into the final days, or the partner testing everything without your users.
