Product Synchronization Best Practices

Introduction#

Catalog sync is where integration projects spend early weeks — and where duplicate SKUs surface months later during a stock reconciliation. Getting product mapping right reduces pain across inventory, orders, and reporting.

This article focuses on ERP catalog strategy, not Shopify theme product cards or collection merchandising UX.

Choose a catalog master#

Odoo as master suits businesses that manage purchasing, manufacturing, or multi-channel pricing in ERP first. Shopify as master suits digital-native brands that experiment with variants in Admin and only later formalize items in Odoo.

Bidirectional product creation without rules produces duplicate barcodes, conflicting titles, and orders that reference SKUs finance cannot find. Pick a master and allow controlled exceptions — for example marketplace-only SKUs created in Shopify with an auto-provision rule into Odoo.

Map variants, attributes, and barcodes#

Shopify variants map cleanly to Odoo when each variant is a distinct product.product with a unique default_code or barcode. Configurable products with Odoo attributes need explicit attribute-value mapping so new Shopify options do not spawn orphan variants.

Store Shopify product_id and variant_id on Odoo (dedicated fields or ir.model.fields) and Odoo product IDs in Shopify metafields or private app metadata when the connector supports it. Never rely on title or handle alone — they change.

• ▸One canonical SKU or barcode per sellable unit
• ▸Explicit attribute mapping table for size, color, and custom options
• ▸Archive or unpublish rules when products retire on either side

Create, update, and archive workflows#

Define which fields sync on create versus update. Title and description may flow Shopify to Odoo for SEO-led brands; weight and HS code may flow Odoo to Shopify for compliance-led exports.

Archiving must be symmetric enough to prevent ghost SKUs: unpublishing in Shopify should not leave Odoo sellable on other channels unless that is intentional. Document whether delete means archive or hard remove.

Pricing and promotional context#

List price and compare-at price can sync from Odoo pricelists or Shopify — but pick one master for base price. Shopify automatic discounts and Odoo pricelist rules interpret promotions differently; order lines must carry enough metadata for Odoo to reconstruct revenue.

When price changes are high frequency, batch sync on a schedule and use webhooks only for critical corrections — see rate limit articles before polling entire catalogs hourly.

Collections and categories#

Shopify collections are merchandising constructs; Odoo product categories support accounting and reporting. Sync only when reporting requires it. Forcing full hierarchy mirrors creates maintenance drag with little ERP value.

Use tags or metafields for lightweight cross-reference when full collection sync is overkill.

Practical recommendations#

• ✓Publish a SKU and variant mapping matrix before the first production sync.
• ✓Store external IDs on both sides before enabling automated create jobs.
• ✓Run a duplicate-detection report on barcode and default_code weekly during rollout.
• ✓Separate catalog sync jobs from inventory and order jobs for clearer failure isolation.
• ✓Validate tax category and fiscal mapping for new products in staging before publish.
• ✓Consult the Customization pillar when standard product fields cannot hold required channel metadata.

Common mistakes#

• !Matching products by title or handle instead of stable external IDs.
• !Creating a new Odoo product for every Shopify variant option change.
• !Syncing list price both directions with no conflict rule.
• !Ignoring archived or draft products and leaving stale availability online.
• !Omitting weight, HS code, or country of origin needed for shipping integrations.
• !Running full catalog pulls on every cron tick and exhausting API budgets.

Conclusion#

Product sync succeeds with a declared catalog master, stable external IDs, and explicit create-update-archive rules — not implicit hope that titles stay unique.

Once catalog mapping is stable, align inventory and order sync to the same SKU keys.