Contentserv Must-Attribute Check
Check Contentserv mandatory attributes before import. Paste or upload your export and see which required fields are missing, per product. Runs in your browser.
When a Contentserv import or channel publish fails, the cause is almost always a record that is missing a required field. This check reads your export and tells you which Contentserv mandatory attributes are empty, on which products, before the platform rejects them.
Contentserv Must-Attribute Check
The interactive version of this tool is coming soon. It will run entirely in your browser — no login, no upload limits.
Planned tool: contentserv mandatory attributes
Need this now? Talk to ClaroWhat it checks
Paste a Contentserv attribute export (CSV or Excel) plus your list of required attribute keys, and the tool reports, row by row:
- Missing mandatory values — products where a required attribute is blank, whitespace-only, or contains a placeholder like
N/A,TBD, or0. - Per-attribute fill rate — what percentage of products actually carry each required attribute, so you can see whether the gap is one bad supplier file or a structural hole.
- Inheritance blind spots — values that look present at the family or master level but are empty on the variant, which is where most channel rejections originate.
- Locale gaps — required fields populated in one language but missing in another, flagged separately so a single-market check does not give false confidence.
- Type mismatches — a number expected but text supplied, an enumeration value outside the allowed list, or a unit field with no unit.
- A clean fix list — every offending product key and the exact attributes it still needs, exportable so you can hand it to a supplier or a data-entry queue.
How it works with Contentserv mandatory attributes
Contentserv enforces completeness through attribute definitions and validation rules: an attribute can be marked required, scoped to a language or channel, and constrained to a data type or controlled value list. A product only becomes publishable when every applicable rule passes. The problem is that the platform usually surfaces failures one record at a time, deep in the workflow, after you have already committed an import.
This tool front-runs that validation. You supply the same set of required keys your Contentserv instance enforces, and it evaluates your raw export against them in bulk.
- 1Load your exportPaste or upload the CSV or Excel file you pulled from Contentserv, including the attribute columns and a product identifier.
- 2Declare what is mandatoryList the required attribute keys, optionally per language or channel, to mirror your Contentserv validation rules.
- 3Read the gap reportSee pass/fail per product, fill rate per attribute, and a downloadable list of exactly what is missing where.
A pre-import check is a triage tool, not a data-quality program. It tells you which records are blocked today; it does not fill the gaps, reconcile conflicting supplier values, or keep records compliant as your attribute model evolves. For that, completeness has to be enforced against a canonical record rather than re-checked on every file. Claro maintains that canonical product-data layer, resolving identity across suppliers and writing validated, provenance-tracked attributes back into your PIM so required fields stay populated by default.
Related resources
Playbook
Map Supplier Attributes to Your Schema
Turn inconsistent supplier columns into the required keys your PIM expects, the step before any must-attribute check.
Guide
Supplier Onboarding Checklist for Distributors
The full sequence for taking a new supplier range live, with mandatory-field validation as a gate.
Glossary
What Is Schema Mapping?
Why supplier fields and your required attributes rarely line up, and how mapping closes the gap.
Glossary
What Is a PIM?
How product information managers like Contentserv model attributes, families, and validation rules.
Tool
CSV Encoding & Delimiter Fixer
Clean a broken export so it parses correctly before you run the must-attribute check.
FAQ
What are mandatory attributes in Contentserv?
Mandatory attributes are fields that Contentserv requires before a product is considered complete and publishable. They are defined on the attribute itself and can be scoped to a specific language, channel, or product type. A record that leaves any applicable required attribute empty will fail validation and cannot be syndicated to that channel.
Why does my Contentserv import say products are incomplete?
The most common reason is that one or more required attributes are blank on the product or its variants, often because the supplier file did not include that column or used a placeholder value. Inheritance can hide this: a value present at the family level may not exist on the individual variant the channel actually publishes. Running a bulk check before import shows every blocked record at once instead of one at a time.
Can I check mandatory attributes without uploading my catalog anywhere?
Yes. This tool runs entirely in your browser, so your export is parsed locally and never sent to a server. That makes it safe to check files containing unreleased pricing, draft specifications, or confidential supplier data without waiting for an upload-approval process.
Does a placeholder like N/A or 0 count as a filled attribute?
In strict Contentserv validation a non-empty value usually passes the required-field rule even if it is meaningless, which lets bad data slip through. This check flags common placeholders such as N/A, TBD, and standalone 0 as effectively missing so you catch records that are technically populated but practically useless before they reach a channel.
How do I keep required attributes populated over time?
A pre-import check fixes the records in front of you today, but new supplier files reintroduce the same gaps. Lasting completeness comes from enforcing required values against a canonical product record that resolves the same item across suppliers and writes validated attributes back into the PIM, so mandatory fields are filled before an import is ever attempted.