The packing table does not care about your marketing stack. It cares how many sticker variants sit in the pigeonholes, how long an operator hunts for “the blue one for SKU 1842,” and what happens when the wrong code goes on the right box.
Brands launching a post-purchase or instructions QR usually ask the 3PL: unique code per SKU, or one code across the catalogue? For most programmes the cheaper, safer answer is one generic dynamic QR. Unique codes are for exceptions, not the default PO.
(The same question shows up in consumer programmes; Swapt’s brand-side write-up argues for a generic code plus a “which product?” page. Below is the 3PL labour version of that decision.)
What “one generic code” means on the floor
- One SKU in the 3PL’s consumables inventory: a roll or stack of identical labels
- Apply rate that does not depend on the picker’s product knowledge
- Reorder is “another box of the same sticker,” not 40 line items with min-order quantities
- If the brand changes the landing page, nobody reprints — that is what a dynamic QR is for
The usual objection is “then we will not know what they bought.” That is a landing-page problem, not a sticker problem. Ask “which product?” or scan the carton barcode you already apply for the carrier. You get ASIN/SKU-level data without SKU-level sticker complexity.
When per-SKU codes are justified
Use unique codes when at least one of these is true:
- The destination must be different with no extra tap (hero SKU, regulated IFU, language-locked leaflet)
- You are encoding lot or serial and that data must travel with the unit after it leaves the building
- The brand is running a promotion that would be fraud-prone if every pack opened the same offer URL
- You already have print-and-apply automation that consumes a unique value per row (and the 3PL is paid for the extra SKU)
If none of those apply, you are paying for pigeonholes.
Lot-level is a third option people skip
Per-SKU is not the same as per-lot. Food, cosmetics, and devices often need lot and expiry on the scan, not a marketing URL. That payload belongs on the inbound/carton QR the warehouse uses, not necessarily on a consumer sticker.
- Consumer / review / refill URL → generic dynamic code
- Traceability → lot QR or GS1 Digital Link with AI 10/17 (lot/expiry) generated at packing or received from the brand
Mixing those two jobs onto one tiny sticker is how you get unreadable codes and angry pickers.
3PL quoting: price the variants, not the “QR project”
When a brand sends a 200-SKU sticker matrix, quote:
- Extra location or tote for label variants
- Apply time vs a single roll
- Mis-apply risk (wrong IFU, wrong promo) and who eats the chargeback
- Who reprints when a campaign URL dies
A generic dynamic code collapses (1)–(3). (4) is a hosting policy: if the generator turns codes off when the brand stops paying, the 3PL is left with dead labels on client stock. Prefer a host whose redirects survive cancel, or insist the brand uses a domain they control.
A practical decision tree
- Is the scan for consumers (how-to, warranty, review)? → One generic dynamic QR.
- Must the first screen be product-specific with zero extra tap? → Per-SKU, and the 3PL needs a pick-face system for the right roll.
- Is the scan for warehouse / recall? → Lot or location QR; do not invent 4,000 consumer SKUs to solve inbound.
- Are POs bursty? → Front-load a year’s generic stickers. You cannot do that sanely with 80 variants.
Print a sample generic code here, then duplicate it in bulk from a one-row spreadsheet when you are ready for a roll.