Review records before publishing
When a record needs review
Each product's category sets its risk level:
| Category | Risk level |
|---|---|
| Food and agriculture | High |
| Halal and kosher | High |
| Electronics and batteries | High |
| Cosmetics | Medium |
| Textiles | Low |
High-risk and medium-risk records always go to review. A low-risk record is approved automatically only when its lowest field confidence is above 85%.
A record also goes to review when:
- two documents give different values for a field,
- an extraction fails,
- a field has low confidence,
- a published product is changed,
- a certificate expires,
- its risk level is unknown.
The review queue
Open Review. The queue has two lists, Waiting and Decided. The selected record shows its source document and each field with its confidence. Fields below 85% are flagged. After a change to a published product, the record shows the published value and the new value. For an expired certificate, the record explains the public status and links to the product.
Approve or reject
A reviewer approves or rejects a record. A rejection needs a reason.
Members with the Owner or Reviewer role can approve or reject.
An approval publishes the record. It goes through the same checks as a manual publish (see Publish and withdraw passports), and no separate publish step follows.
Automatic publishing
Automatic publishing of low-risk records is off by default. Only an Owner can turn it on, and only with a passkey session (Q88).
- When it is on, a low-risk record publishes without a click after its data extraction finishes with nothing to review, as long as the GS1 company prefix is verified and the plan allows it (Q83).
- When it is off, the record stays a draft until an Owner or Admin publishes it.
Your webhooks can send review.required, review.approved, and review.rejected events.