We connect Odoo to Shopify, WooCommerce, PrestaShop, Magento and marketplaces such as Amazon. Products, prices and stock come from Odoo; orders and customers go back to Odoo, ready for invoicing and shipping.
Integrating Odoo with e-commerce means your online store, marketplaces and ERP work on the same data: an order paid on Shopify or WooCommerce lands in Odoo, reduces stock on every channel and becomes an invoice and a shipment without being retyped. URETECH works as an Odoo System Integrator: we use existing connectors, such as the Amazon connector in Odoo Enterprise or those on the Odoo Apps Store, when they cover your cases, and we build with the Odoo APIs only what is missing.
The price depends on the channels to connect, the number of products and special rules (kits, variants, B2B price lists): you find it in the proposal after the free analysis. Odoo licences are separate and listed on our Odoo implementation page.
An item that is out of stock stays on sale on Shopify or Amazon, and the order has to be cancelled.
Every online order becomes a sales order entered by hand, with mistakes on codes, addresses and VAT.
The price changes in Odoo but not in the store, or B2B price lists reach consumers.
The e-invoice and the carrier label wait until someone enters the order.
STOCK SIMULATOR
One item, three in stock, four sales on different channels. Run the day without integration, then with it: see where the extra sale comes from.
Example: Blue hoodie, size M
ERP · SAP Business One
real stock
Website · Shopify
stock shown
Marketplace
stock shown
| Data | Typical direction | Frequency |
|---|---|---|
| Items, descriptions, variants | ERP → shop | on every change or several times a day |
| Prices and price lists (B2B too) | ERP → shop | on every change |
| Stock per warehouse | ERP → shop and marketplaces | every few minutes |
| Orders and payments | Shop → ERP | as soon as the order is paid |
| Customers and addresses | Shop → ERP | with the order |
| Shipping and tracking | ERP or carrier → shop | on dispatch |
| Invoices and documents | ERP → customer | when issued |
For every piece of data we decide which system is in charge: usually the ERP for items, prices and stock, the shop for orders.
Item and quantities are an example. Frequencies are those in the data flow table.
| Data | Typical direction | Frequency |
|---|---|---|
| Products, variants and images | Odoo → store and marketplaces | on every change |
| Prices and price lists (B2B too) | Odoo → store | on every change |
| Stock per warehouse | Odoo → every channel | every few minutes |
| Orders and payments | Store and marketplaces → Odoo | as soon as the order is paid |
| Customers and addresses | Store → Odoo (contacts) | with the order |
| Shipping and tracking | Odoo or carrier → store | on shipment |
| Italian e-invoice | Odoo → SdI exchange system and customer | on issue |
For each piece of data we decide which system is in charge: usually Odoo for products, prices and stock, the store for orders. Kits, partial returns and store promotions that Odoo does not know about are the cases to map before writing code.
The combinations we are asked for most.
Shopify APIs for products, stock and orders: an Odoo Apps Store connector or a custom integration, multiple stores too.
WooCommerce REST API and order webhooks into Odoo; a custom plugin where more logic is needed.
PrestaShop webservice and Magento (Adobe Commerce) REST API connected to the Odoo APIs.
The Amazon connector in Odoo Enterprise for orders and stock, or a custom integration for special rules.
The Italian localisation of Odoo creates the e-invoice from orders coming from the store.
Stripe, PayPal and carriers connected, so labels and tracking start from Odoo.
With marketplaces the stock problem multiplies: the same item is on sale on the site, on Amazon and on other channels. There are two ways: connect each marketplace directly to Odoo, or go through a multichannel platform acting as a hub and connect only that to Odoo. We assess the costs and fees of each with you. Either way, marketplace orders become sales orders in Odoo like those from the site, and stock goes down on every channel at once.
If your ERP is not Odoo, the right page is e-commerce and ERP integration.
Data flows first, then code.
Odoo version (Online, Odoo.sh or server), store, channels and order volumes.
Which system is in charge of each piece of data, product codes, variants, kits, returns and price lists.
We configure the existing connector or build the integration with the Odoo APIs, with queues and a log.
Test orders on an Odoo test database and stock comparison.
Automatic alerts if a flow stops, and ongoing support.
A published Odoo scenario, presented as an example, and related pages.
A solution example with phases and modules. It is a scenario, not a client.
Custom Shopify stores, ready to connect to Odoo.
An example for companies that receive B2B orders by email or PDF as well as on the site.
Tell us your Odoo version, store and marketplaces. We reply within 24 business hours; the quote arrives within 48 hours.
We will email you within 24 working hours to book the 30 minutes. If it is urgent, message us on WhatsApp.
Prefer to talk right away?
Mon–Fri 9:00–12:30 and 14:00–20:00 (CET).
Analysis, setup, Italian e-invoicing and costs.
If your ERP is SAP, Business Central, TeamSystem or Zucchetti.
Custom Shopify stores.
WooCommerce stores.
Upgrades, maintenance and migration.
The other services usually needed alongside this one.