Enriched canonical records with sources, confidence, and review states
Enriched canonical records with sources, confidence, and review states.
Upload the rows that are blocking launch: EAN, SKU, title, price, supplier copy, and whatever fields you have. Central returns verified product records with missing specs, source trails, confidence, review states, product-page copy, schema, and channel-ready export fields.
3 products enriched free · 40+ specs where supported · 15+ sources where discovery runs · confidence on every fact
The team can write a description. The slower work is proving what the product actually is.
Supplier rows often arrive with a title, an EAN, a price, and one paragraph. The launch checklist wants dimensions, materials, compatibility, included items, care guidance, product type, channel attributes, and structured data. When those facts are missing or contradictory, every SKU turns into a small research project.
Central starts with the rows you already have. It finds missing facts, checks source agreement, and turns each SKU into a record your team can review instead of a blank page your team has to research from scratch.
product URL list, or export from the current catalog system.
obvious variants, existing fields, and missing launch-critical attributes.
then Central compares candidate values and assigns confidence.
weak claims move into review.
keeps merchant values, or leaves claims hidden.
schema, review queues, and supported channel or custom CSV/XML/JSON feed previews.
SKU-1842, EAN, short title, price, supplier paragraph, one image. Unknown whether the "dishwasher safe" claim is supported. No structured data or channel-ready fields.
Source list with manufacturer page, supplier PDF, retailer listing, and merchant value. Claim marked Needs source until source agreement or merchant authority is available. Confidence tracked per field and output readiness shown.
Verified product type, dimensions, material, compatibility, included items, care guidance, and channel attributes. Product-page description excludes unsupported care claim or marks it for review. Schema.org/JSON-LD, product FAQ candidates, Google fields, and custom feed preview.
Enriched canonical records with sources, confidence, and review states.
Product-page copy written from verified facts, not supplier filler.
FAQ candidates and Smart Negatives for buyer questions and limitations.
x-central metadata for AI-readable product dataSchema.org/JSON-LD plus x-central metadata for AI-readable product data.
Supported channel outputs and custom CSV/XML/JSON exports where the destination can consume them.
Review queues for conflicts, missing evidence, and merchant decisions.
No. Start with the fields you have. Central should preserve identifiers, read available product context, and show missing or unmapped fields for review.
No. Unsupported claims stay hidden or move into review until a source or merchant decision supports them.
Yes. Lean teams can use Central as the product content workflow. Established teams can use it beside a PIM, ERP, feed tool, or commerce platform.
Full enrichment is 50 tokens per SKU. Simple enrichment is 20 tokens per SKU. Use the token calculator when you know the backlog size.