Peptide lot & batch tracking. Know what shipped.
Connect the received lot to the stored inventory and the outbound order. Define the records your research peptide business needs before the first shipment.

A SKU, a production lot and a shipment reference identify different things.
| Identifier | What it identifies | What it does not establish |
|---|---|---|
| SKU / variant | The product or sellable configuration. | A specific production batch or individual vial. |
| Supplier / manufacturer lot | A defined group of units associated with production. | A unique identity for every unit within the lot. |
| Warehouse receipt | The inbound delivery or receiving event. | The production lot, unless that relationship is separately recorded. |
| Order / shipment reference | The outbound transaction. | Which lot shipped, unless lot and quantity are captured. |
| Serial number | An individual identified unit. | Lot-level tracking does not automatically include serialization. |
Suppliers may distinguish “batch” from “lot,” or use the terms interchangeably. Preserve the original identifier and define the mapping to warehouse records. A receiving date or purchase-order number should not silently replace the source lot.
A lot code may need context. Do not assume “LOT-001” is unique across every supplier and product. Agree on the combination of product, supplier or manufacturer, source lot and any internal reference needed to avoid ambiguity.
Define the record at each warehouse event.
Identify the inbound lot
Record the product, supplier or manufacturer, original lot identifier, received quantity, applicable dates and the inbound reference. Review discrepancies before release.
Preserve identity and status
Record the storage location and relevant status. Transfers, holds and count adjustments should preserve the link to the affected SKU and lot.
Record what left
Where required, capture the lot and quantity selected for each shipment, along with the order reference and shipment date. Confirm how that report is retrieved.
A system can hold lot information at receiving while still deducting outgoing stock only at SKU level. Ask the team to demonstrate the full path before describing the program as shipment-level traceability.
Trace one SKU through two lots and two shipments.
Example SKU RP-EXAMPLE begins with 120 units from Lot A and 80 from Lot B. The program permits mixed-lot orders. These numbers illustrate the record structure; they are not a live account or a product specification.
| Shipment | Lot A quantity | Lot B quantity | Total shipped |
|---|---|---|---|
| EX-100 | 3 | 0 | 3 |
| EX-101 | 2 | 1 | 3 |
| Total | 5 | 1 | 6 |
Start with an order
“Which lot supplied EX-101?”
The record shows 2 units from Lot A and 1 from Lot B. A single lot field with no quantities would lose part of that detail.
Start with a lot
“Where did Lot B go?”
The example shows 1 unit in EX-101 and 79 units remaining. The lot-to-shipment report should reconcile with the stock balance.
Single-lot instructions change the allocation. If a recipient requires one lot, make that an explicit order rule. Do not assume that every program or buyer accepts a mixed-lot shipment.
Map the COA to the lot that actually shipped.
A document attached to the product listing may describe a different batch from the units in a particular shipment. Define the association using the product, supplier or manufacturer, lot and document version.
- Keep the source lot identifier and supplied document reference together.
- Define who reviews the association and supplies updates.
- Preserve the history when a document is corrected or replaced.
- Confirm how an authorized person retrieves the document associated with a shipment.
A document link or QR code is an access method, not proof that the contents match the vial or that the underlying test is valid.

A scannable label helps only when the right data is recorded.
Agree on readable text, code content and scanner compatibility. Confirm whether the barcode or QR identifies a SKU, a lot, a serialized unit or a document link. Those functions are different.
Specify the events at which identifiers are captured—receiving, location movement, picking or shipment confirmation—and the response when a code cannot be read. Manual entry and corrections need an agreed review process too.
Rapid can review applicable labeling and packing requirements. Do not assume unique-vial serialization, every-unit scanning or a particular verification method is included without confirming the scope.
Lot identity and stock-selection rules work together.
FIFO / FEFO
FIFO follows receiving sequence; FEFO prioritizes the earliest applicable expiration date. Neither replaces a record of the lot and quantity actually shipped.
Held inventory
Define how affected units are excluded from normal picking, who reviews the issue and who authorizes release or disposition.
Unresolved identifiers
Keep the source records and investigate a missing, conflicting or unreadable lot. Do not guess a production lot to make inventory available.
Split shipments, partial fills, repacking and stock adjustments can change the movement record. Define how each is recorded. Standard research-peptide returns inspection, restocking and resale should not be assumed; agree on disposition instructions separately.

Traceability records movement. It does not certify the product.
Lot records do not independently establish identity, purity, COA validity, product marketability or suitable storage conditions. Those matters require their own evidence and review.
Use supplier specifications for each product’s storage and transit needs. Rapid can support 2–8°C refrigerated storage where the approved program calls for it. A lot number is not a temperature log, and a carrier service name is not an end-to-end temperature guarantee.
Explore storage requirements →
Review cold-chain shipping considerations →
Run a two-way traceability test.
Use a representative SKU with two known lots and agreed test quantities. Define the expected records and who will review the result.
- Reconcile receiving. Compare the expected lots and quantities with the received stock and documents.
- Fulfill test orders. Include the program’s normal lot rule and, if allowed, a mixed-lot or split-shipment scenario.
- Trace an order back. Retrieve the product, lot, quantity and inbound association for a shipment.
- Trace a lot forward. Retrieve its relevant shipment references, shipped quantities and remaining inventory status.
- Reconcile and review. Compare receipts, shipments and other movements, then resolve differences before launch.
Agree on access and response expectations. Specify who can request reports, how information is exported and how long it is retained. Do not treat an example report or a software feature name as a commitment to unlimited retention or a guaranteed response time.
Decide where the lot record lives.
A storefront may manage the sold SKU while the warehouse records the picked lot. Confirm which system is authoritative for each field and whether lot details return to the store, remain in warehouse reporting or require an export.
Rapid supports Shopify, WooCommerce and other supported order systems. The connection method and data scope need to be confirmed for your program. An order import and tracking update do not automatically establish lot-data synchronization.
Bring requirements the warehouse can demonstrate.
| Requirement | What to provide or confirm |
|---|---|
| Identity | SKU catalog, supplier or manufacturer and source lot format; explain any reused codes. |
| Opening stock | Units by SKU, lot and status, with locations and applicable expiration data. |
| Picking rules | FIFO or FEFO where appropriate, single-lot restrictions and mixed-lot acceptance. |
| Documentation | COA associations, document versions and responsible contacts. |
| Shipment reporting | Required order-to-lot and lot-to-shipment fields, exports and report access. |
| Exceptions & retention | Hold/release authority, corrections, disposition, retention period and applicable costs. |
For quantities, stock availability and cycle counts, use the inventory management guide. For larger business orders, review bulk and wholesale fulfillment. For a new warehouse handoff, see the growth and migration guide.
Make the required record part of the operating plan.
Share your SKU and lot structure, document requirements, order profile and reporting needs. Rapid will review the inventory workflow, supported connections and scope for your program.
Prefer to talk first? Book a 30-minute call.
Peptide lot and batch tracking FAQs.
What is peptide lot and batch tracking?
It is the use of lot or batch identifiers to distinguish groups of research peptide inventory within a product SKU. A traceable fulfillment workflow preserves those identifiers through receiving, storage, picking and shipment records so the business can investigate where particular stock came from and where it went.
How is a lot different from a SKU or serial number?
A SKU identifies a product or sellable variant. A lot identifies a group of units associated with a production batch. A serial number identifies an individual unit. Lot-level tracking does not automatically provide unique-vial serialization.
Do lot and batch always mean the same thing?
Suppliers may use the terms differently. Preserve the manufacturer’s or supplier’s original identifier and define how it maps to the warehouse record. Do not assume that a receiving date, purchase order or internal warehouse reference is the original production lot.
Can Rapid show which lot shipped on each order?
Rapid supports lot and batch workflows where required by the program. Confirm whether the configured picking process captures the lot and quantity on each shipment, how mixed-lot orders appear in reporting and how the records can be exported. Lot organization at receiving alone is not proof of order-level traceability.
Are barcodes required for lot tracking?
A barcode or QR code can help capture an identifier, but its presence does not establish the data it contains or prove that staff record it at shipment. Agree on label content, scanner compatibility, readable text and the events at which identifiers are captured.
How should COAs be linked to peptide lots?
Associate each supplied COA with the correct product, supplier or manufacturer, lot identifier and document version. Define who reviews the association and how corrections are recorded. A COA attached only to a product SKU may not identify the document relevant to a shipped lot.
Can one order contain more than one lot?
It can if the program and recipient requirements allow it. The shipment record should distinguish the quantity from each lot. If a customer requires a single lot, make that restriction explicit before allocation and picking.
Does FEFO replace lot tracking?
No. FEFO is an expiration-based stock-selection rule; lot tracking records the inventory identity. FIFO and FEFO can guide allocation, but a separate record is still needed to identify the lot and quantity shipped. Holds and documented restrictions take priority over normal rotation.
What happens if a lot label is missing or does not match the documents?
Hold the affected inventory from normal fulfillment under the agreed exception process while the discrepancy is reviewed. Keep the source records and obtain authorized instructions. Do not guess a production lot or assign a false match simply to make the stock available.
Does Shopify automatically record the lot shipped?
Do not assume it does. Storefront product data and warehouse lot records serve different purposes. Confirm which system records the picked lot, whether that detail returns to the store and where the shipment-level report will be retained.
How long are lot and shipment records retained?
Retention depends on the service agreement, reporting setup and the brand’s applicable requirements. Specify the required period, access, exports and any additional costs during onboarding. A lot-tracking feature alone does not establish a particular retention period.
Does lot tracking prove peptide quality or regulatory compliance?
No. Lot tracking organizes identity and movement records. It does not independently verify product identity, purity, storage suitability, COA validity or regulatory status. Those matters require their own evidence and review by the responsible parties.
How can I test a fulfillment provider’s lot traceability?
Use a representative SKU with two known lots. Reconcile receiving, fulfill test orders under agreed lot rules, then request an order-to-lot report and a lot-to-shipment report. Compare shipped quantities and remaining stock, and agree on report access and response expectations.
Connect lot records to the wider fulfillment program.
Reference: GS1’s explanation of traceability describes identification and the recording and sharing of supply-chain information. The worked example and test checklist here are Rapid’s practical guidance, not a claim of GS1 certification.
Published by Rapid Fulfillment for research-use logistics planning. Service capabilities depend on product acceptance, configured workflows and agreed terms. Brand owners retain responsibility for products, documents, labels, claims and applicable regulatory obligations.