Before anyone writes a line of configuration, an Odoo project should produce one document: the fit-gap analysis. It lists every business process, says whether standard Odoo handles it, and if not, what the gap is and how to close it. Get this right and the rest of the project has a map. Get it wrong and you spend months discovering requirements during user testing.
This article walks through how a fit-gap workshop actually runs at a dairy plant — who sits in the room, what gets asked, and what the output should look like. It’s based on the way experienced Odoo consulting services teams approach dairy, where the gaps are predictable but the details vary a lot from plant to plant.
Why dairy needs a proper fit-gap, not a demo
Many ERP sales cycles skip straight from a product demo to a quote. For a garment trader, that might be fine. For a dairy, it’s risky.
Dairy combines things that rarely sit together in one business: high-volume daily procurement from small suppliers, quality-based pricing, perishable inventory with shelf lives measured in days, continuous processing, and route-based distribution with daily returns. Odoo handles a lot of this well in standard form. Some of it, it doesn’t touch at all. A demo shows you the parts that work. A fit-gap tells you about the rest.
Who should be in the room
The most common mistake is inviting only managers. The workshop needs people who actually do the work.
For a typical single-plant dairy, that means:
- The procurement head and one collection centre supervisor
- The plant manager and a shift in-charge from processing
- The QA lead
- The stores or cold-room in-charge
- The dispatch or distribution manager
- The accounts head and whoever runs the farmer payment cycle
- The IT lead, who will support the system after go-live
On the consulting side: a functional consultant who has worked on dairy or food processing, and ideally a solution architect for the last day to estimate custom work.
The supervisor and the shift in-charge are the ones who will say, “Actually, we don’t weigh the cans at the centre — the tanker driver writes the total.” That one sentence can change the design of the intake module.
Day one: procurement and quality
Start with milk in, because everything downstream depends on it.
The consultant walks through a single collection cycle from beginning to end. Typical questions:
- How many collection points, and are they owned, franchised or third-party?
- Do you pay by fat alone, fat and SNF, or a two-axis rate chart? How often does the chart change?
- Are morning and evening shifts priced differently?
- What deductions apply — cattle feed advances, loans, veterinary charges, cooperative share?
- How are payments made, how often, and what does the farmer receive as proof?
In standard Odoo, a vendor bill can be created from a receipt, but there is no native concept of a fat/SNF rate chart driving the unit price. That’s almost always a gap. The fit-gap document should record it with enough detail for a developer to estimate: rate chart structure, effective dating, rounding rules, and the payment-sheet format the farmers are used to.
Quality testing gets mapped here too. Odoo’s Quality app can define control points and capture measurements, but linking a failed test to automatic rejection or price penalty usually needs light customisation.
Day two: production and inventory
Next, the plant floor.
Questions here focus on how milk moves and changes:
- How many silos, and how is pooling recorded today?
- What’s standardised — fat percentage only, or SNF too?
- Which products are made, and what is the yield logic? (For example, cream separated per 1,000 litres, or paneer yield per kg of milk solids.)
- Which products are lot-tracked, and what’s the shelf life of each?
- Is there any rework — returned milk reprocessed into another product?
This is where standard Odoo fits well. Manufacturing orders, bills of materials, by-products (cream from skimming, whey from paneer), lot tracking and FEFO picking all exist in the core apps. The gaps tend to be smaller: yield variance reports specific to milk solids, or a silo dashboard showing current fat and volume.
A good consultant will push back here. If the plant wants a custom yield screen, the question is whether a configured report would do the same job. Not every wish becomes a gap.
Day three: distribution, finance and reporting
Last, product out and money in.
Distribution in dairy is often route-based: fixed vehicles, fixed retailer stops, standing daily orders, crate tracking and returns of unsold product the next morning. Odoo’s Sales and Inventory cover the transactions, but route-wise standing orders and crate balances per retailer are common gaps.
Finance covers GST, TDS on farmer payments where applicable, distributor credit limits, and how the board wants to see profitability — by product, by route, or by plant.
The day ends with reporting. Ask each department head: “What three numbers do you look at every morning?” Those become the first dashboards.
What the fit-gap document should contain
At the end of three days, the consulting team should deliver a document — not a slide deck — with, for each process:
- Process name and owner
- Current practice, described in plain words
- Fit status: standard, configurable, minor customisation, or major development
- Gap description and proposed solution
- Effort estimate in days
- Priority: must-have for go-live, or phase two
A dairy fit-gap typically comes out with 60 to 70 percent of processes covered by standard or configurable Odoo. The remaining third is where most of the cost and risk sits, so it’s where you should spend your review time.
Mistakes to avoid
Treating every gap as a must-have. Phase the work. A dairy can go live with farmer payments, production and dispatch, and add route crate tracking a few months later.
Letting the vendor write the fit-gap alone. The plant team should review and sign each line. If they can’t explain a line, it’s not ready.
Skipping the “won’t do” list. A useful fit-gap also records what the business has agreed to change to fit Odoo, rather than customise. That’s often where the biggest savings are.
From fit-gap to implementation
Once signed, the fit-gap becomes the scope baseline for the build. It’s what you hand to Odoo implementation services teams to quote against, and it lets you compare bids on the same footing rather than on whose demo looked better.
If you’re starting from scratch, structured Odoo consulting services focused on discovery are worth doing as a separate engagement before you commit to a full project. It’s also worth checking whether the firm is a certified Odoo partner with dairy references, and whether they bring an existing dairy ERP framework for procurement and distribution that shrinks the custom-work column of your fit-gap.
Three days in a room with the right people saves months later. It’s the cheapest part of the project, and the one most often rushed.
