Shopify doesn't track lots. Every unit of a variant is the same to it, so 40 jars from Tuesday's batch and 40 from Friday's are 80 jars. Lot tracking means giving each batch a code, printing it on every unit, and recording which supplier lots went into the batch and which orders the batch went out in. Makers do it in a spreadsheet beside Shopify or with an app. Without it, a recall or a complaint means treating every unit ever sold as suspect.
The short version
- Shopify has no lot field and no per-batch counts.
- A lot code identifies one batch: often the date plus a product code.
- Print it on every unit and case.
- Record inbound: which supplier lots went into each batch.
- Record outbound: which orders or customers got each batch.
- Test it with a mock recall: can you name every customer for one batch in under an hour?
A lot code that works
| Format | Example | Reads as |
|---|---|---|
| Date and product | 261027-GJ | 2026-10-27, guava jam |
| Julian date and batch | 26300-1 | Day 300 of 2026, first batch |
| Running number | L1043 | Batch 1,043 |
Date-based codes tell you a batch's age at a glance. Keep them short enough to print on a small label. How to create lot numbers covers formats in depth.
Where to print the lot code
On every unit, where a customer can read it to you over the phone: the bottom of a jar, the back label, the crimp of a bag. On every case, larger, with the product name and best-before date. Use the same code on both, and on the packing list, so a shop can tell you which lot it has without opening a case. A date stamp or a label printer that adds the code at print time saves writing it by hand.
Workarounds in Shopify, and why they fail
- A variant per lot. Works for one or two, then clutters the store and the reports.
- A metafield with the current lot. Holds one lot per product, not one per unit.
- A note on each order. Typed by hand, searchable only by reading.
All three record something, but none can answer "who got lot 261027-GJ?" quickly.
A made-up example: a recall drill
Lāwaʻi Jam runs a drill: its pectin supplier "recalls" lot P-5512. With a lot log, the owner finds P-5512 went into two batches, 261013-GJ and 261020-PL, which went into 61 online orders and one café delivery. Customer list ready in 20 minutes. Without it, every jar made since the pectin arrived would be in question.
What to record
| Inbound | Batch | Outbound |
|---|---|---|
| Supplier, their lot, date received | Your lot code, date, recipe version | Order numbers or customers |
| Best-before of each ingredient | Quantity made, best-before | Quantities per lot |
Where this stops working
A spreadsheet lot log works only if every batch, delivery and order gets a line, every day. The outbound side is the hardest: matching Shopify orders to lots by hand. Shopify batch tracking and Shopify expiration dates cover the rest of the record.
How TaroStack does it
TaroStack for Shopify runs inside your Shopify admin and gives every batch a lot code, production date and best-before date. Receiving records the supplier's lot; batches record which lots they used, automatically; and orders record which lots they took, first-expired-first-out. A recall is one report, and timed traceability drills can be shown to a buyer. Lot labels print with GS1-128 barcodes. Free for 14 days.
