Odoo Amazon eBay Integration: What Works Natively and What Doesn't

Does Odoo integrate with Amazon and eBay out of the box?

Amazon: yes, through Odoo's own Amazon connector. eBay: it depends on your Odoo version, and for recent versions you should assume you will need a third-party module or a custom build.

Here is the state of play as of October 2026:

• Amazon. Odoo ships an Amazon connector that pulls orders into Odoo on a schedule, matches Amazon offers to Odoo products by SKU, applies your configured taxes, and handles both FBA and FBM fulfillment. Per Odoo's Amazon Connector feature page, it covers eight marketplaces: US, Canada and Mexico in North America, plus France, UK, Germany, Italy, Spain and the Netherlands in Europe.
• eBay. Odoo's published eBay connector documentation that I could find covers versions 14 to 17. Users on Odoo's own forum report that the eBay connector was dropped from version 18 because of low adoption. That is a user report, not an official announcement, so confirm it against your exact version before you plan around it.
• Everything else (listing creation at scale, settlement and fee accounting, returns, other marketplaces) is where native connectors usually stop and integration projects begin.

The native Amazon and eBay connectors have historically been Odoo Enterprise apps, not Community. If you run self-hosted Community, plan on a third-party module or a custom connector from the start, and verify on your version before you commit.

Which integration route should you choose?

There are four realistic ways to connect Odoo to Amazon and eBay. They differ less in features than in who owns the failure modes when an API changes.

The practical rule: the more your process looks like the vendor's default (orders in, delivery confirmation out), the less custom code you should accept. Every deviation, such as bundled SKUs, split warehouses, or marketplace-specific tax handling, pushes you toward the last two rows.

What does the native Odoo Amazon connector actually cover?

Based on Odoo's own feature description, the connector covers the order-to-delivery loop:

• Scheduled synchronization of Amazon orders into Odoo sales orders.
• Offer-to-product matching by SKU reference, so a clean SKU strategy is a precondition, not an optional extra.
• FBA: stock moves are triggered automatically so Odoo inventory reflects what Amazon ships from its own warehouses.
• FBM: delivery confirmations go back to Amazon, with full or partial shipments handled through backorders.
• Taxes applied to synchronized orders, invoice generation (single or batch), payment registration, and sales reporting.

Odoo's page does not spell out Enterprise requirements, hosting constraints or limitations, so treat those as questions to test during a pilot, not assumptions. These are the checks that decide whether the standard flow is enough:

1. Does stock level in Odoo get pushed back to Amazon listings for your fulfillment model, or only orders pulled in?
2. Can you create or edit listings from Odoo, or only match to listings that already exist?
3. How do Amazon fees, refunds and payouts reach your accounting? Orders and invoices are not the same as settlements.
4. What happens to an order whose SKU has no Odoo match: error queue, silent skip, or auto-created product?

Run those four against a sandbox database with a handful of real orders before you decide the native connector is enough.

What are your eBay options if Odoo no longer ships a connector?

If you are on version 17 or earlier with Enterprise, the official eBay connector exists and is documented. On newer versions you have three paths:

• Third-party app store module. eBay modules are listed for recent Odoo versions. Judge them on selection criteria, not star ratings: when it was last updated for your exact Odoo version, whether it uses eBay's current APIs rather than deprecated ones, whether source is readable, the license, and whether the vendor supports upgrades. The forum thread above notes that some users find third-party quality uneven.
• Middleware. Reasonable if eBay is one of many channels and you do not want to own the code.
• Custom connector. The right call when eBay order handling has to fit unusual rules, such as variation listings mapped to Odoo variants, multi-warehouse allocation, or business-to-business tax handling.

Whichever you pick, do not stay on an old Odoo version purely to keep an old connector. Connector maintenance is cheaper than a frozen ERP.

What data has to sync between Odoo, Amazon and eBay?

Most integration failures are mapping failures, not API failures. Decide the direction and the owner of each object before writing or configuring anything.

The row that quietly breaks finance teams is the fifth: importing orders gives you sales, but only marketplace settlement data tells you what was actually deducted and paid out.

What are the common pitfalls in an Odoo marketplace integration?

Duplicate orders from retries

Marketplace APIs time out and your job retries. Without an idempotency check you import the same order twice. The cheapest defense is storing the marketplace order id with the channel prefix and refusing to create when it already exists:

def import_order(env, channel, external_id, vals):
    ref = '%s:%s' % (channel, external_id)
    Order = env['sale.order']
    existing = Order.search([('client_order_ref', '=', ref)], limit=1)
    if existing:
        return existing
    vals['client_order_ref'] = ref
    return Order.create(vals)

In production, back this with a database-level unique index on your own dedicated field rather than relying on the search alone, since two workers can both pass the search before either creates.

One SKU for FBA and FBM

If the same SKU is fulfilled both by Amazon and by you, give FBA its own stock location in Odoo. Otherwise Odoo's on-hand quantity includes stock you cannot touch, and your FBM listing oversells.

Rate limits and queues

Marketplace APIs throttle. Design synchronization as queued jobs with backoff, not as a loop inside an HTTP request or a single scheduled action that fails entirely on one bad record.

Tax and invoicing assumptions

Marketplace orders arrive with tax handling that depends on the destination and on whether the marketplace collects it. Confirm with your accountant which orders need Odoo invoices and which are covered by the marketplace, before automating invoice generation.

Credentials and authorization

Amazon and eBay both use OAuth-style authorization with token expiry. Monitor authorization health, since an expired token looks like "no new orders" and can go unnoticed for days.

Which setup fits your business?

If your case lands in the last three rows, an Odoo development and integration service is usually cheaper than discovering the gaps after go-live. Either way, start by writing the object-by-object mapping from the previous section.

How do you roll out an Odoo marketplace integration safely?

1. Clean SKUs first. Export your marketplace listings and Odoo products, match them by SKU, and fix mismatches before connecting anything.
2. Use a staging database and connect a single marketplace account.
3. Import a bounded window of orders and compare totals against the marketplace's own reports.
4. Test the awkward cases: partial shipment, cancellation, refund, an unknown SKU.
5. Go live with one marketplace, watch for a week, then add the next.
6. Set monitoring: alert on failed jobs, expired authorization, and zero orders imported over an unusual period.

Teams that connect everything at once cannot tell which channel caused a stock discrepancy. One marketplace at a time keeps every problem attributable.

Need Odoo connected to Amazon and eBay?

If you would rather not own the integration code yourself, Netalith builds and maintains marketplace connections. See the marketplace integration service for Amazon SP-API and eBay work, and request a quote priced to your scope.