Odoo already runs your products, stock, pricelists, orders and invoices, and it does that well. It also comes with its own shop. From building shops on Odoo, our view is that Odoo on its own is not built to serve a fast storefront with real traffic, and that its web front holds a marketing team back.
So the build we recommend has three parts: a headless storefront for everything the customer sees, Meilisearch in the middle holding a fast copy of the catalogue, and Odoo behind it, receiving the orders. The rest of this post covers why, how the data moves, which Odoo plan and API it needs, and what your marketing team can change on its own afterwards. It also covers what changes when the same Odoo feeds a marketplace or a dropship platform.
Why is Odoo on its own not enough for a fast shop?
Odoo does include a shop. Odoo eCommerce, in Odoo’s words, “provides an open-source platform for building and managing an online store”. For a small catalogue with modest traffic that can be enough. We see three reasons it stops being enough.
The web front is Odoo-specific technology. Odoo’s pages are rendered with QWeb, which Odoo describes as “the primary templating engine used by Odoo” and “an XML templating engine”. Its JavaScript runs on Owl, a UI framework “built by Odoo”, and Odoo’s own documentation says the framework “is also used in other situations, such as the Odoo website”. Few web developers outside the Odoo world work with either, and in our experience finding one for a design or campaign change takes a while. Within those templates, design and campaign pages are limited to what the theme and the website builder allow.
Odoo’s cloud is not meant to answer page views through the API. Odoo’s acceptable use policy prohibits “sending large numbers of RPC or remote API calls to our systems without appropriate throttling” and gives the working figure: “Throttled calls are typically acceptable for unsustained usage at a rate of 1 call/second, with no parallel calls.” A product listing and a product page from a handful of visitors exceed that within seconds, and the policy says customers who break its rules “may see their subscriptions suspended without prior notice”. Odoo names one exit: “On Odoo.sh the dedicated hosting mode can be considered as an alternative to lift this restriction.” On-premise, the ceiling is your own server.
Every API call is a separate piece of work. In Odoo’s JSON-2 API, “All calls to the JSON-2 endpoint run in their own SQL transaction.” A page that needs a product, its price and its stock either makes several round trips or depends on a custom method that bundles them.
Odoo is an ERP, and it is good at being one. A shop page has to load in a moment for every visitor, during a campaign as well, and that is a different job.
How does the layer between the storefront and Odoo work?
We use Meilisearch as that layer. It holds a copy of every product with its prices and stock, and the storefront reads listings, product pages, search and filters from it. Odoo never sees a page view.
What Meilisearch documents about itself, and why it matters here:
| Meilisearch, in its own documentation | What it means for the shop |
|---|---|
| “Every query returns results in under 50 milliseconds, whether your index contains a thousand documents or tens of millions.” | Category pages and search do not wait on the ERP |
| Built for “search-as-you-type interfaces, faceted navigation, filtering, sorting” | Filters by size, colour or price come with it |
| “Typo tolerance is enabled by default” | A search for a misspelled product still finds it |
| A partial update means “fields not included in the update remain unchanged” | A stock change updates only the stock field |
| “Processing operations asynchronously allows Meilisearch to handle resource-intensive tasks without impacting search performance.” | A full catalogue re-sync runs without slowing the shop |
The last row has a consequence worth knowing: updates are queued as tasks, so a change reaches the shop shortly after it is made. For prices and descriptions that does not matter. For stock it is one more reason the order step checks with Odoo.
Data moves in two directions:
- Odoo to Meilisearch, for catalogue, prices and stock. Odoo’s automation rules can send a webhook notification, a POST request “with the values of the selected Fields” to a URL you set, so an edit in Odoo triggers an update. A scheduled full sync on top catches anything a webhook missed.
- Storefront to Odoo, for orders. Orders skip the copy and go straight into Odoo, written once, with retries, and never lost when Odoo is briefly unreachable.
Does your Odoo plan allow an external shop?
Check this first, because it can end the project before it starts. Odoo’s API documentation states that “access to data via the external API is only available on Custom Odoo pricing plans” and “is not available on One App Free or Standard plans.” Syncing to Meilisearch and writing orders back both need that access.
Where Odoo is hosted decides how much you can extend it:
| Hosting | What it means for the integration |
|---|---|
| Odoo Online | “Odoo Online is incompatible with custom modules or modules from the Odoo Apps Store”, so the integration works with standard methods only |
| Odoo.sh | Odoo’s platform for “development, staging and production branches, allowing you to develop or use custom modules” |
| On-premise | You host Odoo Enterprise yourself. Custom modules are possible |
The custom module question decides whether the integration can add one method inside Odoo for a job like “create this web order and confirm it”, or has to string several standard calls together from outside.
Which system owns what?
Meilisearch holds a copy of products, prices and stock, and Odoo stays the system that owns them. Settle the rest before anyone writes code.
| Data | Owned by | Why |
|---|---|---|
| Products and variants | Odoo | Stock, purchasing and invoicing all hang off the product record |
| Prices and discounts | Odoo | Pricelists handle “different prices and discounts based on currencies, time periods, purchase volumes, customers’ location, and/or customer type” |
| Stock levels | Odoo | The storefront displays a number it did not calculate |
| Tax rates | Odoo | The invoice is posted in Odoo, so the shop’s rates come from there |
| Orders and invoices | Odoo | Fulfilment and invoicing happen in Odoo |
| Order confirmation e-mail | Usually Odoo | On a client’s headless shop running on Odoo, it comes out of an Odoo template |
| Pages, campaigns, navigation, images | The storefront and its CMS | Odoo does not need to know about them |
| Product descriptions | Your choice | Either side works. Pick one deliberately |
If product descriptions live in Odoo, your content team files a request every time a sentence changes. If they live in the CMS, operations loses sight of what the shop says. Decide before launch, because moving them later means a content migration.
What does a marketplace need from Odoo?
Selling on a marketplace adds a second shop front to the same Odoo, and that shop front belongs to someone else. Odoo documents its own connectors for some of them: its TikTok Shop connector lists Germany, Spain, France, Italy and Ireland among its supported markets, and its Amazon connector covers Amazon.de, Amazon.fr, Amazon.es, Amazon.it and Amazon.nl. With or without a connector, the work comes in five parts, in the order it happens.
The catalogue. Each marketplace decides which product data it needs. Limango lists German product data as a requirement, Fressnapf asks whether you can supply EAN numbers, and Shop Apotheke asks for product data and customer service in the languages it requires. Limango, Fressnapf and PcComponentes all run their marketplaces on Mirakl, so the connection goes to the same kind of interface each time, while the catalogue rules stay each retailer’s own. Odoo holds the product record and the integration translates it into each marketplace’s fields. The link that has to hold is the SKU. Odoo’s TikTok Shop documentation puts it this way: “The TikTok Shop Seller SKU must correspond exactly to the Internal Reference of the product or its variant.” On a marketplace you are still the seller in the distance contract. Article 6 of the Consumer Rights Directive puts the pre-contractual information on “the trader”, and Article 6a, which adds duties for the marketplace, says its information on how obligations are shared comes “without prejudice to any responsibility” the third-party trader has. The EU guarantee notice is one duty that applies to every trader selling goods to consumers.
The price. The price a marketplace buyer pays is set on the marketplace. TikTok Shop sets prices “at the SKU level” within a range per market, and Temu “supports merchants in submitting both a supply price and a retail price”. Odoo’s own TikTok Shop and Amazon connectors list orders and stock quantities among their supported features, and no price sync. In Odoo, a separate pricelist keeps the marketplace price apart from the shop price, because a pricelist can be “tailored to only apply to specific customers, customer groups, sales orders”. The order that arrives in Odoo should carry the price the buyer actually paid.
The stock. One pool of stock feeding several shop fronts is where overselling starts, because each front only knows the number as often as it is sent. Odoo’s TikTok Shop connector processes inventory every 30 minutes. Its Shopify connector sends the “free quantity (Quantity on Hand minus Reserved Quantity)” of one mapped location, which is the right number to publish. Decide which warehouse each marketplace sells from: Odoo supports several warehouses, and the TikTok Shop connector has a warehouse field “to limit stock fetching to specific warehouses”. Holding back a few units of a fast seller costs less than cancelling an order a buyer has already paid for.
The order import. A marketplace order has to become an Odoo sales order before anyone can pick, ship or invoice it. Odoo’s TikTok Shop connector fetches orders every five minutes and creates a contact for each new buyer. For a marketplace without an Odoo connector, the integration writes the order through the JSON-2 API and confirms it with the action_confirm method that Odoo names for sales orders. Mark every order with its channel: a sales team per marketplace, which Odoo’s Amazon connector lets you set per account, and the marketplace’s order number in Source Document, the field for “the reference of the document that generated the quotation/sales order”. Then mind the clock. TikTok Shop cancels an order that is not ready for collection by its shipping due time.
Returns and cancellations. Write this part into the brief from the start. In Odoo, a return before invoicing is a reverse transfer, and after invoicing it also needs a credit note, which Odoo calls “the only legal method for canceling, refunding, or modifying a validated invoice”. The connectors carry part of it. A cancellation on TikTok Shop updates the order in Odoo, while “canceling an order in Odoo does not reflect on TikTok Shop”, and refunds stay in TikTok Shop’s Partner Center and Amazon’s Seller Central. Temu gives sellers “a 24-hour window to respond to a consumer’s cancellation request”, and Limango has you ship with a delivery note and a return label in the parcel. Decide who books the credit note when the marketplace refunds a buyer, and how a cancellation made in one system reaches the other.
Is a dropship platform the same integration as a marketplace?
On a marketplace where you ship your own orders, and on a dropship platform, you hold the stock and ship the parcel. The difference is who sells to the buyer. On a marketplace you are the seller: the contract is yours, the platform runs the storefront, and you set the price. On a dropship platform the retailer is the seller. It sells under its own name and at its own price, sends you a purchase order, and you ship to its customer on its behalf. Urban Outfitters’ guide is written for “Vendors that Drop Ship directly to the consumer on behalf of URBN”, and Dsco requires each item to carry a cost, which “is what a supplier charges a retailer for the item.”

A dropship platform runs on documents with deadlines. The retailer sends a purchase order. You acknowledge it, confirm the shipment with tracking, invoice the retailer and keep the inventory feed current. Wayfair’s dropship programme requires the purchase order, the cancellation, the advance ship notice and the inventory document, and says to send the ship notice “immediately after the shipment leaves your facility”. Over its API it expects a full inventory feed “at least once every 24 hours” and smaller updates “ideally every 30 minutes”. Rithum, which runs Dsco, tells suppliers to update inventory “at least daily”, and whether an order needs an acknowledgement depends on each retailer’s rules. These programmes reach European suppliers too. Virtualstock describes itself as a European dropshipping and curated marketplace platform, and Wayfair and URBN both publish dropship guidance for EU suppliers.
Odoo answers the marketplace half with its own connectors. The dropship half is different. Odoo’s documentation uses “EDI” for electronic invoicing over Peppol and for importing one Odoo database’s purchase order into another as UBL XML. It names no X12 or EDIFACT order messages, and its Dropship route covers the opposite direction, where the Odoo company buys and its vendor ships. In Odoo, the retailer’s purchase order becomes an ordinary sales order, with the retailer as the customer and the end buyer as a separate delivery address, which Odoo supports on a contact. The acknowledgement, ship notice, invoice and inventory feed go back through an integration on the JSON-2 API, in the format the platform accepts.
Grouped by the kind of integration they ask for:
| Platform | What it is | How sellers or suppliers connect, in its own documentation |
|---|---|---|
| TikTok Shop | Marketplace | Odoo’s own TikTok Shop connector, or TikTok Shop’s seller API |
| Shopee | Marketplace | Odoo’s own Shopee connector |
| Limango | Marketplace | Mirakl: catalogue by CSV, XML, XLSX, SFTP or API |
| Fressnapf | Marketplace | Mirakl |
| PcComponentes | Marketplace | Mirakl API |
| Urban Outfitters (URBN) | Marketplace and dropship | Mirakl for the marketplace, Rithum’s Dsco for dropship |
| Best Buy | Marketplace and dropship | Mirakl for the marketplace, Rithum for dropship |
| Temu | Marketplace | Seller API, with a separate partner platform for Europe |
| Shein | Marketplace | Seller API on the SHEIN Open Platform |
| Etsy | Marketplace | Seller API |
| Back Market | Marketplace | API, or CSV in the back office |
| Newegg | Marketplace | Seller API |
| Depop | Marketplace | Partner API, not open to the general public |
| The Iconic | Marketplace | Seller Center API, documentation behind a login |
| Shop Apotheke | Marketplace for EU-registered companies | Not stated publicly |
| Overstock | Marketplace | Not stated publicly |
| Poshmark | Marketplace | Not stated publicly |
| Dsco (Rithum) | Dropship platform | API, or CSV and EDI files |
| CommerceHub and OrderStream | Dropship platform | Supplier portal and spreadsheet upload |
| Virtualstock | Dropship and curated marketplace | Supplier portal; technical specification not public |
| Wayfair | Retailer with a dropship programme | API, or EDI (X12, EDIFACT) or CSV over VAN, AS2 or SFTP |
| Nordstrom | Retailer with a dropship programme | Through Dsco |
| Costco, Kohl’s, NOTHS, Bauhaus | Supplier programme not published | Not stated publicly |
Which Odoo API should the integration use?
Build on the External JSON-2 API, which is “new in version 19.0”. Odoo’s documentation says the older XML-RPC and JSON-RPC endpoints are “scheduled for removal in Odoo 22 (fall 2028) and Online 21.1 (winter 2027)”. An integration written against them today has to be rewritten, and on Odoo Online sooner.
Three details from the JSON-2 documentation shape the build:
- One API key per integration. Odoo recommends “dedicated bot users” for automated integrations, so the key has only the permissions it needs and the access log shows which system made each change.
- No transaction spans two calls. “Using the JSON-2 API, it is not possible to chain multiple calls inside a single transaction.” Odoo calls this “especially dangerous when performing operations related to reservations, payments, and such”, which describes a checkout. Its fix is one method doing all related work, written “in a dedicated module” if needed. On Odoo Online that module is not an option.
- Each database is different. “The actual models, fields and methods available are specific to every database”, and each one lists its own on a
/docpage.
Which stock number, and when does an order count?
Two decisions that look small and cause most of the support tickets later:
- Stock. Odoo documents two numbers: on-hand, “the number of units currently available in inventory”, and forecasted, which is on hand plus incoming minus outgoing shipments. They differ exactly when an item is popular. Pick one for Meilisearch, and check availability against Odoo again when the order is placed.
- Orders. Odoo’s own shop moves an order from “Quotation Sent” to “Sales Order” once “the payment has been successfully received”. An external shop has to decide where in that flow it writes.
What can your marketing team change without a developer?
This is the reason to build the storefront separately, so write it down before launch.
| Without a developer | Stays with whoever runs Odoo |
|---|---|
| Page layout, campaign and landing pages | Pricelists and discounts |
| Navigation, images, editorial copy | Tax settings |
| SEO titles and descriptions | Stock rules and which quantity the shop shows |
| Product descriptions, if they live in the CMS | Order flow and confirmation e-mail templates |
If the left column ends up in a ticket queue anyway, the project has not done its job.
Questions to ask before you start
Ask these of whoever builds it and whoever administers Odoo:
- Are we on a Custom plan, and where is Odoo hosted?
- Which system holds product descriptions, and who can edit them without a request?
- Which stock number goes to the shop, and is it checked again at checkout?
- How quickly does a change in Odoo reach Meilisearch, and how often does the full sync run?
- What happens to an order placed while Odoo is unreachable?
- Is the integration on JSON-2, and if not, when does it move?
- Which steps of creating an order run as separate calls, and what happens if one fails halfway?
- Who is notified when a sync fails, and who is notified when it succeeds but skips records?
Question 8 is the one most often missing, because a sync that skips records still reports success and nobody gets told.
If your marketing plan needs a better shop and the engineers who could build it are busy with the product, this is the work we do. Our Odoo e-commerce integration page explains how we connect a headless storefront to Odoo, and what a website audit reveals covers how we look at an existing shop before anyone scopes a rebuild.