Shopify and Odoo can be a useful pair: a customer-facing storefront connected to inventory, sales and accounting. Growing merchants often consider this combination when multiple channels, warehouses or more detailed back-office processes make manual entry impractical.
Then they look at integrating the two and find a dozen connectors, a hundred forum threads, and no clear answer to the only question that matters: what will actually work for my store?
Use this guide to choose a connector, prepare your data and test the flows before launch. The ownership model below is an example integration design, not the specification of every connector. The Waslio Odoo Connector remains coming soon; a custom integration enquiry is a separate service.
Which Shopify–Odoo connector fits your setup?
Start with your Odoo version and hosting. Odoo’s 19.0 setup documentation currently specifies Odoo.sh and version 19.0 for its official integration. Check that requirement before following its installation instructions. For a different deployment, assess a compatible third-party connector or a custom integration against your actual requirements.
The official connector overview describes scheduled synchronization, not real-time webhooks. Its documented default is a ten-minute order cycle, with inventory pushed after order synchronization. Products are imported from Shopify into Odoo; do not assume the example ERP-to-store product flow later in this guide is included.
| Check | Evidence to request | Decision it supports |
|---|---|---|
| Version and hosting | A supported combination matching your database | Whether installation is a viable option |
| Required data flows | A demonstration using your representative order and product | Whether configuration covers the work |
| Failure handling | A visible error, a safe retry and a reconciliation result | Whether your team can operate it |
| Maintenance | A named owner and upgrade process | Who will keep the connection working |
Multiple warehouses or bundles are reasons to test carefully, not automatic reasons to commission custom software. Start with the smallest option that meets the required flows. Add custom work only where a demonstrated gap justifies the cost and responsibility.
How to connect Shopify orders to Odoo: a launch sequence
This sequence is a project checklist. Use the selected vendor’s current installation instructions for credentials, permissions and account-specific settings.
- Record the environment. Note the Odoo version, hosting, company, Shopify store and connector version. Name an operational owner. Agree whether fulfilment happens in Shopify or Odoo before configuring the connection.
- Choose a representative sample. Include a straightforward order, a discount, a shipping charge, a cancellation and a partial fulfilment. Use an authorized test environment and appropriate test records rather than experimenting on active customer orders.
- Prepare mappings. Match products, variants and locations. Record unresolved or duplicate SKUs as exceptions. Decide how tax and payment mappings will be checked by the responsible business owner.
- Connect using the supported installation flow. For the official option, follow Odoo’s connector configuration guide. Keep credentials in the designated settings; an enquiry form or shared spreadsheet is not a credential store.
- Import a controlled order range. Check that each source order has the expected destination record. Compare quantities, discounts, shipping and the final total. Repeat the synchronization and verify that it does not create duplicates.
- Verify stock and delivery separately. Confirm what a quantity means on both sides and which system sends shipment updates. Use the inventory sync troubleshooting checklist before enabling broader stock writes.
- Roll out with a recovery plan. Keep the initial scope small, record the first successful reconciliation and assign an owner to the exception queue. Expand after the sample flows pass. The ERP implementation checklist covers wider launch responsibilities.
The five flows, and which system owns each
The table below is a proposed custom ownership model. Verify each direction against your selected connector; it is not a list of native features.
| Flow | Direction | Owner | Where connectors struggle |
|---|---|---|---|
| Orders | Shopify → Odoo | Shopify | Discounts, taxes, partial payments, edited orders |
| Products & variants | Odoo → Shopify | Odoo (SKU, price, cost); Shopify (copy, images) | Variant option mapping, bundles |
| Stock | Odoo → Shopify | Odoo | Multi-location, reserved vs available, timing |
| Fulfilment | Odoo → Shopify | Odoo | Partial shipments, multiple tracking numbers |
| Refunds & returns | Shopify → Odoo | Shopify initiates | Restock decisions, credit notes, gateway fees |
Orders: the flow that decides everything
Every Shopify order should become exactly one Odoo sales order, once, with the same total.
That sentence hides four problems.
Once. Shopify webhooks retry. Your integration must check whether the order already exists (by Shopify order ID, not by order name — names can be reused across stores) before creating anything.
Same total. Shopify discounts can apply to lines, orders or shipping. Taxes can be included or added. Map the allocations, shipping charges, tax rules and rounding into the correct Odoo fields or lines; taxes do not simply become generic sales-order lines. Test the totals, then reconcile payments, fees and payouts separately.
Payment. Agree how the integration maps payment methods and records payments in Odoo. Verify the chosen configuration with the person responsible for reconciliation; a payment record and a gateway payout are different records.
Edited orders. Decide what happens if an order changes after import: supported updates, a controlled hold or a manual exception. Test the selected connector rather than assuming edits are either ignored or fully supported.
Products: split ownership by field, not by system
The instinct is to pick one system as "the master" for products. In practice, ownership splits by field:
Example ownership: Odoo can own SKU, barcode, weight, cost and base price in a custom flow, while Shopify retains marketing copy, images and collections. Choose ownership field by field; the direction depends on the connector and your business process.
The sync should touch only Odoo-owned fields when pushing to Shopify, and never pull Shopify-owned fields back. The moment a sync overwrites a merchandiser's carefully written description with the ERP's "PROD-4471 RED L," trust is gone.
Variants need an explicit mapping between Shopify variant IDs and Odoo product variants. Matching option labels can help the initial mapping, but names alone are not a durable identifier. Record the mapping before the first sync and define how new variants are added.
Bundles are supported through apps, including Shopify's own Bundles app. Decide how the sold bundle and its components map to Odoo kits or individual products, and test stock, discounts and returns. See Shopify's bundle requirements.
Stock: available, not on-hand
Agree the sellable quantity per location, including reservations and any channel buffer. Shopify distinguishes available, committed, unavailable and incoming stock. Do not copy a physical on-hand total into an available field without checking the meaning. The inventory guide walks through timing and double-reservation problems.
Two details that prevent overselling:
- Buffer. Keep one or two units back for fast movers, so the seconds between a sale and the next sync don't create a negative.
- Measure freshness. Event-driven stock updates can reduce delay when supported; scheduled connectors need an interval and buffer appropriate to sales velocity. Keep a reconciliation job even when using events.
Fulfilment: the flow customers actually see
When a delivery is validated in Odoo, create the Shopify fulfilment with the courier name and tracking number. Shopify then sends the shipping notification the customer expects.
Partial shipments must create partial fulfilments. Multi-parcel deliveries need every tracking number, not just the first. And if you use a dispatch tool that books couriers directly from Shopify (as Waslio Courier does), decide which side creates the fulfilment — never both.
Refunds and returns: scope them, don't assume them
A Shopify refund may require a credit note against the original posted invoice. Handle stock separately: was the item physically returned, damaged, never shipped or refunded without return? Preserve Shopify's restock decision while following Odoo's return and inspection workflow. A damaged physical return can still need a receipt into an inspection location rather than sellable stock.
Gateway fees on refunds are the small thing that becomes a big reconciliation problem. Decide how they're recorded on day one.
Connector, custom, or both?
Use an off-the-shelf connector when its supported version, data flows and operating model match your requirements. Test your representative catalogue, order exceptions and recovery process before relying on it.
Consider custom work when a tested requirement remains unsupported, such as a particular order-edit process or ownership rule. Compare the cost of the gap with implementation and ongoing maintenance.
Consider a hybrid when a connector covers most required flows and a bounded extension can handle the remainder. Make sure the two components cannot both write the same fields without a clear rule.
The Waslio Odoo Connector is coming soon. If you need help now, we can discuss a scoped integration project and assess the required flows against your current setup.
Need to connect Shopify and Odoo?
Share your version, hosting, connector and the flow that needs attention. Describe one concrete example without sending credentials or customer records.
Discuss the integration →
FAQ
Does Shopify integrate with Odoo natively?
Odoo documents an official connector for Odoo 19.0 on Odoo.sh. Confirm current requirements and supported flows in its setup guide. Other connectors have their own compatibility requirements.
Which should be the master, Shopify or Odoo?
Choose ownership by field and by flow. The model in this guide is illustrative; the connector must support the directions you need. Do not let two independent processes overwrite the same field without a conflict rule.
How often should stock sync between Odoo and Shopify?
Set a freshness target based on sales velocity and your stock buffer. The official Odoo 19.0 connector uses scheduled synchronization; other implementations can differ. Measure actual delay and reconcile mismatches.
Can I sync Shopify orders to Odoo with discounts and taxes?
Validate the selected connector with representative discounted and taxed orders. Compare quantities, shipping, rounding and final totals, then reconcile payments and payouts separately.
Is a custom Shopify Odoo integration worth it?
Custom work is justified when a tested business requirement is not met by a suitable connector and the value exceeds implementation and maintenance costs. Multiple warehouses alone do not prove that custom work is necessary.
Connector facts checked against the linked Odoo documentation on 14 October 2026. Setup steps above are a launch checklist; verify availability and behavior in your own environment.
Implementation patterns are illustrative. Availability, permissions and pricing vary by platform, version and plan. Confirm these for your setup; effort estimates are not quotations.