Demo Odoo: what to test before you commit

Opening the shared demo puts you in a shared database that lasts only a few hours and opens as admin. Neither Odoo's docs nor the redirect name that sample company's country, currency, or chart of accounts. Fit is a question for a separate Odoo Online trial: free instant access, no credit card, with the United States and Canada on the country list. The trial page does not state how long your database lasts. Learn the menus on the shared demo, then test tax, documents, and plan limits on a trial with your country set before you subscribe.

What you open when you look for a demo odoo

Three different things share the word demo in search results. Mixing them up is how a good afternoon becomes a bad subscription.

The shared demo needs no registration. Requesting https://demo.odoo.com redirects to a master demo path, then to a demo worker URL that includes user=admin and key=admin, as of October 2026. Odoo’s Online documentation says each of these shared databases is available for only a few hours. Treat it as a throwaway classroom. Do not load customer names, prices, or bank files into it. Do not treat the sample company as your fiscal setup. Neither the docs nor the redirect name the country, currency, or chart of accounts that master database uses.

The Odoo Online trial is a private database with your own name on a .odoo.com domain. The trial form asks for your name, company, domain, email, phone, country, language, company size, and primary interest, and it includes an app picker. Start Now accepts the Subscription Agreement and Privacy Policy. Copy on that page says free instant access and no credit card. It does not say how many days the database lasts, how many users it allows, or whether sample data is loaded. Confirm those three points in the inbox message you receive after signup, before anyone keys a month of invoices.

Odoo Online itself is a private database hosted by Odoo, used in a browser with no local install. The same administration page says you can run it for production or to test Odoo, including customizations that do not require custom code. It also says Odoo Online is incompatible with custom modules and with modules from the Odoo Apps Store. A trial on Odoo Online can prove configuration. It cannot prove an Apps Store connector or a module your developer would write.

Once you have your own database, duplication is the safe way to experiment. Duplicating an Odoo Online database defaults to "For testing purposes," which disables external actions such as emails, payments, and delivery orders. Duplicates expire after 15 days, and a database can have at most five duplicates unless Odoo Support extends the limit. That 15-day clock applies to duplicates. Ask Odoo to confirm the original trial's duration in the signup message. If a test must send a sandbox payment or a carrier label, run it on a database that is not flagged for testing purposes, or the external action will be switched off.

Hosting transfer documentation names three regions: Americas, Europe, and Asia. If a customer contract or a bank requires data to stay in a region, ask Odoo which region your trial database uses before you import anything sensitive.

What the shared demo hides

A polished sample company can make quote screens, inventory screens, and a dashboard look finished. The decisions that change the bill, and the ones that are painful to undo, sit outside that sample.

Country and tax package

Fiscal localization is installed from the company country, as the fiscal localization guide describes. The United States package follows US GAAP when the country is United States, and it includes optional modules for US accounting reports, check layouts, NACHA payments, 1099 reporting, AvaTax, and US payroll. Sales tax varies by jurisdiction, and AvaTax is documented for the United States and Canada. The Canada package (l10n_ca) ships provincial and territorial fiscal positions for AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, and YT, plus International, a Canadian chart of accounts, Balance sheet (CA) and Profit and loss (CA), Canadian check layouts, and optional CPA005 EFT payments. Tax follows the province of delivery. A shared demo that never asks for your country leaves every one of those pieces untested.

The lock after the first posted entry

The localization package can be changed only if no entry has been posted. In a multi-company database each company can use a different localization, but branches always follow the parent company. If someone posts a sample journal during a casual click-through, that company can lose the option to swap the package. Start the tax test on a company that has never posted, with the country set before the first invoice.

Studio and the plan it pulls you onto

Studio’s own page says installing Studio on a Standard-plan database triggers an upsell to Custom. Yearly or multi-year contracts get an upsell order with a 30-day limit. Monthly contracts switch at the next bill. Adding a field because the screen looks close to your current one can be the click that changes the price list.

Apps you cannot install on Odoo Online

Custom modules and Apps Store modules are incompatible with Odoo Online. If the fit depends on a shipping connector, an industry module, or code, an Online demo or trial leaves that module uninstalled. That test belongs on Odoo.sh or on-premise, which the Custom plan allows. Odoo.sh hosting is not included in the Custom price.

Who calls whom

The pricing page says the External API, meaning calls into Odoo from outside software via JSON-RPC or XML-RPC, is a Custom-plan feature. Calls that Odoo initiates, including payment providers, delivery carriers, VoIP, and bank synchronization, are part of the Standard plan. A storefront that pushes orders into Odoo is a different plan question from Odoo calling a carrier.

Your own credentials

Bank feeds, payment providers, and carriers need your accounts. Sample data leaves your bank file, your payment processor, and your warehouse labels untested. Connect a sandbox only after you know whether the database is flagged for testing purposes, because that flag disables payments and delivery orders.

Two sentences on One App Free that disagree

The pricing FAQ says installing Studio or adding companies on a One App Free database automatically switches the database to the Custom plan. The same FAQ says the free plan allows multiple companies and that Studio can be the one free app. Both statements are on the page as of October 2026. Get Odoo to say which rule a new database follows before you design a free pilot around a second company or around Studio.

Legal compliance sits outside the demo

Odoo Enterprise Subscription Agreement version 13, dated 24 September 2026, is governed by Belgian law. Odoo SA does not warrant that the software complies with any local or international law or regulation. A demo company that prints a clean invoice has not confirmed US GAAP, 1099s, or a provincial return. Those checks are the tax test above, run on your country package.

Five tests to run on your own trial

Run these on the trial database after you set the company country, not on the shared demo. Write the expected result before you click. A pass is a document you would send to a customer or a vendor, with the tax, the terms, and the quantities your team uses this month.

Bring five real documents to the screen: a recent quote, a vendor bill that was received against a purchase order, a customer ship-to in a second state or province, a second legal entity or branch if you have one, and the name of one outside system that must exchange data with Odoo.

1. Quote to cash on your payment terms

Create a customer with the payment terms you use (net 30, a deposit, or progress billing). Raise a quotation with one stocked product and one service. Confirm the order, deliver or complete the service, and invoice it. Check that the due date, the deposit line, and the revenue account match what your controller expects under the localization you installed. If you want to push the invoice to a payment provider, do it from a database that is not set to "For testing purposes," because that flag disables payments.

2. A vendor bill matched three ways

Enter a purchase order, receive a partial quantity, and record the vendor bill for the received quantity only. The bill should match the receipt, leave the remainder open, and hit the stock and expense accounts your accountant named in advance. This is the test that catches a chart of accounts that looks familiar and posts differently. If the US check layout or Canadian check layout matters for how you pay that vendor, print one check to PDF and compare the alignment with the stock you use.

3. Tax by delivery jurisdiction

For a US company, invoice a customer with delivery in a different state from your warehouse and confirm the fiscal position and tax lines follow that delivery, not the office on your letterhead. Optional pieces you may need later, and should at least see in the app list, include US accounting reports, NACHA, 1099 reporting, and AvaTax. For a Canadian company, pick the fiscal position for the delivery province (ON, QC, BC, or whichever you ship into) and confirm GST, HST, PST, or QST on the invoice matches how you file today. Tax follows the province of delivery in the Canada localization. AvaTax is documented for Canada as well as the United States. One invoice in one province is a start. A second invoice into a zero-rated or out-of-country fiscal position (International is in the Canada list) shows whether the package covers that odd order as well as the home province.

4. A second company or a branch

Skip this if you have a single entity. If you have two companies, create the second with its own country so its localization can differ, then post nothing until the package is the one you meant. If the second location is a branch, expect it to follow the parent. The pricing FAQ’s two statements on multi-company and One App Free are the reason to watch the subscription banner after you add the company. Screenshot the plan name before and after.

5. One outbound link and one inbound link

Outbound first, because Standard includes calls Odoo initiates: a payment provider, a delivery carrier, or bank synchronization. Connect a sandbox or a single bank account and import a short statement. Odoo’s accounting features page says machine-learning reconciliation automatically matches 95% of bank transactions. That figure is Odoo’s own claim. Score the match rate on your statement and keep the number. Your file is the one that matters.

Inbound second. If another system must create or edit records in Odoo, that path is the External API and it sits on the Custom plan. Name the system, the direction of the call, and the plan that direction requires, and keep that note with the screenshots. Building the integration can wait until the plan is chosen.

While you are in accounting, resist posting a pile of opening balances until tests 3 and 4 are done. The localization package locks once an entry is posted.

Which plan and edition those tests imply

The public demo is not labeled Community or Enterprise on the editions page. The editions page describes two editions and calls Community the core of Enterprise. It shows a feature table that includes Accounting, Studio, Payroll, Helpdesk, and inventory barcode. Read the live checkmarks yourself before you repeat a feature claim internally. The copy we rely on for buying is the pricing page and the download page, where the labels are explicit.

The download page lists Community and Enterprise installers for Odoo 20, 19, and 18 (Windows, Ubuntu/Debian, RPM, and sources). Enterprise download requires a subscription code. A Try without installing link goes to the trial. The mobile app and Virtual IoT rows are labeled Odoo Enterprise. The Online, localization, and Studio pages linked above are the 19.0 set. Ask Odoo whether version 20 changed trial or localization behavior before you rely on a 20 database for those tests. Ask for a 19.0 or 20 screen only if you know which version the project would run.

Plans, as of October 2026, from the US pricing page:

• One App Free (What Odoo says you get: One app, unlimited users, Odoo Online. Dependent apps the chosen app requires stay free. · Published figures: USD 0)
• Standard (What Odoo says you get: All apps on Odoo Online · Published figures: USD 24.90, USD 31.10, and USD 38.90 per user per month shown together)
• Custom (What Odoo says you get: All apps on Odoo Online, Odoo.sh, or on-premise, plus Odoo Studio, Agentic AI, multi-company, and External API. Odoo.sh hosting is extra. · Published figures: USD 49.00, USD 61.00, and USD 76.20 per user per month shown together)
• Light User (What Odoo says you get: A user designated Light User, or an active employee record not linked to an active non-portal user. Sold via an advisor quote. · Published figures: USD 8.90 per light user)

The pricing card shows Yearly and Monthly toggles, and a footnote says the discount is valid for 12 months for the initial users ordered. The three Standard figures and the three Custom figures were on the cards at the same time, so do not treat one of them as the yearly price and another as the monthly price until you toggle the live page and write down which number moves. A pricing URL with a Canada country parameter still showed US dollars in October 2026. Budget licenses in USD and ask for a Canadian quote if you need CAD.

A paying user is an active backend user who creates, views, or edits documents, or an employee record in the HR app with no linked user. Portal users such as customers and suppliers are not paying users. Count warehouse staff who only confirm receipts before you assume they are free portal users. If they edit documents, they are paying users.

Subscription price includes hosting, maintenance, and email support Monday to Friday, 24/5, in English, French, Spanish, or Dutch. It excludes implementation services, Odoo expert services, in-app credits (SMS, contact auto-complete, lead generation, and AI scan of vendor bills and expenses), Odoo.sh hosting, and maintenance of custom code. Odoo describes Online storage as unmetered up to 100GB under its acceptable-use policy. Hosting and licenses are the subscription lines. Implementation hours and in-app credits are billed separately, and they are the lines that move the budget. Odoo pricing by plan and user count walks the same cards in more detail.

Assume 12 paying users on Standard, which is a common finance-plus-operations core for a single-entity distributor under a few dozen staff. At the three published figures the monthly license math is USD 298.80, USD 373.20, or USD 466.80, before you know which toggle applies, and before Light Users at USD 8.90. The same 12 users on Custom, which is where Studio, multi-company, External API, Odoo.sh, and on-premise sit, come to USD 588.00, USD 732.00, or USD 914.40 a month on those same unpublished toggle assignments. If tests 4 or 5 failed on Standard, price Custom before you compare Odoo with another system. One App Free at USD 0 is coherent only when one app, including its dependent apps, covers the work and you have confirmed the multi-company and Studio rules in writing.

Renewal sits in the same agreement as the compliance disclaimer. If the prior price is below the current list price, renewal charges can rise by up to 7% per year of the previous term. Put that ceiling next to the Standard or Custom figure you lock, once the toggle is clear.

What the first block of hours costs

License fees leave the company unconfigured. Odoo sells Success Packs as hour bundles, with a 15% discount on the first pack for a new customer. Travel time and expenses are extra. These are Odoo SA consultant hours. A partner or independent project is a separate statement of work, so ask each bidder to price data migration as its own line.

As of October 2026, from the Success Packs page:

• Starter (Hours: 4 · Returning price: USD 580 · New-customer first pack: USD 493)
• Basic (Hours: 25 · Returning price: USD 3,600 · New-customer first pack: USD 3,060)
• Standard (Hours: 50 · Returning price: USD 7,000 · New-customer first pack: USD 5,950)
• Custom (Hours: 100 · Returning price: USD 12,500 · New-customer first pack: USD 10,625)
• Pro (Hours: 200 · Returning price: USD 25,000 · New-customer first pack: USD 21,250)

Starter includes no app customization. The Standard pack is the smallest one Odoo describes as including data import assistance. Performance work requires a pack of at least 50 hours. The Custom pack includes customizations, and extra monthly charges apply for maintenance of extra modules or lines of code. The Pro pack includes customizations and developments. A trial that proved you need a custom field, an import of open orders, and a faster pick screen has already walked past Starter and Basic.

Odoo states that companies under 50 employees usually buy Success Packs directly from Odoo, companies over 50 employees usually use a partner, and companies over 250 employees should contact Odoo. Above 50 users the project estimator tells the visitor to contact Odoo for an in-depth analysis. The estimator also says 80% of projects within the selected scope are put in production in 200 hours or less. Scope is the variable: two legal entities or an inbound integration change the plan and the scope conversation separately from headcount. Before you sign hours with anyone, read how to choose an Odoo implementation partner.

The same page states "98% implementation success rate, vs 65% without success pack" and labels that comparison "(self)". Use it as Odoo’s own marketing line. Judge a proposal by named people, hours against your five workflows, references you can call, a phase plan, and who owns the configuration and any code afterward.

Odoo says companies over 50 employees usually use a partner. Ask both Odoo and the firm that would run the project to price the same scope, with data migration on its own line in each answer. On our own projects, the aim for a first usable phase is 8 to 12 weeks. How long an Odoo implementation takes covers the drivers that move a project inside or outside that kind of window: data quality, the number of apps, and whether custom code is in phase one. ERP implementation for a company your size is the broader engagement around that phase, including the cutover and the weeks after go-live.

When a trial is enough and when you scope a pilot

Keep the shared demo if you still need to learn where menus sit. A few hours is enough for that, and the database will disappear on Odoo’s clock.

Move to the trial when the question is your company: country set to United States or Canada, one quote, one receipt, one tax jurisdiction, and a written note on Standard versus Custom. Stay on the trial if those documents post the way finance described and you do not need Apps Store modules, custom code, or an inbound API.

Scope a paid first phase when any of these showed up in the notes: a second company whose plan banner changed, Studio fields you cannot live without, an inbound integration, a chart of accounts you do not want to rebuild after go-live, or data import of open orders and stock. The smallest public hour block that includes import help is the 50-hour Standard Success Pack at USD 5,950 for a new customer or USD 7,000 returning. If you are over 50 employees, ask for the same scope as a fixed first phase from the firm that would run the project, with data import priced on its own line.

Either way, export your test documents and screenshots before the database expires or you lose the duplicate. The trial page does not give the original database a retention period. Duplicates expire after 15 days. A pilot that lives only in someone else’s memory will get re-decided during the project, at a higher rate.

What to record so the decision survives the demo

Close the laptop with a one-page record. Future you, and anyone pricing the project, needs the same six lines.

1. Database type: shared demo, trial, or duplicate, plus the date and time you started. Shared demos last only a few hours. Duplicates last 15 days and block emails, payments, and delivery orders when left on the testing-purposes setting.
2. Company country, localization name, and whether any entry was posted before you finished the tax test.
3. Plan name shown in the subscription banner before and after any Studio install or second company.
4. Pass or fail on each of the five workflows, with the invoice PDF and the vendor bill attached.
5. Direction of every integration: Odoo calls out (Standard) or an outside system calls in (Custom).
6. Which pack features the tests implied, so the ask matches the pack that carries each: import assistance has a floor at the 50-hour Standard pack, customizations at the 100-hour Custom pack, and travel and custom-code maintenance are extras on top. Give each bidder the five workflows and ask for hours against those.

That page is the briefing for a working session on Odoo implementation. Bring the five documents with it. The conversation can then price the gap between what the trial already proved and what still has to be configured on your data.

How Flectic can help

Flectic implements Odoo one app at a time for companies of 20 to 100 people in the US and Canada, so a demo should test the apps that remove your manual work first. Flectic sends a written proposal with a fixed price for each phase before work starts. Review the Odoo implementation approach with us, then Book a free discovery call with Flectic and bring your trial results.

Sources

• Odoo Online, Odoo, October 2026
• Odoo shared demo, Odoo, October 2026
• Odoo Online Trial, Odoo, October 2026
• Odoo Pricing, Odoo, October 2026
• Odoo Success Packs, Odoo, October 2026
• Studio, Odoo, October 2026
• United States fiscal localization, Odoo, October 2026
• Canada fiscal localization, Odoo, October 2026
• Fiscal localizations, Odoo, October 2026
• Odoo Enterprise Subscription Agreement, Odoo, October 2026
• Download, Odoo, October 2026
• Compare Editions, Odoo, October 2026
• Hosting, Odoo, October 2026
• Accounting features, Odoo, October 2026