How it works

From supplier source to maintained catalog.

Each delivery passes through an explicit workflow so source changes, uncertain values and destructive updates are visible before they become canonical catalog state.

01

Source

Add the supplier and source. Use manual file upload or a configured inbound adapter where appropriate.

02

Profile

Inspect file structure, headers and schema characteristics before mapping the source.

03

Map

Map source fields to canonical targets and define deterministic transformations.

04

Normalize

Apply mappings, dictionary resolution, identity rules and normalization logic to source rows.

05

Compare

Evaluate proposed changes against current catalog state, source priority and existing overrides.

06

Review

Route uncertain values, conflicts and identity questions to human review.

07

Commit

Commit approved changes with locking, auditability and rollback safeguards.

08

Repeat

Reuse mapping versions, aliases and prior decisions when the supplier sends the next delivery.

The objective is fewer repeated exceptions.

The system accumulates operational knowledge instead of treating every supplier file as an unrelated cleanup job.