ERP Selection Consultant, Canada

How Canadian shortlists differ by company size

The products a Canadian business looks at depend mostly on operational complexity: number of provinces you sell into, whether you hold stock or manufacture, whether a US entity is involved and how much internal administration capacity you have.

• Owner-led firms moving beyond QuickBooks or Sage 50. The comparison usually includes Zoho with Zoho Books at the center, Odoo, ERPNext and a stronger accounting setup with connected apps.
• Mid-sized distributors, manufacturers and contractors. Dynamics 365 Business Central, Acumatica, NetSuite and Sage's larger products often join Odoo, depending on whether inventory, production or project costing drives the decision.
• Groups with a US subsidiary or parent. Multi-company consolidation, intercompany trade in two currencies and reporting to a US owner move to the top of the criteria.

None of these is a recommendation. A product reaches the demo stage only after it passes written knock-out questions, and the most important one in Canada is usually simple: is the Canadian setup a maintained part of the product, or something a partner assembles for each customer? That answer affects upgrade risk, support and cost for as long as you use the system. For a neutral look at small-business options, see the best ERP for small businesses comparison.

Comparing Canadian and cross-border partners

Canadian buyers often receive proposals from a mix of firms: partners based in Canada, US partners that serve Canadian customers, and offshore teams working through a local contact. Each model can work, but each brings different questions, and the proposals rarely line up neatly.

I rebuild every proposal in a single grid before anyone compares totals:

• Phases, deliverables and hours by role, with names and seniority of the consultants assigned.
• Assumptions, exclusions and the tasks your staff are expected to carry out, especially data cleansing and report building.
• Which currency the partner bills in, and how exchange movements are handled across a long project.
• Change request rates and approval steps.
• Support hours after go-live and whether they cover your time zone, from Pacific to Atlantic.
• Direct experience with Canadian tax configuration, French documents and Canadian banks, supported by references.

Reference calls are where Canadian experience shows. I ask the same questions of each reference: how tax and bilingual requirements were handled, how disputes were resolved and what they would change. Typical proposal red flags are covered on vendor proposal review, and a formal tender is covered by ERP RFP consulting.

Canadian scenarios every demo should cover

I send each vendor a script and a sample of your data in advance, then chair the session so every product covers the same ground. For Canadian companies the script usually includes:

• Layered sales tax. A sale shipped to another province, one to a Quebec customer and one to an exempt customer, showing how GST or HST and PST or QST are determined and where input tax credits are tracked. Your accountant confirms the treatments that apply to your business.
• French and bilingual output. An invoice, a quote and a statement printed in French for a Quebec customer, plus the user interface in French if staff need it. The engagement runs in English; French wording on templates is checked by your team or the partner.
• CAD and USD together. A USD purchase from an American supplier with duty, brokerage and freight added to landed cost, then payment from a USD bank account.
• Canadian banking. A supplier payment run that produces the EFT file your bank accepts, and a bank feed reconciliation.
• Payroll connection. Many Canadian companies use a dedicated payroll product, so the demo should show payroll journals posting by province, department or job.

Your process owners rate every scenario as out of the box, configured or custom-built, and vague answers are followed up in writing before scoring is final.

Hosting, privacy and commercial terms to check

Cloud ERP raises questions about where data lives. Some Canadian organizations, especially those serving public bodies or handling sensitive personal information, prefer or are asked to keep data in Canada. Federal and provincial privacy laws, including Quebec's own rules, may also affect how personal information is stored and transferred. For every product still in contention I record the hosting region, whether Canada is offered as a location, which sub-processors are used and how access by the vendor and partner is controlled. Your privacy officer or lawyer decides what is acceptable.

On the commercial side, Canadian buyers should check a few points that are easy to miss:

• Billing currency. Many subscriptions are priced in US dollars. Ask whether CAD pricing is available and how renewals are converted.
• Edition. Confirm that you are licensing the edition or localization intended for Canada, not a US edition with workarounds.
• User types. Clarify which users need full licenses and which can use cheaper limited access.
• Renewal and term. Minimum terms, automatic renewal and caps on price increases.
• Add-ons. Tax, EDI, payroll connectors or bank integration apps with separate subscriptions.
• Exit. Data export rights and formats if you leave.

Every answer is recorded and attached to the recommendation, so the project starts with no hidden commercial surprises.

Why an independent selection pays off in Canada

Many Canadian businesses first hear about ERP from a partner that sells licenses and implementation together. That is a legitimate model, but it means early advice comes from a firm with a particular product to place. My income comes only from the client, never from a license margin or finder fee, which leaves me free to recommend a smaller option, a different partner or no change at all.

The selection is run remotely. Workshops and demos are scheduled when your head office and the main users are available, which is easier for Eastern and Atlantic teams but entirely workable for Prairie and West Coast companies with some planning. Recordings let colleagues in other provinces review demos before scoring, and scores are entered in a shared workbook. Visits can be agreed by arrangement, though a well-run remote process rarely needs them.

Once the choice is made, the scoring evidence and agreed scenarios carry straight into delivery, and I can move with the project as your client-side ERP implementation consultant in Canada. If you are still asking whether you need an ERP at all, start with ERP evaluation. For context, see my Canadian ERP consulting page, the ERP vendor selection method and the Canada hub.