Research Peptide Record Retention Schedule for Canadian Labs

Quick answer: what records should a Canadian RUO peptide buyer keep?#

A research peptide record retention schedule should keep the full story of a material, not just the receipt. For a Canadian research-use-only peptide lot, that means preserving the documents that let someone later answer five questions:

1. What exactly was ordered and received?
2. Which lot or batch was involved?
3. What evidence supported identity, purity, storage, and condition?
4. Who handled, moved, opened, aliquoted, quarantined, or disposed of the material?
5. Why was the lot accepted, questioned, rejected, or excluded from a research workflow?

The practical record set includes the order confirmation, invoice, shipping record, import or customs notes when relevant, supplier product page snapshot, lot-matched certificate of analysis, analytical traces or method notes when available, vial photos, receiving inspection, storage log, temperature excursion records, chain-of-custody log, aliquot map, deviation log, supplier support emails, RUO claims review, and final disposition note.

That sounds like a lot of paperwork until a question appears months later. A vial label does not match a COA. A freezer record shows an unexplained temperature excursion. A supplier updates a product page and removes the old lot language. A researcher tries to compare a BPC-157 lot with a later BPC-157 listing. A GLP-adjacent partner asks whether the source file, analyst report, and custody trail were preserved. A content editor links to a supplier page and needs to prove the page was treated as research-use-only, not as a human-use recommendation.

Retention is the difference between "we think this was fine" and "here is the evidence bundle we reviewed." This article gives Canadian labs, procurement reviewers, and editors a copy-ready schedule for that evidence bundle. It is research-use-only. It is not medical advice, legal advice, regulatory clearance, dosing guidance, administration guidance, treatment guidance, import advice, tax advice, or a substitute for institutional policy.

Use it with the research peptide batch documentation template, supplier response log template, peptide COA verification checklist, storage and vial inspection checklist, peptide reconstitution guide, chain-of-custody log, deviation log template, and the documentation audit trail checklist. Those pages describe or connect the records. This page decides how long the records survive and when the archive should be reviewed.

Why retention matters in RUO peptide work#

Peptide records are easy to under-save because many purchases look operationally simple. A small box arrives. The vial is labelled. The product page says purity. A COA exists somewhere. The material goes into a freezer or cold room. Everyone assumes the context is obvious.

The context is rarely obvious later.

Research peptides sit at the intersection of supplier marketing, analytical chemistry, cold-chain handling, non-clinical biology, and Canadian compliance risk. Health Canada has warned consumers about unauthorized injectable peptide products promoted online for anti-aging, weight loss, bodybuilding, athletic performance, injury recovery, sleep, and similar outcomes. Northern Compound's editorial standard is deliberately different: ProductLink paths are documentation routes for research-use-only materials, not personal-use recommendations.

That distinction has to be visible in the archive. If a record bundle contains a careful COA review but also saves a screenshot full of consumer-result claims with no claims-audit note, the future reviewer sees a messy file. If a supplier updates the page later, the team may not know which representation existed at the time of review. If a lot is later excluded because storage history was weak, the decision can disappear unless the deviation and final disposition note are retained beside the batch file.

Retention also protects science. A peptide lot can affect interpretation even when the biological model is sound. Purity, identity, fill amount, salt form, storage condition, freeze-thaw history, light exposure, shipping delay, solvent choice, aliquot mapping, and custody gaps can all become hidden variables. A result that looks biological may be partly logistical. The archive is how a lab reconstructs that possibility instead of guessing.

Finally, retention protects editorial quality. Northern Compound publishes supplier and compound guides that route readers to live product pages such as Semaglutide, TB-500, GHK-Cu, and Selank. Those links preserve attribution, but the link itself is never proof of quality. The editorial record should show that the page was assessed as a research procurement destination, with RUO language, COA availability, and claim boundaries reviewed at the time of publication or refresh.

The retention principle: keep the evidence for the decision, not just the file#

A weak archive asks, "Do we have a document?"

A stronger archive asks, "Can someone reproduce the decision we made from the documents we kept?"

That difference matters. A COA PDF with no lot match, no download date, and no connection to the order is only partial evidence. A receipt with no product page snapshot does not show which specifications were represented. A storage log with no vial ID does not prove which material was stored under which condition. A support email that says "yes, it is pure" but does not identify the lot or method is not much help.

Use four retention rules:

1. Retain the source record. Keep the original PDF, email, screenshot, label photo, tracking page, or exported log when possible. Do not rely only on a summary note.
2. Retain the interpretation. Write down why the record was accepted, questioned, rejected, or escalated. A future reviewer needs the decision trail, not just the raw file.
3. Retain the relationships. Connect the COA to the lot, the lot to the vial, the vial to custody events, custody events to storage history, and storage history to any study or content decision.
4. Retain the exception. If something went wrong, keep the deviation record beside the ordinary batch file. Exceptions are the records most likely to matter later.

The schedule below is intentionally conservative because RUO peptide records are often used outside a formal quality system. A small lab, editorial team, or supplier reviewer may not have a validated document-management platform. That makes naming, folder structure, access control, backups, and review cadence more important, not less.

Copy-ready retention schedule#

Use this table as a starting point. Replace the retention periods with stricter institutional, sponsor, GLP, accounting, import, privacy, safety, or contractual rules when those apply.

The table uses seven years as a practical conservative default for many business and research files, not as a universal law. A regulated GLP study, sponsor contract, institutional policy, tax rule, privacy requirement, or safety file may require something different. When a stricter rule exists, use it. When no formal rule exists, do not default to deletion just because a material is small or labelled research-use-only.

The three-bucket archive model#

A peptide archive becomes easier to maintain if every record falls into one of three buckets.

Bucket 1: source evidence#

Source evidence is the record as close to the original event as possible. Examples include supplier PDFs, order confirmations, courier tracking pages, label photos, unopened-vial photos, receiving forms, freezer logs, support emails, and downloaded COAs.

Do not edit these files casually. If a file must be annotated, keep the original and create a reviewed copy. If a webpage is important, save a dated PDF or screenshot instead of assuming the live page will remain unchanged. Supplier product pages can change, COA links can rotate, and listings can disappear. The source file should show what was visible when the decision was made.

Bucket 2: decision records#

Decision records explain what the team concluded from the source evidence. They include acceptance notes, rejection notes, quarantine decisions, supplier scorecard updates, deviation outcomes, and article refresh decisions.

This bucket is where a lot of weak archives fail. Teams keep raw evidence but forget the interpretation. Six months later, nobody remembers whether a COA was accepted because the method was adequate, because the lot matched, because the supplier confirmed a missing detail, or because the material was not used in a sensitive endpoint. A one-paragraph decision note can save hours of reconstruction.

Bucket 3: indexes and relationships#

Indexes connect records. The batch file index should point to the COA, receiving record, storage log, custody log, deviations, supplier messages, and final disposition. The article file should point to the supplier review, claims audit, ProductLink targets, references, and refresh date. The supplier scorecard should point to the lots that influenced the score.

This bucket is not glamorous. It is the reason the archive works.

Folder structure for a small Canadian lab or editorial team#

A simple folder structure beats a clever one that nobody uses. The goal is to let a future reviewer find a lot file even if the original buyer, editor, or lab owner is unavailable.

/peptide-records
  /suppliers
    /supplier-name
      supplier-scorecard.md
      correspondence-index.md
  /lots
    /YYYY
      /SUPPLIER_COMPOUND_LOTID
        00-index.md
        01-order-and-receipt/
        02-product-page-snapshot/
        03-coa-and-analytics/
        04-vial-and-storage/
        05-chain-of-custody/
        06-deviations-and-disposition/
        07-editorial-or-study-links/
  /templates
    batch-documentation-template.md
    coa-review-template.md
    custody-log-template.md
    deviation-log-template.md
    retention-schedule.md

Use stable names. Include the supplier, compound, and lot ID when available. Avoid vague folders like new peptides, screenshots, misc, or old orders. If the lot ID is missing, that absence is itself a documentation gap. Name the folder with the best available identifier and add a note explaining what is missing.

For an editorial site like Northern Compound, the same pattern applies to content decisions. A supplier or product page should not be treated as a permanent citation unless the article has a record of what was checked. A ProductLink to Tirzepatide or MOTS-c should be supported by a current-page review, not by a memory of a previous page state.

File naming rules that prevent archive rot#

Good retention fails when files cannot be found. Use boring, sortable names.

The file name should answer date, supplier, compound, lot, and record type. It does not need to be poetic. It needs to be searchable.

What to keep for each lot#

The lot file is the core unit. A product category page can be useful, but research interpretation happens at the lot level. Different lots can have different COAs, test dates, storage history, packaging, support responses, and deviations.

1. Procurement and product snapshot#

Keep the order confirmation, invoice, shipping address context, supplier name, product name, SKU, fill amount, and product URL. Save a dated product page snapshot showing the exact representation reviewed at the time of purchase or editorial refresh. If the page includes a research-use-only statement, storage language, COA link, or claim language, preserve it.

If the page uses consumer-style wording, do not silently ignore it. Add a claims-audit note. The research-use-only compliance checklist exists for this reason. A ProductLink can preserve attribution, but it cannot sanitize a page whose general impression is personal use.

2. COA and method evidence#

Keep the COA as downloaded, plus any traces or method pages the supplier provides. Record whether the COA is lot-specific, whether the compound name matches the label, whether the test date is visible, whether the method is named, whether identity and purity are both addressed, and whether the issuer is clear.

Use the COA verification checklist for the review itself. The retention schedule should then preserve both the COA and the review outcome. If the COA is generic, stale, mismatched, or missing method context, retain the problem note and any supplier response. Do not overwrite the original weak record with a later replacement without keeping the timeline.

3. Receiving inspection#

Keep photos of the outer package when relevant, the cold-pack state, vial label, seal, powder appearance, damage, condensation, missing paperwork, and any mismatch between the product page, label, and COA. The storage and vial inspection checklist is the working tool; the archive keeps the result.

A receiving file should be contemporaneous. A note written three weeks later is better than nothing, but it should be marked as late. The point is not to shame the team. The point is to preserve the reliability of the record.

4. Storage and temperature history#

Keep the initial storage location, storage condition, freezer/fridge identifier, temperature records when available, move records, thaw events, light exposure concerns, and any temperature excursion log. For small teams, even a simple monthly export plus deviation notes is better than no history.

Storage language matters because peptide stability is context-dependent. An unopened lyophilized vial is not the same record as a prepared working solution. A cold shipment received promptly is not the same record as a delayed warm package. A vial used in sensitive assay work deserves a stronger storage trail than a vial held only for preliminary screening. When a lot is prepared into solution, archive the solvent, volume, concentration calculation, label text, storage assumption, and discard logic using the reconstitution documentation handoff checklist instead of leaving those details in bench notes.

5. Chain of custody and aliquot mapping#

Keep every event that changes who controls the material, where it is stored, whether it has been opened, and how child aliquots connect to the parent vial. A custody log does not need to be dramatic. It needs to answer who, what, when, where, and why.

For aliquots, keep the parent vial ID, child vial IDs, preparation date, storage location, disposition, and any internal concentration note needed to interpret later records. This article does not provide preparation, dosing, administration, or protocol instructions. It only describes the documentation relationship between parent and child records.

6. Deviations and disposition#

Keep every meaningful exception. Examples include late delivery, missing COA, lot mismatch, damaged label, unclear storage condition, weak support response, page claims that conflict with RUO framing, unexplained custody gap, freezer excursion, or decision to exclude a material.

The final disposition is the decision layer. Accepted, accepted with limitations, quarantined, excluded, replaced, returned, disposed, or supplier-follow-up-open are all different outcomes. The archive should show which one happened and why.

What to keep for editorial and SEO pages#

Northern Compound is an editorial funnel, not a lab notebook. But content records still matter because the site routes qualified readers toward research supplier pages. A high-intent buyer guide can become risky if the article's archived rationale is weak.

For each article or linkable asset that references supplier/product paths, keep:

• the published MDX file or version-control commit;
• title, slug, target keyword, public category, and article type;
• ProductLink slugs used at publication;
• confirmation that dead slugs were avoided or allowed to fall back safely;
• internal links added from older posts;
• outbound reference list;
• compliance review notes;
• last refresh date;
• reason for any material update;
• outreach file if the article is a linkable asset.

This record helps future editors avoid accidental duplication, raw Lynx product URLs, outdated claims, and dead product paths. It also makes refresh work easier. If an article routes to Cagrilintide, Retatrutide, or 5-Amino-1MQ, the next editor should know when that route was last checked and what claim boundary applied.

Annual review workflow#

A retention schedule is only useful if someone reviews it. Use a lightweight annual archive review.

1. Export a list of lot folders, supplier folders, article files, and open deviations.
2. Confirm every active lot has an index file, COA review, receiving record, storage/custody status, and disposition status.
3. Confirm every disposed or excluded lot has a final decision note.
4. Check whether any supplier scorecard needs an update because of repeated documentation, storage, claims, or support issues.
5. Check whether any article still links to a page whose product availability, claim language, or COA path has changed.
6. Mark records eligible for deletion only if no legal, institutional, sponsor, privacy, tax, import, safety, publication, or dispute hold applies.
7. Record who reviewed the archive, what was changed, and what remains open.

Do not delete records just because a retention date arrived. A retention date is a review trigger, not an automatic shredder. If a lot is linked to published data, supplier dispute, unresolved deviation, article claim, or ongoing procurement decision, preserve it until the reason to hold it is resolved.

Disposal and deletion notes#

Deletion is a controlled event. The record of deletion may need to outlive the deleted files.

Before destroying any peptide record, ask:

• Is the material still present?
• Is any child aliquot still present?
• Is the record linked to an internal or published result?
• Is the record linked to an active supplier scorecard?
• Is the record linked to an article, buyer guide, or outreach asset?
• Is there an unresolved deviation, temperature excursion, lot mismatch, or supplier dispute?
• Does an institutional, sponsor, accounting, import, privacy, safety, or legal rule require longer retention?
• Would deleting the record make a future claim impossible to verify?

If the answer to any of those questions is yes, keep the record. If deletion is appropriate, record the file set, date, approver, method, and reason. For physical records, use secure disposal. For digital records, follow the organization's retention and backup policy rather than simply deleting one local copy while cloud backups persist indefinitely.

Common retention failures#

Failure 1: keeping only the COA#

A COA is important, but it is not the entire record. Without order context, lot match, receiving condition, storage history, custody, and final decision, the COA becomes an isolated artifact. It says something about a sample or lot, but not necessarily about the material used or reviewed.

Failure 2: relying on live webpages#

Supplier pages change. COA links change. Product titles change. Claims become more cautious or less cautious. A live page is not a stable archive. Save the page state that informed the decision.

Failure 3: mixing supplier-level and lot-level evidence#

A supplier can have a strong scorecard and still ship a weak lot. A lot can have a strong COA and still fail receiving because the package arrived warm or the label was damaged. Keep supplier-level, product-level, and lot-level evidence connected but distinct.

Failure 4: deleting exceptions first#

Teams sometimes clean archives by deleting the messy files. That is backwards. Deviations, support emails, mismatch notes, and exclusion decisions are exactly the files most likely to explain a later problem.

Failure 5: treating RUO as a reason to save less#

Research-use-only status does not make evidence less important. It makes the boundary more important. The archive should show that the material was handled and described as RUO, not marketed or interpreted as a personal-use product.

Copy-ready index template#

Paste this into 00-index.md for each lot folder.

# Research Peptide Lot Archive Index

Material name:
Supplier:
Product page URL:
ProductLink slug if used editorially:
Lot/batch ID:
SKU/fill amount:
Order date:
Receipt date:
Archive owner:
Retention review date:
Final disposition:

## Source evidence
- Order confirmation:
- Invoice/receipt:
- Product page snapshot:
- Shipping/tracking:
- Receiving photos:
- COA:
- Analytical traces/method notes:
- Supplier correspondence:

## Review records
- COA review result:
- Receiving inspection result:
- Storage/vial inspection result:
- RUO claims audit result:
- Supplier scorecard impact:

## Movement and condition
- Initial storage location:
- Current storage/disposition:
- Temperature records:
- Chain-of-custody log:
- Aliquot/parent-child map:
- Deviations:

## Decision
Accepted / accepted with limitations / quarantined / excluded / disposed / replaced / follow-up open:
Decision rationale:
Reviewer:
Date:

This index is intentionally plain. It should be readable without special software and easy to migrate if the archive moves from one storage platform to another.

Copy-ready retention policy paragraph#

Use this paragraph in an internal SOP, procurement note, or editorial operating doc:

Research-use-only peptide records are retained as evidence bundles, not isolated documents. Each lot archive should preserve procurement records, product-page state, lot-matched COA and analytical evidence, receiving inspection, storage history, chain-of-custody events, aliquot relationships, deviations, supplier correspondence, RUO claims review, final disposition, and an index connecting those files. The default review period is life of lot plus seven years unless a stricter institutional, sponsor, GLP, accounting, import, privacy, safety, publication, dispute, or legal requirement applies. Retention expiry is a review trigger, not automatic destruction. Deletion requires documented approval and confirmation that no active hold applies.

ProductLink and supplier-record considerations#

When an article references a live product path, keep the editorial and supplier records aligned. For example, a recovery article may route readers to BPC-157, TB-500, or BPC-157/TB-500 blend. A weight-management research page may reference Semaglutide, Tirzepatide, or Retatrutide. A skin or copper-peptide article may reference GHK-Cu.

The archive should never imply that a ProductLink is a recommendation for human use. The link is a route to inspect current supplier information with attribution. A retained supplier record should support that framing by preserving the COA path, RUO statement, storage language, product identity, and claims-audit note.

Avoid raw product URLs in MDX. Use ProductLink components so attribution parameters remain consistent and unavailable product slugs can fall back safely. If a product slug is known to be dead, do not add it as a live product recommendation. Keep the editorial file focused on research documentation rather than trying to force a commercial route.

How this schedule connects to other Northern Compound assets#

This page is the archive map. The surrounding assets are the working forms.

If a team uses only one of these assets, use the batch template. If a team uses two, add the COA checklist. If a team wants the archive to survive staff changes, add this retention schedule.

Record-hold decision tree#

Use a record hold when ordinary retention review is not enough. A hold means the archive owner pauses deletion because a specific reason exists to preserve the evidence. The hold can be informal for a small RUO procurement archive, but it should still be written down.

Start with the question: would deleting this record make a current or future decision harder to defend? If yes, hold it.

A hold should have an owner and a review date. Without an owner, a hold becomes clutter. Without a review date, it becomes permanent by accident. Permanent retention can be appropriate for serious deviations, published work, or externally reviewed studies, but it should be an explicit choice.

Example scenarios#

Scenario 1: product page changed after publication#

An article originally linked to a supplier page because the page showed clear RUO language, a visible COA route, and conservative product identity. Six months later, the live page changes. The new page might have a different title, new claims, new storage language, or a different COA link.

The archive should answer what Northern Compound reviewed at publication time. Keep the original page snapshot, publication commit, claims-audit note, ProductLink slug, and refresh decision. If the live page becomes riskier, update the article or product route. Do not rely on memory and do not pretend the current page is what existed when the article was written.

Scenario 2: COA is replaced by a newer certificate#

A supplier replaces a COA PDF with a newer certificate. That can be good, but it can also erase the evidence that supported an older lot. Keep both files with download dates. Mark which lot each certificate supports. If the newer certificate belongs to a different lot, do not let it overwrite the original decision record.

This is especially important for recurring product categories such as Semaglutide, Tirzepatide, BPC-157, or GHK-Cu, where buyers may assume the current page describes the historical order. The retention schedule should keep the lot history separate from the catalogue page.

Scenario 3: a vial is excluded from a sensitive endpoint#

A lab receives a peptide with matching order and COA records, but the package arrives warm and the supplier's storage language is ambiguous. The team decides not to use the lot in a sensitive endpoint. The material may still be physically present, but its study disposition is excluded.

That decision should not live only in a chat thread. Keep the receiving record, temperature note, supplier response, deviation log, final disposition, and archive index update. The value of the archive is not only proving that good lots were accepted. It is also proving that questionable lots were slowed down.

Scenario 4: a child aliquot is found without a parent link#

A freezer inventory review finds a child vial labelled only with compound name and date. The parent lot is unclear. The archive owner should mark it as an identity/custody gap, search for parent-child evidence, and record the result. If the link cannot be reconstructed, the material should not be treated as equivalent to a documented lot.

Retain the late-entry note even if the material is disposed. The note prevents the same gap from being rediscovered later with no context. It can also inform a preventive action: require parent ID, child ID, preparation date, storage location, and custodian on every aliquot label.

Scenario 5: an editor wants to remove old outreach files#

Outreach files are not lab records, but they still matter for linkable assets. They show what claims were made to potential backlink targets. If an outreach pitch described an asset as a documentation checklist and explicitly avoided dosing/treatment claims, keep that file with the article record. If the article is later refreshed, the outreach file helps ensure the public pitch and live page still match.

For this article, the outreach record belongs beside the asset because the page is designed for backlinks from lab operations, GLP-adjacent, LIMS/ELN, and research procurement audiences. It should not be pitched to peptide-use communities or consumer wellness sites.

Minimum metadata for every retained record#

Every retained file should carry enough metadata to stand alone if it is separated from the folder. The minimum is:

• record title;
• date captured or created;
• person or role who captured it;
• supplier or source;
• compound/material name;
• lot or batch ID when available;
• related order, article, or study ID;
• reason the record was kept;
• retention review date;
• access or confidentiality note where relevant.

Metadata is not bureaucracy for its own sake. It is how a folder of PDFs becomes a usable archive. A COA named coa.pdf inside a folder called old stuff is fragile. A COA named with supplier, compound, lot, and download date, referenced from an index with a reviewer note, is evidence.

Access control and backup notes#

Retention also means protecting records from accidental change, loss, or inappropriate access. A small team does not need an enterprise quality system to follow basic archive hygiene.

Use these controls where practical:

1. Keep original evidence in a read-only or restricted folder after review.
2. Store working notes separately from original files.
3. Back up archives to at least one controlled location.
4. Avoid leaving sole copies in personal inboxes or local desktops.
5. Limit access to records that contain personal, payment, shipping, or supplier-confidential information.
6. Record archive migrations so folder paths do not break silently.
7. Test restoration occasionally; a backup nobody can restore is not a backup.

For editorial work, Git history helps but does not replace supplier evidence. The repository can show what Northern Compound published. It may not show the product page, COA, supplier email, or claims-audit screenshot that informed the decision. Keep those in the asset archive or supplier review folder.

FAQ#

References and further reading#

• Health Canada, non-clinical laboratory study data and GLP guidance — Canadian context for non-clinical studies, GLP principles, recording, archiving, and reporting when data supports drug submissions.
• Standards Council of Canada, Good Laboratory Practices — Canadian GLP monitoring and accreditation context based on OECD principles.
• OECD, Establishment and Control of Archives that Operate in Compliance with the Principles of GLP — archive-control guidance for GLP environments; useful as a stricter reference point even when an RUO buyer is not claiming GLP compliance.
• FDA, Data Integrity and Compliance With Drug CGMP Questions and Answers — explains data integrity expectations including attributable, legible, contemporaneous, original, and accurate records in a regulated-manufacturing context.
• Health Canada, policy on collection and retention of records related to health product compliance and enforcement — useful Canadian reference for record collection, handling, retention, and disposal concepts in health-product compliance contexts.
• Government of Canada Digital Privacy Playbook, When to keep and delete — plain-language retention and disposition planning reference for personal-information contexts; useful for thinking about deletion rationale and disposal plans.

Bottom line#

A research peptide archive should let a future reviewer reconstruct the lot, the evidence, the handling history, the exceptions, and the decision. If the archive cannot do that, the team has kept files but lost the record.

For Canadian RUO peptide work, the practical move is simple: build one lot folder, keep original evidence, write decision notes, connect the records with an index, review the archive annually, and treat deletion as a controlled event. That standard is not flashy. It is what keeps supplier claims, COA evidence, storage history, chain of custody, and editorial compliance from becoming folklore.