ClearGate: One decision per order, against the policy you set.

Allow, Review or Hold. Every reason named.

Review, 5 lots wait on a pharmacist: the board grouped by why, 2 on a recall signal with 4 Passports out, 2 held or blocked, the oldest 8 days, 1 awaiting evidence with Vera's request drafted, and 1 ready to review, each with its reason and its next step

The Review board: every lot that waits on a pharmacist, grouped by why, each with its next step. Brennick Compounding is a sample pharmacy; its suppliers, people, lots and figures are invented.

A decision you cannot replay is only an opinion.

ClearGate decides each order against the policy you wrote: Allow, Review or Hold, every reason named, signed with who, when and why, and replayable on question.

Pinned, screened, signed. The same run every time.

The same run whether a person clicked Run or your policy re-ran itself when evidence landed.

Every check, in the methodology

Your policy is pinned
Your saved policy, or Standard if none is saved, is pinned with its version before a rule runs.
Never read against a later policy
Four rails fire
The supplier, substance eligibility, the prescriber and the qualification file, each its own line of evidence.
The worst rail governs
Every rule runs
Hold beats review beats allow, and every rule still runs after the first one fires.
Every reason named, not just the first
Signed and chained
Who, when and why, signed and hash-chained to the decision before it.
A receipt that is never rewritten
Replayed on question
The stored evidence and the pinned policy replay to the same decision and the same reasons.
One answer for an inspector

Checks and ClearGate decisions are automated, and say so. A Passport issues only from a lot a named person has reviewed.

Four rails fire. The worst one governs.

A rail is one independent line of evidence. A rail you did not give inputs for is marked not provided and does not affect the verdict.

Supplier

The supplier's qualification file and the lot, against the rules you turned on.

Substance eligibility

FDA's codified lists at 21 CFR 216.23 and 216.24, re-read from the eCFR every 24 hours.

Prescriber

NPPES, the public prescriber registry, resolved live at the moment of the screen.

Qualification file

The supplier file's own status, current, due or overdue, read at order time.

Allow, Review or Hold. Every reason that fired.

Hold beats review beats allow, and all the rules are still evaluated after the first one fires, so a hold explains itself fully.

What each one needs, 5: ZS-0442 zinc sulfate, a recall case for 1 day, review exposure; batch ZN-2026-0929-01, an ingredient recall, review exposure; AS-1180 ascorbic acid, held by a person for 7 days, open the lot; the ascorbic acid batch, held through its ingredient for 8 days; BM-5584 progesterone, maker not named, review Vera's request — Each lot with the reason it is held and the one next step that answers it.

One order in. One signed decision out.

Strict, Standard or Lenient, plus eleven named toggles and one threshold. Nothing free-form, so the gate never makes a judgment you did not write.

Three floors, and exactly how they differ.

A preset is the floor, not the ceiling. Every one still holds on the hardest public-record signals; what changes is how much of the file must be in place and who releases.

Strict: complete, current, human-reviewed
Standard: cleared lot, current file, no hard signals
Lenient: only enforcement and recall signals hold

Discover Order-level COA traceability

Held, recalled or waiting, 5, the longest AS-1180 at 8 days, each drawn from the day it entered its state: ZS-0442 and ZN-2026-0929-01 on a recall signal for 1 day, the ascorbic acid batch and lot AS-1180 held for 8 and 7 days, and BM-5584 waiting for the maker's name for 1 day — What holds, and for how long: a recall signal, a person's hold, an ingredient's hold, a missing maker.

Deciding and releasing are two switches, on purpose.

Every saved check or received shipment re-runs the lot against your policy. Releasing is a separate choice: saving Standard or Lenient lets a cleared lot release its Passports on a policy Allow, and only ever from a reviewed lot.

Re-runs itself when evidence lands
Release on Allow only once you choose it
Only ever from a reviewed lot

Discover Supplier packet diligence

Release checks on batch CB-2026-1007-01: its compounding record on file; the lot decision cleared, 2 owed with its Passports; release rules not run; watched for recalls, not checked yet; the public source check not evaluated; the Passport can issue, with what is owed shown. The release rules have not been run on this lot — Release checks, each in words, including the ones that have not run.

Single order, whole PO, or supplier rail only.

Screen one order with supplier, product, lot, order reference, and optionally a prescriber. Through the API, a whole purchase order screens one line per supplier, product and lot, and the worst line governs the order.

One signed decision per line
The worst line governs the PO
Supplier rail alone, when that is all you have

Discover Trust Center

The four checks across 12 orders on a telehealth platform: supplier release policy, 4 meet and 8 need review; substance eligibility, 12 meet; prescriber or facility legitimacy, 12 not provided; supplier-file review cadence, 5 meet and 7 need review. In all, 21 meet the policy, 15 need review, 0 do not meet and 12 not provided — Four rails on every order, counted across 12 orders. A rail with no inputs reads not provided.

A versioned receipt, never a verdict on the medicine.

Every screen produces a receipt: the four rail results, the rules that fired, the policy version, who ran it, and when. It is never rewritten, only superseded, and replays to the same decision and the same reasons.

Rail results, rules, policy version, signer, time
Never rewritten, only superseded
A decision about paperwork, stated as such

Discover the evidence engine

Order NH-10482, ketoprofen 10% cream from Brennick Compounding: needs review. The worst decides: supplier and lot need review, because a document renewal or supplier review is coming due, with the next step in Tessaline Supply's file; substance eligibility meets, a USP monograph on record for a 503A facility; the prescriber rail not provided — One order's decision: each rail with why it fired and what comes next, and the worst one governs.

Everything on this page, in full.

The complete text, for the reader who wants the whole story before a call.

Every check, in the methodology

Every reason, and what closes it 7 review, 8 hold

Review: Lot still pending: The lot is still pending review. Closed by: wait for receiving, or review the lot. lot_pending
Review: File incomplete: The qualification file is not complete. Closed by: close the open elements. file_incomplete
Review: Below your completeness minimum: The file is below the completeness minimum you set. Closed by: raise the file over your threshold. below_min_completeness
Review: File coming due: A document renewal or supplier review is coming due. Closed by: renew before the date. file_attention
Review: Needs a person-reviewed lot: Your policy asks for a person-reviewed lot. Closed by: a named person reviews it. needs_human_review
Review: No supplier file: No qualification file is on record for the supplier. Closed by: start the supplier file. no_file
Review: The supplier reported a recall of another lot: The supplier reported a recall of one of its other lots. Closed by: confirm this lot is not affected, and record why. supplier_reported_recall
Hold: FDA enforcement match: An FDA enforcement or recall record matches the supplier. Closed by: judge the record, and record why. fda_enforcement_hit
Hold: Recall exposure: The lot is exposed to an FDA recall or enforcement signal. Nothing releases from it. recall_exposure
Hold: Accreditation expired: The accreditation on file is past its date. Closed by: a current certificate. accreditation_expired
Hold: Lot flagged: The lot is flagged on its evidence. Closed by: close the finding on the lot. lot_flagged
Hold: Manufacturer not named: No document names the original manufacturer, so its registration cannot be established (21 U.S.C. 353a(b)(1)(A)(ii)). Closed by: name the manufacturer, or get the maker's certificate. manufacturer_not_named
Hold: File overdue: An expired document or an overdue review. Closed by: renew the document, or review the file. file_overdue
Hold: Unqualified supplier: No file, and your policy holds an unqualified supplier. Closed by: qualify the supplier first. no_file
Hold: Custom item not attested: A custom item you require is not attested. Closed by: attest it, with who and when. custom_required

What each decision writes, and what happens next

Meets your policy (allow): No hold rule and no review rule fired; an Allow is the absence of a fired rule, which is why it carries no reason codes. A ClearGate hold left on the lot by an earlier decision is lifted, and the earlier record is never rewritten. Under a saved Standard or Lenient policy the Passport releases once the lot's own floor is met and a named person has reviewed the lot, stamped with the policy id and version that authorized it. Under Strict, or with no policy saved, 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 (review): At least one review rule fired and no hold rule did. No hold is stamped, and a hold left by an earlier decision is lifted. 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 (hold): At least one hold rule fired. clearGateHold is stamped on the lot, which blocks a Passport on its own. 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 signed.

The run, signed and replayable 5 steps

What an order is: Either a dispensed order or a purchase order from a supplier; both run through the same gate. Send 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.
Trigger: An order is screened, a check is saved, or a shipment is received. Every document stays kept as received. 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.
Pin: Your saved policy, or Standard if none is saved, is pinned with its id and version before a rule runs, so a decision is never read against a policy you changed afterwards.
Evaluate: The supplier qualification file and the lot are read against the policy. Every rule runs. Hold beats review beats allow, and every reason carries the policy rule code that produced it.
Sign: The decision is signed and hash-chained to the one before it, with the policy version pinned inside the record, and with who, when and why. Then it is stored.
Act: 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.
Signed and hash-chained: A decision nobody can reconstruct is an opinion. Each decision carries a signature and a hash over the decision before it. The log shows whether the chain is intact, so a record that was altered cannot pass as one that was not.
Replayable: A decision stores the evidence it read and a snapshot of the policy version that governed it. Replaying it re-runs the same evaluator against the same inputs, and a correct decision replays to the identical decision, label, and reasons.
Reason-coded: Every reason names the policy rule that fired and the level it fired at, so the log answers why this order held rather than only that it did.
Exportable per decision: Through the API, each entry downloads as a signed determination PDF for the batch record, alongside the whole-log export.
Superseded when the world changes: When a supplier recall lands after an Allow, that entry is marked superseded and asks for a re-run. The signed record itself is never rewritten.
The policy in force is visible: The console names the preset and the policy version that is governing right now, so a decision is never read against a policy you have since changed.

The four rails, in full

Supplier ClearGate: Documentation against your policy. The supplier's qualification file and the lot are evaluated against the rules you turned on, and every reason names the rule that fired.
Substance eligibility: Whether a substance is eligible to compound for your facility type, resolved against FDA's lists as codified at 21 CFR 216.23 and 216.24 and re-read from the eCFR every 24 hours, as a decision against your eligibility policy, never a legal opinion.
Prescriber registry: NPPES, live. A prescriber NPI or a name scoped to a state is resolved against the public registry at the moment of the screen.
Qualification file: Your supplier record. The six-element file's own rollup, current, due, or overdue, is read as a rail in its own right, so a file that stopped moving shows up at order time.
The composite: All four rails fire on every screen and the worst rail governs; all four resolving is what produces an Allow. One signed verdict, a decision about an order against the policy you set, never a statement that the medicine is safe, effective, or approved.
Single order: Supplier, product, lot, order reference, and optionally a prescriber NPI or name. All four rails fire and the composite verdict is signed.
Whole PO: One line per supplier, product, and lot. One signed decision per line, and the worst decision governs the PO, which is what a buyer needs at the desk.
Supplier rail only: The supplier documentation rail on its own, for when a supplier name is all you have. The full screen runs this plus three more rails.

Floors, switches and toggles 3 presets, 11 toggles, 1 threshold

Strict: Everything must be complete, current, and human-reviewed. Any hard signal holds, and a supplier with no qualification file at all is a hard hold rather than a soft review.
Standard: A cleared lot, a current file, and no hard signals. Gaps drop to review rather than hold. This is the default when no policy has been saved.
Lenient: Only the hardest public-record signals hold. An FDA enforcement hit on the supplier and recall exposure on the lot still stop the order; everything else allows.
Re-run automatically when evidence arrives: Every saved check or received shipment re-evaluates the policy against the lot and stores the signed decision, with no one having to click Run. All three presets do this.
Release Passports on a policy Allow: A Passport releases once its lot is cleared, carries no hold, satisfies the policy and has been reviewed by a named person, stamped with the exact policy version that authorized it. A saved Standard or Lenient policy does this; Strict does not, and a workspace that never saved a policy releases by hand.
Who pulls the trigger: The difference is who pulls the trigger, never what gets recorded. An automatic decision produces the same signed, hash-chained, replayable record a manual run produces. An uncleared lot, a lot carrying a hold, or a lot exposed to a recall never publishes a Passport.
A bounded library: Above the preset floor sits a fixed library of toggles and one threshold. Each maps to a field ClearGate evaluates, so a policy can never ask the gate for a judgment it does not make.
Require a cleared lot: Hold if the lot is flagged; review if it is still pending.
Require a complete qualification file: Review until all six file elements are satisfied.
Require a current file: Hold on an expired document or overdue review; review when one is coming due.
Block on expired accreditation: Hold when the accreditation on file is past its renewal date.
Block on an FDA enforcement hit: Hold when the supplier matches an FDA enforcement or recall record.
Block on recall exposure: Hold when the lot is exposed to a recall signal.
Require a human-reviewed lot: Review until a person has reviewed the lot, not just the automated gate.
Hold on an unqualified supplier: Hold, not just review, when there is no qualification file on record, so the gate can stop an order from a supplier you have never qualified.
Require a ClearGate Allow before a Passport: Block issuing an Evidence Passport on a lot until it has passed ClearGate with an Allow decision, so the policy rail cannot be skipped.
Re-run ClearGate automatically: Every saved check or received shipment re-evaluates the policy against the lot.
Release Passports on a policy Allow: Only from a cleared, reviewed lot with no hold. Billing applies exactly as on a manual release.
Minimum file completeness: Review when the qualification file is below this percent complete. Set anywhere from 0 to 100.
Custom required items, operator-attested: Your own required documents, an insurance certificate on file, for example. Never auto-graded: a required item that has not been attested holds the order, and an attested item carries who attested it and when. Every element is labeled Veritura evaluated or Operator attested, so the file never overstates what was checked.

POST /v1/cleargate API

One endpoint at order time: One decision per order against the policy you set: meets your policy, needs review, or does not meet policy, with a tamper-evident signed record behind it. Wire it into your fulfillment, Shopify, or pharmacy system.
Identify the order: Send a lot_id, or send supplier with optionally product and lot and the lot is resolved for you. Supplier is required when no lot_id is given. order_id carries your own order or PO reference on the signed decision.
Test and live keys: Self-serve from Settings. A test key returns a sandbox decision, a live key a production one, and the response says which environment it came from. Rotate any time, revoke instantly.
The same path as the dashboard: The API and the dashboard run the same decision path, so a decision made by an integration is indistinguishable in the log from one made by a person.
Beside it: POST /v1/eligibility: Allow, Review, or Hold on whether a substance is eligible to compound for a facility type against the current FDA lists. POST /v1/passports: issue from a cleared lot with an order reference; an uncleared lot can never publish a Passport.
Errors: 401: a valid API key is required (Authorization: Bearer vk_live_... or vk_test_...). 400: provide supplier (and optionally product and lot), or a lot_id.
Signed webhooks: Subscribe to passport.issued, lot.recall_hit, supplier.alert, file.changed, lot.held, lot.hold_lifted and lot.conflict_hit. Every delivery is HMAC-signed in the X-Veritura-Signature header, so a recall that lands after fulfillment finds its way back to your systems.
Plan: API access is on the Operations plan; Platform is quoted against a written scope.

The Receiving Gate is not ClearGate

Two gates, two vocabularies: ClearGate decides an order against your policy and answers in Allow, Review, or Hold. The Receiving Gate dispositions a shipment and sets the lot state that ClearGate then reads. A receiving disposition is not a ClearGate decision, and neither one is an evidence posture of Clear, Review, or Hold.
Documentation release ready: Every gate is satisfied on the record: the label reconciles to the paperwork, the COA is present, and the micro evidence is attached rather than asserted. Sets the lot to cleared.
Request supplier correction: A documentation gap is open that the supplier has to close. The gate drafts the exact ask for this exact lot. Sets the lot to pending review.
Quarantine pending evidence: The certificate is missing, or a micro result was marked present with no source result, method, or evidence reference behind it. Nothing moves downstream on an assertion. Sets the lot to pending review.
Hold for human review: Neither can be settled on paper at the bench. The record routes to a person and names what has to be reconciled before any reliance. Sets the lot to flagged.
A clean receipt does not lift every flag: A documentation release does not clear a lot whose flag came from a recall signal, a routing for human review, or a high-severity finding on its documentation; a receipt cannot answer a document finding, a corrected certificate can. A re-receipt that comes back quarantine or correction supersedes an earlier clear until the gates pass again.
Where the two meet: The disposition sets the lot state, one of the inputs ClearGate evaluates. With auto-decide on, ClearGate re-runs the moment the receipt is saved. The nine gates are documented on receiving for compounding pharmacies. Documentation receiving gate only, not a product quality, safety, efficacy, compliance, or FDA-approval determination.

What a decision never means

Not an approval: An Allow means the documentation meets your policy. No decision ever means Veritura approves the supplier.
No determinations: Veritura does not test medicine, approve suppliers, recommend purchases, or make medical, legal, product-safety, or FDA-approval determinations.
No paid placement: Suppliers cannot pay for a better result or a better position: no listing fee, no subscription, and no pay-to-rank. Results are filtered by what the record shows, never ranked.

Checks and ClearGate decisions are automated, and say so. A Passport issues only from a lot a named person has reviewed.

Questions, answered plainly.

Supplier documentation against your policy, substance eligibility against the current FDA lists, the prescriber against the public NPPES registry, and the supplier's qualification file. All four fire, and the worst rail governs.

Review names what is pending, such as a renewal coming due. Hold names hard signals, such as an enforcement match on the supplier, and a hold blocks a Passport on its own. Hold beats review beats allow.

Only if you choose it, and never from an unreviewed lot. A workspace that has not saved a policy releases by hand. Save Standard or Lenient and a cleared lot that a named person has reviewed releases its Passports on a policy Allow; Strict keeps every release with a person.

Yes. Strict, Standard, and Lenient are presets, and every one still holds on the hardest public-record signals. What changes is how much of the file must be in place and who releases.

Still have questions? Talk to a person.