Order time is when the paperwork matters most and gets checked least. This is the whole run, in the order it happens, and the same run whether a person clicked Run or your policy re-ran itself when evidence landed.
What happens between the call and the answer.
One order or lot is read against the policy the customer wrote, and the decision comes back Allow, Review or Hold with every reason naming the rule that fired.
The operator picks a preset and can override eleven named toggles and one threshold. It is a bounded library mapped to fields the evaluator actually reads, not a free-form rule language.
An order is screened, a check is saved, or a shipment is received.
ClearGate evaluates. When the policy has auto-decide on, no one has to click Run; the trigger is recorded but the record produced is identical to a manual run.
The supplier qualification file and the lot are read against the policy. Hold beats review beats allow. Every reason carries the policy rule code that produced it.
The decision is signed and hash-chained to the one before it, with the policy version pinned inside the record.
The decision is stored.
A hold stamps clearGateHold on the lot, which blocks the passport on its own. A later allow or review clears that hold; the signed record itself is never mutated.
Someone questions a decision.
The stored evidence and the pinned policy snapshot are fed back through the same evaluator. A correct decision replays to the identical decision, label and reasons.
Three ways it comes back.
Hold beats review beats allow. All the rules are still evaluated after the first one fires, so the record names every reason rather than only the one that decided it.
A lot_id, or a supplier with optionally a product and lot so the lot is resolved for you. Your own order reference rides along, and supplier is required when no lot_id is given.
Your policy, at its pinned version
Your saved policy, or the Standard preset when you have not saved one. Its id and version are pinned before a single rule runs, so a decision is never read against a policy you changed afterwards.
No hold rule and no review rule fired. An Allow is the absence of a fired rule, which is why it is the one decision that carries no reason codes.
allow -> Meets your policy
At least one review rule fired and no hold rule did.
review -> Needs review
At least one hold rule fired.
hold -> Does not meet policy
What each decision carries, and what it does to the order next.
Meets your policy
What it writes on the lot
A ClearGate hold left on the lot by an earlier decision is lifted. The earlier record itself is never rewritten.
What happens to the order next
Under Standard or Lenient the Passport releases as soon as the lot's own floor is met, stamped with the policy id and version that authorized it. Under Strict the release stays with a person. If an enforcement or recall signal lands on the supplier after this Allow, the entry is marked superseded and asks for a re-run.
Needs review
Reason codes it can carry
lot_pendingThe lot is pending review.
file_incompleteThe qualification file is not complete.
below_min_completenessThe qualification file is below the policy minimum percent complete.
file_attentionA document renewal or supplier review is coming due.
needs_human_reviewPolicy requires a human-reviewed lot.
no_fileNo supplier qualification file is on record for this supplier.
What it writes on the lot
No hold is stamped, and a hold left by an earlier decision is lifted.
What happens to the order next
The order stays yours to decide. If you turned on Require a ClearGate Allow before a passport, a release attempt on this lot answers 409 cleargate_required until an Allow is on record.
Does not meet policy
Reason codes it can carry
fda_enforcement_hitFDA enforcement or recall signal(s) on the source.
accreditation_expiredAccreditation is expired.
recall_exposureThis lot is exposed to an FDA recall or enforcement signal.
lot_flaggedThe lot is flagged.
file_overdueThe qualification file is overdue: an expired document or an overdue review.
no_fileNo supplier qualification file is on record, and policy holds on an unqualified source.
custom_requiredA custom policy item is required and not attested.
What it writes on the lot
clearGateHold is stamped on the lot, which blocks a Passport on its own.
What happens to the order next
A release attempt on that lot is refused with a 409: cleargate_hold where the lot is otherwise cleared, lot_pending_review where it is not. Close the reason that fired and the next decision lifts the hold. The held decision stays in the log exactly as it was written.
A ClearGate decision always means the documentation meets your policy. It never means Veritura approves the supplier.
Veritura does not test medicine, approve suppliers, recommend purchases, or make medical, legal, product-safety, or FDA-approval determinations. There is no paid or subjective placement: suppliers cannot pay for a better result or a better position, no listing fee, no subscription, and no pay-to-rank. Where results are ordered rather than filtered, the order is set by a published documentation-coverage grade, and that grade is never a recommendation, a preference, or a statement about any product.
What the gate reads
