The Quick Take
Tax mapping is a short table that causes long problems. Each Shopify tax line (a title and a rate) needs to point at one Odoo tax record, and the sale order will carry whatever you choose. Pick a purchase tax by mistake, or an archived one, or a 20 percent tax that is price-excluded when your store prices include tax, and every order from then on books wrong.
Synco's "Suggest with AI" button on the Tax Mapping section fills the rows you left empty with an existing Odoo tax of the same rate and shows how confident the model was. You review the rows and press Save. This guide explains what happens between the click and the suggestion.
Related reading: Shopify Odoo tax mapping page, tax sync guide for Odoo v16 to v19, tax_id versus tax_ids, tax-included pricing, how AI helps sync Shopify and Odoo.
Why Rate Matching Alone Is Not Enough
A naive connector maps by rate: Shopify says 20 percent, find an Odoo tax at 20 percent, done. That breaks in every real Odoo database for a simple reason: there are several taxes at every common rate.
A typical Odoo company has, at 20 percent alone:
- a sales tax, price excluded
- a sales tax, price included
- a purchase tax
- an archived copy from a migration
- a tax that belongs to a different company in the same database
- an intra-community or reverse-charge variant with the same displayed rate
Rate narrows the list. It does not finish the job. Finishing the job used to mean a person with Odoo open in another tab reading tax names. That is the step the suggestion replaces.
What Happens When You Click Suggest
The button only acts on rows that are empty. Rows you already mapped are never touched.
1. Read the shop's context. Synco asks Shopify whether prices include tax and which country the store bills from. If Shopify does not answer in time, those fields are simply unknown and the suggestion carries on without them. 2. Load candidate taxes from Odoo. Only taxes in the shop's configured company (or shared with no company), active, with type "sale", are read. Purchase taxes and archived taxes never appear. 3. Filter by rate. For each empty Shopify row, the candidates are the Odoo taxes whose amount equals the Shopify rate. If the Shopify rate is zero, zero-rated and exempt taxes are the candidates. 4. Ask the model. For each row with more than one candidate, TypeSafe's Jev is asked which tax fits, given the Shopify title, the rate, whether prices include tax, and the country. It answers with a probability per candidate and for "none". 5. Fill the row. If the best candidate clears the confidence floor, the row is filled and labelled "Suggested by AI (92% sure). Review before saving." If no candidate clears it, the row stays empty and the page says no existing Odoo tax clearly matches.
Nothing is saved. The page is in the same unsaved state as if you had picked each tax yourself. Press Save when you are happy; Cancel throws the suggestions away.
Reading The Badge
The percent is the model's probability for the chosen tax relative to the other candidates and to "none". Use it as a reading order, not a verdict.
- A single candidate at the right rate is filled without asking the model and shows no uncertainty; there was nothing to judge.
- A high percent with two candidates usually means one is clearly a sales tax with a matching price-include setting and the other is not.
- A middling percent usually means two plausible sales taxes differ only by name. Open Odoo, check which one your accountant uses on manual invoices, and pick that.
If a suggestion is wrong, change it in the dropdown as usual. The badge disappears once you touch the row.
Tax-Included Stores
This is the case where the suggestion earns its place. A Shopify store with prices including tax needs the Odoo tax to also be price-included, or Odoo recomputes the line and the sale order total no longer equals the Shopify order total. The suggestion reads the Shopify setting and prefers the matching Odoo tax. A manual mapper often does not notice the difference until the first reconciliation.
Full background on how line totals are computed in that mode: tax-included pricing guide.
When It Says No
"No suggestions: no existing Odoo tax clearly matches the empty rows" means one of three things:
- there is no active sales tax at that rate in the shop's company
- the only taxes at that rate are archived or belong to another company
- the model could not separate two candidates and declined rather than guess
In all three cases the fix is in Odoo, not in the connector: create or unarchive the right tax, or give the two taxes distinguishable names. Then click Suggest again.
Synco does not auto-create taxes from a suggestion. It can create a tax during order sync when a configured fallback allows it, but that is a separate, explicit setting; the suggestion feature only ever points at taxes that exist.
What It Does Not Do
- It does not map by order; it maps the table that every order then uses.
- It does not pick fiscal positions. Those follow the customer and are configured separately.
- It does not change rows you already filled.
- It does not run during sync. Sync reads the saved table.
A Short Rollout
Before the first sync, open Tax Mapping, click Suggest, review each filled row against the tax your accountant expects, Save. Then sync one order per tax rate and compare the Odoo sale order total to the Shopify order total. If they match to the cent, the mapping is right. If they are off by the tax amount, the price-include setting is wrong on that Odoo tax.
Frequently Asked Questions
Will AI tax mapping create a new tax in Odoo? No. It only picks from taxes that already exist in the shop's Odoo company, are active, apply to sales, and have the same rate.
Does it understand tax-included pricing? Yes. It reads whether the Shopify store has prices including tax and prefers the Odoo tax whose price-include setting matches.
What if two Odoo taxes have the same rate? That is exactly when the AI is asked. The model picks by name and context and shows how sure it was. You review before saving.