Odoo Post Implementation Review: 30/60/90 Day Checklist and Template

Go-live is where most ERP budgets end and most ERP problems begin. A structured Odoo post implementation review, backed by Odoo ERP support and maintenance, turns the first 90 days into proof that the project worked, or an early warning that it did not.

This guide is for owners, finance leads and project sponsors whose Odoo 19 or Odoo 20 system has just gone live. It covers the post-launch period only. For the steps before launch, see our Odoo implementation checklist from planning to go-live.

What is an Odoo post implementation review?

An Odoo post implementation review is a planned check of adoption, data, processes and results after go-live, run against the goals you set before the project started. It is not a bug list and not a sales meeting.

A good review answers four questions. Are people working in Odoo or around it? Do the numbers in Odoo match reality? Do the main processes run end to end without manual fixes? Is the business getting the gains it paid for?

Most published advice stops at "review adoption and data". That is the right idea, but it gives you no dates, no owners, no KPIs and no report format. This guide fills those gaps with a 30, 60 and 90 day plan and an ERP post implementation review template you can copy.

When should you run the 30, 60 and 90 day reviews?

Run the first review 30 days after go-live, the second after your first full month-end close, and the third at 90 days. Each review has a different job, so do not merge them.

Review	Main question	Who attends	Output
Day 30	Is the system stable and used?	Sponsor, key users, partner lead	Blocking issues closed, hypercare exit decision
Day 60	Do processes and data hold up at month-end?	Finance lead, key users, partner	Reconciled close, process fixes list
Day 90	Are we getting the expected value?	Sponsor, department heads, finance	KPI report, backlog, support plan
Day 180 (optional)	Did the gains stick?	Sponsor, finance	Short KPI update

Book all three dates in the go-live plan, before launch day. Reviews that are scheduled after go-live tend to slip, and silent workarounds grow while they do.

What to check in the first 30 days after Odoo go-live

The first 30 days are hypercare: fast fixes, close watching and no new features. The goal is a stable system that every user can work in every day.

Use this ERP post go-live checklist for the first month:

• Blocking issues: every issue that stops an order, a delivery or an invoice has an owner and a fix date.
• Opening balances: finance confirms customer, vendor, stock and bank balances in Odoo against the old system.
• Access rights: no shared logins, no users with admin rights they do not need, and leavers archived.
• Shadow spreadsheets: list every sheet still used alongside Odoo and give each one an end date.
• Batch entry: check that orders, receipts and timesheets are entered on the day, not at the end of the week.
• Integrations and scheduled jobs: confirm that webshop, bank and shipping syncs run without failed jobs.
• Support queue: count tickets per user and per topic, so training gaps show up early.

Odoo makes the access check easy. Its user documentation explains how to archive users from the Manage Users list, which you should do for testers, temporary staff and project accounts once go-live is over.

Decide at day 30 whether hypercare can end. A simple rule: no open blocking issues for five working days, and every key user able to complete their core process alone.

What to check at 60 days: process and data stabilization

The 60 day review is about stabilization: proving that Odoo survives a full month-end close and that stock and bank data match reality. Month-end is where hidden setup errors show up.

Check these areas in order:

1. Bank reconciliation: all bank lines for the month matched or explained. Odoo's bank reconciliation guide covers matching rules and reconciliation models that cut manual work.
2. Stock count: count a sample of high-value and fast-moving items and post differences through Odoo inventory adjustments.
3. Stock valuation: the stock value on the balance sheet matches the inventory valuation report.
4. Receivables and payables: aged balances look right and no invoice is stuck in draft.
5. Taxes: the first tax return from Odoo agrees with the source invoices.
6. Process speed: time a few real orders from quote to invoice and compare with the baseline.

Then lock the month. Odoo's year-end documentation explains that a lock date stops changes to posted entries on or before that date, with logged exceptions for administrators. A locked first month is a simple sign that finance trusts the numbers.

What to check at 90 days: KPIs, ROI and the backlog

The 90 day review compares results against the baseline you captured before the project and decides what comes next. This is where the post implementation report is written and signed.

By day 90, you should have three months of real data. Pull the KPIs in the next section, compare them with the baseline, and mark each one green, amber or red. Do not expect full payback yet; our guide to measuring Odoo ROI with a baseline and KPIs explains why full ROI takes longer.

Also review adoption. If some teams still work outside Odoo, the cause is usually training or design, not attitude. Our Odoo change management playbook covers adoption fixes in depth.

Finally, sort every request raised since go-live into one backlog. Fix defects first, then small improvements, then new features. Price new features as change requests, as our guide to controlling Odoo scope creep explains.

Which Odoo post go-live KPIs should you track?

Track six KPIs that show both adoption and business results, and compare each with its pre-project baseline. The targets below are illustrative starting points, not industry benchmarks.

KPI	What it shows	Where to find it in Odoo	Illustrative 90 day target
Active users	Adoption across teams	Users list, digest emails	All licensed users active weekly
Work done in Odoo	Shadow spreadsheets retired	Key user check, document counts	No core process outside Odoo
Month-end close days	Finance stability	Accounting, lock dates	Close faster than baseline
Stock accuracy	Inventory data quality	Physical Inventory counts	Counted items match system stock
Quote to invoice time	Process speed	Sales and Invoicing reports	Shorter than baseline
Tickets per user	Training and design gaps	Helpdesk or support log	Falling month on month

Odoo can send some of these to managers automatically. Its digest emails can share KPIs such as connected users, won opportunities, revenue and closed tickets on a daily, weekly, monthly or quarterly schedule. Adding custom KPIs needs Studio.

Odoo 19 and Odoo 20 checks for the post-launch review

Add a short version check to every review, because Odoo 19 and Odoo 20 bring dates and changes that affect support, integrations and cost. These items are easy to miss in a busy first quarter.

Check	Odoo 19	Odoo 20	Why it matters
Standard support	Planned to September 2028	Planned to September 2029	Sets your next upgrade window
XML-RPC / JSON-RPC integrations	Supported	Deprecated, removal planned in Odoo 22	New integrations should use JSON-2
AI features	Own API keys on Odoo.sh and on-premise	Run on Odoo AI IAP credits	Credits are a running cost to watch
User count	Matches subscription?	Matches subscription?	Extra users are billed at list price
Lock dates	Set after each close	Set after each close	Protects closed periods

Odoo's support policy table lists Odoo 20 standard support as planned to September 2029. Note the date in your report, so the next upgrade is a plan and not a surprise.

Odoo's external API documentation says XML-RPC and JSON-RPC are deprecated, with the common and object services scheduled for removal in Odoo 22. If your go-live used them, plan the move with our JSON-2 API migration guide.

On Odoo 20, AI features use Odoo AI IAP credits, so track credit use per month. Also compare active users with your contract: the Odoo Enterprise Subscription Agreement asks customers to notify Odoo when users exceed the agreed number.

How do you triage issues found in a post-launch review?

Rank every finding by business impact, not by who shouted loudest, and fix them in that order. A simple four-level scale works for most companies.

1. Critical: stops orders, shipments, invoicing or payroll. Fix within one working day.
2. High: wrong numbers in stock, accounting or tax. Fix before the next month-end.
3. Medium: slow or manual steps with a workaround. Plan into the next sprint.
4. Low: layout, labels and nice-to-have reports. Add to the backlog.

Get every promise in writing. One Odoo forum poster, after a troubled rollout, warned others to get every promise in writing and plan for ongoing costs. A written review report with owners and dates does exactly that.

For defects that come from untested scenarios, reuse the test scripts from your acceptance phase. Our guide to Odoo UAT scenarios and defect triage has a format you can carry into live support.

Post implementation report template for Odoo

Keep the post implementation report to one or two pages, with the same sections at every review so results can be compared. Copy this structure into a document or an Odoo Knowledge article.

Section	What to write	Owner
1. Scope and date	Review stage (30, 60 or 90 days), apps and companies covered	Project sponsor
2. Goals recap	The three to five goals from the business case	Project sponsor
3. KPI results	Baseline, current value, status for each KPI	Finance lead
4. Adoption	Active users, shadow spreadsheets left, training gaps	Key users
5. Data quality	Reconciliation, stock count and balance checks	Finance and warehouse
6. Open issues	Count by severity, oldest open item	Partner lead
7. Version and licensing	Support date, deprecated APIs, user count, credit use	IT or admin
8. Decisions needed	Items needing budget or sign-off	Sponsor
9. Next steps	Backlog priorities, support plan, next review date	Partner lead

Sign the report at each stage. The day 90 sign-off is the formal end of the project and the start of ongoing support.

Post go-live review checks by industry

The review structure stays the same in every industry, but the riskiest checks change. Weight your review toward the line that matches your business.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Manufacturing	Wrong BOMs and work order costs	Compare actual and planned costs on closed orders	Review BOMs, routings and costing
Distribution	Stock mismatches across warehouses	Cycle counts and inventory adjustments	Fix routes, run count plans
Retail and eCommerce	Webshop and POS stock out of sync	Check sync jobs and stock per channel	Repair connectors, align stock
Professional services	Unbilled timesheets	Compare timesheets with invoiced hours	Tune billing rules
Multi-company groups	Intercompany entries that do not match	Reconcile intercompany balances monthly	Review intercompany rules

For finance-heavy reviews, also check approvals and audit trails. Our guide to Odoo internal controls and audit trails lists the controls worth testing after launch.

How iVentureTeam helps with Odoo go-live support and post-launch reviews

iVentureTeam runs independent Odoo post implementation reviews, whether we built your system or another partner did. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Hypercare: fast fixes in the first 30 days, with a daily issue log and a clear exit rule.
• Month-end support: a guided first close, bank and stock reconciliation and lock dates.
• KPI review: baseline against actuals, written up in the report template above.
• Training gaps: targeted sessions from our Odoo ERP training team where the ticket log shows confusion.
• Ongoing care: a support plan sized to your backlog, with version and API checks each quarter.

Not sure where to start? Run the free Odoo health check tool for a quick view of your version, modules and likely issues.

Odoo post implementation review case study: Indep Consulting

A Belgian cleaning-chemicals company shows why the reports you review after go-live must answer management's own questions. Indep Consulting runs chemicals, equipment and maintenance contract businesses.

Sales, stock and accounting data had sat in separate tools, so questions like product margin or vendor spend were slow to answer. Maintenance contracts and customer claims had no systematic tracking tied to sales records.

We implemented Odoo Sales, CRM, Inventory, Accounting and eCommerce over a 12 week delivery, then built 8 custom SQL reports, including product margin, vendor summary, stock rotation and a contract report.

The result was a 2x faster management reporting cycle, with margins and stock rotation visible on demand. Read the Indep Consulting Odoo ERP and SQL reporting case study.

The bottom line on an Odoo post implementation review

Book the 30, 60 and 90 day reviews before go-live, measure against a baseline, and write the results down. That is how a launch becomes a working system.

The first month is about stability, the second about trusted numbers, and the third about value. A short signed report at each stage keeps everyone honest, and it gives you a clear list of what to fix next.

Ready to review your Odoo go-live?

Get an independent view of how your first 90 days on Odoo are going. Request an Odoo post-launch review, call +91-90235-15208, or email business@iventureteam.com.