Skip to main content
Onboard is the module for everything that happens before records are clean: receiving files, mapping them to the schema, resolving identities, and enriching gaps so the data is ready for downstream operations. The two surfaces under Onboard are Status and Supplier Portal.

​
Status

A pipeline view of in-flight onboarding jobs. 
file received → mapped → resolved → enriched → ready
For every batch (a file upload, a portal submission, a scheduled scrape), Status shows:
  • Stage — the current step in the pipeline.
  • Counts — total rows, mapped, unmatched, in review, ready.
  • Errors and stalls — surfaced with a one-click jump to the failing operation.
  • Run history — every previous batch from the same source, with timing and outcome.
Each stage maps to an operation:
StageOperation
MappedData Source Mapping
ResolvedFind Duplicates / Find Similarities
ValidatedValidate Data
NormalizedNormalize Data
EnrichedBulk Enrichment
SyncedPush & Sync
You can chain these into a pipeline so each new batch flows through the same gates without manual intervention.

​
Supplier Portal

A hosted intake surface you can share with suppliers. Suppliers don’t need a Claro account — they upload files or fill structured forms via a tokenized link.

​
What suppliers see

  • A branded portal with your workspace name and logo.
  • Clear instructions for the schema you expect (column names, required fields, allowed enum values).
  • A file uploader with inline schema validation — bad files are rejected with line-level error messages.
  • An optional structured form for small submissions.
  • A submission history so suppliers can resubmit corrections.

​
What you see

  • Submissions land as Data Sources on the relevant catalogue.
  • Pre-mapped where possible: known suppliers with a saved mapping skip straight to validation.
  • New suppliers go through Data Source Mapping first.
  • Schema violations are flagged and routed back to the supplier (with optional auto-email).

​
Configuring a portal

Per portal, you configure:
  • Target catalogue(s) — which catalogues this portal feeds.
  • Schema — required fields, optional fields, enum value lists.
  • File formats — CSV, XLSX, fixed templates.
  • Notifications — who is alerted on submission, who is alerted on validation failure.
  • Auth — public link, password, or per-supplier tokens.

​
A typical onboarding flow

  1. Supplier receives a Supplier Portal link.
  2. Supplier uploads their feed.
  3. Data Source Mapping matches their SKUs to existing records; unmatched rows are flagged.
  4. Validate Data checks schema and rule conformance.
  5. Bulk Enrichment fills gaps from supplier docs, web sources, or model generation.
  6. Reviewer approves uncertain items in Notifications.
  7. Push & Sync publishes to downstream platforms.
Most teams configure this as a chained pipeline so the entire flow runs unattended after step 2.