Shopify to Odoo, new products added without duplicates
Adding products shouldn’t feel like double-entry bookkeeping. But if you sell on Shopify and run operations in Odoo, you’ve probably copied the same SKU, price, and description twice… then cleaned up the duplicates later.
This Shopify Odoo sync hits eCommerce managers first (new items land daily). Ops leads feel it when inventory and accounting don’t match. And agency teams building “systems that scale” end up babysitting catalogs instead of improving conversion.
This workflow automatically creates new Shopify products in Odoo, checks SKU first to prevent duplicates, and stops itself when the item already exists. You’ll see how it works, what you need, and where people usually get stuck.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Shopify to Odoo, new products added without duplicates
flowchart LR
subgraph sg0["Shopify New Product Hook Flow"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Initiate Flow", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/shopify.svg' width='40' height='40' /></div><br/>Shopify New Product Hook"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/odoo.svg' width='40' height='40' /></div><br/>Lookup Odoo Product"]
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Product Exists Check", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/odoo.svg' width='40' height='40' /></div><br/>Generate Odoo Item"]
n5@{ icon: "mdi:cog", form: "rounded", label: "Halt Duplicate Detected", pos: "b", h: 48 }
n0 --> n1
n1 --> n2
n3 --> n4
n3 --> n5
n2 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n1 trigger
class n3 decision
classDef customIcon fill:none,stroke:none
class n1,n2,n4 customIcon
The Problem: Product Catalog Drift (and Duplicate SKUs)
Most teams don’t notice the problem on day one. It shows up after a week of new products, a couple of price changes, and one rushed “quick upload” before a promo. Shopify becomes the source of truth for what’s live, while Odoo becomes the source of truth for inventory, invoicing, and reporting. When those two catalogs drift, you get mismatched internal references, missing items, and duplicates that look identical until they break a sales order. Honestly, the worst part is the mental load of not trusting your own data.
None of these alone is the problem. Together, they are.
- Manual product entry in Odoo turns into a daily chore that can take about 1–2 hours a week for even a small catalog.
- Duplicates happen when the SKU/internal reference is typed differently, which means you “have the product” but can’t actually use it reliably.
- Teams delay creating products in Odoo, so inventory, purchasing, and accounting end up working off yesterday’s catalog.
- Fixing the mess later is slower than doing it right up front because you also have to merge history, reporting, and stock moves.
The Solution: Duplicate-Free Shopify → Odoo Product Creation
This n8n workflow watches for newly created products in Shopify and mirrors them into Odoo automatically. The key is that it doesn’t blindly create items. As soon as Shopify sends a new product event, the workflow searches Odoo using the Shopify SKU and checks it against Odoo’s “Internal Reference” field. If it finds a match, it stops right there. No extra products, no catalog noise, no cleanup. If it doesn’t find a match, it creates a new product in Odoo and maps the essentials you actually need to operate: product name, public price, internal reference (SKU), and description.
The workflow starts with a Shopify “new product” trigger. Then it looks up an existing Odoo product by SKU and runs a simple decision check. Finally, it either creates the Odoo product or halts to prevent duplicates.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you add 20 new products in a month (a few collections, a few restocks, some bundles). Manually, entering each one into Odoo often takes about 10 minutes once you copy the name, SKU, price, and description and double-check fields. That’s roughly 3 hours of repetitive work, plus the inevitable “wait, which SKU is correct?” moments. With this automation, the “time spent” becomes close to zero: create the product in Shopify, and Odoo is updated automatically after the SKU check runs in the background.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Shopify for the new product trigger.
- Odoo to search and create products.
- Shopify API access (create a private/custom app in Shopify admin)
- Odoo XML-RPC credentials (from your Odoo user and database settings)
Skill level: Beginner. You’ll mainly connect accounts and confirm a few field mappings like SKU → Internal Reference.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A new product is created in Shopify. The workflow is triggered right away, so it reacts to real product creation instead of waiting for someone to run an import.
Odoo is searched using the SKU. The automation looks up an existing Odoo product where the Internal Reference matches the Shopify product’s SKU, which is the cleanest way to avoid “same product, different record.”
A simple decision prevents duplicates. If Odoo already has that SKU, the workflow stops (it uses a “do nothing” halt). If there’s no match, it moves forward to create the product.
The product is created in Odoo with mapped fields. Product name, public price, internal reference, and description are set automatically so your Odoo catalog stays usable for sales, inventory, and accounting.
You can easily modify the mapped fields to include things like categories, taxes, or variants based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Configure the Shopify Trigger
This workflow starts when a new product is created in Shopify. You’ll configure the trigger and ensure it connects to your Shopify store.
- Add or open Shopify New Product Hook and confirm it is connected after Initiate Flow.
- Verify the trigger listens for new product creation events in Shopify.
- Credential Required: Connect your Shopify API credentials in Shopify New Product Hook.
⚠️ Common Pitfall: If the trigger doesn’t fire, re-check the Shopify app permissions to ensure product read access is enabled.
Connect Odoo for Product Lookup
Next, the workflow checks whether the Shopify product already exists in Odoo to avoid duplicates.
- Open Lookup Odoo Product and set it to search your Odoo products based on a unique Shopify identifier (such as SKU or product ID).
- Credential Required: Connect your Odoo credentials in Lookup Odoo Product.
- Confirm the connection flow: Shopify New Product Hook → Lookup Odoo Product.
Set Up Product Existence Logic
The workflow uses a conditional check to route new products to creation and duplicates to a halt node.
- Configure Product Exists Check to evaluate the result of Lookup Odoo Product (for example, check if the returned list is empty).
- Confirm the true/false outputs: Product Exists Check routes to Generate Odoo Item when the product does not exist.
- Confirm the alternate route: Product Exists Check routes to Halt Duplicate Detected when a duplicate is found.
Tip: Add a small sample payload to Lookup Odoo Product during testing to validate your condition logic in Product Exists Check.
Configure Odoo Product Creation
If the product doesn’t exist, the workflow creates it in Odoo.
- Open Generate Odoo Item and map Shopify fields (name, SKU, price, inventory) to Odoo product fields.
- Credential Required: Connect your Odoo credentials in Generate Odoo Item.
- Leave Halt Duplicate Detected as-is; it serves as a safe stop when duplicates are detected.
Test and Activate Your Workflow
Run a full test to confirm the product sync flow is working end-to-end.
- Click Execute Workflow and create a test product in Shopify to trigger Shopify New Product Hook.
- Verify that Lookup Odoo Product runs and Product Exists Check routes correctly.
- Confirm new products appear in Odoo via Generate Odoo Item, and duplicates end in Halt Duplicate Detected.
- Once verified, toggle the workflow to Active for production use.
Common Gotchas
- Shopify credentials can expire or lose permissions after app changes. If things break, check your Shopify app scopes and regenerated access token first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Odoo XML-RPC access can fail due to the wrong database name or user permissions. If the lookup returns nothing every time, confirm the Odoo database, user role, and that “Internal Reference” is the field being queried.
Frequently Asked Questions
About 30 minutes if you already have Shopify and Odoo access ready.
No. You’ll connect Shopify and Odoo, then confirm the SKU and field mappings.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in standard Shopify and Odoo hosting costs (no extra per-task fees from this workflow itself).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but plan your “source of truth” first. You can extend the Odoo product creation step to map extra fields like category, tax rules, or barcode, and you can add logic in the conditional check to handle variants differently. Some teams also add a Google Sheets log to track what was created and when. If you want to swap the trigger (for example, run on a schedule), you can replace the Shopify trigger with a Cron-based approach and keep the same SKU lookup logic.
Most of the time it’s the wrong database name, username, or XML-RPC endpoint. Re-test the Odoo credentials in n8n and confirm the user has permission to read and create products. If the lookup node succeeds but always returns “no match,” check that you’re searching the Internal Reference field and that your Shopify SKU is actually populated.
A lot—practically, it’s limited by your n8n plan and how often you create products.
Often, yes, because the duplicate-check logic is straightforward in n8n and you can self-host for unlimited runs. n8n also makes it easier to control what happens when Odoo returns “multiple matches,” when SKUs are blank, or when you want to add a second lookup rule. Zapier and Make can still do it, but you may end up paying more as volume grows, and the error handling can feel cramped. If your automation needs are only “new product → create product” with zero branching, those tools can be fine. Talk to an automation expert if you want help choosing.
Once this is running, new products stop being a two-system chore. Your Shopify catalog stays your storefront, Odoo stays your operations brain, and the workflow keeps them in sync.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
