Onboard a new supplier in days, not quarters.
Send us one file — a price list, a PDF, an Excel export — and Claro maps it to your own SKUs before your team opens it.
Supplier onboarding is a matching problem, not a data-entry problem
Every new supplier range starts the same way: a spreadsheet nobody trusts yet. Someone has to decide which rows are genuinely new, which already exist under a different code, and which are the same part with a typo in the spec. That work does not scale with the number of suppliers you take on, so most distributors simply take on fewer than they could — or let the backlog grow until a range launches three months late. Claro treats onboarding as a matching problem, not a data-entry problem, and runs it the same way on the first file and the thousandth.
Why onboarding one supplier range still takes weeks
A new supplier range means weeks of manual mapping before anything reaches the ERP.
Every supplier formats their catalog differently — languages, units, column names, none of it consistent.
By the time the mapping is done, the supplier has already sent an updated price list.
How supplier onboarding works with Claro
Any format: Excel, PDF, EDI, a scanned price list.
Every row matched to your own SKU, or flagged as new.
Duplicates and near-duplicates caught before write-back.
Clean data lands in ERP and PIM, ready to sell.
Who runs supplier onboarding this way
What goes in, what comes back
Claro writes back through files and APIs rather than certified connectors, so this list is a guide, not a limit.
Supplier onboarding: common questions
How long does it take to onboard a supplier range?
A first range is usually days rather than weeks, because the mapping is generated and reviewed rather than typed. Once a supplier's format is learned, later updates from that same supplier run in hours — the format handler is reused instead of rebuilt.
What file formats can Claro read?
Excel and CSV, PDF price lists, EDI and BMEcat, supplier portal exports, API feeds, and scanned documents. There is no pre-cleaning step: the file goes in as the supplier sent it.
How does Claro know a product is new rather than one we already stock?
It compares attributes rather than descriptions — bore, material, pressure rating, pack size — and returns a confidence score per row. Whether a row maps automatically depends on your rules, that confidence score and the impact of getting it wrong: trusted, low-impact rows can map automatically, and uncertain or high-impact ones go to review as new-product candidates.
Do we have to replace our PIM or ERP?
No. Claro sits above them. Your ERP stays authoritative for operations; Claro handles the ingestion, matching and validation, then writes approved records back.
What happens to rows Claro is unsure about?
They go to a review queue grouped by pattern, so a reviewer approves a whole class of rows as one decision. Confident rows write straight through; nothing uncertain writes back without your team's review.
See it work on your own catalog.
Bring one supplier file and we'll run supplier onboarding on your real data — matched, classified and reviewable.