Salsify Blocked Product Fix List

Paste a Salsify product export and this tool tells you exactly why each item is blocked from a channel — which required attribute is missing, which value fails a validation rule, and which records are ready to publish. It turns a wall of Salsify blocked products into a prioritized, plain-language fix list you can work through in order.

What it checks

The tool reads the readiness and validation columns Salsify produces on an export and reconstructs, per record, what is keeping a product from going live. It surfaces:

• Missing required attributes — fields a channel marks as mandatory (for example a UNSPSC category, a net weight on a CPG case pack, or a finish on a furniture SKU) that are empty or whitespace-only.
• Failed validation rules — values that exist but break a constraint: a GTIN that fails its check digit, a price below MAP, a string longer than a marketplace title limit, or an enum value that is not on the channel’s accepted list.
• Format and unit mismatches — dimensions in inches where the channel expects centimeters, a date in the wrong pattern, or a unit of measure that does not map to a UNECE Rec 20 code.
• Digital-asset gaps — records flagged as blocked because a primary image, spec sheet, or required asset role is absent or below a minimum resolution.
• Readiness by channel — a per-channel breakdown so you can see that an MRO fastener is publish-ready for one retailer but blocked for another that demands an extra compliance attribute.
• A prioritized fix list — records grouped by the single change that unblocks the most SKUs, so you fix the highest-leverage issue first instead of editing one product at a time.

How the blocked-products logic works

Salsify computes readiness by evaluating each product against a channel’s requirement set: required attributes, allowed values, format rules, and asset roles. When a product fails any rule for a target channel, Salsify marks it blocked and records the reason in the export. This tool parses those reasons, normalizes them into a consistent vocabulary, and rolls them up so patterns become obvious — for example, that 80% of an industrial-distribution import is blocked on one empty country_of_origin field rather than on hundreds of unrelated problems.

Treat the output as a worklist, not a guarantee: it reflects the rules present in your export at the moment you ran it. Channel requirements change, so re-run after you re-sync Salsify with the latest channel mappings. The same triage logic that fixes a Salsify backlog applies to any syndication target — see the related resources below for the durable fix.

Related resources

FAQ

Why are my products blocked in Salsify? +

A product is blocked when it fails at least one rule in a target channel’s requirement set — a missing required attribute, a value that breaks a validation rule, a format or unit mismatch, or a missing digital asset. Salsify records the specific reason on the export; this tool groups those reasons so you can see whether you have one systemic gap or many unrelated ones.

How do I find every product that is blocked at once? +

Export the relevant records with their readiness and validation columns from Salsify, then paste the file here. The tool lists every blocked record, the reason for each, and a count of how many SKUs share the same root cause — so a 5,000-row furniture import becomes a short list of fixes rather than 5,000 individual edits.

What is the fastest way to unblock the most products? +

Fix the most common root cause first. Because the tool groups records by the single change that unblocks the largest number of SKUs, you can clear, for example, one missing country_of_origin value across an entire MRO range before touching anything else, then move to the next-largest group.

Is my catalog data uploaded anywhere? +

No. The tool runs entirely in your browser. Your Salsify export is parsed locally in JavaScript and never sent to a server, which is why there is no login and no file-size limit.

Will this fix the blocked products for me? +

This tool diagnoses and prioritizes; it does not edit your Salsify records. It tells you exactly what to change. To fill missing attributes at scale with sourced, validated values and write them back, you need an enrichment layer — that is what Claro is built for.