Syndigo Retailer Reject Translator

When a retailer or data pool kicks an item back through Syndigo, you get a terse validation code and a row reference, not an explanation. This tool turns a list of Syndigo retailer rejects into plain-language fixes, so a category manager onboarding a new MRO, CPG, furniture, or industrial supplier knows exactly which attribute failed and what a passing value looks like.

Syndigo Retailer Reject Translator

Runs in your browser · no upload

Paste your reject report (CSV/TSV, or one reject message per line), or upload it

Translate rejects Upload a file Try an example Clear

Independent tool, not affiliated with Syndigo or GS1. Syndigo's and retailers' rule-code tables aren't public, so messages are explained by pattern, not by an official code lookup. See how Claro fills and fixes the attributes behind rejects →

What it checks

Paste the reject report or item-level error list you received from Syndigo (or the receiving retailer’s data pool) and the translator groups and explains every failure:

• Message decoding. Reads each reject message, names the GS1 / GDSN attribute it mentions in plain words (netContent becomes Net content), and sorts it into a human-readable cause (missing value, wrong format, out-of-range, invalid code-list entry). Syndigo’s and retailers’ rule-ID tables are not public, so rule IDs are grouped, not looked up.
• Mandatory attribute gaps. Flags required fields that are blank for the target market or category — brand name, net content, GPC brick, country of origin, and similar must-fill attributes.
• Code-list violations. Picks out rejects for values that are not members of the expected GS1 code list (unit of measure, packaging type, allergen codes) and, for units of measure, suggests the nearest valid UN/ECE Rec 20 codes.
• Identifier and check-digit errors. Re-validates every GTIN and GLN in the report with the GS1 check digit, so you can tell a true reject from a transcription typo.
• Unit and dimension consistency. Highlights net content, gross weight, and dimension values that fail range or UOM checks — a frequent reject for furniture and industrial pallet items.
• Severity grouping. Separates hard rejects that block publication from warnings, and counts how many distinct SKUs each error touches so you can fix the highest-impact rules first.

How Syndigo retailer rejects work

Syndigo operates a GDSN-certified data pool. When you publish an item to a retailer, the message is validated against the GS1 GDSN standard plus that retailer’s own community-specific rules. A failure at either layer comes back as a structured rejection referencing a rule or attribute, often using GS1 BMS terminology rather than the field labels you see in your PIM.

That gap is why rejects feel cryptic: the message names the canonical GDSN attribute, while your team thinks in PIM column names. This translator bridges the two. It pattern-matches each message, turns the GDSN attribute name into a readable field name, explains the usual cause and fix, and, for unit-of-measure rejects, suggests valid UN/ECE Rec 20 codes. Where a reject is really a formatting or check-digit issue rather than a content gap, it says so, so you do not re-key data that was already correct.

All processing happens client-side in JavaScript. There is no upload step, no account, and no file-size limit beyond your browser’s memory.

Related resources

FAQ

Why does Syndigo reject my products? +

A rejection means the item failed either a GS1 GDSN standard rule or a retailer’s community-specific rule. The most common reasons are blank mandatory attributes for the target market, values that are not valid code-list entries, invalid GTIN or GLN check digits, and net-content or dimension values that fall outside the allowed range or use the wrong unit of measure.

What is the difference between a GDSN validation error and a retailer reject? +

A GDSN validation error is raised by the standard itself and applies to every recipient — for example, an invalid GTIN. A retailer reject comes from rules a specific retailer adds on top of GDSN, such as requiring an extended description or a particular packaging code. An item can pass GDSN and still be rejected by one retailer’s community rules.

How do I fix a 'value not in code list' reject? +

The attribute expects a member of a GS1 code list, but free text or a non-standard value was sent. Replace the value with the correct code-list entry — for example, a valid UNECE Rec 20 unit of measure or a defined packaging-type code. For units of measure, this tool suggests the nearest UN/ECE Rec 20 codes; for other code lists, check the value against the GS1 code list named in the reject.

Do I need to re-publish every item after fixing rejects? +

Only the items whose attributes changed. Group rejects by rule first: one code-list or mandatory-field fix often clears the same error across hundreds of SKUs at once. Correct the source data, then re-publish the affected subset rather than the whole catalog.

Is this tool affiliated with Syndigo? +

No. It is an independent, free utility that helps you interpret rejection messages. It does not connect to your Syndigo account and processes your report entirely in your browser.