Odoo Fit Gap Analysis: Workshop, Gap Scoring and Fix Before You Sign

Most Odoo projects that go over budget were mispriced in the first month, when nobody checked the requirements against standard Odoo. Our Odoo implementation services start with exactly this fit gap analysis.

This guide is for owners, finance leads and project managers who have a requirements list and a shortlist of partners. If you still need that list, start with our ERP requirements document template for Odoo, then come back to test it.

What is an Odoo fit gap analysis?

An Odoo fit gap analysis is a line-by-line test of your requirements against what standard Odoo already does, with a decision for every gap. It is not a demo and it is not a requirements document.

The fit-gap step proves, in a real database, which needs Odoo meets out of the box and which need work. Each line ends with a fit status, a chosen fix, an owner and an effort range: the fit-gap matrix.

Why should you run an ERP gap analysis before signing a contract?

An ERP gap analysis before signing turns an open-ended project into a priced scope, because every gap is known and costed up front. After signing, the same gaps cost more and cause disputes.

• Price accuracy: a quote built on a scored matrix reflects real work, not a sales demo.
• Fewer change requests: gaps found in month three become paid changes; gaps found in week one are part of the plan.
• Less custom code: testing standard flows first often removes "needs" that were really habits.
• Upgrade safety: every custom module you avoid is one less module to port at the next Odoo version.

Odoo's own community guidance points the same way. An Odoo staff answer on the forum notes that over 60% of initial "needs" are dropped a few weeks after going live, once users find standard features are enough.

Our post on what a failed Odoo implementation really costs shows what happens when this step is skipped.

How do you prepare for Odoo requirements gathering and the fit-gap workshop?

Good Odoo requirements gathering means arriving with real documents, real users and a clean database, not a wish list. Preparation takes one to two weeks and decides the quality of everything after.

1. Freeze the requirements list: number every requirement so it can be traced into the matrix.
2. Pick the version: use Odoo 20 for a new project unless a needed localization or module is only proven on Odoo 19.
3. Set up a clean database: a standard trial or test database with the apps you plan to license, and no custom code.
4. Collect real samples: ten recent sales orders, purchase orders, invoices, a stock count and a month-end pack.
5. Name the key users: one person per process who does the work daily, plus one decision-maker.
6. Choose the plan and hosting assumption: Standard on Odoo Online, or Custom on Odoo.sh or on-premise, because that changes which fixes are allowed.

How do you run the fit-gap workshop against standard Odoo 19 or 20?

Run the fit-gap workshop process by process, with key users clicking through their own transactions in standard Odoo while a consultant logs each step. Show the work, do not describe it.

Plan one value stream per session, such as quote to cash, procure to pay, plan to produce or record to report.

1. Walk the current process: the key user explains today's steps with a real document in hand.
2. Replay it in Odoo: the consultant runs the same transaction in standard Odoo, using settings only.
3. Mark each step: fit, partial fit or gap, with a one-line reason.
4. Ask why five times: challenge each gap until you know the business reason behind it.
5. Log the gap: give it an ID, owner, frequency and the business impact if it is not solved.

Odoo's own guidance on process design asks whether a process scales to triple the current volume and keeps a clear audit trail. Use those questions as your fit test.

For how this step fits the wider project plan, see our Odoo ERP implementation methodology.

What goes into a fit gap analysis template for Odoo?

A useful fit gap analysis template has one row per requirement and columns that force a decision, an owner and an effort range. Keep it in a shared spreadsheet that both sides sign.

Column	What to record	Example
Gap ID	Unique number traced to the requirement	SAL-07
Process	Value stream and step	Quote to cash, approval
Requirement	What the business needs, in plain words	Manager approves discounts over 15%
Fit status	Fit, partial fit or gap	Partial fit
Root cause	Why the need exists	Margin control on large deals
Chosen fix	Rung on the fix ladder	Studio approval rule
Score	Impact + frequency + fix risk (3 to 9)	7
Phase	Go-live, phase 2 or dropped	Go-live
Effort range	Hours or cost band	Low
Owner and sign-off	Client and partner names	Finance lead, consultant

How do you score and prioritize gaps in an Odoo gap analysis?

Score every gap from 1 to 3 on business impact, frequency and fix risk, then add them up: high totals are must-solve, low totals are phase 2 or dropped. Simple scoring beats long debates.

Factor	1 point	2 points	3 points
Business impact	Convenience only	Slows a team or adds manual work	Legal, financial or customer risk
Frequency	Monthly or rarer	Weekly	Daily or every transaction
Fix risk	Standard or settings	Studio or Apps Store module	Custom code or new integration

This is our working method, not an Odoo standard. Use it as a starting point and adjust the weights with your team.

• Score 8 to 9: must solve before go-live, and challenge the fix hard because it is expensive.
• Score 6 to 7: solve at go-live if a low-risk fix exists; otherwise plan it for phase 2.
• Score 3 to 5: try a process change or drop it, and recheck after a month of live use.

Configure, Studio, app or custom: which Odoo fix should you choose?

Pick the lowest rung on the fix ladder that solves the gap safely, because each rung up adds cost, plan requirements and upgrade work. Custom code is the last option, not the first.

Fix rung	When it fits	Plan and hosting impact	Upgrade risk
Standard	Odoo already does it	Any plan	None
Configure	A setting, rule or field option solves it	Any plan	Very low
Process change	The need is a habit, not a requirement	None	None
Odoo Studio	Fields, views, reports, approvals, automations	Custom plan	Low to medium
Apps Store module	A tested third-party app covers it	Odoo.sh or on-premise	Medium
Integration	The data lives in another system	Custom plan for the external API	Medium
Custom module	Nothing else works and the score is high	Odoo.sh or on-premise	High

Odoo Studio covers fields, views, models, automation rules, webhooks, PDF reports, approval rules and security rules. Odoo's docs warn that installing Studio on the Standard plan triggers an upsell to the Custom plan.

On the Odoo pricing page, Custom costs US$61.00 per user a month billed yearly in the US, against US$31.10 for Standard. In India the yearly prices are Rs 1,350 and Rs 725. Price a Studio fix as a plan change too.

Odoo Online is incompatible with custom modules or Apps Store modules. So an Apps Store or custom fix also means Odoo.sh or on-premise hosting.

Before you choose a module from the Odoo Apps Store, check who maintains it for the next version. Our guide to third-party Odoo module costs lists what to ask.

For deeper rules on when code is worth it, read our guide to Odoo customization.

What changes in an Odoo 20 fit gap analysis?

An Odoo 20 fit gap analysis should test the new AI and automation features and the API change, because both can turn old gaps into fits or new costs. Odoo 20 was released in September 2026.

• AI in automation: Studio automation rules can now call an AI Agent with written instructions, which can close some routing and drafting gaps without code.
• AI cost: Odoo 20 AI runs on Odoo AI IAP credits at EUR 1 per credit; own OpenAI or Gemini keys are no longer used, so log AI fixes with a monthly credit estimate.
• Integrations: XML-RPC and JSON-RPC are deprecated in Odoo 20 and scheduled for removal in Odoo 22, so new integration gaps should be designed on the newer API.
• Light Users: at US$8.90 a month in the US, Light Users can close "too many licenses" gaps for occasional users.

How does the fit-gap matrix shape your Odoo implementation contract?

The signed fit-gap matrix should become the scope annex of your Odoo implementation contract, with each gap ID, fix and phase listed. That is how you sign with confidence.

1. Attach the matrix: the contract references gap IDs, not vague module names.
2. Price by rung: standard and configuration work, Studio work and custom code are priced separately.
3. Set acceptance tests: each high-score gap gets one test that proves it is solved in UAT.
4. Define change requests: any new gap after sign-off goes through a priced change request.
5. Agree the phase 2 list: deferred gaps are named and dated, not forgotten.

Our published Odoo implementation ranges are a sense check, not a quote: small projects US$3k to US$9k (4 to 8 weeks), mid-size US$9k to US$27k (8 to 14 weeks), and large US$27k to US$150k+ (12 to 24 weeks). See our Odoo implementation cost guide.

For how to keep the scope under control after signing, read our post on Odoo scope creep and change requests.

Which gaps show up most often by industry?

Each industry brings its own typical gaps, so test those processes first in the workshop. The table lists the patterns we check early.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Manufacturing	Routings, scrap and costing	MRP, work orders, quality checks	Test BOMs and costing on real products
Wholesale and distribution	Customer pricing, landed costs	Pricelists, routes, landed costs	Score pricing gaps, avoid custom pricing code
Retail and eCommerce	Stock across channels	POS, website and Inventory on one database	Map each channel and its sync gap
Professional services	Billing rules and margins	Projects, timesheets, invoicing policies	Test billing rules before choosing Studio
Chemicals and regulated goods	Lots, safety data, claims	Lot tracking, Helpdesk, quality	Separate compliance gaps from habits

How iVentureTeam helps with an Odoo fit gap analysis

iVentureTeam runs the fit-gap workshop with your key users, scores every gap with you and hands over a matrix you can sign or take to any partner. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Workshop design: an agenda by value stream, a clean Odoo 20 database and a numbered requirements list.
• Gap scoring: impact, frequency and fix risk for every gap, reviewed with your decision-maker.
• Fix choice: standard, configuration, Studio, module or code, with plan and hosting impact noted.
• Studio and code where needed: our Odoo customization services build only the gaps that earn it.
• Scoped proposal: a phased plan and budget built from the matrix. For a first number, try the Odoo project estimate tool.

Odoo fit gap analysis case study: Indep Consulting SPRL

A Belgian cleaning-chemicals company moved sales, stock, accounting, eCommerce and contract servicing into one Odoo system, using configuration first and custom work only where reporting needed it.

Indep Consulting runs cleaning chemicals, equipment and maintenance contracts. Sales, stock and accounting sat in disconnected tools, customer pricing and intercompany moves were manual, and trading partners expected EDI.

Most gaps closed through configuration: custom pricelists for customer segments, intercompany transfer rules, claim management tied to orders, and EDI. The one area that earned custom work was management reporting, delivered as 8 SQL-based reports.

The project covered 10+ business areas in 12 weeks of delivery, and the management reporting cycle became 2x faster. Read the Indep Consulting Odoo ERP and SQL reporting case study.

The bottom line on Odoo fit gap analysis

Run the fit gap analysis before you sign, test in a clean standard database, score every gap and pick the lowest safe fix. The matrix is your scope, budget and change control in one document.

Teams that skip it usually pay for the same analysis later, as change requests, and carry more custom code into every upgrade.

Ready to test your requirements against standard Odoo?

Bring your requirements list and we will show you what fits, what does not and what each gap will cost. Plan your Odoo fit-gap workshop with us, call +91-90235-15208, or email business@iventureteam.com.