Centra and Mirakl
Integration Agency & Consultants
Operational pressure usually mounts when marketplace order volume outpaces manual data entry. At scale, the gap between stock levels in Centra and listings on Mirakl leads to overselling and marketplace penalties. We establish Centra as the source of truth for inventory and catalogue data across your marketplaces, protecting revenue by ensuring stock accuracy as orders ramp up. Our approach is shaped by experience managing these specific scaling challenges across high-volume retail environments.
Scoping data truth and channel logic
Integrating Centra and Mirakl enables swift connectivity, enhancing your multi-channel and omnichannel retail strategies. Our expertise ensures seamless system integration. Leverage our consulting and delivery skills to boost operational efficiency and tech stack performance. We provide comprehensive training to support rapid scaling and unified retail strategies.
Solution Design
Our design for the Centra and Mirakl integration treats Centra as the source of truth for global product data and inventory. We typically push inventory updates to Mirakl on a defined schedule to maintain marketplace accuracy. A primary design decision involves the logic for marketplace-specific attributes, ensuring Centra data maps correctly to Mirakl's mandatory category structures.
We manage the trade-off between real-time order imports and batch reconciliation. While immediate order sync improves fulfilment speed, we ensure it does not complicate the consolidation of marketplace fees and taxes. We prioritise reliable order flow into Centra for warehouse processing and manage financial settlement via a scheduled process. This ensures the operations team works from a clean fulfilment queue, while finance closes the month using verified data.
Mapping skus and carrier status codes
Centra acts as the primary e-commerce backend for product information and inventory, with data synchronised to Mirakl for marketplace listings. Centra's External ID is mapped to the Mirakl shop-sku to maintain catalogue truth across channels. To protect against overselling, the integration deconstructs Centra's native bundle structures into individual SKUs at the middleware level before updating Mirakl's price and stock feeds.
Marketplace orders flow from Mirakl into Centra for fulfilment, but the integration must first send a manual or automated 'Accept' status back to Mirakl before any shipping or payment actions occur. Once an order is marked as shipped in Centra, tracking numbers are pushed to the Mirakl shipping_notifications endpoint. This process uses a static mapping table to translate Centra Carrier IDs into the specific carrier-code enums required by Mirakl, ensuring dispatch updates are accepted on the first attempt.
Orchestrating the connection on enterprise middleware
Cogent2 uses IPaaS to streamline Centra and Mirakl integrations, enhancing data flow and connectivity. Benefits include reduced integration time, improved scalability, seamless data synchronization, and simplified management, enabling efficient collaboration and faster deployment of solutions for clients.
Monitoring sync integrity and operational drift
Standard dashboards often mask the underlying operational drift that causes reconciliation debt. We surface the health of the Centra and Mirakl connection by identifying hidden issues like orphaned orders and carrier mapping failures. Our platform monitors the integrity of the data flow, specifically watching for instances where a Centra shipment is created before the Mirakl 'Accept' status is confirmed. By detecting these sequence errors and inventory mismatches early, we prevent small sync failures from compounding into systemic blocks that require manual month-end fixes.
Operational handover for exceptions and manuals
Handover focuses on how your finance, ecommerce, and operations teams run the integration day to day. We define ownership for exception handling, such as when a Mirakl order requires manual intervention due to data errors. Ecommerce teams learn to manage marketplace listing statuses, while ops teams monitor fulfilment syncs.
Documentation is provided as an operational manual rather than a technical archive. It details what to check on a regular schedule to ensure inventory parity and how to interpret alerts from the integration layer. We ensure your team understands the operating model, including the path from a Mirakl sale to a Centra shipment. This approach ensures you maintain control of the system without relying on external support for routine monitoring.
Governance and marketplace rating protection
Post launch, we provide monitoring to ensure your data flows remain stable. We manage technical escalations and monitor for sync failures, letting your team focus on trading. Our support is designed for active marketplace operations, identifying and resolving issues in the order-to-fulfilment chain before they affect your marketplace seller rating.
Common failures
Sequence errors in order acceptance
Operational impact: Mirakl considers an order 'Accepted' only after an explicit acknowledgement. If Centra captures payment or generates a shipment before the integration sends the 'Accept' status back to Mirakl, the marketplace will reject the update as a sequence error. This leaves orders stranded in Mirakl while the warehouse has already processed the goods, creating a mismatch in financial and fulfilment status that requires manual intervention to resolve.
Rejected dispatch due to carrier mismatch
Operational impact: Shipment updates from Centra will fail if the Carrier ID does not match the Mirakl 'Carrier Code' list exactly. When a tracking number is pushed without a valid enum value, Mirakl rejects the notification. Customers are left without tracking details, and the order remains 'Awaiting Shipment' on the marketplace, even if the parcel is already with the courier. This often forces CX teams to manually copy-paste tracking data into the Mirakl back office.
Broken bundle logic
Operational impact: Mirakl does not support Centra's native bundle or kit structures. If the integration attempts to push a Centra bundle SKU directly to a Mirakl price or stock feed, the update will typically fail or result in incorrect inventory levels. This leads to overselling because the marketplace cannot see the component-level stock constraints, forcing the warehouse to cancel orders that the system claimed were available.
Partial refund synchronization
Operational impact: Returns processed in Centra do not always trigger the correct financial reversal in Mirakl, particularly regarding partial refunds. If the integration fails to decrement the correct amount or specific line items within the Mirakl order at the point of the Centra refund, the payout statement will remain incorrect. Finance teams are then left with reconciliation debt that must be cleared manually at month-end.
Frequently asked questions
If Centra is our product master, how do we prevent overselling on Mirakl marketplaces?
Centra should be the single source of truth for inventory, acting as the stock master for Mirakl. The integration must ensure that when an item is sold, on any channel, the inventory level in Centra is updated and then synchronised with Mirakl. This prevents overselling by making sure the stock levels on Mirakl accurately reflect the total available inventory, which protects the customer experience and your seller rating.
What happens if we fail to acknowledge a Mirakl order in Centra quickly enough?
Mirakl enforces a strict 'acceptance' window for new orders; if an order is not acknowledged via the API within this time, it is automatically cancelled. The integration must be designed so that a new Sales Order from Mirakl is accepted almost immediately upon creation in Centra. Failure to do so results in lost sales and can negatively impact your performance metrics on the marketplace.
How do shipping confirmations get from Centra back to the Mirakl marketplace?
When an order is fulfilled in Centra, the integration must send the shipment details back to Mirakl to trigger the 'shipped' status and customer notifications. This requires mapping Centra's 'Shipping Method' to the specific carrier codes recognised by Mirakl, as Mirakl will reject tracking updates with an unrecognised carrier. This is a common failure point that can delay customer communication and the payment process.
Why can't we just handle Mirakl integration manually from Centra?
While manual processing is possible for very low order volumes, it creates significant operational drag and risk as you scale on Mirakl. Teams end up spending hours on manual data entry for product listings, inventory updates, and re-keying Sales Orders between Centra and the marketplace. This frequently leads to stock sync errors causing overselling, or fulfilment delays that harm the customer experience.
Will we get the real customer email address for orders placed on Mirakl?
Not always, as many Mirakl marketplaces use a proxy or anonymised email address to protect customer privacy. When an order from Mirakl creates a customer record in Centra, this proxy address must be used for all transactional communication. This means your operational processes for handling customer service enquiries and sending order updates must be configured to work with these Mirakl-generated email addresses.