Skip to main content

Solutions

Qoridex is built for product and catalogue data where an exception needs a human decision and that decision needs to be defensible.

Product data verification

The problem A title says navy, the colour field says black, and no rule can tell which one is right.

Attribute-level review of records flagged by deterministic detection, with the original value always preserved.

What happens
Flagged fields and their relevant relationships are reviewed against the project’s permitted evidence and rules.
What you receive
You receive the reviewed data, or for a check-only project your own values plus a check report listing each flag and its reason. Your original stays preserved, and cases the evidence cannot settle go to QA instead of being guessed.

Attribute review, unit and value checks, with the original preserved.

One record, field by fieldIllustration. Not a real record or result.
TitleCotton T-shirt, Navy, MNo finding
ColourBlackDoes not agree with the titleNeeds review
SizeMNo finding
Material(empty)No evidence suppliedCannot be determined

A flagged field is compared with client-permitted evidence and the project rules. The value received stays on record as it arrived.

Exception handling

The problem Flagged fields need someone qualified to judge them, not whoever happens to be free.

Findings become controlled tasks routed only to workers qualified and authorised for that project.

What happens
Findings are organised into controlled tasks under the project’s routing rules. Tasks reach reviewers qualified for the category and authorised on the project.
What you receive
Decisions made by people permitted to make them, each recorded against the task.

Task routing, qualified reviewers and project authorisation.

Findings organised into tasksIllustration of routing. Not real workers or tasks.
  1. Findings
    • Colour mismatch
    • Material missing
    • Size conflict
  2. Project routing rules
    • Task category
    • Reviewer qualification
    • Project authorisation
  3. Reviewers
    • Qualified for the category, authorised on the projectReceives tasks
    • Qualified, not authorised on this projectReceives none
    • Authorised, not qualified for this categoryReceives none

Evidence-backed correction

The problem A changed value with no reason behind it cannot be checked or defended later.

A correction records the new value and the reason behind it, with an evidence reference where one is linked.

What happens
A reviewer who corrects a value records the reason and can link permitted evidence for the case. A reviewer may also record that the case cannot be determined.
What you receive
You receive the reviewed data; Qoridex keeps the reason and any linked evidence reference in its decision record.

An evidence trail, the rationale on record, and no guessing.

What a correction carriesIllustration. Not a real record or result.
  1. Original value, preservedColour: Black
  2. Reviewed valueColour: Navy
  3. Reason on recordThe title and the client-permitted product photo both show navy.
  4. Evidence referenceClient-permitted product photo

Illustrative outcome after review and QA, subject to the agreed project rules.

Client-ready delivery

The problem You need to know the file you received is the one that was finished, and that it will not change underneath you.

A reproducible snapshot and a checksummed export package, with an explicit acknowledgement and acceptance trail.

What happens
A final snapshot is generated only when the work behind it has concluded, then exported as a package with a checksum.
What you receive
Your file, plus a check report for a check-only project, delivered as an export package recorded with a checksum. A later revision arrives as a new version; the one you already have does not change.

FINAL snapshots, checksummed exports and versioned revisions.

Delivered as versionsIllustration. Not a real delivery.
  1. Version 1FINAL snapshot generatedExport package, checksum recordedDelivered, then acknowledged
  2. Version 2Revision requested on Version 1New FINAL snapshot and packageNew checksum recorded

Version 1 stays exactly as delivered.

Two ways to run a project

Check only

Reviewers flag a wrong field with an approved reason and do not type a value. You receive your file with your own values, plus a check report listing each flagged field, its value, the result and the reason.

Check and correct

Reviewers propose the right value with a reason. You receive the file with the agreed corrections applied, and a check report if anything was flagged.

The mode is fixed once work starts, so one delivery never mixes the two.

Next steps

See each stage in detail

How It Works shows who acts at each of the six stages, what reviewers see, and what is kept on record.

See the six stages

Discuss a pilot

Tell us which product data you want checked and which evidence reviewers may use.

Access is provisioned by us. There is no public sign-up.

Request a Pilot