Mirakl

Mirakl integration

Home/Integrations/Mirakl integration/Product listings

How do you prepare product listings for each Mirakl retailer?

Quick answer

Every Mirakl-powered marketplace sets its own category tree, required attributes, allowed values, and image rules, so Mirakl product listings that work on one retailer usually need mapping before the next. Acenda keeps one master product record, maps it to each retailer's requirements, checks listings before submission, and shows item-level errors when a retailer rejects one.

See the Mirakl-powered marketplaces Acenda connects.

Last reviewed: October 8, 2026 · Based on retailers' public information and Acenda's integration work.

Book a Demo

Set by each retailer

Category tree, required attributes, allowed values, image rules

Kept once in Acenda

Master SKU, UPC/GTIN, core description, specs

Example retailer rules

Macy's: specific color and size naming · Lowe's: GS1 UPC, Prop 65 declaration, front-facing image

When a listing is refused

Item-level error tied to the SKU and field

What changes from one Mirakl retailer to the next?

Every Mirakl-powered marketplace sets its own category tree, required attributes, allowed values, and image rules. A listing that passed on one retailer usually needs mapping before it will pass on the next.

Macy's requires specific color and size naming. Lowe's asks for a GS1 UPC, a Prop 65 declaration, a front-facing image, and its category templates. Those are examples, not a shared checklist.

Manage one product catalog in Acenda and publish it to multiple Mirakl-powered marketplaces, including Macy's, Nordstrom, Kohl's, Lowe's and more. Acenda adapts your listings to each retailer's category and attribute requirements, and keeps inventory, pricing, orders and shipping in sync from one place.

How does a master record differ from a channel listing?

Keep your internal product record — master SKU, UPC/GTIN, core description, universal specs — separate from the listing each retailer receives. Acenda stores the fact once and applies mapping rules per destination.

Illustrative example

Your internal PIM names a color attribute “Warm Oak”. Retailer A requires selecting “Oak” from a controlled dropdown, while Retailer B requires a broad color category (“Brown”) plus a secondary finish field (“Oak Wood”). Acenda stores the fact once and applies mapping rules per destination.

What should you check before you submit?

Check the listing against that retailer's rules before you send it. Acenda checks listings before submission.

Check	What to verify
Product identity	Are GTINs/UPCs valid, unique, and correctly assigned to single sellable units?
Taxonomy	Is the item mapped to the exact leaf category in the retailer's active schema?
Attribute completeness	Are all mandatory fields populated with accepted picklist values?
Variant structure	Are parent-child variation axes (size, color) cleanly defined with distinct child values?
Media assets	Do image URLs meet minimum resolution, background, and slot-count rules?

What's the difference between submitted, processed, and published?

Submitted means the retailer accepted the file format. Processed means the retailer's checks finished without attribute or GTIN errors. Published means the product is live on the retailer's storefront and a shopper can buy it.

01

Submitted

The data was formatted correctly and accepted by the retailer's endpoint.

02

Processed

The retailer's validation finished without attribute or GTIN errors.

03

Published

The product is live and purchasable on the retailer's storefront.

What happens when a retailer rejects a listing?

Acenda shows the retailer's error for the specific SKU and field. Correct the product data or the mapping, then resubmit.

For one retailer's rules in depth, see Macy's product attribution and Macy's size and color variants.

Mirakl product listings FAQ

Can one product record feed every Mirakl retailer?

Yes, as the source. Acenda keeps one master record and maps it to each retailer's categories, attributes, and allowed values, so the listing each retailer receives fits its own rules.

Why do Mirakl retailers reject listings?

Common causes are a missing required attribute, a value that isn't on the retailer's allowed list, a product mapped to the wrong category, and images that don't meet the retailer's rules. Requirements differ by retailer.

How do I fix a rejected Mirakl listing?

Acenda shows the retailer's error for the specific SKU and field. Correct the product data or the mapping, then resubmit.

Keep reading

Mirakl-powered marketplacesWhich retailers these listings are going to.Selling on multiple Mirakl marketplacesWhat carries over, and what you remap per retailer.Inventory and offersHow price and quantity publish after the listing is in.Launching a new Mirakl marketplaceMap a small assortment before you turn a channel on.Macy's product attributionOne retailer's attribute rules, on their own page.

Get listings ready for each retailer.

Book a Demo

Book a demo.