Mirakl as a Channel

Confirm both values come from the correct retailer's seller portal, not from a different retailer's Mirakl instance and not from Mirakl's own website. The Base URL must be the specific HTTPS API endpoint for your retailer (e.g. https://bestbuy.mirakl.net) with no trailing path, and the API Key must belong to your active seller account on that marketplace. Regenerate the API Key in the retailer portal if you are unsure it is still valid.

Check the job logs for the specific Mirakl API error. Common causes: the offer's category or attribute set does not match what the retailer's catalog expects (each retailer defines its own required fields); the SKU is already published under a different offer ID and conflicts; or the marketplace requires seller approval for that product category. Confirm with your retailer account manager that your seller account has permission for the category you are publishing.

Verify the Sync Orders template has Carrier and Tracking Number mapped: both are required for Mirakl to mark an order shipped. Confirm the Sync Orders job has run after the order was fulfilled in Flxpoint (check the last-run timestamp). If the job ran cleanly but tracking still did not appear, check the logs for a silent Mirakl API rejection and open a support ticket with the order number.

Mirakl-powered marketplaces match offers to existing catalog products via EAN, UPC, or a retailer-specific product identifier. If an offer lands on the wrong product page, the identifier in your Flxpoint listing does not match the correct product in the retailer's catalog. Verify the EAN/UPC/SKU matches the exact value in the retailer's Mirakl catalog, and confirm the required identifier format with your retailer account manager.

Run Test Connection to confirm the API Key is still valid: some retailer configurations rotate or expire keys. Confirm the Get Orders job is scheduled and check its last-run timestamp. Verify the order status filter matches the statuses used by that retailer's Mirakl instance (labels vary, e.g. WAITING_ACCEPTANCE vs SHIPPING). If the connection is valid and the job runs without errors but returns nothing, confirm orders exist in the seller portal and that the date-range window covers them.

This means the retailer's Mirakl marketplace domain has a broken DNS/Cloudflare configuration on their end: Cloudflare itself flags the error with owner_action_required: true and retryable: false, meaning retrying the job will not resolve it. This is not a Flxpoint connection issue; the retailer (or whoever manages their Mirakl domain's DNS/Cloudflare setup) needs to fix it before Get Orders can succeed again.

This occurs when the retailer's Mirakl instance accepts the offer import but fails to create the listing due to internal validation errors. Flxpoint now verifies the detailed offer result report from the retailer; if the report indicates the offer was rejected or is still pending, the listing status will update to Failed with a specific reason. If you see a Published status, the offer has been confirmed as successfully created or updated on the retailer's side. For older listings that appear out of sync, trigger a manual Publish Listings job to refresh the status.

Both credentials come from the specific retailer's seller or supplier portal, not from Mirakl's main website. For Best Buy, log into the Best Buy marketplace seller portal and find the API credentials section; for Lowe's, use the Lowe's supplier portal. The Base URL is the API endpoint for that retailer's Mirakl instance (e.g. https://bestbuy.mirakl.net) and the API Key is generated in your seller account settings. Contact your retailer account manager or onboarding team if you cannot locate them.

No: Best Buy and Lowe's each run their own independent Mirakl marketplace with different API endpoints and credentials. You must create a separate Flxpoint channel for each retailer, and each channel has its own connection settings, listing operations and order flows. Products published to one retailer's Mirakl instance are not automatically visible on another's.

The Flxpoint Mirakl channel uses the Mirakl Direct API. Mirakl Connect is a separate app-based layer some retailers offer. Many retailers who use Mirakl Connect still expose a Mirakl Direct API endpoint that Flxpoint can connect to. If your retailer specifically requires Mirakl Connect and does not support a direct API connection, contact Flxpoint support to confirm compatibility before setting up the channel.

The channel supports Sync & Link Listings (sync price, quantity and status to the retailer's Mirakl catalog), Publish Listings (create new offer listings on the marketplace), Get Orders (import orders from the retailer's Mirakl marketplace into Flxpoint), and Sync Orders (push shipment tracking back to the marketplace). Select the processes you need when creating the channel in Flxpoint.

After entering credentials, use the Test Connection button during setup to confirm the API Key and Base URL are valid. Once connected, run each process manually on a small test set before enabling schedules: publish one known-good SKU, import a test order, and trigger a Sync Orders run to confirm tracking reaches the retailer portal. Verify directly in the retailer's Mirakl seller portal that the test listing and tracking appear as expected before turning on full automation.