Chapter 2 Odoo Go-Live Sequence

Odoo is a modular system. The advantage is that companies can enable applications as needed. The challenge is that new users may not know where to start.

This chapter provides a general go-live sequence suitable for small and medium-sized companies. It is not the only correct answer, but it is a safe path for most companies implementing Odoo by themselves for the first time.

Overall Principles

The go-live sequence should follow three principles:

• Master data before business documents;
• Main process before automation;
• Native Odoo before custom development.

Many projects fail not because Odoo cannot do something, but because the sequence is reversed. Teams start with complex approvals, reports, integrations, and custom pages, while master data and business processes are not yet stable.

Recommended Go-Live Stages

Do not skip Stage 0 and Stage 1. They may not create business documents, but they determine whether the system will be stable later.

Stage 0: Prepare The Test Database

The test database should first complete these basic actions:

• Create company information;
• Set language and time zone;
• Create business users other than the administrator;
• Install the modules required for the current phase;
• Configure basic document layout;
• Prepare a test customer, test vendor, and test product set.

Do not be afraid of making a mess in the test database. Its value is to let the team make mistakes before go-live.

Stage 1: Master Data

Master data is the foundation of Odoo.

Recommended preparation sequence:

1. Company data;
2. Users and permissions;
3. Customers and contacts;
4. Vendors;
5. Product categories;
6. Products;
7. Warehouses and locations;
8. Taxes;
9. Bank accounts;
10. Opening inventory and accounting balances.

If customer, product, and vendor data are not clean, do not rush to import them. It is better to import a smaller set of high-quality data than a large amount of incorrect data.

Stage 2: Sales, Purchase, And Inventory Loop

For trading companies, the first process to validate is usually:

Customer quotation -> Sales order -> Purchase order -> Receipt -> Delivery -> Customer receipt

This stage should verify:

• Can sales users create quotations?
• After a quotation is confirmed, does inventory generate a delivery demand?
• If there is not enough stock, can purchase replenish the goods?
• After purchase receipt, does inventory increase?
• After delivery, is the customer order status correct?
• Can partial delivery, order cancellation, and returns be handled?

Finance does not need to be very detailed at this stage, but business documents must move smoothly.

Stage 3: Finance Loop

After the business process works, finance should join the validation.

The finance stage should verify:

• Can a sales order create a customer invoice?
• Can a purchase order match a vendor bill?
• Can customer payments be registered?
• Can vendor payments be registered?
• Can bank statements be imported or synchronized?
• Can bank transactions be reconciled with invoices or payments?
• Are receivables, payables, and aged reports understandable?

Many Chinese companies think of "invoice" as the official VAT invoice. In Odoo, an Invoice is an accounting receivable or payable document, not the same as a Chinese tax-control invoice. If a domestic company needs to connect to a tax invoicing platform, it should be evaluated separately.

Stage 4: Permissions And Reports

Permissions should not wait until after go-live. Once the business process works, testing should switch to real role-based accounts.

At minimum, test these roles:

• Can sales users see only the customers and orders they are responsible for?
• Can warehouse users receive and deliver goods, but not change sales prices?
• Can purchase users create purchase orders, but not edit accounting entries?
• Can finance users process invoices and payments, but not casually change inventory?
• Can managers view reports without participating in daily document entry?

Reports should also be confirmed at this stage. Do not wait until after go-live to discover that the indicators management needs are not available.

Stage 5: Go-Live Rehearsal

Run at least one full rehearsal before go-live.

Do not test only the smooth path. Intentionally test exceptions:

• Sales order cancellation;
• Partial delivery;
• Customer return;
• Partial purchase receipt;
• Vendor bill amount different from the purchase order;
• Partial customer payment;
• Bank statement line without a matching invoice;
• Employee without permission for a certain button.

Only when exception flows can also be handled is the system truly usable.

Stage 6: Formal Go-Live

Before formal go-live, define a cutover date.

For example:

Starting from August 1, 2026, all new sales orders will be entered in Odoo. The old system will be used only for historical lookup and no longer accepts new transactions.

At cutover, handle:

• Opening inventory;
• Opening receivables;
• Opening payables;
• Unfinished sales orders;
• Unfinished purchase orders;
• Unfinished deliveries and receipts;
• Bank balances;
• Old system read-only or data-entry stop rule.

Do not let two systems enter the same type of business for a long time. The data will eventually fail to match.

Stage 7: Phase-Two Optimization

After phase one goes live, consider phase two.

Phase two is suitable for:

• Approval flows;
• Automatic replenishment;
• Pricing rules;
• Commissions and rebates;
• Website eCommerce;
• POS stores;
• WeChat, WeCom, payment, and logistics integrations;
• Management dashboards;
• Industry-specific custom modules.

Customization at this stage is usually more accurate because the customer already knows what native Odoo can do and what is truly missing.

Go-Live Methods Not Recommended

Avoid these approaches:

• Installing every module on the first day;
• Building custom development before testing the native process;
• Operating directly in production without a test database;
• Letting only the owner or administrator test, without real role users;
• Changing master data at large scale during go-live;
• Not defining the cutover date between the old system and Odoo.

Minimum Success Standard For Self-Implementation

If a customer is not sure whether the system is ready, use this table:

Meeting these conditions makes go-live much safer.