The Quick Take
The first sync is the moment a connector stops being a setting and starts being a change to live data. Most connectors handle it by writing immediately and letting you find out what happened from the result. Synco runs a read-only scan of both stores first and shows you, in three tabs, what the first run would do: which products would link, which need a yes or no from you, which might link to the wrong record, which would be created, which Shopify fields Odoo would overwrite, which stock quantities would be written at each location, and which recent orders would not sync.
You decide, then press Go live. This guide walks through what the check looks at, how to read each tab, and what changes when you confirm.
Related reading: go-live checklist, connect Shopify to Odoo setup checklist, AI product matching, inventory direction guide, warehouse mapping guide, features page.
Why A Scan Before A Sync
Three things go wrong on first syncs, and all three are invisible until after the write:
- Wrong links. Two products that look alike get linked, and every order and stock update from then on goes to the wrong record.
- Overwrites. Odoo is set as the source for a field, and the first sync replaces a Shopify title or internal reference the merchandising team spent months on.
- Stock surprises. A location mapping points at a warehouse view instead of a stock location, or stock sits one level down in a child location, and the first run writes zero to a hundred variants.
Each of these is cheap to spot by reading both catalogs and expensive to undo after a write. So the check reads first.
Before It Looks: A Few Questions
The check opens with a short intent step. In your own words, say what must not be touched: a brand, a category, test products, anything you want held back. Those products get a hold tag and are skipped on every sync path from then on, not just on the first run. You can also say how you want prices and fields handled, and the scan uses those answers to decide what it needs to ask you about.
The Scan
The job fetches the full Shopify catalog, the full Odoo catalog, Odoo facts (companies, warehouses, locations, attributes, pricing rules, the fields the connector needs), recent orders, and stock. It is read-only on both sides and runs in the background; the page shows progress and the result is kept, so you can come back.
Then it runs checks. The product checks include:
- an exact or likely match between a Shopify product and an Odoo template, and a single Shopify product that could match several Odoo templates
- Shopify option names with no Odoo attribute, and products with more than three options
- Odoo templates with variants Shopify does not have (phantom combinations) and kits
- the same SKU or barcode used more than once, and variants with no SKU or barcode at all
- Odoo missing a field the connector needs, and prices that look different between the two sides
- Odoo internal references that the first sync would replace, and per-field overwrites where Odoo is the source
- suppliers that would be created, and products excluded by your filters
- for stores that already sync: existing links pointing at an Odoo product that is gone, archived, the wrong variant, or shared by several variants
Where a match is ambiguous, the same AI model used by AI product matching is asked which Odoo product the Shopify product is, and the pair is shown as "Likely match" with a percent.
Reading The Products Tab
Four cards summarize the catalog.
- Will link. Odoo products matched to Shopify by a unique identifier. No decision needed.
- Needs your review. Likely matches and anything else waiting for a yes or no. Confirm, skip, or accept everything at a confidence you choose.
- May match the wrong product. Duplicated identifiers and similar titles. These still sync, but the fix is in Shopify or Odoo: correct the identifier, then scan again.
- Will be created. Products that exist on one side only, split into Shopify-only to create in Odoo and Odoo-only to create in Shopify as drafts. Each create step can be turned off here.
Below the cards: "Fields the first sync would change". For every field where Odoo is the source and the two stores differ, you choose per field whether to keep the Shopify value or let Odoo update it. Keep all or let Odoo update all are one click. "Things to fix in Shopify or Odoo" lists what does not block go-live but will affect how well products match, each with where to fix it.
Reading The Inventory Tab
This tab answers one question: what numbers would the first stock run write, and where?
- Which way stock will flow, from your inventory direction setting, stated plainly.
- This location will not sync: a Shopify location mapped to an Odoo location that cannot hold stock, with the one you probably meant offered as a replacement.
- Stock sits one level down: mapped locations whose quantities live in child locations the mapping does not cover.
- Quantities that will be written, per variant per location, with "Will drop to 0" and "First quantity" called out, and "No update" rows with the reason (unlinked product, a setting that skips it, undecided review).
- A setting will skip some updates and Your category filter, so a filter that silently drops half the catalog is visible before it does.
Reading The Orders Tab
Available after the product review. It lists recent orders that would not sync and why, and which order lines still have no Odoo product. If a line has no product, the order cannot become a clean sale order; this is where you learn that before the first customer order does.
Go Live
The last step shows exactly what will happen: how many variants will be linked, which settings change and to what (products set to update only, order lookup by SKU or barcode), which fields keep their Shopify values, how many products will be created on each side, how many are still undecided and so stay unlinked and uncreated, and how many are held back. Press Go live. The links are written, the hold tags applied, the settings saved, the create jobs queued, and the first sync starts through the normal queues.
For a store that already syncs, the button reads Apply fixes, the settings are left alone, and only confirmed links and fixes are written.
What To Do With The Result
Scan, fix the red rows in Shopify or Odoo, scan again. Two or three passes is normal for a catalog with history. The scan is cheap; a wrong link is not.
Frequently Asked Questions
Does the first-sync check write anything? No. The scan is read-only. Writes happen only when you press Go live, and only what you confirmed.
My store already syncs. Is the check still useful? Yes. It runs as a health check with the same scan plus a check of existing links, and only confirmed fixes are applied.
What does a Likely match mean? Two products that probably refer to the same thing but have no exact identifier match. Shown with a confidence percent; nothing is linked until you answer.