Odoo CRM Consultant in Canada

From opportunity to manufacturing order without rekeying

For a Canadian manufacturer, the value of keeping CRM inside Odoo shows up after the deal is won. A confirmed quotation becomes a sales order, and depending on routes the order can trigger a manufacturing order, a purchase of components or a delivery from stock. When the CRM is a separate tool, someone retypes the order and the configuration details are the first thing to get lost.

What I design so that chain holds:

• Products and variants that match how you sell, so a rep choosing size, finish or capacity produces the right bill of materials rather than a free-text note.
• Quotation templates per product family with standard options, terms and drawings attached where useful.
• An engineering review stage for non-standard requests, with the estimator assigned as an activity owner.
• Realistic delivery dates. Odoo can calculate commitment dates from lead times; I agree with planning when the calculated date is trusted and when a planner confirms it.

The production side is covered by Odoo Manufacturing. In CRM terms, the result is a pipeline where the forecast and the production plan start from the same data.

Tax on the order depends on where the goods are going

Canadian sales tax follows the place of supply, so the same product can carry different taxes for a customer in Ontario, Alberta, British Columbia or Quebec. The tax mapping itself belongs in accounting, and the Odoo Accounting Canada page covers it. What the CRM must do is make sure the quotation knows where the goods are going before tax is calculated.

The CRM-side rules I put in place:

• Delivery addresses as separate contacts under the customer, so a billing address in one province and a job site in another are both available when quoting.
• Province captured at conversion for every business customer, because fiscal positions in Odoo can be selected automatically by country and province only if that data exists.
• Exempt and special status recorded on the customer, with supporting documents attached, rather than a rep deleting tax on a quote line.
• US buyers on their own fiscal position and price list, with no Canadian sales tax and freight terms stated.

Your accountant confirms each scenario. My job is to make sure the quote a rep sends from Odoo CRM matches the invoice finance posts later, so nobody has to issue a credit note to correct tax.

Dealers, trade shows and inbound leads from coast to coast

Canadian companies that sell nationally deal with long distances and staggered working hours. A lead from Vancouver arriving late in the afternoon in Halifax may not be seen until the next day if routing ignores time zones. I set up Odoo sales teams by region, with assignment rules that consider territory and working hours, and a backup owner for each team.

The sources I usually connect:

• Dealer and distributor reorders, which should create quotations or orders directly, through email, the customer portal or a B2B shop, not new leads.
• Trade shows, imported as a tagged campaign and checked against existing companies before anything is created.
• Search and LinkedIn campaigns, with campaign, medium and source carried from the web form onto the lead and the eventual order.
• Quebec inquiries, routed to a French-speaking rep, with the customer's language set so Odoo prints quotations and emails in French.

Field reps covering large territories can use Odoo on mobile to check stock, log visits and send quotes. I test that on their phones before training. For campaign tracking that feeds the pipeline, see B2B lead generation.

Matching companies on the Business Number

Duplicate customers are a bigger problem in an ERP-connected CRM than in a standalone one, because each duplicate carries its own orders, invoices and credit position. Canadian companies have a useful identifier for avoiding them: the Business Number and the related GST/HST registration number that business customers often share on purchase orders and credit applications.

How I use it in Odoo:

• Tax ID on the company for registered business customers, required before the first order on account.
• Duplicate checks at creation and before imports, using the registration number first, then website domain and address. Odoo flags similar records; more complete deduplication rules depend on edition.
• Parent companies and sites so a national account with several delivery locations stays one relationship.
• A named data owner who merges flagged records on a schedule.

When moving from Sage, QuickBooks or an older CRM, I clean on these identifiers before import, not after. The ERP data migration page explains how.

Keeping HubSpot or Salesforce, editions and poor-fit cases

Some Canadian companies arrive with HubSpot running marketing and sales, or with Salesforce required by a US parent. Keeping the existing CRM can be right when marketing automation or group reporting depends on it. Then I define the boundary: the CRM owns leads and early opportunities, Odoo owns customers, quotations, orders and invoices from an agreed point, and shipping and payment status flow back.

The CRM app is part of Odoo Community. VoIP, Studio, lead enrichment and some automation may require Enterprise or paid services, and features move between versions, so I check your edition before design is finalized.

Odoo CRM is a weaker fit when:

• Odoo will hold only accounting and not orders or production, removing the main benefit.
• The team runs complex enterprise deals that need advanced forecasting and account planning.
• Marketing owns the funnel and needs nurture and scoring in the same tool.

See the general Odoo CRM page, my Odoo consultant Canada page, CRM consulting, the ERP consultant Canada page and the Canada hub.