Turn Data Exceptions Into Verified Decisions
Product data verification for e-commerce and catalogue teams. Defined checks flag the fields that need review, and qualified people decide them. Corrections keep the original value and a recorded reason, with permitted evidence linked where available.
Access is provisioned by us. We are preparing to onboard a small number of pilot clients.
- 1Possible issue foundA defined check flags a field that disagrees with the record.
- 2Client-permitted evidenceReviewers use only evidence the client allows.
- 3Qualified reviewersA qualified reviewer decides the case. Where policy requires it, a second reviewer answers without seeing the first answer.
- 4QADisagreements go to a separate QA reviewer.
- 5Decision and reason recordedOutcome, reason and evidence kept; the original stays.
Illustration of the process. Not a real record or result.
Product data checked by people, with every decision on record
Qoridex is a managed service for product and catalogue data. Defined checks flag fields that need review. Qualified reviewers compare each case with permitted evidence and record what it supports, contradicts, or cannot establish.
The original record is preserved. Nothing is delivered until every flagged case is settled. You receive the reviewed file and, for a check-only project, a report of every flagged field. Each change stays traceable to the decisions and evidence behind it.
Verified Data Path
Six stages, each leaving a record. Nothing advances on assumption.
-
Controlled intake
Your file is stored unchanged, with its checksum.
-
Deterministic detection
Defined checks flag fields, each with a reason code.
-
Qualified verification
A qualified, authorised reviewer decides each case.
-
Independent reverification
Where policy requires it, a second reviewer answers blind.
-
QA adjudication
Disagreements go to a separate QA reviewer.
-
Verified delivery
Nothing is delivered until every case is settled.
Problems solved
Exceptions that automation cannot close
Unit mismatches, contradictory attributes and missing values need judgement, not another rule.
Corrections you cannot audit
A changed value is only useful if you can see who changed it, on what evidence, and what it was before.
Source data you cannot risk losing
Received data stays immutable. Corrections are derived, never written over the original.
- Evidence Client-permitted pack label photo reads 5 kg
- Reviewer one Correct to 5 kg
- Reviewer two, without seeing the first answer Correct to 5 kg
- Illustrative outcome after review and QA 5 kg, subject to the agreed project rules. The original 500 g is preserved.
Why Qoridex
Independent second pass
Where policy requires it, a second qualified reviewer works blind to the first answer.
Adjudicated disagreement
Two reviewers disagreeing is routed to QA, not averaged away.
Field-level lineage
Every changed value traces back through its resolution, the decisions and any linked evidence to the original record. An unchanged value traces straight to the original.
Versioned revisions
A revision produces a new version. The version you already received stays exactly as delivered.