Research Peptide Receiving SOP for Canadian Labs

Quick answer: the receiving SOP in one page#

A research peptide receiving SOP is the written procedure a Canadian lab uses when a peptide package arrives. It answers a simple question: can the lab connect the package, vial, lot, COA, product page, storage instruction, and claim boundary into one defensible research-material file before the vial enters inventory?

The SOP does not prove potency, sterility, clinical suitability, or therapeutic value. It prevents preventable documentation failures. It keeps a clean vial from being accepted against the wrong COA, keeps a warm shipment from disappearing into routine stock, and keeps a supplier page with personal-use claims from being treated as a clean research source.

The short version:

1. assign a receiver before the shipment arrives;
2. capture the delivery time and package condition before opening;
3. photograph the package, packing slip, vial label, cap, crimp, visible material, and storage instructions;
4. match the vial to the order, invoice, product page, and COA;
5. review the COA for lot, purity, identity, test date, and method detail;
6. inspect vial integrity and visible material without making potency claims;
7. record the unopened storage instruction and first storage location;
8. log any temperature excursion or chain-of-custody gap;
9. screen the supplier page for research-use-only language and red-flag claims; and
10. write a disposition: accept, clarify, quarantine, reject, or reserve under a lab-defined non-critical category.

Use this SOP with the research peptide import documentation checklist, the research peptide cold-chain shipping acceptance checklist, the research peptide storage SOP, the research peptide freezer temperature mapping checklist, the research peptide quarantine log template, the research peptide deviation log template, the peptide COA verification checklist, the research peptide sterility and endotoxin checklist, the peptide storage and vial inspection checklist, the peptide temperature excursion log, the research peptide documentation audit trail checklist, the research peptide label reconciliation checklist, the research peptide lot release checklist, the research peptide batch documentation template, the research peptide chain-of-custody log, and the research peptide supplier scorecard. Those pages handle individual pieces. This page puts the receiving workflow in order: package triage first, label reconciliation second, release or quarantine third, then SOP-controlled storage before a lot settles into long-term cold storage. Once a lot is accepted for solution preparation, route the file to the peptide reconstitution guide, its handoff checklist, and the peptide solvent compatibility matrix for neutral documentation of solvent choice, concentration math, and solution-age controls.

Copyable one-page receiving log#

Use this log as the minimum receiving record when a package arrives. It is intentionally plain: the goal is not to write a perfect SOP paragraph, but to preserve the evidence another reviewer will need later.

Research peptide receiving log

Receiver:
Backup reviewer:
Date and local delivery time:
Carrier and tracking number:
Supplier:
Product page URL captured:
Product page capture filename:
Order or invoice number:
Packing slip present? yes/no
Material name on order:
Material name on vial:
Declared amount or fill:
Lot/batch on vial:
Lot/batch on COA:
COA filename and test date:
COA methods visible: HPLC/UPLC / MS / other / unclear
Supplier-stated unopened storage condition:
Shipping-temperature language captured? yes/no

Package condition before opening:
Photos captured: exterior / label / packing slip / insulation / cold pack or indicator / vial label / cap-crimp-stopper / visible material
Temperature evidence: logger / indicator / cold-pack state / surface reading / none
Delay, wet box, crushed package, missing insulation, or other deviation:

Vial condition:
Visible material condition:
Label, cap, crimp, stopper, or glass concern:
RUO claim screen result:
Human-use/dosing/treatment/cosmetic/performance claim concern:

Initial disposition: accept / clarify / quarantine / reject / reserve under written low-criticality category
Reason for disposition:
Supplier question sent? yes/no
First storage or quarantine location:
Time moved to storage/quarantine:
Reviewer signoff:

The log should be completed before the vial disappears into normal inventory. If a row is unknown, write "unknown" rather than smoothing it over. "No logger present" is a useful record. "Probably fine" is not.

First-15-minute receiving workflow#

The first 15 minutes after delivery decide whether the material record is reconstructable. The receiver should not start with interpretation. Start with evidence capture.

This workflow is deliberately conservative. A failed row does not automatically prove a material is unusable, but it does mean the vial should not be silently accepted. The next move is evidence preservation, supplier clarification when appropriate, and a written disposition.

Accept, clarify, quarantine, reject: decision language#

Receiving records get weak when the final decision uses casual language. Use controlled words instead.

Do not invent a reserve category after the package fails. If the category did not exist before the shipment arrived, "reserve" is usually undocumented acceptance with nicer language.

Why a receiving SOP is different from a COA checklist#

COA review asks whether an analytical document is credible. Receiving asks whether the vial in hand still belongs to that document.

That distinction matters. A lot-matched COA can be useful and a receiving file can still fail. The package may arrive crushed. The vial label may not match the COA. The cap may be loose. The visible material may look wet when the product was described as lyophilized. The product page may have changed since the order was placed. The supplier may have provided storage language in an email that never reached the person who put the vial away.

The receiving SOP is the bridge between supplier documentation and local chain of custody. It turns scattered evidence into one record another reviewer can audit later.

For Northern Compound readers, this is also a compliance filter. A page can show a plausible chromatogram and still be unsuitable as a cited supplier route if it leans on dosing, injection, disease-treatment, body-composition, tanning, cosmetic-result, or testimonial language. The research-use-only compliance checklist should be part of receiving because claims discipline is evidence of supplier discipline. Before the package exists, the research peptide supplier due diligence packet gives the upstream evidence folder: supplier page captures, COA routes, support questions, storage policies, claim audit, and pass/clarify/reject decision language.

Scope: what this SOP covers and what it does not#

This SOP covers receipt and documentation of research-use-only peptide materials. It is written for Canadian research buyers, small lab teams, and procurement reviewers who need a practical receiving procedure without pretending to operate a full GMP release program.

It covers:

• package condition and delivery timing;
• lot, label, invoice, and COA matching;
• physical vial inspection;
• visible lyophilized-material observations;
• storage instruction capture;
• temperature-excursion documentation;
• supplier communication records;
• RUO claim screening;
• disposition decisions; and
• batch-file organization.

It does not cover:

• human dosing;
• administration routes;
• injection technique;
• reconstitution instructions;
• treatment protocols;
• bodybuilding cycles;
• cosmetic use;
• veterinary use;
• clinical release testing;
• sterility assurance; or
• claims that any material is safe or effective for people.

A receiving SOP should be deliberately boring. Its job is to reduce ambiguity, not to create a promotional page around the compound. That is especially important for high-interest categories such as recovery peptides, GLP-1 pathway materials, skin peptides, and cognitive research peptides, where search demand often pulls weak content toward human-use promises.

Roles before the shipment arrives#

A receiving SOP fails when nobody owns it. The first section should name the role responsible for receipt and the backup role if the primary receiver is absent.

A practical role map looks like this:

Small teams may combine roles, but the record should not become anonymous. "Received by lab" is weaker than "received by J.S. at 10:22, photographed, placed in quarantine box Q-2 pending COA-lot clarification." The second sentence lets a later reviewer reconstruct the event.

Before ordering, the team should also decide where uncertain material goes. Quarantine cannot be a vague idea. It needs a physical or digital location: a labelled box, a separate freezer rack, a folder status, or an inventory tag that prevents the vial from being treated as accepted stock while the question is unresolved. If the material will later be prepared as a working solution, the same receiving file should point to the peptide reconstitution guide, solvent compatibility matrix, and freeze-thaw log template so solution-preparation math, vehicle rationale, label records, and thaw history do not get separated from receipt evidence.

Step 1: preserve package context before opening#

The receiving workflow starts before scissors touch the mailer.

Record:

• carrier and tracking number;
• delivery date and time;
• time the package was first handled by the receiver;
• whether the package was left in a mailbox, lobby, loading area, vehicle, or controlled receiving area;
• visible package damage;
• wetness, crushing, punctures, tears, or heat exposure;
• whether the package was expected to include insulation, cold packs, desiccant, light protection, or a temperature indicator; and
• any carrier exception, delay, or failed delivery attempt.

Take photos while the package is still intact. Photograph the outer package, damaged areas, shipping label with private address details redacted if the image will be shared, and any temperature indicator or cold-pack condition after opening.

This is not theatrics. The first day after delivery is where many chain-of-custody gaps happen. A package can sit warm in a mailbox, move through an unlogged front desk, or be opened by someone who separates the packing slip from the vial. If the file starts only when the vial reaches storage, the most uncertain period is invisible.

Step 2: match order, vial, product page, and COA#

Do not judge appearance before identity. A normal-looking vial with the wrong lot number is not acceptable.

The lot-matching section should capture:

1. supplier name;
2. product page URL captured on the access date;
3. order or invoice number;
4. product name exactly as ordered;
5. vial label name;
6. vial amount or fill claim;
7. lot or batch number on the vial;
8. lot or batch number on the COA;
9. COA file name and date;
10. product-page storage instruction;
11. support-email storage instruction, if different; and
12. reviewer initials.

If the product page, label, invoice, and COA use different identifiers, do not improvise the mapping. Ask the supplier to connect them in writing. Some suppliers legitimately use internal manufacturing codes, public lot codes, and fulfilment labels. That can be acceptable if the mapping is documented. It is weak if the buyer has to infer it.

For broad sourcing context, a reader may begin with where to buy research peptides in Canada or a category page such as where to buy recovery peptides in Canada. The receiving decision is narrower. It belongs to the exact vial and lot, not the category page.

Step 3: capture the COA while it is still current#

A COA can disappear, change, or be replaced after the order. Save it immediately.

At minimum, the receiving file should preserve:

• COA PDF or screenshot;
• product page screenshot or PDF;
• access date;
• lot number;
• product name;
• stated purity;
• identity method;
• test date;
• analytical lab or supplier lab name;
• method notes where available;
• fill amount;
• storage instruction; and
• any supplier response connecting the COA to the vial.

The peptide COA verification checklist is the deeper worksheet for HPLC, mass confirmation, chromatograms, expected-versus-observed mass, and accept/clarify/quarantine/reject decisions. The receiving SOP should not duplicate every COA rule, but it should require that COA review happen before the vial is accepted into normal inventory.

A useful distinction: the receiver can capture the COA; the documentation reviewer should interpret it. That prevents a package-opening task from silently becoming an analytical-quality decision.

Step 4: inspect vial integrity without turning it into use guidance#

Vial inspection is not administration guidance and not a potency test. It is a container, closure, label, and visible-condition screen.

Inspect and photograph:

• glass cracks, chips, scratches, stress marks, or breakage;
• cap condition;
• crimp tightness and alignment;
• stopper position;
• stopper puncture marks;
• leakage or powder outside the container;
• residue on the vial exterior;
• label legibility;
• label adhesion;
• relabelling signs;
• product name and amount;
• lot number; and
• visible material appearance.

A compromised closure should stop the normal workflow. Do not let a strong COA rescue a cracked vial, displaced stopper, leaking container, or unexplained puncture mark. The COA describes an analytical sample or batch record. It does not prove that this received vial maintained container integrity through shipping and receipt.

Visible material should be described cautiously. Dry-looking powder, cake, film, puck, or residue can vary by formulation, fill, vial geometry, and lyophilization process. The receiver should write what is seen, not what it means biologically. "White cake, no visible moisture, no foreign matter observed" is useful. "Looks potent" is not.

Step 5: separate material state from storage assumptions#

Many weak peptide-storage pages collapse everything into one generic rule. A receiving SOP should separate material state.

Northern Compound does not provide reconstitution or administration instructions. The point is documentation hygiene. Preserve the supplier's current storage language and the lab's own handling record. If the supplier page, COA, label, and support email disagree, document the conflict and resolve it before acceptance.

For category examples, inspect live ProductLinks only as current documentation paths: BPC-157 or TB-500 for recovery-category material, Semaglutide or Tirzepatide for incretin-pathway research, GHK-Cu for copper-peptide matrix biology, and Selank for cognitive research models. The link helps a reader inspect the current supplier page. It does not certify the lot or recommend personal use.

Step 6: define temperature-excursion handling#

A temperature excursion is any period where the material may have been outside the supplier's stated condition. It can happen during shipping, delivery, bench staging, freezer transfer, equipment alarm, inventory move, or delayed unpacking.

The SOP should require a written excursion note when any of these occur:

• package arrives later than expected;
• carrier shows a delay or exception;
• package is warm, wet, crushed, or opened;
• cold pack is absent when expected;
• temperature indicator shows an out-of-range event;
• vial sits unlogged before storage;
• freezer or refrigerator alarm occurs;
• storage location is unknown for any period; or
• supplier storage instructions were missing or conflicting.

Use the research peptide cold-chain shipping acceptance checklist for the package-level go/no-go screen and the peptide temperature excursion log for the detailed excursion record. The receiving SOP should specify the initial rule: separate the material, label it pending review, preserve evidence, contact the supplier if needed, and do not return it to accepted inventory until disposition is written.

Do not declare a material fine or ruined from generic peptide folklore. Stability depends on the molecule, material state, excipients, duration, temperature, moisture, light, container, and validated supplier data. The serious move is narrower: document the event, ask whether lot- or material-state-specific evidence exists, then write the decision.

Step 7: screen RUO claims before accepting the supplier route#

Claim screening belongs in receiving because supplier language affects trust.

A page can fail the RUO layer even if the package and vial look clean. Red flags include:

• dosing instructions;
• injection or administration directions;
• disease-treatment claims;
• injury-healing promises;
• weight-loss promises;
• cosmetic before-and-after framing;
• tanning or appearance-result claims;
• bodybuilding cycle language;
• testimonials from personal users;
• statements that imply the material is safe or effective for people; and
• vague legal disclaimers paired with human-use sales copy.

A clean supplier page should identify the material, provide lot-level documentation where available, state research-use-only positioning, and avoid telling readers how to use the compound personally.

This matters for conversion quality. Northern Compound should send better-qualified readers to product pages, not looser ones. If a reader clicks through to inspect a current Lynx Labs page, the editorial frame should remain documentation-first: COA, lot, storage, material identity, and RUO boundaries.

Disposition: accept, clarify, quarantine, reject, or reserve#

A receiving SOP should end with a decision, not a pile of observations.

"Reserve for non-critical method development" should not be a loophole. It is only appropriate if the lab has already defined what non-critical means, how the vial is labelled, and how it is prevented from entering a meaningful endpoint study. If that category does not exist, use quarantine or reject.

One-page receiving log template#

Copy this into a lab note, spreadsheet, or batch-file template.

Research peptide receiving SOP log

Material name:
Supplier:
Product page URL:
Product page access date:
Northern Compound source URL:
Order/invoice number:
Tracking number:
Carrier:
Delivery date/time:
Receiver name/initials:
Package first handled at:
Package condition:
Insulation/cold pack/desiccant/temperature indicator present:
Carrier delay or exception:

Vial label product name:
Vial amount/fill claim:
Lot/batch number on vial:
Lot/batch number on COA:
COA file name:
COA date:
COA purity/identity methods captured:
Supplier storage instruction:
First storage location:
Time from receipt to storage:

Vial exterior condition:
Cap/crimp/stopper condition:
Visible material appearance:
Photos saved? yes/no
Temperature excursion suspected? yes/no
If yes, excursion log file:
Supplier contacted? yes/no
Supplier response file:
RUO claim screen pass? yes/no
Scientific endpoint fit reviewed? yes/no
Disposition: accept / clarify / quarantine / reject / reserve
Reviewer initials and date:

The log is intentionally plain. A record that gets used is better than a perfect template that nobody fills out.

Supplier email templates#

Lot mapping question#

Subject: Lot mapping question for [product] received on [date]

Hello,

We received [product name] on [date]. For our research-material receiving file, can you confirm how the vial code [vial code] maps to COA lot [COA lot] and order [order number]?

We are only asking for lot traceability, identity documentation, and storage-record purposes. We are not asking for dosing, administration, treatment, cosmetic, athletic, or personal-use guidance.

Thank you.

Storage clarification question#

Subject: Storage clarification for [product] lot [lot number]

Hello,

For [product name] lot [lot number], can you confirm the recommended unopened storage condition and whether the current COA or product page is the controlling source for that instruction?

We observed [brief receiving condition, if relevant]. Please let us know what record should be kept beside the COA for research-use-only documentation.

We are not asking for human-use, dosing, route, treatment, or personal-use guidance.

Vial condition question#

Subject: Vial condition documentation for [product] lot [lot number]

Hello,

During receiving inspection for [product name] lot [lot number], we observed [crack / loose crimp / label issue / visible material concern / package damage]. We have attached photos for documentation.

Can you advise whether this vial should be replaced, rejected, or held pending further review for research-material documentation purposes?

We are not asking for personal-use guidance.

Short questions usually get better answers than essays. The goal is to produce a record that can be saved beside the COA.

How this SOP changes common Northern Compound categories#

Recovery-category research materials#

Recovery-category searches often involve BPC-157, TB-500, and fixed blends. The receiving SOP should keep the file away from injury-healing claims and focused on material identity, lot, vial condition, storage, and model fit. For blend materials, the receiving file should also capture ratio clarity and whether each component is supported by documentation.

GLP-1 and incretin-pathway materials#

For Semaglutide, Tirzepatide, and related incretin-pathway materials, search intent often drags content toward weight-loss language. The receiving SOP should avoid that. It should document exact identity, lot, purity, storage condition, and cold-chain or temperature-excursion evidence where relevant.

Skin and matrix-biology materials#

For GHK-Cu, the receiver should capture material form and supplier language carefully. Copper-peptide pages can blur research, cosmetic, and topical-consumer language. A compliant receiving file stays with batch identity, visible condition, storage record, and endpoint fit.

Cognitive research materials#

For Selank and adjacent cognitive research materials, a receiving SOP helps prevent subtle endpoint work from being compromised by uncertain storage, contamination, label mismatch, or RUO-claim drift. It should not borrow anxiety, focus, sleep, or mood claims from consumer search results.

Common receiving failures#

Failure: accepting the vial before matching the COA#

The easiest mistake is to put the vial away because it looks normal, then check the COA later. Reverse the order. If the lot does not match, the material should not enter normal inventory.

Failure: losing the product-page version#

Supplier pages change. Save the page or screenshot on the access date. If storage instructions, RUO language, or COA access changes later, the original receiving record still shows what the buyer saw.

Failure: treating photos as optional#

Photos are cheap chain-of-custody evidence. They are especially useful when package damage, label mismatch, or visible material questions arise. File names should include date, supplier, product, lot, and photo type.

Failure: hiding uncertainty in accepted inventory#

If a package arrives warm or wet, the wrong move is to write a vague note and store it with accepted stock. Separate it physically or digitally until the decision is made.

Failure: letting commercial urgency lower the standard#

Scarce, expensive, or high-demand materials should receive stricter documentation, not looser documentation. Search demand is not a reason to accept a weak batch file.

Folder structure for the batch file#

The receiving SOP should end with a folder that another reviewer can open without asking the receiver what happened. A simple structure is enough:

2026-05-16_supplier_product_lot/
  01_order/
    invoice.pdf
    packing-slip.pdf
    product-page-accessed-2026-05-16.pdf
  02_coa/
    coa-lot-[lot].pdf
    coa-review-notes.txt
  03_receiving-photos/
    package-exterior.jpg
    package-damage-if-any.jpg
    packing-slip.jpg
    vial-label.jpg
    vial-cap-crimp-stopper.jpg
    visible-material.jpg
    cold-pack-or-indicator.jpg
  04_storage/
    supplier-storage-instruction.txt
    first-storage-location.txt
    temperature-excursion-log-if-needed.txt
  05_supplier-communications/
    lot-mapping-question.txt
    storage-clarification-response.pdf
  06_disposition/
    receiving-decision.txt
    reviewer-signoff.txt

The names are intentionally uncreative. Searchable file names beat clever labels. Include date, supplier, product, lot, and record type wherever possible. If a file later gets exported from email, renamed by a phone, or moved into a shared drive, the name should still explain what it is.

For teams using a spreadsheet, the same structure can become columns: product, supplier, order, lot, COA file, product-page capture, package condition, vial condition, storage instruction, excursion status, RUO claim screen, disposition, reviewer, archive path. The format matters less than consistency. The audit question is always the same: can another person reconstruct the acceptance decision without relying on memory?

Pre-receipt checklist before the first order#

Receiving is easier when the rules are written before the package arrives. The pre-receipt checklist should be short enough to run during supplier evaluation.

Before ordering, capture:

• the supplier page and access date;
• whether a current lot COA is visible or available on request;
• whether the product page states research-use-only language;
• whether the page avoids dosing, administration, treatment, cosmetic, body-composition, or testimonial claims;
• whether storage expectations are visible before purchase;
• whether shipping-temperature language is clear enough to interpret a delayed package;
• whether support can answer lot, COA, and storage questions;
• whether the material belongs to the intended non-clinical endpoint; and
• where the package will be received and who will inspect it.

This prevents a common failure: the buyer asks serious questions only after the vial is already sitting on the bench. If a supplier cannot explain basic lot, storage, and RUO documentation before purchase, the receiving SOP will probably end in clarification or quarantine after purchase.

The research peptide supplier scorecard is the pre-receipt tool. The receiving SOP is the post-delivery tool. Both should point to the same standard: evidence first, claims second, conversion last.

Three receiving gates#

A compact way to run the SOP is to treat it as three gates. Do not move to the next gate until the previous one has either passed or been formally escalated.

These gates keep the receiving process from becoming a box-checking ritual. A team can pass package condition and still fail documentation. It can pass documentation and still fail compliance. It can pass compliance and still be unsuitable for a specific research endpoint. The SOP should keep those decisions separate.

How to handle partial failures#

Not every receiving problem deserves the same response. A missing product-page screenshot is not the same as a cracked vial. A delayed package is not the same as an unknown product identity. The receiving SOP should define partial failures in advance.

Clarify when the issue is documentary and likely answerable: a lot-code mapping, storage wording, COA access problem, product-page mismatch, or support confirmation. The vial should remain separate until the answer is saved.

Quarantine when the issue could affect interpretation or chain of custody: warm package, wet box, unknown time outside storage, damaged insulation, unclear vial identity, visible material concern, missing COA, or conflicting storage instructions. Quarantine is a temporary evidence state, not a punishment.

Reject when the issue is not reasonably repairable: broken glass, compromised stopper, leakage, unexplained puncture, wrong material, no lot traceability after supplier contact, or supplier page language that makes the route inappropriate for a research-use-only file.

Reserve only when the lab has a written, lower-criticality category and can prevent the vial from entering meaningful endpoint work. Without a defined reserve category, "we will only use it for something minor" is just undocumented acceptance.

A good receiving SOP is not harsh for the sake of being harsh. It is consistent. It prevents a buyer from treating a cheap material strictly and an expensive material generously because the second decision feels more painful.

Category-specific receiving notes#

The same SOP applies across categories, but the record should emphasize different risks.

The table is not a recommendation to use any compound. It is a reminder that receiving files should match the research risk. A mitochondrial endpoint can be distorted by storage and contamination. A GLP-1 pathway material may need tighter temperature records. A skin-category page may require stricter claim screening. The SOP stays the same; the emphasis changes.

Internal review questions before signoff#

Before a receiving decision is signed, ask five questions:

1. Could another reviewer match the vial to the COA without asking us? If not, clarify or quarantine.
2. Could another reviewer reconstruct the first hour after delivery? If not, the chain-of-custody record is weak.
3. Did we preserve the supplier's storage instruction as it appeared on the access date? If not, capture it before the page changes.
4. Does the supplier page stay inside RUO boundaries? If not, fail the claim screen even if the analytical document looks good.
5. Does the final disposition match the evidence? If the evidence says uncertainty and the file says accepted, the SOP failed.

These questions are useful because they separate confidence from convenience. The receiver may feel confident because the vial looks normal. The documentation reviewer may feel confident because the supplier is familiar. The scientific reviewer may feel confident because the planned model is straightforward. The file should not rely on feelings. It should show the evidence.

Inventory reconciliation handoff#

A receiving SOP is only the first control point. After the lot is stored, run a periodic research peptide inventory reconciliation checklist so expected counts, physical vials, storage location, lot-matched COAs, quarantine status, and disposition records still agree.

FAQ#

References#

• International Council for Harmonisation. Q1A(R2): Stability Testing of New Drug Substances and Products.
• International Council for Harmonisation. Q1B: Photostability Testing of New Drug Substances and Products.
• Health Canada. Guidelines for Temperature Control of Drug Products during Storage and Transportation (GUI-0069).
• U.S. Food and Drug Administration. Visual Inspection of Injectable Products: Guidance for Industry.
• Centers for Disease Control and Prevention. Vaccine Storage and Handling Toolkit resources.
• World Health Organization. Temperature sensitivity of vaccines.
• Gervasi et al. Strategies for overcoming protein and peptide instability in biodegradable drug delivery systems. Advanced Drug Delivery Reviews.
• Awwad et al. Designing formulation strategies for enhanced stability of therapeutic peptides in aqueous solutions: a review. Pharmaceutics.

Bottom line#

A research peptide receiving SOP protects the first hour of the material record. It turns package condition, lot identity, COA capture, vial inspection, storage instruction, temperature-excursion review, RUO claim screening, and final disposition into one auditable workflow.

Use it before the vial enters inventory: verify the COA, inspect the storage and vial condition, log any temperature excursion, save the result in the batch documentation template, and apply the supplier scorecard before treating a supplier route as clean.