Before you make a change to your live Odoo environment — a new module, a modified workflow or a complete version upgrade — you want to test first. "Just trying it quickly in production" sounds harmless, until a wrong posting ends up in your real accounts. That is what the Odoo test environment is for: a complete copy of your production database in which nothing can break.
What is a test environment?
A test environment (also called a staging or duplicate database) is a 1-to-1 copy of your live Odoo, including all your customers, products and settings. You can click around, post entries and change data in it — without anything changing in your real environment. Does something go wrong? Then you throw the copy away and make a new one.
How do you make a copy?
On Odoo.sh: in the project dashboard, drag the production branch to staging, or click the branch and choose "Duplicate". Within 5–15 minutes you have a fully working staging environment on a separate URL — recognisable by the coloured bar at the top, so nobody accidentally works in the wrong environment.
On Odoo Online: via the customer portal (odoo.com → My Databases) you request a test environment that uses a recent backup. It too runs on its own URL, separate from your live database.
Veelvoorkomende valkuilen
The test environment is deleted automatically after 1 month. Don't build long-running tests in a staging — Odoo.sh cleans up automatically. For longer projects, such as preparing an upgrade over several weeks, use a dev branch.
Emails, payments and integrations. In a test environment, outgoing emails are blocked by default and external APIs (banks, webshops, parcel carriers) are not executed. That is deliberate: it means you won't send a payment reminder to a real customer from a test. If you want to test mail flows, use a mail catcher or your own test address.
Stale data. A staging that is three weeks old says little about your current situation. Always make a fresh copy just before an important test.
When do you use a test environment?
- Before every Odoo version upgrade — test at least your invoicing and inventory flow
- Before you install a new module or change configuration
- To walk through new workflows with colleagues before they go live
- For training new users, without the risk of real postings
- To test reports or data imports with your real data
Practical tip: agree on one rule within your team — configuration changes never go straight into production, however small. Need help setting up a good test workflow? Contact DAADit Group or start the free Business Scan.
Start the Business Scan →Before you roll out a change in your live Odoo environment — a new module, an adjusted workflow or a complete version upgrade — you want to test first. "Let's just quickly try it in production" sounds harmless, until a wrong entry lands in your real books. That is exactly what the Odoo test environment is for: a full copy of your production database where nothing can break.
What is a test environment?
A test environment (also called staging or a duplicate database) is a one-to-one copy of your live Odoo, including all your customers, products and settings. You can click around in it, post entries and change data — without anything changing in your real environment. Something goes wrong? Throw the copy away and make a new one.
How do you create a copy?
On Odoo.sh: in the project dashboard, drag the production branch to staging, or click the branch and choose "Duplicate". Within 5–15 minutes a fully working staging environment is available at a separate URL — recognisable by the coloured bar at the top, so nobody accidentally works in the wrong environment.
On Odoo Online: through the customer portal (odoo.com → My databases) you request a test environment that uses a recent backup. It also runs on its own URL, separate from your live database.
Common pitfalls
The test environment is automatically deleted after 1 month. Do not build long-running tests in a staging environment — Odoo.sh cleans up automatically. For longer projects, such as preparing an upgrade over several weeks, use a dev branch.
Emails, payments and integrations. In a test environment outgoing emails are blocked by default and external APIs (banks, webshops, carriers) are not executed. This is intentional: you don't want to send a payment reminder to a real customer from a test. If you need to test mail flows, use a mail catcher or your own test address.
Stale data. A three-week-old staging says little about your current situation. Always make a fresh copy right before an important test.
When do you use a test environment?
- Before every Odoo version upgrade — test at least your invoicing and inventory flows
- Before you install a new module or change configuration
- To walk through new workflows with colleagues before they go live
- For training new users, without the risk of real postings
- To test reports or data imports with your real data
Practical tip: agree on one team rule — configuration changes never go straight into production, however small. Need help setting up a solid test workflow? Contact DAADit Group or take the free Business Scan.
Start the Business Scan →