CRM and ERP integration: what to connect first
CRM and ERP integration for a company of about 40 to 100 people is a choice among three routes.
CRM and ERP integration for a company of about 40 to 100 people is a choice among three routes. Odoo can keep CRM, Sales, and Accounting in one database, so a quotation uses the same customer, pricelist, and catalog. Dynamics 365 Sales reaches Business Central through Dataverse, and default item-availability jobs run every 30 minutes. Dual-write is the near-real-time link between finance and operations apps and Dataverse, separate from Business Central. A CRM from another vendor needs middleware, or Odoo Custom when it calls Odoo's API.
As of October 2026, a US yearly list pair is USD 65 for Sales Professional and USD 80 for Business Central Essentials per user per month. Canada lists CAD 88.20 and CAD 108.50, plus tax. Odoo Standard, in the euro prices displayed that month, is EUR 24.90 per user per month and includes CRM and Accounting on one database.
Three routes for a company of about 50 people
How ERP and CRM overlap is the starting point. NetSuite's March 5, 2026 overview lists the objects people expect to share: customers, products, pricing, orders, invoices, and service cases, and it describes the payoff as shorter sales cycles and less checking between systems. A company of about 50 people still has to pick the route and the order of records.
Three routes cover the stacks we see at that size.
- One database. Odoo CRM, the Sales app, and Accounting share customers, pricelists, invoice addresses, and the product catalog. Confirming a quotation converts it to a sales order on the same opportunity. There is no sync job between those apps.
- Native Microsoft sync, and there are two of them. Business Central online integrates with Dynamics 365 Sales through Dataverse on a schedule. Dual-write is Microsoft's out-of-the-box bidirectional link between finance and operations apps and Dataverse. Using the finance-and-operations design on a Business Central project is how quote-to-cash programs start from the wrong map.
- Middleware, when the CRM is not the ERP vendor's CRM. A direct point-to-point tool can carry a few events. Price lists, tax amounts, and posted invoices need the rules of the native map, or a flow someone owns. Point-to-point versus middleware is the longer architecture note. This page stays on the records that make a quote become cash.
Our system integration practice starts from the route, then from the object order, then from the product you already pay for. Teams that stay in the Microsoft cloud often pair that work with Dynamics 365 Sales next to Business Central. If the CRM product itself is the problem, CRM implementation is a separate decision from the pipe.
Which records to connect first
Buyers ask, "Why would you need to put the customer in the ERP before the project has sold?" You can wait until the deal is sold. On the Business Central map, only active Dataverse accounts whose relationship type is Customer couple to Business Central, and only Business Central customers that are not blocked couple the other way. A prospect can stay in Sales. The masters the first won order depends on still have to exist before that order moves.
Microsoft's own prerequisites are the sequence. Hand this list to whoever configures the integration.
- Currencies and units of measure. Currency synchronizes from Business Central to Dataverse only. Foreign-currency prices and customers also require those currencies to be coupled to Sales transaction currencies. Units of measure must be coupled to Sales unit groups before items and resources can couple.
- Salespeople. A salesperson or purchaser comes from Dataverse users into Business Central. Customers cannot couple to Sales accounts until salespeople are coupled to Dynamics 365 Sales users.
- Customer price groups, coupled to Sales prices, before item and resource prices.
- Items and resources, which become products in Sales. Items that sync across automatically create a price list.
- Customers and contacts. Contacts synchronize both ways for person contacts tied to a company.
- Quotes and orders. A Sales order synchronizes when its status is Submitted. A Business Central order synchronizes when its status is Released, except orders waiting on prepayment, which sync as Open.
- Posted invoices and payment status. Posted invoices move to Sales when Create Invoice in Dynamics 365 Sales is selected, and they arrive with status Billed. Payment status (Partial or Complete) updates when account statistics are refreshed.
The integration jobs themselves run in a fixed order: unit of measure, resource-product, item-product, customer price group, sales price, then posted sales invoice, as Microsoft's Sales integration setup lists them. Skipping ahead produces errors that look like a connector bug and are a missing parent row.
In Odoo the same idea shows up as a screen rule. The New Quotation button exists once the Sales app is installed, which Odoo's quotation documentation spells out. The customer is optional on the opportunity and required, or explicitly skipped, before a quotation can be sent. Choosing Create a new customer on that popup creates another customer record. Connect, or in Odoo select, the existing customer before the quote goes out.
How Dynamics 365 Sales syncs with Business Central
Business Central's online integration with Dynamics 365 Sales goes through Dataverse. Microsoft states that Business Central integrates only with Dynamics 365 Sales, and that other apps which change the Sales data model, for example Project Service Automation, can break that integration. If Project Service Automation is installed, treat a working customer sync in a sandbox as a gate before you plan the cutover.
Synchronization is scheduled job-queue work and does not promise real-time consistency. Default Sales integration jobs, including item availability, run every 30 minutes. A rep who quotes available stock at 10:05 can be looking at a quantity the warehouse changed at 9:40. When you need a live read, Microsoft points to Business Central virtual tables or Business Central APIs. On a tight inventory item, quote the quantity from a virtual table or the API when the rep is on the phone.
What moves, and in which direction
- Salesperson and purchaser (Direction: Dataverse users into Business Central · Rule that surprises people: Required before customers can couple)
- Customer and account (Direction: Both ways · Rule that surprises people: Active Dataverse accounts with relationship type Customer, and Business Central customers that are not blocked)
- Contact (Direction: Both ways · Rule that surprises people: Person contacts tied to a company)
- Currency (Direction: Business Central to Dataverse · Rule that surprises people: Must be coupled before foreign-currency customers and prices)
- Customer price group and sales price (Direction: Business Central to Sales · Rule that surprises people: A price edited in Sales can spawn a new Business Central price list per order)
- Sales order (Direction: Both ways, with status gates · Rule that surprises people: Submitted in Sales; Released in Business Central; prepayment orders sync as Open)
- Posted sales invoice (Direction: Business Central to Sales · Rule that surprises people: Only when Create Invoice is selected; status arrives as Billed)
- Payment status (Direction: Toward Sales · Rule that surprises people: Updates when account statistics are refreshed)
Sources for the map, as of October 2026: Manage customers using Dynamics 365 Sales and Synchronization and data integration, Microsoft.
Bidirectional sales-order sync and the legacy sales-order integration are mutually exclusive, per the same Sales integration setup. With bidirectional sync, changes to price, tax amount, and expected shipment date in Business Central synchronize back to Dynamics 365 Sales. After an order is Submitted in Sales, line changes are locked until the order is reverted. Tax amount here is a mapped field on that order. Ask each bidder to show the tax on your own orders, including Canadian GST, HST, PST, or QST. The field mapping is the documented behavior. Calculation and filing of those taxes is a finance setup you should see on your data.
Write-in products, items or resources not registered in either app, need a Write-in Product Type and a Write-in Product No. on Sales and Receivables Setup. Those write-ins cannot be mapped to an item or resource that is already coupled to a Sales product. The Sales order Name maps to the Business Central External Document Number, which is the field your warehouse and your customer will quote back when the order number and the CRM name differ.
Changes made by the integration user account stay unsynchronized. Microsoft recommends that people avoid editing data with that account. An edit made while logged in as the integration user is a silent miss on the next job.
Price lists and the company ID
Customer price groups and sales prices sync from Business Central to Dynamics 365 Sales. If someone changes a product price in Sales and that item is used on a Business Central sales order, Business Central creates a new sales price list for each order. Items that sync to Sales automatically create a price list that Microsoft says "should not be edited manually", or synchronization errors follow. The newer pricing experience only syncs sale price lists with amount type Price, product type Item or Resource, Allow Updating Defaults off, and no minimum quantity. A price list with a quantity break, or with Allow Updating Defaults on, will sit in Business Central and never appear in Sales. That is a setup filter, and it looks like a failed integration from the sales floor.
In a multi-company Business Central to Dataverse setup, document mappings for orders, quotes, and opportunities only consider rows whose company ID matches the current company. Sales users must set that company ID or the documents do not synchronize. Microsoft recommends match-based coupling so the same customer is not inserted twice, and number-series prefixes when primary keys are not unique per company. If the Sales order has no company ID, that company's document mapping skips it and the order does not synchronize. People then create a second account by hand. Set the company ID and use match-based coupling before anyone submits the order.
What dual-write covers on finance and operations apps
Dual-write is an out-of-the-box, tightly coupled, bidirectional integration between Dynamics 365 finance and operations apps and Dataverse. A change on either side writes to the other. It runs near real time and supports an initial sync plus play, pause, and catch-up modes. The customer engagement apps named in the overview include Dynamics 365 Sales.
The application scenarios Microsoft documents are the quote-to-cash ones finance leaders ask about: an integrated customer master, access to finance and tax reference data, an on-demand price engine, an integrated prospect-to-cash experience, and lookup of on-hand inventory. Installing the dual-write solution adds company and party concepts to Dataverse. That is a closer coupling than Business Central's 30-minute job queue. Business Central keeps the Dataverse job queue described above.
Currency decimal precision in the customer engagement apps can be extended to 10 decimal places so currency does not lose precision between the finance and operations apps and Dataverse. The change is opt-in. Organizations that work within four decimal places can leave it off. If you sell in units where the fifth decimal changes the extended price, turn it on before the initial sync.
Live dual-write has real-time synchronization limits, including transaction timeouts and transaction size limits. Microsoft's async page, a preview and not for production, exists so high-volume entities that can accept eventual consistency can avoid those limits. Have Microsoft or your implementer run your largest order and your largest customer payload in a test environment and record the limit you hit. Keep production on live dual-write, because the async mode is a preview.
How Odoo CRM shares Accounting without a connector
A quotation in Odoo waits on the Sales app. Install that app and the New Quotation button is there. The quotation uses the shared customer, pricelist, invoice address, and product catalog. Confirming it converts the quotation to a sales order on the same opportunity. Accounting, listed with CRM on the Standard and Custom plans, reads that same database. For a company whose CRM is Odoo, the integration project between CRM and the general ledger is the decision to install those apps, plus the discipline to pick the existing customer.
One App Free is one app and unlimited users. It cannot hold CRM and Accounting together. Standard and Custom include all apps. External API, Odoo Studio, and multi-company sit on Custom. Odoo.sh hosting is extra. Implementation is not included in the per-user fee.
Odoo defines External API as outside software calling Odoo's JSON-RPC or XML-RPC API. Calls that Odoo itself starts, such as payment providers, carriers, and bank sync, are not External API and can stay on the Standard plan. A third-party CRM that pulls or writes Odoo data is External API and needs Custom. Keeping Salesforce, HubSpot, or another CRM beside Odoo Accounting is a Custom-plan decision for every user on that subscription, not a connector you bolt onto Standard.
Success Packs, shown in euro on the same pricing site as of October 2026, are general implementation time for new customers, with 15 percent off the first pack only. They run from Starter at EUR 499 for 4 hours through Pro at EUR 16,830 for 200 hours (Basic EUR 2,635 for 25 hours, Standard EUR 4,675 for 50 hours, Custom EUR 8,415 for 100 hours). Above 50 users the estimator says to contact Odoo. Odoo states that 80 percent of projects in the estimator scope go live in 200 hours or less, and claims a 98 percent implementation success rate with a pack versus 65 percent without. Both figures are vendor claims on the Success Packs page. The packs are not a published CRM-to-ERP integration product. Budget them as implementation hours for the whole suite, then ask for a separate line if a third-party CRM is in scope.
What licenses cost at about 50 people
License list price and integration cost are different bills. For Business Central and Dynamics 365 Sales, the pricing pages publish user licenses. They tell you to contact a partner to purchase Business Central, and they say the checkout price can differ. They do not publish a separate connector SKU on those cards, and they do not publish a project price for the sync. Treat any fixed fee for the integration as its own quote.
US and Canada list prices below are per user per month, paid yearly, as of October 2026. Canada adds applicable tax. Do not convert one card into the other. Sales Premium on the US page includes 1,000 Copilot Credits per user. A footnote on the US Sales page says Power Automate use requires additional licenses.
- Sales Professional (United States: USD 65 · Canada: CAD 88.20)
- Sales Enterprise (United States: USD 105 · Canada: CAD 142.50)
- Sales Premium (United States: USD 150 · Canada: CAD 203.50)
- Business Central Essentials (United States: USD 80 · Canada: CAD 108.50)
- Business Central Premium (United States: USD 110 · Canada: CAD 149.20)
- Business Central Team Members (United States: USD 8 · Canada: CAD 10.90)
US figures: Dynamics 365 Sales pricing and Dynamics 365 Business Central pricing. Canada figures: Sales and Business Central. Prices are informational.
A 20-user mix
Assume 8 people who quote need Sales Professional and 12 people who ship and invoice need Business Central Essentials. Nobody in this mix needs Premium, Team Members, or Sales Enterprise. At US yearly list prices as of October 2026, the sales seats are 8 times USD 65, which is USD 520 per month. The Business Central seats are 12 times USD 80, which is USD 960 per month. Together that is USD 1,480 per month, or USD 17,760 over twelve months, before tax and before Power Automate.
The same headcount on the Canada yearly cards is 8 times CAD 88.20, which is CAD 705.60, plus 12 times CAD 108.50, which is CAD 1,302. Together that is CAD 2,007.60 per month, plus applicable tax. The Canadian total is higher because the Canadian card is higher, not because of an exchange-rate conversion.
If those 8 sales users also need their own cloud flows, Power Automate Premium is USD 15 per user per month, paid yearly. Eight users add USD 120 per month, and the US stack in this example becomes USD 1,600 per month. Process is USD 150 per bot per month, paid yearly, for one unattended desktop flow at a time per bot. Hosted Process is USD 215 per bot per month, paid yearly, and includes a Microsoft-hosted virtual machine. Those are marketing figures, and the page says the actual price is at checkout. Cloud flows sit within service limits that you should read on your agreement before you put invoice posting on a flow.
Odoo, for 20 full users on the yearly toggle displayed in October 2026, is 20 times EUR 24.90, which is EUR 498 per month on Standard, for 12 months and for the initial users ordered. The struck price beside it is EUR 31.10, which would be EUR 622 per month for the same 20 users if that discount did not apply. Custom, required when a third-party CRM calls the API, is 20 times EUR 44.90, which is EUR 898 per month on the same 12-month initial-user basis, against a struck EUR 56.90 (EUR 1,138 for 20 users). A light user is EUR 7.90 and is sold through an advisor quote. These are euro amounts as displayed. Confirm the US or Canada checkout before you put them in a budget. Hosting on Odoo.sh and implementation hours sit outside that per-user line.
When middleware is enough for quote-to-cash
"The choice between a direct point-to-point tool and a more robust setup often depends on your data volume and complexity." That is the right test, and the vendor price pages make it concrete. Someone in the same thread notes, "We've built a good few with Zapier between Salesforce and ERPs for clients." A few events is what that class of tool is priced for.
Zapier bills in USD. The annual option is about 33 percent below monthly billing. As of October 2026:
- Free (Price billed annually: USD 0 · What you get: 100 tasks per month, two-step Zaps, polling every 15 minutes)
- Professional, 750 tasks (Price billed annually: USD 19.99 per month · What you get: Multi-step Zaps, polling every 2 minutes. Monthly billing is USD 29.99)
- Team, 2,000 tasks (Price billed annually: USD 69 per month · What you get: Polling every 1 minute, up to 25 users. Monthly billing is USD 103.50)
- Team, 50,000 tasks (Price billed annually: USD 399 per month · What you get: The same Team features at a higher task cap)
- Enterprise (Price billed annually: Custom · What you get: Quoted)
A task is a successful action, not the trigger. Tasks reset monthly. Non-USD prices, including CAD, convert from USD at payment time and can change between invoices. Source: Zapier pricing, October 2026.
Assume 150 won quotes a month. One Zap creates the customer and a second action creates the order. That is 300 tasks, inside the Professional 750-task plan at USD 19.99 per month on annual billing. Assume instead that each night you push a 2,000-row price list and each row is one successful action. That single night spends 2,000 tasks, which is the entire Team 2,000-task plan at USD 69 per month, with nothing left for orders. A 50,000-task Team plan at USD 399 per month would cover a heavier catalog and still has a ceiling. Price lists and tax rows are a volume problem on a task meter. A new customer and a won quote are not.
Polling every 1 to 15 minutes can be faster than Business Central's 30-minute default job. Polling speed and the coupling rules solve different problems. A Zap does not know that a Sales order must be Submitted, that price groups flow from Business Central, that a missing company ID drops the document, or that an edit by the integration user will not come back. You can rebuild each of those checks as a step. You then own them when either product changes.
Power Automate Premium at USD 15 per user per month is the Microsoft-stack version of the same choice. It includes cloud flows within service limits. It still needs a person who can read a failed run. For a 50-person company whose CRM and ERP are both Microsoft and whose objects fit the standard map, the native job queue already encodes the order, price, and invoice rules above. Add Power Automate for a side process the map does not cover, such as a notice to a coordinator, and keep invoice creation on the Business Central path that sets status to Billed.
Enterprise integration platforms often publish no list price on the pages buyers compare. Do not budget from a blog range. Ask for the platform fee, the task or connection metric, and the hours to recreate the seven-step object order as separate lines.
Where customers, prices, and invoices go wrong
The failures below are the ones Microsoft documents for the Sales and Business Central integration, plus the Odoo popup that inserts a second customer. They show up as duplicate accounts, a Sales order that never leaves the CRM, and a posted invoice the rep cannot find in Sales.
Customers duplicate when both sides create records and match-based coupling was skipped. They also duplicate when a Sales user cannot see the existing account because the company ID does not match, so they add a new one. In Odoo they duplicate when the quotation popup creates a new customer for a company that already has an account. The fix is operational: one owner for the customer record, match on a key you control, and a company ID filled in before anyone submits an order.
Orders never leave Sales when status is still short of Submitted. They never leave a multi-company Business Central company when the Sales user left company ID blank. They arrive in Sales as Open when Business Central is waiting on prepayment, which is correct per the map and confusing if the rep expected Released. Line edits after Submitted stay locked until someone reverts the order. Two order integrations turned on together are not a supported pair: bidirectional sync and the legacy sales-order integration exclude each other.
Prices disagree when Sales is treated as the price book. Standard sync sends customer price groups and sales prices from Business Central to Sales. A salesperson who changes the product price in Sales can cause a new Business Central price list on every order that uses the item. Price lists with a minimum quantity, or with Allow Updating Defaults turned on, fall outside the newer pricing filter and stay behind. The automatic price list created for items syncing to Sales is the one Microsoft tells you to leave unedited.
Tax on the order updates in Sales when bidirectional order sync is on, because tax amount is one of the three fields that travel back with price and expected shipment date. A quote built in Sales before that sync, or an order still on the legacy integration, will not pick up a tax change finance just posted. Show this on a real order in both countries you sell to, and include the tax setup those orders use.
Invoices in the CRM fail to match ERP orders in two separate cases. If Create Invoice is off, the posted invoice never arrives in Sales. If account statistics have not been refreshed, payment status does not move to Partial or Complete, so the invoice can already be Billed while Sales still shows no payment update. Status Open applies to Business Central orders waiting on prepayment, which sync as Open. Reps then call finance, finance re-keys, and you have two documents for one shipment. Run the invoice job only after the price-list and customer jobs in the fixed order Microsoft lists. An invoice that arrives before its item and price parent is another false error.
Availability is stale by up to one job interval on the default schedule. Quoting a ship date from Sales during that window is how you promise stock the warehouse no longer has. Use virtual tables or the Business Central API when the quote depends on a live quantity, and keep the 30-minute job for the rest of the catalog.
Project Service Automation, or any app that changes the Sales data model, can break the Business Central integration even when every job is green in a tenant that does not have that app. Test the combination you will run.
How to start the first phase
List the systems that touch a customer, a price, an order, or an invoice, including the ones you plan to add this year. Mark the owner of each record. If both Sales and Business Central can create customers today, stop adding automation until match-based coupling and the company ID are in place. New writers on an uncleansed customer table multiply the duplicates.
Pick the route from the stack you have. Odoo CRM plus Sales plus Accounting is a configuration and data problem inside one database. Dynamics 365 Sales plus Business Central is the Dataverse job queue and the seven-step coupling order. Finance and operations apps are dual-write, with a test of timeout and payload size on your largest documents. A CRM from another vendor is middleware or, on Odoo, the Custom plan, priced per user, plus a flow design you can hand to a second person.
Move one slice. Couple currencies, units, salespeople, price groups, items, and a handful of known customers. Submit one order. Post one invoice with Create Invoice selected and refresh account statistics. Compare the Sales document to the Business Central document field by field, including tax and the external document number. Retire any second writer, including a spreadsheet import, once those fields match. Leaving two writers running is how the next duplicate appears.
Flectic sets the timeline for a first phase in the written scope, with a fixed price, before work starts. That first phase covers a bounded slice, such as customers, prices, and submitted orders for one company, and it depends on the quality of the records you already have.
Ask each bidder to price data migration, the native coupling, and any middleware as separate lines. Ask them to name the people who will configure the job queue or the flows, and to show the sync on your items, your price breaks, and your tax. Code, field maps, and run history should stay with you when the project ends.
How Flectic can help
Flectic connects Odoo or Dynamics 365 with the CRM and accounting tools you keep, so your team stops re-keying customers, prices and invoices between systems. Every flow gets one named owner per record and a documented failure path, agreed before any data moves, as set out in the system integration service. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call with Flectic to map the first flows.
Sources
Dual-write overview, Microsoft, October 2026
Set up and manage dual-write async (preview), Microsoft, October 2026
Integrating with Dynamics 365 Sales, Microsoft, October 2026
Synchronization and data integration, Microsoft, October 2026
Manage customers using Dynamics 365 Sales, Microsoft, October 2026
Dynamics 365 Sales pricing (United States), Microsoft, October 2026
Dynamics 365 Sales pricing (Canada), Microsoft, October 2026
Dynamics 365 Business Central pricing (United States), Microsoft, October 2026
Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026
Odoo pricing, Odoo, October 2026
Create and send quotations, Odoo, October 2026
Odoo Success Packs, Odoo, October 2026
Power Automate pricing, Microsoft, October 2026
Zapier pricing, Zapier, October 2026
CRM and ERP Integration: Everything You Need to Know, NetSuite, March 2026
Who is using an ERP and CRM integration?, Reddit, October 2026
An ERP system that I can integrate with CRM, Reddit, October 2026
Frequently asked questions
Can your ERP be integrated with your CRM?
Yes, through one shared database, a native sync, or middleware. Odoo CRM, Sales, and Accounting can share customers and prices without a connector. Dynamics 365 Sales uses a Dataverse job queue with Business Central, while finance and operations apps use dual-write. A CRM from another vendor needs a flow you own, or Odoo Custom if that CRM calls Odoo's API.
Is dual-write the same thing as the Dynamics 365 Sales to Business Central integration?
They are different connections. Dual-write is a near-real-time, bidirectional link between finance and operations apps and Dataverse, with an initial sync plus play, pause, and catch-up. Business Central online uses its own Dataverse synchronization and a scheduled job queue, and Microsoft states that Business Central integrates only with Dynamics 365 Sales. Other apps which change the Sales data model, for example Project Service Automation, can break that integration. Live dual-write also has transaction timeouts and size limits that stay unpublished, and the async option is a preview that is not for production.
How fast does Business Central sync with Dynamics 365 Sales, and what happens if the job queue is 30 minutes behind?
Standard synchronization is scheduled work, and the default jobs, including item availability, run every 30 minutes. A rep can quote item availability that the warehouse has already changed. When a quote depends on a live quantity, Microsoft points to Business Central virtual tables or APIs. Payment status in Sales stays short of Partial or Complete until account statistics are refreshed, so the invoice can already be Billed while Sales still shows no payment update.
Why do we get duplicate customers when Sales accounts and Business Central customers both create records?
Both applications can insert a customer when records are matched loosely. Microsoft recommends match-based coupling, and in a multi-company setup the company ID on the Sales document has to match the Business Central company or people create a second account by hand. Number-series prefixes help when primary keys repeat across companies. In Odoo, choosing create a new customer from the quotation popup also inserts another customer record.
Why do invoices in the CRM not match the orders in the ERP?
Posted invoices move from Business Central to Dynamics 365 Sales when Create Invoice is selected, and they arrive with status Billed. If Create Invoice is off, the posted invoice never arrives in Sales. If account statistics have not been refreshed, payment status does not move to Partial or Complete. Status Open is for Business Central orders waiting on prepayment. Run the invoice job after units, products, price groups, and sales prices, which is the fixed job order.
Who owns the price and the tax: the CRM quote or the ERP order?
On the standard Business Central map, customer price groups and sales prices move from Business Central to Sales. Editing the product price in Sales can make Business Central create a new price list for each order that uses the item. Tax amount, price, and expected shipment date travel back to Sales when bidirectional sales-order sync is on. Have the bidder show that tax field on your own orders, including Canadian taxes.
If we already use Odoo CRM, do we still need a connector to Odoo Accounting?
You need the Sales app before CRM can send a quotation, and Accounting on the Standard or Custom plan reads the same database, so those Odoo apps do not use a connector between them. One App Free is a single app and cannot hold both CRM and Accounting. A third-party CRM that reads or writes Odoo uses the External API, which is on the Custom plan. Calls Odoo itself starts, such as a bank sync, can stay on Standard.
Is Zapier or Power Automate enough for quote-to-cash, or do we need a native connector?
Zapier fits a small number of successful actions, such as a won quote creating a customer and an order, and it polls every 1 to 15 minutes depending on the plan. A full price list is a weak fit, because each successful row write spends a task. Power Automate Premium is a per-user cloud-flow license and still needs an owner for each flow. Native Business Central coupling already encodes submitted status, price direction, and company ID, which a generic flow has to recreate.