Other ERPsFree checklistPDF, Excel, Word exportOdooAfrica

Odoo Go-Live Checklist for African Manufacturers

Odoo is flexible, and that flexibility means go-live failures usually come from skipped basics: localization, tax, currencies, stock opening and backups. This checklist lists those checks for manufacturers working in African markets.

0%

0 of 36 items complete

12 critical items still open - these are the highest-risk gaps.

Download checklist:

Localization and tax

Currency and finance

Inventory and manufacturing

Users, security and infrastructure

Cutover and support

Do not go live with any critical item open. Record owner and date for every non-critical item that is deferred.

Go-live readiness review

Optional: have an expert review your open items before cutover.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Walk through the groups with your consultant and key users a few weeks before go-live, and again in the final week. Mark each item as complete only after you have tested it with real data, not after it has been configured. Export the list to share with the steering group.

Localization and tax first

Odoo ships fiscal localization packages for many countries, and the package installed at database creation drives the chart of accounts and tax setup. Choose the right one early, because changing it after posting is difficult. Always test the tax report against a manual calculation using real invoices.

  • One localization per company
  • Separate tax records for zero-rated and exempt
  • Fiscal positions for exports and exempt customers

Manufacturing and stock

Most manufacturing issues come from unit of measure conversions, wrong bills of materials and opening stock that does not tie to the ledger. Run an end-to-end test of a manufacturing order, from purchase receipt to finished goods delivery, and compare the cost to your expectations.

Common mistakes

Teams often skip restoring a backup, give users admin rights to save time, or load opening stock without a reconciliation. Plan a rehearsal and keep a rollback decision point so you can go back to the old system if needed.

Frequently Asked Questions

Does this apply to Odoo Community and Enterprise?

Yes for the general items. Some features, such as certain localization or e-invoicing connectors, differ by edition and version, so confirm availability for your edition with your partner before the project plan is fixed.

Why test a backup restore?

A backup that has never been restored is unproven. Restoring to a test server confirms the files and database are complete and tells you how long recovery takes, which matters during a power or hosting failure.

How many rehearsals are needed?

At least one full dress rehearsal of data load and reconciliation is a sensible minimum, and two is better for complex multi-warehouse operations. Each rehearsal should produce a timed runbook for the real cutover.

Can I use it for other ERPs?

Many items, such as tax testing, opening balances, user access and backups, apply to any ERP. The product-specific items, like fiscal positions and work centers, should be adapted to your system's terminology.

If you want an AI assistant over your Odoo or other ERP data after go-live, Netray can set that up privately, read-only and with the generated queries visible.