esedark
Menu
Back to notes

Odoo / Shopify / orders and stock

Odoo Shopify integration: requirements for orders and stock

A connection is only the start. Agree which system owns each field, how exceptions are handled and how the team will verify orders and stock.

An Odoo Shopify integration should answer an operational question: can the team explain what sold, what remains available and what needs review? Importing a test order does not establish that a connection handles cancellations, returns or an outage during a sales campaign. I would ask suppliers to describe those journeys before comparing prices.

This guide helps a retailer using Odoo as its ERP choose between an existing connector, an extension and custom development. The decision is which option covers your order and inventory rules with clear ownership of exceptions, rather than which product advertises the most features.

Decide which system owns each field

Prepare a field map covering product and variant identifiers, location, sellable quantity, price, order status and shipment reference. For each, record the authorised source, destination, update condition and person who resolves conflicts. “Two-way sync” is not a sufficient requirement: it might allow a merchandising change to overwrite an operational value.

One possible design, subject to your business rules, receives orders from Shopify and calculates in Odoo the quantity published for each agreed location. It should not assume physical stock equals sellable stock. Decide how reservations, damaged goods, other channels and safety buffers affect availability. Also assign ownership of titles, images and prices if these belong in scope.

Require stable mappings between variants and locations. Missing or repeated SKUs need an explicit resolution process; do not authorise matching solely by product name. The guide to field ownership and data conflicts develops this principle for CRM. Here, it informs the purchase of an ecommerce connector.

Choose configuration, an extension or custom development

Existing connector: request a demonstration using your variants, locations and order states on the actual Odoo version, hosting arrangement and modules. If it covers the workflow and exposes exceptions, configuration, a bounded migration and acceptance testing may be enough. Requiring operational control does not automatically justify a new connector.

Extension: this can fit when an existing connector covers the core but lacks a specific rule. The proposal should isolate that extension and assign responsibility for compatibility when the underlying product changes. Confirm that its terms allow the modification before approving it.

Custom development: evaluate it when verified alternatives cannot cover necessary rules or connections. Include documentation, monitoring and maintenance in the purchase. I would not commission implementation while catalogue mappings or inventory ownership remain unresolved. A bounded assessment and access test may be the right first step. Confirm API compatibility, permissions and subscription eligibility against your own accounts; product names alone do not establish access.

A matrix for comparing proposals and accepting delivery

For every row, request included/optional/excluded status, an owner, evidence and cost. These are proposed checks to agree with a supplier, not completed connector tests or client results.

Workflows to verify before accepting an Odoo Shopify integration
WorkflowRule to agreeAcceptance evidence
CatalogueVariant, SKU and location mapping; a destination for ambiguous records.A valid variant is linked; a duplicate identifier stops without overwriting another product.
OrderImport eligibility, fields, currency, discounts and tax treatment validated by the business.Agreed lines and totals are preserved; delivering the same event again does not create another order.
StockAuthoritative source, reservations, locations and sellable quantity.A sale, reservation and adjustment produce expected quantities; a late update cannot restore obsolete stock.
Cancellation and returnSeparate cancellation, refund and physical receipt; name the restock approver.A refund does not restock goods unless explicitly required; a partial return affects only the relevant units.
Partial shipmentMapping of lines, quantities and tracking references.Shipping part of an order leaves the remainder pending; a repeated update does not repeat business effects.
Outage and recoveryPending-work record, reconciliation and an owner for discrepancies.After interruption, saved operations, pending work and mismatches are identified before resuming.

Also agree normal load, test peak and acceptable delay. Unmeasured values remain proposal dependencies. Shopify's official webhook documentation states that ordering and delivery are not guaranteed and recommends reconciliation. I would therefore require a final-state check and discrepancy recovery alongside event notifications.

Example: a refund is not a stock return

Hypothetical example: an order contains two units and one is refunded before anyone knows whether it will return to the warehouse. Proposal A treats every refund as a restock. Proposal B separates the financial refund, receipt and decision to offer the unit for sale again. They buy different behaviour.

Operations must decide what happens to an item that has not arrived or is damaged. The acceptance check should show its state in both systems, sellable quantity and reasons for any mismatch. A manual step may be acceptable, but it needs a named owner and instructions. Do not promise to eliminate all overselling: define the remaining exposure during delays and the trading policy that manages it.

For clothing retail, also evaluate size exchanges and reserving the last unit across checkout and the website. The clothing store software buying matrix specifies those workflows and transfers between locations before choosing the system.

Define scope, deliverables and cutover

List stores, companies, warehouses, variants, states and data directions. Separate invoicing, accounting, carriers, lots, serial numbers and other channels: connecting orders does not automatically include them. The appropriate business owner must supply the tax treatment; technical implementation does not replace that validation.

Require the field map, versioned rules, agreed configuration or code, synthetic-data test evidence, incident records and operating instructions. Specify company-controlled accounts, limited permissions and rights to the materials. For migration, agree a cutoff, treatment of open orders and a way to distinguish historical records from new work. Before live cutover, rehearse a small import and a return to the previous process, reconciling completed work to avoid repeating operations.

Handover should leave someone on the team able to find a pending order, understand its reason and follow the recovery procedure. The automation responsibility matrix helps separate implementation from ongoing operation.

Budget for implementation, maintenance and exit

Compare connector licensing, analysis, data cleanup and mapping, extensions, migration, testing, launch and training. Effort depends on catalogue quality, locations, states, customisations and exceptions. I do not supply my own rate or a licence price without checking the specific scope and terms.

Over the same comparison period, add subscriptions, hosting, monitoring, support, manual reconciliation and adaptation to API or version changes. Distinguish correcting an accepted requirement from adding a new rule. Request support hours, incident priorities and an owner for a stalled queue. Budget for exporting mappings, transferring access and documenting pending work when changing suppliers. The software proposal guide covers milestones and exclusions so the initial price is not mistaken for total cost.

What to send me to scope a first delivery

Send your Odoo version and hosting setup, relevant modules, stores, locations, approximate variant and order volumes, existing connector and three common exceptions. Include an anonymised order, who owns inventory and the manual process you want to replace. Leave out credentials and personal data.

I can review the scope of integration design, implementation and maintenance with you. You can share your retail workflow so we can define a first delivery, its exclusions and the evidence needed to accept it.

Review my Odoo Shopify integration