Data Panda brings your Mirakl data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Mirakl is a French SaaS platform founded in Paris in 2012 by Philippe Corrot and Adrien Nussenbaum, both formerly of Rueducommerce. It raised a $555M Series E in September 2021 at a valuation above $3.5 billion. Retailers such as Carrefour, Macy's, Best Buy Canada, Media Markt, Decathlon, H&M and Urban Outfitters run their third-party marketplaces on top of it.
Mirakl is not a storefront. It is the marketplace layer that a retailer bolts onto an existing storefront (Magento, Adobe Commerce, Shopify, SAP, Salesforce Commerce and so on) so the shop can sell third-party inventory next to its own. The platform handles seller onboarding, catalog ingestion per seller, offer management, order routing to the right seller, messaging between buyer and seller, returns, and seller payouts through Mirakl Payout.
The reason a warehouse matters for Mirakl data: the questions a marketplace P&L owner really has live across tables. Take rate per seller, offer freshness by category, order defect rate per seller, return rate per seller and payout reconciliation with the ledger sit in the Offers, Orders and Order Messages tables. Pulling them out is where marketplace performance stops being a monthly export exercise and starts being a report the category manager opens each morning.
Take rate, seller performance and payout reconciliation in one view.
Keep Mirakl in sync with the storefront, PIM, ERP and support desk around it.
Use your marketplace history to spot weak offers, weak sellers and weak categories before the buyer does.
Internal tools on top of Mirakl data for the people who run the marketplace day to day.
A list of concrete reports, automations and AI features we have built on Mirakl data. Pick the one that matches your situation.
Does the commission we recognised match what Mirakl Payout paid out?
Commission per order on the Orders side, joined to the Mirakl Payout cycles and then to the bank entries in the ERP. Flags the sellers and the payout cycles where the reconciliation does not close, so finance stops carrying a floating difference at month-end.
Which sellers are dragging the marketplace score down?
Order defect rate, return rate, cancellation rate and Order Message first-response time composed into a seller scorecard. Ranks the sellers whose behaviour is hurting the storefront's reputation and keeps the category manager on the ones worth a conversation, not a delist.
Where is the catalog thin where the shop has demand?
Search and category-page traffic from the storefront joined to live offer count and offer-to-sale conversion per category. Surfaces the categories where buyers arrive and leave because the coverage is too shallow, so seller recruitment goes where the gap is real.
Take rate, commission recognition and Mirakl Payout reconciled against the ERP ledger, per seller and per cycle. The month-end closes without a spreadsheet matching marketplace commission to the bank feed by hand.
Seller performance, category coverage and 1P versus 3P mix in one view. Category managers walk into a seller conversation with defect rate, return rate and messaging SLA already on the page, not on a to-do for next week.
Offer freshness, onboarding funnel and Order Message SLA in one place. Ops spots the seller whose offers went stale or whose messaging is sliding, before the storefront rating notices.
Enriched product records in Akeneo flow into Mirakl with attributes, translations and media mapped to the marketplace category tree. New SKUs go live as offers without a merchandiser pasting attribute grids into the Mirakl back office, and any change in the PIM propagates to the marketplace listing the same day.
Mirakl sits on top of Magento so the storefront sells own stock and third-party offers side by side. Orders split into 1P and 3P lines, each routed to the right fulfiller, and reporting consolidates 1P revenue from Magento with 3P commission from Mirakl against one customer and one basket.
A Shopify merchant that wants to add third-party sellers bolts Mirakl onto the store. Shopify keeps its 1P orders and customer record, Mirakl manages the 3P seller catalog and payouts, and both streams land in the warehouse so cohort LTV and marketplace take rate live in the same report.
Mirakl Payout cycles flow into Exact Online as vendor payments on each seller's account, with commission revenue booked on the operator side and VAT treatment preserved. Finance closes the month without exporting payout reports and stitching them into the books by hand.
These are the 3 tables we currently pull from Mirakl into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Mirakl data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
No. Mirakl is the marketplace layer, not the storefront. Retailers run Mirakl on top of Magento, Adobe Commerce, Shopify, SAP, Salesforce Commerce and similar platforms so the shop can sell third-party seller offers next to its own. In the warehouse you end up with two linked streams: 1P orders from the storefront and 3P offers, orders and payouts from Mirakl, joined on the same customer.
The Peliqan connector exposes three core tables out of the Mirakl operator API: Offers (one row per seller offer on a SKU, with price, stock and last-update timestamps), Orders (one row per marketplace order with seller, commission and status) and Order Messages (buyer-seller messaging with timestamps for first response and resolution). Together these cover take rate, offer freshness, seller defect rate and messaging SLA.
Commission per order lives in the Orders table, seller payout cycles sit in the Mirakl Payout module, and the bank entries sit in Exact Online, Business Central or whichever ERP holds the ledger. The warehouse joins the three on seller, cycle and amount so the cycles that do not reconcile surface on a single report instead of a month-end spreadsheet.
We review your Mirakl setup and the systems around it. Together we pick the first thing worth building.