How to choose an Odoo partner in Canada

As of October 2026, Gold on Odoo's partnership page means 300 new Enterprise users in a year, six certified staff and 80 percent retention. Ready is 10 new users and one certified resource. Silver is 75 new users, three certified resources and 70 percent retention. Those tests do not cover GST, HST, PST or QST. For a first implementation, match the card's average project size to your user count, then have the bidder show the Canada chart, the provinces you ship into, and whether payroll is inside the fee.

Service fees are the partner's. Odoo does not take a percentage of them. As of April 2026, Octura's manufacturer guide prices a one-site project of 10 to 25 users at CAD 25,000 to CAD 55,000 on a fixed-fee statement of work. As of May 2026, Solvync's cost guide prices a focused first release at about CAD 8,000 to CAD 18,000 and leaves license, hosting and taxes outside that figure. There is no shared Canadian rate card behind either figure.

What Ready, Silver and Gold require

Odoo lists four levels: Learning, Ready, Silver and Gold. The operational bars that matter for a shortlist are the three official tiers. As of October 2026 the partnership page sets them as follows.

• Ready (New Enterprise users a year: 10 · Certified internal resources: 1 · Retention: Not published on that row)
• Silver (New Enterprise users a year: 75 · Certified internal resources: 3 · Retention: 70 percent minimum)
• Gold (New Enterprise users a year: 300 · Certified internal resources: 6 · Retention: 80 percent)

The current partnership agreement, the French text published with the 19.0 legal documents, uses the same figures: 10, 75 and 300 net new Enterprise users a year, and 1, 3 and 6 employees certified on at least one of the last three versions. Retention in that text is 70 percent for Silver and 80 percent for Gold. Each quarter, the level is set to the highest level whose three tests are met.

An older English agreement is still online in the Odoo 14 user docs. It sets Silver at 50 new users and 2 certified employees, and Gold at 150 new users and 3 certified employees, with the same 70 percent and 80 percent retention floors. That page is not the current program. If a proposal cites 50 or 150 new users as the bar, ask the firm to walk the current tests instead.

The partnership fee is not your project price. The partner pays it to Odoo, and the same fee applies to Ready, Silver and Gold. As of October 2026 the Japanese version of the partner page shows Learning at USD 990 and Ready, Silver and Gold at USD 3,950. The English partner page localizes those fees, and one presentation of it lists 590 euros for Learning and 2,950 euros for the three official tiers. Read the currency on the page you open. Service work is the partner's revenue: analysis, configuration, deployment, development, training and hosting, at prices the partner sets.

A Gold badge still leaves you to name the consultant who will map your provinces.

How to read a Canada partner card

Each card shows a tier, a reference count, an average project size, a large-project size, industry tags and a certified-expert count. Compare the average to your user count. The large-project figure tells you the firm has delivered something bigger. It is a weak signal for a 20-person first phase.

Cards visible for Canada in October 2026 included these four.

OERP Canada showed Gold, an average project of 18 users, a large project of about 200 users and 129 references. A distributor with about 20 users is close to that average and far from 200. Ask for a reference near 20 users, in your industry, in a province you ship to, and call that customer.

Bista Solutions Canada showed Gold, an average of 28 users, a large project of about 100 and 12 references. A 25-user company sits near the average. Twelve references is a short list, so ask to speak with two, and ask which office configured the file.

Smart Information Technologies Ltd showed Silver, an average of 15 users, a large project of about 100 and 22 references. Silver's published test is 75 new Enterprise users, three certified resources and 70 percent retention. For a 15-user services firm, that average is the useful field. Keep a Ready firm on the list when they can open a finished Canadian company and name the person who configured it.

Captivea Canada's card showed Silver and an average project of 39 users. The firm's own Canada page is Silver-labelled, and other pages on that site call the Canada office Gold. On the day you meet them, read the live card and ask which quarter the level was last set. Then ask them to open a Canadian company of about that size.

Public lists disagree with each other. OEC.sh's Canada page presents a Gold-only list as the full set. ERP Research's Canada page is a lead-gen directory whose title and body do not state the same total. Neither page shows how a tier is earned, and neither prices a statement of work. Write down the live card, then spend the meeting on the chart, the provinces and the people.

What a Canadian rollout adds to the scope

A quote copied from a US rollout misses the Canada package. Installing a company with country Canada installs Canada - Accounting (l10n_ca), Canada - Accounting Reports (l10n_ca_reports) and Canadian Checks Layout (l10n_ca_check_printing). Odoo's Canada chapter says that package adds a Canadian chart of accounts, default taxes, and one fiscal position per province and territory plus International.

If the country is blank, or no localization module matches, Odoo installs the generic chart l10n_generic_coa, which is the US chart, by default (accounting localization guide). The installed chart is the generic US chart. Have the partner read the module name on a test company before discovery hours are spent.

Fiscal positions follow the delivery

The tax that applies follows the province where delivery happens. A customer in another province who is shipped goods should have that province's fiscal position. A customer who picks up goods should not. An international vendor who charges no tax uses the International fiscal position.

Assume your warehouse is in Ontario. A Quebec customer who receives a shipment should sit on the Quebec fiscal position. A Quebec customer who collects the goods at your dock should not. Shipped goods use the destination province, a pickup does not, and a no-tax international vendor uses International.

The fiscal positions named in the Odoo 19 Canada docs are Alberta, British Columbia, Manitoba, New Brunswick, Newfoundland and Labrador, Nova Scotia, Northwest Territories, Nunavut, Ontario, Prince Edward Islands (that is Odoo's label), Quebec, Saskatchewan, Yukon and International. Tick every province you ship into. Ask the partner to post one customer invoice on each of those positions, plus a pickup order and an international vendor bill.

A Mississauga page says, "The province-by-province tax model is where a generic team comes unstuck." (Mississauga Canada page).

A Canadian user on the Odoo forum wrote, "Canadian legislation requires that the early cash discount be applied before taxes." (early cash discount thread). The thread's example is a 2 percent discount on CAD 1,000 plus GST and QST, and the user could not get the calculation they wanted. That report is one configuration complaint. Have your partner post the same invoice on a test company and walk the journal entry with the person who files your return.

Another Canadian user asked, "My Canadian CoA does not have accounts 111313 (Outstanding Receipts) and 111314 (Outstanding payments). Is this normal?" (default accounts thread). Have the partner name the installed chart and confirm the module is Canada - Accounting.

Checks and the CPA005 file

Canadian check printing supports three layouts: check on top (Quicken or QuickBooks), middle (Peachtree) and bottom (ADP). If you still print checks, pick the layout your bank stock uses and print one void check in week one.

The documented Canadian EFT path is a file the company uploads. The separate module CPA005 Payments (l10n_ca_payment_cpa005) builds a CPA005 file for Canadian batch payments. The bank needs a 5-digit destination data centre and a 10-digit originator ID, and the company short name is capped at 15 characters. Ask the partner to generate the file with your originator ID and your short name. If a proposal promises a live feed from your bank, ask to see that feed on your account. The Canada chapter documents the file you upload.

Payroll and French

Payroll is the line that makes two quotes incomparable. Odoo 19's payroll localization index includes the United States and does not include Canada. CPP, EI, QPP and provincial income tax are a product decision you make before you compare fees: a third-party app, a payroll bureau outside Odoo, or a scope that leaves payroll where it is.

On the Odoo Apps Store, the module odoo_hr_payroll_canada describes itself as a Canada payroll localization for Odoo 19 Enterprise covering CPP, CPP2, EI, and federal and Ontario tax (app page). It is not an Odoo S.A. module, and it requires Enterprise Payroll. A companion app maps payslips to the l10n_ca chart. The page covers federal and Ontario tax, so a Manitoba or Quebec payroll still needs its own answer. Put the app name, the bureau's name, or a line that payroll is excluded in the statement of work.

French is a question about who does the work. A Quebec page sells the setup with the line "We configure your instance French-first." (Quebec setup page). Ask whether that means a French user interface, French training material, or a consultant who can run workshops in French. Quebec staff often need the consultant in the room. The Canada chapter does not document a Revenu Québec filing screen. If a proposal says the system files with Revenu Québec, have them show that step on a test company before you count it as included.

What published Canadian fees include

Odoo says partners set their own service prices. There is no Odoo rate card for implementation in CAD. Each range below is that firm's own page, dated to the month on it.

Calibre Consulting Corp. of Calgary tells buyers, "There is no price list because each build is different." (customer page). The same page says, "A fixed scope and a fixed number. You approve the number before work starts." (customer page).

A Calgary implementation page names the commercial shapes as "Fixed price, time and materials, or a dedicated team." (Calgary implementation page). It adds, "A well-defined, single-module rollout suits a fixed price. Evolving scope or multiple integrations suit time and materials." (Calgary implementation page). That page ties a fixed price to a single closed module and time and materials to evolving scope or several integrations. Your scope of accounting, sales, purchasing and inventory sits between those examples, so ask which commercial shape the bidder priced and which modules sit inside the number. EDI, a custom module and a payroll app that is still being chosen are the moving scope that page describes, so price them on time and materials or on a later phase with their own number. A fixed fee that excludes tax configuration, French training, data migration and a named go-live window cannot be lined up against a time and materials estimate that includes them.

Three published ranges, with different contents

The April 2026 manufacturer guide calls these fixed-fee statements of work in CAD.

• 10 to 25 users, one site (Fee: CAD 25,000 to CAD 55,000 · Calendar: 8 to 12 weeks)
• 25 to 75 users, multi-site or bilingual (Fee: CAD 55,000 to CAD 120,000 · Calendar: 12 to 20 weeks)
• 75 to 250 users, multi-company, EDI or custom modules (Fee: CAD 120,000 to CAD 180,000 or more · Calendar: 20 to 32 weeks)

The May 2026 Calgary guide leaves license, hosting and taxes outside every row.

• Focused first release: about CAD 8,000 to CAD 18,000
• Accounting, sales, purchasing, inventory: CAD 18,000 to CAD 45,000
• Operations-heavy rollout: CAD 45,000 to CAD 95,000 or more

The May 2026 blog presents its bands as that firm's estimates and lists development at CAD 85 to CAD 175 an hour beside them.

• 11 to 50: CAD 20,000 to CAD 60,000
• 51 to 200: CAD 60,000 to CAD 150,000

Assume 25 users, one warehouse in Ontario, shipments to Ontario and Quebec, an English interface, payroll left with your current bureau, and a scope of accounting, sales, purchasing and inventory.

On the manufacturer guide, 25 users and one site match CAD 25,000 to CAD 55,000 and the 8 to 12 week calendar. The middle row as published reads 25 to 75 users, and multi-site or bilingual, at CAD 55,000 to CAD 120,000 over 12 to 20 weeks. This example is one site and English, so neither condition is met, and the match stays CAD 25,000 to CAD 55,000. Ask which band they used if the quote jumps. If Quebec staff need French screens, 25 users falls inside 25 to 75, and the bilingual condition on that page puts the fee at CAD 55,000 to CAD 120,000 over 12 to 20 weeks.

The Calgary guide's middle band is defined by those four apps, not by a user count. The matching published range is CAD 18,000 to CAD 45,000, and license, hosting and taxes are extra. The page does not state a French adder. Ask for one if you need it.

The blog's 11 to 50 user band includes 25 users, so the matching range is CAD 20,000 to CAD 60,000. The hourly rate sits beside that band. The page does not show it already divided into the fee.

All three of those matching ranges contain every amount from CAD 25,000 through CAD 45,000. The Calgary middle band starts lower, at CAD 18,000, and excludes license, hosting and taxes. The blog's matching band starts at CAD 20,000. The manufacturer guide's one-site band starts at CAD 25,000.

The blog's development rate is CAD 85 to CAD 175 an hour. Rounded to the nearest hour, CAD 20,000 at CAD 175 an hour is 114 hours, and CAD 60,000 at CAD 85 an hour is 706 hours. An hourly estimate needs the hours written down before you compare it with a fixed fee. The pricing configurator shows 25 hours of Odoo expert time and does not show a dollar rate for that pack. Those hours stay out of the partner's CAD service total. Next to a CAD 20,000 implementation band, 25 hours is a small block.

An 80-user multi-company project with EDI matches the manufacturer guide's top band: 80 is inside 75 to 250, and the page names multi-company and EDI among the conditions, at CAD 120,000 to CAD 180,000 or more over 20 to 32 weeks. The same headcount falls in the blog's CAD 60,000 to CAD 150,000 band for 51 to 200 users. The Calgary guide calls its top band an operations-heavy rollout and does not tie it to a user count, so ask where EDI is priced.

Gestisoft publishes distribution packages at CAD 37,500, CAD 52,500 and CAD 69,500 starting (distribution ERP packages). The fine print excludes licenses and a 20 percent project-management fee, and the pages are Business Central. Adding that 20 percent fee to the CAD 37,500 sticker produces CAD 45,000 before licenses. Leave that sticker out of an Odoo comparison.

License and Odoo.sh, in US dollars

As of October 2026, the pricing configurator shows US dollars, not CAD. Do not expect a partner's CAD service quote to include these lines unless the statement of work says so.

• One Odoo.sh worker (List, per month: USD 72 · Discounted figure shown: USD 57.60)
• Staging environment (List, per month: USD 18 · Discounted figure shown: USD 14.40)

Storage is USD 0.25 per month per unit before the annual discount (pricing configurator).

Above 16 workers the configurator tells you to contact Odoo. Sixteen workers at the list rate are USD 1,152 a month (16 times USD 72). At the discounted figure they are USD 921.60 a month (16 times USD 57.60). A worker is a hosting unit, and a user is a person. The partner must put the worker count in writing.

Where the database and the backups sit

Odoo describes three hosting types. Odoo Online is the SaaS edition: you open the database in a browser and Odoo operates it. Odoo.sh is the PaaS edition and is the path that allows custom developments and third-party apps. On-premise means Odoo is installed on your own computer or server.

A third-party payroll app needs that second or third path. Online is the edition Odoo operates. Odoo.sh is the one described as allowing third-party apps. When a project is created on Odoo.sh, the deploy form includes a hosting-location choice (Odoo.sh project creation). Partners can start a trial on a partnership code. A paying client project needs an Enterprise subscription that includes Odoo.sh. Have them show the location field on the project they create for you.

Odoo's privacy policy, effective September 24, 2026, says customer databases are hosted in the cloud region closest to the customer, and the customer can request a region change subject to availability. Americas production locations are the USA and Canada, on Google, OVH and Amazon. Americas backups are Europe (France and the Netherlands) plus Canada, on Google and OVH. Buyers cannot choose or restrict backup locations. Odoo commits to at least three redundant backup copies of each customer database, in data centres far enough apart to survive a region-wide or country-wide incident.

Production in Canada is available as a location inside the Americas region. Neither Odoo Online nor Odoo.sh lets the buyer keep every backup copy in Canada: Americas backups are France, the Netherlands and Canada, and the privacy policy says buyers cannot restrict those locations. A contract that requires both production and backups inside Canada has to be answered with on-premise or partner-hosted servers. The policy names countries, not cities. Ask for the country of the production database and the countries of the backup copies in the same email.

What to ask before you sign

Use the first call for the Canadian file. The country-neutral parts of a statement of work, including how to read scope and change control, are covered in our guide on how to choose an Odoo implementation partner. On a Canadian shortlist, these are the questions that change the price.

1. Which provinces have you taken through to a filed return, and can we speak to that customer? Ask for a company whose user count is near yours.
2. Will the chart stay on Canada - Accounting, or will you replace it? Open a test company and read the installed module names.
3. Is payroll in the statement of work or written out? If it is in, is the path the third-party Enterprise app, limited on its page to federal and Ontario tax, or a bureau? Who maintains it after go-live?
4. Is French a translated interface, French training, or a French-speaking consultant in the workshops? Ask for a reference that matches the answer.
5. Who answers the first ticket after go-live, by name, and in which time zone? Write that name into the support schedule.
6. Is the service price CAD or USD? Which of these are inside it: license, Odoo.sh, data migration, tax configuration, French training, payroll, and a named go-live window?
7. Who are the people on the phase, how many hours is each of them in for, and who owns custom modules if we leave?

A bidder who cannot answer questions 2, 3 and 6 on the call does not have a number you can compare, so leave the tier until those three are written down.

How to choose the firm for a first phase

Run the shortlist in this order.

1. Write down tier, reference count, average users, large-project users and the certified-expert count from the live card. Keep the current tests in mind: 10, 75 and 300 new Enterprise users, one, three and six certified people, 70 percent and 80 percent retention.
2. Ask for a reference whose user count is near yours, in your industry, in a province you ship to. A Gold card with a large project near 200 users is a weak size match for a 20-user first phase. A Ready firm with a finished Canadian file can still be the firm you hire.
3. Have each firm install country Canada and show the chart, a fiscal position for every province you ship to, a pickup order, and a CPA005 file if you pay suppliers by EFT.
4. Put payroll and French in the statement of work as priced lines or as written exclusions. Compare fees only after that.
5. Put the price in CAD. Place license and Odoo.sh beside it in USD, using the October 2026 configurator figures, unless the statement of work has already converted them.
6. Name the consultants, their hours, the go-live window and the owner of any custom code.

When we plan a first phase, we target a system your team can run in 8 to 12 weeks. That phase runs under the Flectic Accelerated Delivery Framework: the Canada chart, the provinces you ship into, and payroll in or out are settled before configuration starts. We stay on the file after go-live. Companies that are still choosing a system can start with ERP implementation for a 20 to 100 person firm and the Odoo vs Business Central comparison. For the Odoo path itself, see how a phased Odoo implementation is scoped, migrated and supported after go-live.

Where Flectic fits

Flectic holds no certification from Odoo or Microsoft. We are an independent consultancy that implements Odoo and Dynamics 365 for companies of 20 to 100 people in the US and Canada, with no vendor quota on either. Among the options above, we sit at the small-firm, named-consultant end of the shortlist.

Choose Flectic if

• You have about 20 to 100 users and want the Canada chart, provincial fiscal positions and the payroll decision settled in writing before the first phase is priced.
• You want one named senior consultant leading the work from discovery to launch.
• You are still unsure whether Odoo is the right platform and want a written recommendation before you commit.

Look elsewhere if

• Your contract or board requires an Odoo Silver or Gold partner.
• French-language workshops or Canada-only hosting for every backup copy are hard requirements and we have not confirmed them with you in writing.
• You are above about 100 users or run several entities across provinces.

If the first group fits, see how we scope Odoo implementation for companies in the US and Canada.

How Flectic can help

If you are comparing Odoo partners in Canada, the quote matters more than the tier. Ask every bidder for a written plan that names the Canada chart, the provinces you ship into, whether payroll is in or out, and who configures each line.

Flectic does that work in discovery. The discovery call is free, and Flectic then sends a written proposal with a fixed price for each phase before work starts. You can set that plan beside any partner's statement of work, line by line, before you pick a firm.

We implement Odoo for companies of 20 to 100 people in the US and Canada, one app at a time on a single database, and we hold no certification from Odoo or Microsoft. If a Gold partner is the better match for your contract, the plan still shows you what to ask them. See the Odoo implementation scope, then book a free discovery call.

Sources

• Odoo Partnership: Benefits, Conditions & Pricing, Odoo, October 2026
• Odoo partnership page, Japanese, Odoo, October 2026
• Contrat de Partenariat Odoo (19.0 French text), Odoo, October 2026
• Odoo Partnership Agreement (14.0 English), Odoo, October 2026
• Canada fiscal localization (Odoo 19), Odoo, October 2026
• Accounting localization howto, Odoo, October 2026
• Payroll localizations (Odoo 19), Odoo, October 2026
• Canada HR Payroll Localization, Odoo Apps Store, October 2026
• Odoo Privacy Policy, Odoo, October 2026
• Odoo Hosting Types, Odoo, October 2026
• Create a project on Odoo.sh, Odoo, October 2026
• Odoo Pricing Configurator, Odoo, October 2026
• Odoo for Canadian manufacturers, Octura Solutions, April 2026
• Odoo implementation cost in Canada, Solvync, May 2026
• Odoo implementation cost Canada, Odiware, May 2026
• Calibre Consulting Corp. customer page, Odoo, October 2026
• Odoo implementation in Calgary, iTechnolabs, October 2026
• Odoo partner in Canada, Brainvire, October 2026
• Odoo Partner Quebec, Octura Solutions, October 2026
• Early cash discount, Canada, Odoo Forum, October 2026
• Default accounts in the USA and Canada, Odoo Forum, October 2026
• Odoo partner in Canada, Captivea, October 2026
• Odoo Partners in Canada (2026), OEC.sh, October 2026
• ERP Research's Canada partner directory, ERP Research, October 2026
• Standard ERP implementation for distribution, Gestisoft, October 2026