✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WooCommerce Mirakl Connector: marketplace offers & orders as tables

Read directly from the connector's offer and order postmeta alongside wc_orders. Sort by marketplace, filter by sync status, and inline-edit stock or price without paging through each product.

♾️ Lifetime License available

SleekView table view for WooCommerce Mirakl Connector

See every marketplace offer and order in one place

The WooCommerce Mirakl Connector pushes products to Mirakl-powered marketplaces (Carrefour, Decathlon, Best Buy) and pulls orders back. The stock WooCommerce screens show the local product posts and wc_orders, but the connector's sync status, offer ID, marketplace SKU, and last-error string live in postmeta keys like _mirakl_offer_id, _mirakl_sync_status, and _mirakl_last_error. None of those show up as columns in the default lists.

SleekView reads those connector meta keys directly and exposes them as first-class columns next to your normal product and order fields. A merchandising view can show _mirakl_offer_id, marketplace, price, stock, and sync status side by side. A fulfilment view joins wc_orders with _mirakl_order_id so marketplace orders are flagged distinctly from direct-channel orders, with shipment status visible inline.

Inline edits route through WooCommerce's CRUD layer where supported, so price or stock changes still fire the connector's save_post and product-update hooks that schedule the next Mirakl push. Re-trigger a failed sync by flipping _mirakl_sync_status back to pending across forty rows in one pass, instead of opening each product to fix one failed offer at a time.

Workflow

Compose views across products, connector meta, and orders

1

Pick a source

Choose product posts for merchandising views, or wc_orders for marketplace order workflows. SleekView detects HPOS automatically and switches schemas without config changes.
2

Add connector meta columns

Pick _mirakl_offer_id, _mirakl_sync_status, _mirakl_last_error, and any custom marketplace meta keys from the column picker. The picker only lists meta keys actually present in your data.
3

Save and scope per role

Each saved view is gated by WordPress capability. Merchandisers see offer-focused columns, support sees order-focused columns, finance sees totals and adjustments. One config per workflow.
4

Edit inline or bulk-retry

Edit price, stock, or sync status right in the row. The connector's product save hook fires for each change, so the next scheduled Mirakl push includes the updates without manual intervention.

Sample columns

A typical Mirakl offers view

SleekView joins product posts with connector postmeta so offer ID, marketplace, and sync status sit next to price and stock.
Source: wp_posts (post_type=product) + wp_postmeta + wp_wc_orders
SKU Marketplace Offer ID Price Stock Sync status
SKU-2041 Carrefour MK-88241 €49.00 12 Synced
SKU-2042 Decathlon MK-88242 €34.50 0 Pending
SKU-2043 Carrefour MK-88243 €129.00 4 Rejected
SKU-2044 Best Buy MK-88244 $72.00 23 Synced

Comparison

Default WooCommerce Mirakl Connector admin vs SleekView

Default WooCommerce Mirakl Connector admin

  • Connector status lives in postmeta and isn't surfaced in the product list
  • No combined view of marketplace, offer ID, and sync status per product
  • Failed offer sync requires opening each product and reading _mirakl_last_error
  • Marketplace orders look identical to direct orders in wc_orders without a distinguishing column
  • No way to bulk-retry rejected offers across many products at once

SleekView

  • Surface _mirakl_offer_id, marketplace, and sync status as first-class columns
  • Join product posts with wc_orders filtered by _mirakl_order_id
  • Bulk-flip _mirakl_sync_status back to pending to retry failed offers
  • Save per-marketplace filtered views (e.g. "Carrefour rejected")
  • Switch the same data between table and kanban grouped by sync status

Features

What SleekView gives you for WooCommerce Mirakl Connector

Marketplace columns alongside core product fields

Build a merchandising view with SKU, price, stock, marketplace, and _mirakl_offer_id in one row. Each view picks its own connector meta keys from a list scanned from your actual postmeta.

Bulk-retry failed offer sync

Filter by _mirakl_sync_status equal to rejected, flip the column inline to pending across the whole filtered set, and the connector's scheduled push picks them up on the next cycle.

Marketplace versus direct-channel filters

Show only orders where _mirakl_order_id is set, grouped by marketplace. Save that filter as a fulfilment view so marketplace SLAs never get mixed up with direct-channel orders.

Audience

Who uses SleekView for WooCommerce Mirakl Connector

Marketplace merchandisers

See SKU, marketplace, offer ID, price, and stock in one table. Update price or stock inline and the connector schedules the next Mirakl push automatically through the product save hook.

Marketplace support

Filter orders by _mirakl_order_id and customer email, see marketplace name and shipment status inline. No need to open each order to find which channel it came from.

Channel managers

Compare offers across Carrefour, Decathlon, and Best Buy side by side. Sort rejected offers by _mirakl_last_error and route them to the right merchandiser without exporting.

The bigger picture

Why marketplace operations need joined product and order views

Selling on Mirakl-powered marketplaces means running two product catalogues at once: the local WooCommerce catalogue and the per-marketplace offer. Stock, price, and status need to stay in sync across both, and when a marketplace rejects an offer the merchandiser needs to see why, fix it, and retry. The default WooCommerce product list doesn't surface any of that, because connector data lives in postmeta rather than in dedicated columns.

SleekView pulls those meta keys into first-class columns, so the marketplace state is visible at a glance instead of hidden one product deep. Marketplace orders flow back into wc_orders with a _mirakl_order_id, and fulfilment teams need to handle those distinctly from direct-channel orders because the SLAs and labelling rules differ. A joined view filtering by that meta key keeps marketplace SLAs from getting mixed into the general queue.

Finance and channel managers benefit too, because a saved view of rejected offers grouped by marketplace replaces a fortnightly CSV export. None of this requires patching the connector, it is all just reading meta that the connector already writes.

Questions

Common questions about SleekView for WooCommerce Mirakl Connector

It reads postmeta keys prefixed with _mirakl_ on product posts, and joins wc_orders where the connector has set _mirakl_order_id. The agent UI scans your installation and lists only meta keys actually in use, so you pick real keys instead of guessing names.

 

Yes. SleekView reads wc_orders and joins the connector's _mirakl_order_id stored in wc_orders_meta when HPOS is enabled. On legacy stores it falls back to shop_order posts and postmeta, no config changes required.

 

Yes. Filter by _mirakl_sync_status equal to rejected or error, then inline-edit the status back to pending across the whole filtered set. The connector's scheduled job picks them up on its next push cycle.

 

Yes. Price, stock, and status edits go through WooCommerce's CRUD layer, so woocommerce_update_product and save_post_product still fire. The connector hooks those events and schedules the next Mirakl push as normal.

 

Yes. Group or filter by the meta key that stores the marketplace identifier (typically _mirakl_marketplace or per-marketplace offer ID keys). Save each marketplace view separately and gate access by WordPress capability.

 

Yes. Any postmeta key is selectable as a column. Custom keys added by your team or by other extensions show up in the picker scoped to keys actually present in your postmeta table.

 

SleekView paginates server-side with indexed lookups on post_type and joined postmeta. Aggregate columns are opt-in per view so heavy joins only run when explicitly enabled, keeping the offer list snappy at scale.

 

Yes. Any saved view exports to CSV with the visible columns, including connector meta. Useful for sending merchandising reports to marketplace managers without spinning up a separate reporting tool.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView