Channel Readiness
Find out from us, not from the marketplace.
Every channel has rules — required attributes, title limits, image sizes, identifier formats, and increasingly, legal fields. Zuduno runs those rules before you submit and tells you which attribute failed, on which rule, for which channel.
The failure classes
Why listings get rejected.
Most listing failures fall into a small set of operational patterns. Zuduno makes each pattern visible as a specific check and a clear action.
- 01Missing required attributeRequired for the product type on that channel, and the product type is the channel's, not yours.
- 02Identifier mismatchThe GTIN on the listing does not match the catalogue record, or its check digit is wrong.
- 03Title or bullet over the limit255 characters here, 200 there, 120 on the third — and truncation changes the meaning.
- 04Image fails the channel's ruleMinimum dimension, background, or the ratio the category requires.
- 05A compliance field the channel now enforcesGPSR responsible person, EPR registration, hazardous-goods flags. This is the row that grew in 2026.
How a check works
Three steps, and the middle one is the product.
Rule sets per channel
Each channel's requirements are encoded as rules and versioned, so a rule change is a diff rather than a surprise. Rules are data; adding a channel does not mean writing code.
A failing check, shown
The product, the channel, the rule, the attribute, and what would fix it — in one row. Not a percentage score, not a red dot: the sentence a person can act on.
Resolution before submission
Fix it once in the product master and every channel projection is re-checked, because the projections are generated rather than maintained.
- BlocksDEEPR packaging registration number missingLUCID number required before listing · 41 SKUs affected
- BlocksFRGPSR responsible person not setEU economic operator required on the offer · 41 SKUs
- CheckES · es-ESCN code missing on 2 of 6 variantsNeeded per variant for the flat customs duty
- ReadyDE · de-DETitle within channel limit55 / 200 characters
- ReadyAllGTIN present and check-digit valid8412345678904
Before, not after
A check runs against the channel’s rules, and a failure is a task.
Compliance attributes as blocking checks
The rows nobody else checks
- EPR registration number, per market
- GPSR responsible person and contact, per product
- CN / HS code, per variant
- Product Identifiers for low-value consignments — mandatory from 1 November 2026
- Packaging data per market, under PPWR
These are product facts with legal meaning and a market-specific answer. Zuduno models them as readiness rules with an authority, validity window and blocking outcome, rather than free-text attributes that pass because nothing checks them.
Pre-submission validation is not a new category: Salsify, Sales Layer, Akeneo, WISEPIM and inriver all do it. This row is where Zuduno is different.
Per market, not only per channel
A channel is not a country
amazon.de places goods in Germany and in Austria, and the obligations differ. A readiness check that only knows the channel cannot say whether the listing is legal where it will actually be sold.
Zuduno’s rules are resolved over the markets a channel serves, so the answer to “is this ready?” is a per-market answer.
Joined to stock and orders
A listing with no stock is still a failed listing
Readiness in Zuduno reads availability, because a listing that passes every content rule and has nothing behind it will still cost you a cancellation and a metric. The join between the two is the point.
Versus the alternatives
What else could tell you.
| The marketplace's own report | A feed tool | Enterprise PIM readiness | Zuduno | |
|---|---|---|---|---|
| When you find out | after submission | before, format only | before, content only | before submission |
| Names the failing rule | sometimes | yes | yes | yes |
| Compliance fields as blocking checks | no | no | rarely | yes |
| Resolved per market, not only per channel | no | no | no | yes |
| Reads stock | no | no | no | yes |
FAQ
Questions people actually ask
Which channels’ rules exist today?
Rule sets are configured per channel and per market. A rule set describes what a channel requires and checks your catalogue against it; submitting the listing to the channel is the connector’s job, and the connector directory says which of those you can switch on.
Does it fix the listing for me?
No. It tells you exactly what to fix, on which attribute, for which channel. AI review is suggestion-only: nothing writes to your catalogue without a person approving it, and every approval is logged.
Can our business rules be included?
Yes. Rules are configured as data rather than hard-coded into a connector, so channel requirements and company-specific checks can be handled within the same readiness model.
Does it cover Mirakl operators?
Each Mirakl operator is its own channel with its own taxonomy and its own required attributes, and is modelled that way rather than as one generic Mirakl connector. The integrations directory lists them individually.
What about bol, Kaufland, eMAG and Allegro?
The model separates each channel's rule set from the connection that exchanges data with it. That lets readiness work remain consistent across marketplaces while integration scope is evaluated channel by channel.
What changes for you
What checking first changes.
A rejection becomes a task on a list before submission, instead of a suppressed listing found by whoever noticed the sales stop.
Marketplace manager
Readiness checks before submission
When a second country classifies your products differently for EPR, you change one classification rather than a spreadsheet.
Compliance or operations lead
EU compliance attributes as blocking checks
Nobody has to remember which marketplace calls the same field by which name — the rule set does, per channel and per market.
Anyone submitting a listing
Channel dialects and field mapping
Run it against your worst channel.
The one with the rejection history. Your rule sets are configured with the team.