The first weeks after go-live decide whether Odoo becomes the system everyone trusts or the one everyone works around. We are often called in at this stage to rescue a project, and the same problems come up again and again. Almost all of them can be fixed.
1. Stock in Odoo does not match the shelves
Usually caused by opening stock imported without lots, receipts validated late or returns done outside Odoo. Fix: do one clean stock count, adjust it in Odoo, and make every movement go through a transfer from then on.
2. Accounting reports look wrong
Wrong account mapping on products or taxes sends entries to the wrong place. Fix: review product categories, tax mapping and journal settings, then correct the past entries in one controlled batch.
3. The team is back in Excel
This means Odoo is harder than the old way for some task. Fix: ask each team which step is slow, simplify it with a filter, a report or a small automation, and train again on just that screen.
4. Screens are slow
Often caused by heavy custom fields, missing database indexes, too many scheduled actions or a server that is too small. Fix: measure first, then clean the slow code or resize the server.
5. Invoices and documents print badly
Default report layouts rarely match local needs such as Urdu text, sales tax details or a company stamp. Fix: adjust the QWeb report templates once, for every document type.
6. Users can see or change too much
Everyone was made an administrator to save time during setup. Fix: create proper access groups by role and remove admin rights from daily users.
7. Integrations stop syncing
Marketplace or courier connections fail silently when a password or API key changes. Fix: turn on error logs and alerts so failed orders are seen the same day.
8. Nobody can upgrade
Heavy custom code written without upgrades in mind blocks every new version. Fix: replace custom code with standard features or maintained apps where possible, and port the rest properly.
In most rescues the software was fine. The real problems were missing training, unclear ownership of master data and customizations nobody documented. Fixing those three makes Odoo stable surprisingly fast.
Frequently asked questions
Should we start a new Odoo from zero?
Rarely. Most systems can be repaired by keeping what works and fixing what does not, which is faster and cheaper than starting again.
Can someone else fix what our partner built?
Yes. Another partner can audit and fix an existing Odoo. Make sure you have admin access and a copy of all custom modules first.