Mirakl Connector FAQs

These frequently asked questions cover the most common setup and synchronization topics for the Odoo Mirakl Connector. For a full feature list and sync matrix (scheduled jobs, manual operations), see Mirakl Connector Features.

Getting Started

Is this application compatible with both Odoo Enterprise and Community editions?

Yes. Fully compatible with Odoo Enterprise (On-premise and Odoo.SH) and Odoo Community. Not compatible with Odoo Online (SaaS) as it does not support third-party apps.

How do I connect my Odoo database to my Mirakl Seller Portal?

Mirakl uses secure API Keys (not OAuth) to connect external systems. To connect:

Generate an API Key from your Mirakl Seller Portal.
Enter this API Key, your Shop ID, and the Mirakl Marketplace URL into your Odoo instance configuration.
Click Test Connection to verify the credentials.

Step-by-step instance creation: Configure Mirakl Marketplace.

How do I test that my Mirakl connection is working?

Open your Mirakl instance record and click the Test Connection button. A confirmation message indicates the API Key, Shop ID, and Marketplace URL are valid.

Can I connect multiple Mirakl marketplaces to one Odoo database?

Yes. The connector supports multiple instances — connect as many Mirakl marketplaces or shops as needed to a single Odoo database. Each instance maintains its own API credentials, warehouse, pricelist, scheduled actions, workflow configuration, and order status filters.

Master Data

Why do I need to import "Master Data" before syncing orders or products?

Mirakl uses internal codes for routing shipments and classifying items. Importing Master Data pulls Mirakl’s Logistic Classes, Shipping Zones, Channels, Carriers, Offer States, and Product Categories into Odoo. The connector needs this foundational data mapped so it can correctly link product listings, resolve carriers when importing orders, and avoid validation errors from the marketplace.

Details: Import Mirakl Master Data In Odoo.

Do I need to re-import Master Data if I change something in Mirakl?

Yes. If you add a new shipping zone, configure a new carrier, or change logistic classes in your Mirakl Seller Portal, run the Import Master Data operation manually to keep Odoo in sync.

Products & Listings

Can I create brand new products or export unlisted offers/products directly to Mirakl from Odoo?

No. The connector does not support the creation of new offers/products directly from Odoo to Mirakl. To sync your catalog, first stage your products in the Mirakl Seller Portal. Once listed on the marketplace, run the Import Listings/Offers operation in Odoo to link them via their SKUs. Odoo can then push continuous stock updates to those existing listings.

How are products matched between Mirakl and Odoo?

Products are matched by SKU. When importing a listing, the connector searches for an existing Odoo product with the same SKU. If no match is found and Create Product If Not Found is enabled on the instance, a new Odoo product is automatically created from the Mirakl offer/product data.

Are product images and variant attributes imported from Mirakl?

No. The connector imports listing metadata (SKU, description, product references, offer state, logistic class, shipping zone, channel) but does not import product images or variant attribute trees. Manage these directly in Odoo.

How does price sync work for listings?

When importing listings, enable Update Price? to update the listing item price in Odoo. Prices are stored as fixed-price items on the instance’s configured pricelist. Currency conversion is applied automatically if the pricelist currency differs from the company currency.

Orders

How do orders get into Odoo?

Orders arrive in Odoo via automatic background jobs (the scheduled “Import Order” cron runs every 15 minutes by default) or manual imports from the Operations menu. See Import Mirakl Orders In Odoo.

Can I limit which orders are imported?

Yes. Orders can be filtered by:

Order Status filter on the instance (defaults to Shipping; configurable under the Orders tab).
Date Range in the manual import wizard, with a Based On option to filter by Create Date or Update Date.
Marketplace Order ID field to import specific orders by their Mirakl IDs (bypasses date filtering and the queue).

How are taxes handled for Mirakl orders?

Taxes are applied based on the instance’s Tax System setting:

Default: Uses Odoo product taxes only; ignores Mirakl tax lines.
According to Marketplace: Uses Mirakl tax amounts; auto-creates missing taxes.
Marketplace with Fiscal Position: Same as above, with Odoo fiscal position mapping applied.

How does the Financial Workflow Configuration work?

The connector matches each imported order to a Financial Workflow Configuration record using Payment Type and Financial Status (Paid / Unpaid / Any). The matched workflow defines the order processing steps (auto-confirm, auto-invoice, auto-payment) and the payment term assigned to the customer. If no matching workflow is found, the order import fails with a clear error in the queue logs.

See Workflow Configurations and Configure Marketplace Order Workflow.

How are customer details and company contacts handled during order import?

The connector extracts billing and shipping addresses into separate Odoo partner records (invoice and delivery types). If the Create Company Contact? setting is enabled and the customer provided a company name, a parent company contact is also created and the billing/shipping contacts are linked to it.

What happens if an order is canceled on the Mirakl marketplace?

The connector detects when an imported order’s state becomes Canceled on Mirakl. During the next sync, it cancels the corresponding Odoo Sale Order and its delivery pickings, and posts the Mirakl cancellation reason code and label in the order chatter.

How does Odoo know which Delivery Method (Carrier) to use when importing an order?

The connector matches Mirakl’s shipping method name against existing Odoo delivery methods, filtered by the order’s destination country first (by exact name or by the Mirakl Shipping Method Name configured on the carrier). If no country-specific match is found, the same lookup is repeated without the country restriction. If still nothing matches, a new delivery method is automatically created so the order import does not block.

Inventory & Tracking

How does inventory synchronize between Odoo and Mirakl?

Stock is exported from Odoo to Mirakl either via the scheduled “Export Product’s Stock to Mirakl” cron (every 25 minutes by default) or manually via the Export Inventory operation. The exported quantity is calculated from the instance’s configured Warehouse and the Stock Based On setting (Quantity On Hand, Free To Use, or Forecasted).

Note: Only products marked as Storable in Odoo are included in the export.

When I validate a delivery in Odoo, how is tracking updated in Mirakl?

Once a delivery order reaches the Done state, the connector sends the tracking number and carrier information to Mirakl and marks the order as SHIPPED on the marketplace. You can also trigger this manually from the delivery using the Update in Marketplace button, or in bulk via the Export Tracking Details operation. The scheduled “Export Order Status/Tracking Information” cron runs every 25 minutes by default.

Details: Mirakl Update Order Status from Odoo.

What if my delivery carrier is not linked to a Mirakl carrier?

If the Odoo delivery method has a Mirakl Carrier assigned, the connector sends the matching carrier code to Mirakl. If no Mirakl carrier is linked, a Tracking URL is required on the delivery — without it, the tracking push will fail. Configure carriers under Marketplaces ‣ Mirakl ‣ Shipping & Logistics ‣ Carriers.

Troubleshooting

What should I check if synchronization fails or an order/product is stuck?

The Mirakl connector uses a Queue Job system for bulk imports. If something fails:

Open Marketplaces ‣ Queues ‣ Queues and look for jobs in Failed state.
Click into a failed queue line to view the exact error message.
After fixing the underlying issue (e.g., creating the missing SKU), use the Retry Failed action to reprocess the line.
For tracking export failures, check the picking’s marketplace exception message — the exact error is stored on the delivery order.
Review centralized logs at Marketplaces ‣ Queues ‣ Logs.
For persistent connection errors, verify your API Key is still valid using Test Connection on the instance.