Supplier data repair

Fix supplier product data before it reaches the store.

Upload supplier CSVs, product URL lists, PDFs, or GTIN-only rows. Central returns normalized fields, verified missing facts, source/confidence context, review states, and product-page or feed-ready output previews.

Import my products Gather missing facts ↓

3 products enriched free · confidence on every fact · unsupported claims stay hidden · supported channels + custom feeds

Supplier row · repair auditmessy input · verified output
EAN · price · SKUpreserved
grossweight headernormalized
Dimensionsmissing
Compatibility claimneeds source
Feed-ready fieldsready
source + confidence visible→ review output
why it matters

Supplier data is a starting point, not a publishable record

Supplier files are useful because they give you identifiers, prices, variants, and starting descriptions. They are risky because they also arrive with inconsistent headers, missing attributes, duplicated values, untranslated copy, and claims with no visible source.

Central keeps the useful parts and fixes the parts that block publishing. It reads the file, preserves factual invariants such as identifiers and prices, finds missing product facts, verifies what sources support, and separates publishable content from claims that need review.

Central mechanism

Verified facts become reusable outputs.

  • 3 products enriched free
  • confidence on every fact
  • unsupported claims stay hidden
  • supported channels + custom feeds
input / output

What you provide and what comes back

User entersinput
Input
Supplier CSV, XLSX export, product URL list, product PDF, or GTIN/EAN rows.
Input
Messy columns such as descr, colour, pack, grossweight, or unlabeled custom fields.
Input
Supplier claims such as "eco", "compatible", "professional grade", or "waterproof".
Central returnsverified workflow
Output
Clean product records with mapped fields, normalized units, deduplicated attributes, and missing facts filled where verified.
Output
Human-readable field names, mapped attributes, and review notes when a column cannot be interpreted safely.
Output
Claim state: verified, needs source, needs merchant decision, or hidden until verified.
operational map

The supplier-file problems Central should make visible

Problem in the file
Central action
Safer output
Random headers and mixed units.
Maps field names, normalizes units, and keeps original values visible for review.
Product attributes that can feed pages and channels.
Thin descriptions copied across many SKUs.
Builds content from verified facts instead of expanding weak supplier copy.
Product-page copy with unsupported claims removed.
Important category fields missing.
Searches for dimensions, materials, capacity, compatibility, care, warnings, and other category-specific facts.
Source-backed fields with confidence.
Supplier and manufacturer values disagree.
Shows the conflict and lets merchant data win where appropriate.
Review queue instead of silent overwrites.
workflow

Supplier data repair workflow

1

Upload the supplier file or paste product URLs

Upload the supplier file or paste product URLs.

2

Central identifies products

identifiers, variants, existing fields, and obvious gaps.

3

Field names are normalized while original headers remain available for traceability

Field names are normalized while original headers remain available for traceability.

4

Source discovery fills missing facts where supported

flags conflicts.

5

Central generates product-page copy

FAQ candidates, schema, and channel-ready fields from verified values.

6

The team reviews conflicts

approves publishable fields, and exports the repaired catalog.

proof artifact

Proof artifact: messy supplier file to verified record

Raw supplier input

Raw supplier input

EAN, short title, price, grossweight, colour, one paragraph, missing dimensions. Claim: "compatible with all models." Supplier column needs mapping context.

Source/confidence panel

Source/confidence panel

Manufacturer page and supplier PDF agree on dimensions; merchant value kept for price; color label normalized from anthracite to merchant-approved display value. Marked Needs source because no source supports universal compatibility. Marked Needs merchant decision.

Output preview

Output preview

Product type, dimensions, material, color, package weight, description draft, schema fields, and Google-ready attributes. Claim removed from generated description and shown in review queue. Field waits for approval, mapping, or ignore decision.

outputs

Outputs for the team

01

Repaired product records with source trails and confidence

Repaired product records with source trails and confidence.

02

Field mapping notes for messy supplier columns

Field mapping notes for messy supplier columns.

03

Normalized units and values for product pages and feeds

Normalized units and values for product pages and feeds.

04

Product-page descriptions, FAQ candidates, and Smart Negatives from verified facts

Product-page descriptions, FAQ candidates, and Smart Negatives from verified facts.

05

Schema.org/JSON-LD and x-central metadata for AI-readable product data

Schema.org/JSON-LD and x-central metadata for AI-readable product data.

06

Review queue for unsupported claims, conflicts, and merchant decisions

Review queue for unsupported claims, conflicts, and merchant decisions.

FAQ

Questions before you start.

Can Central handle messy column names?

+

Yes. The workflow should map obvious headers, preserve original headers for traceability, and ask for a merchant decision when a column cannot be interpreted safely.

Does Central overwrite supplier data automatically?

+

No. Merchant values can be kept, source conflicts stay visible, and uncertain claims can remain hidden or in review.

Can I use supplier PDFs or URLs?

+

Yes where the workflow supports those inputs. The page should show CSV as the primary input and URLs/PDFs as supporting source material.

What happens after repair?

+

Use the verified record for product pages, schema, widgets, supported channels, or custom CSV/XML/JSON exports.