A useful bulk-order label should tell a receiver what the product is, which packaging level they are holding, how many units that level contains, and which batch or order record it belongs to. Put product identity and quantity on every level that may be ordered, stored, picked or received separately.
Do not make one number do three jobs. A SKU identifies a product configuration; a batch or lot identifies a production group; a case or logistic-unit identifier identifies a particular handled unit. Clear labels keep those roles separate.
Quick answer
- Name the packaging level: pack, inner pack, case or pallet.
- State quantity as a hierarchy, such as 10 cones × 20 packs = 200 cones per case.
- Keep the SKU, product revision and stated dimensions consistent across documents.
- Connect batch or lot information to the exact product identifier it describes.
- Recheck labels when pack quantity or case configuration changes.
| Packaging level | Quantity field | Identity field | Useful traceability field |
|---|---|---|---|
| Saleable pack | Cones per pack | Product name and SKU | Batch/lot when used |
| Inner pack | Saleable packs per inner | Inner-pack identifier | Batch/lot and pack date if applicable |
| Shipping case | Inners or packs per case; total cones | Case-level product reference | Order, batch/lot and case number |
| Pallet or logistic unit | Cases per pallet; total cases | Logistic-unit reference | Shipment and destination references |
Start with the packaging hierarchy
A 200-count offer can be one package containing 200 loose units, 20 packs of 10, or another defined arrangement. The total may be identical while the receiving, storage and picking work is not.
Write the hierarchy from the smallest meaningful level upward:
- cones per saleable pack;
- saleable packs per inner pack;
- inner packs per shipping case; and
- cases per pallet, when applicable.
GS1’s data model treats base unit, pack or inner pack, case and pallet as separate hierarchy levels. It also notes that a change in case quantity can require a new identifier at the affected higher packaging level. Whether a particular business needs GTINs at every level depends on its channels and trading partners, but the underlying discipline is useful even for a small buyer: do not reuse one ambiguous description for several physical configurations.
Good quantity statement
“10 cones per retail pack × 20 retail packs per case = 200 cones per case.”
Bad quantity statement
“200 pack.”
The bad version could mean 200 units, 200 retail packs or a product name inherited from an old spreadsheet. Multiplication is less glamorous, but considerably better at receiving inventory.
Give each identifier one job
The label becomes easier to audit when each field has a defined purpose.
- Product name: plain-language identity for people.
- SKU: the seller’s internal code for a specific product configuration.
- GTIN or other trade identifier: a standardized identifier when used by the relevant channel or partner.
- Batch or lot: a group produced or handled together under a defined record.
- Serial or case number: one particular physical unit, when individual tracking is needed.
- Purchase order: the commercial transaction that requested the goods.
A batch number should not silently replace a SKU. Two batches may contain the same SKU, while one shipment can contain several batches. GS1’s logistic-label guidance likewise connects a batch or lot to the product identifier shown on the label.
For empty pre-rolled cones, a practical product record may also include stated overall length, tip construction, paper description and pack revision. Only print claims that belong to that exact SKU and are supported by current documentation.
Make the label match the product page and purchase order
Label checks should begin before production, not after cartons reach the dock.
Compare these fields across the quote, approved specification, product page, purchase order, inner-pack label and case label:
- product name and SKU;
- stated dimensions and material description;
- cones per pack;
- packs per case;
- total cones per case;
- batch or lot format;
- packaging revision; and
- barcode or identifier data, where used.
If one source says “200 count,” another says “20 packs,” and a third says “10 per pack,” the math may be consistent—but someone should state the relationship explicitly. The guide to 1-pack, 2-pack, 4-pack and 6-pack totals shows why pack language needs a visible multiplier rather than an assumption.
Use the current 200-count product entry to confirm live options and included items. Do not infer a case configuration, batch format or certification from this article if the live product record does not state it.
Design for receiving, not only printing
A label can be technically present and operationally useless. Receiving staff should be able to read the important fields without opening every carton or rotating a pallet through interpretive dance.
Place human-readable product identity and quantity near the barcode or encoded data. Keep critical text large enough to read in the actual print size. Avoid placing labels over seams, corners or tape paths that distort the code.
Before approval, print the label at final size and check:
- text legibility under warehouse lighting;
- barcode scan from the expected distance and angle;
- contrast and quiet zones required by the chosen data carrier;
- resistance to ordinary handling and label rubbing;
- agreement between encoded data and human-readable text; and
- correct placement on every packaging level.
This is not a claim that every shipment needs a standardized logistic label. It is a buyer’s quality check. Regulatory and trading-partner requirements vary by market and product category; confirm them with the appropriate qualified adviser or channel.
Record changes before they become count disputes
A change from 10 packs per case to 12 is not merely a warehouse preference. It changes the quantity relationship, case dimensions, weight, receiving expectation and possibly the case-level identifier.
Use a short change record:
| Change | Records to review |
|---|---|
| Cones per pack | Product page, SKU/GTIN decision, artwork, price comparison |
| Packs per case | Case label, case identifier, dimensions, weight, purchase order |
| Paper or tip revision | Product specification, claims, sample approval, batch record |
| Label layout | Scan verification, human-readable fields, print proof |
| Mixed batches in one case | Traceability rule, receiving instructions, case label |
Do not solve an identifier conflict by covering the old label with a new one unless the relabeling process is controlled and the encoded data, human-readable fields and system records all agree.
Bulk-label approval checklist
- [ ] Every packaging level is named clearly.
- [ ] Cones per pack, packs per case and total cones reconcile mathematically.
- [ ] Product name, SKU and revision match the approved specification.
- [ ] Batch/lot fields are distinct from product and order identifiers.
- [ ] Encoded data matches the printed text.
- [ ] Case dimensions and weight belong to the labeled configuration.
- [ ] Final-size print is legible and scans successfully.
- [ ] Label placement avoids seams, corners and tape paths.
- [ ] Quantity or configuration changes trigger a label review.
- [ ] Receiving instructions explain which discrepancies require a hold.
FAQ
Is a SKU the same as a batch number?
No. A SKU identifies a product configuration in a seller’s system. A batch or lot identifies a defined production or handling group of that product.
Should the case show total cones or number of packs?
Ideally it should make both clear: packs per case, cones per pack and total cones. That removes ambiguity during receiving and unit-cost calculations.
Does every packaging level need a different barcode?
Not automatically. The answer depends on which levels are trade items, how they are ordered or scanned, and the requirements of the market and trading partner. GS1 rules distinguish packaging levels when they need separate identification.
What if one case contains more than one batch?
Agree on the traceability rule before packing. GS1 logistic-label guidance places limits on representing multiple batch numbers on one logistic label, so mixed-batch cases may need a different operational approach.
Suggested internal links
- Anchor: “how multipack totals work” — https://conebarnshop.com/blogs/learn/200-count-cone-multipack-totals
- Anchor: “how to calculate cost per cone” — https://conebarnshop.com/blogs/learn/pre-rolled-cone-cost-per-unit
- Anchor: “how to inspect a bulk pack on arrival” — https://conebarnshop.com/blogs/learn/bulk-pre-rolled-cone-receiving-inspection
- Anchor: “current 200-count product options” — https://conebarnshop.com/s/200packhomepage
Image recommendation
- Theme: A real photograph of an unbranded small pack, inner carton and shipping case with plain example labels.
- Alt text: “Example labels on a small pre-rolled cone pack, inner carton and shipping case.”
- Avoid: unreadable invented barcodes, third-party brands, unsupported certifications or AI images presented as traceability proof.
References
- GS1, “Global Data Model Attribute Implementation Guide — Trade Item Hierarchy”: https://www.gs1.org/standards/gs1-global-data-model-attribute-implementation-guide/16
- GS1, “Pack/case quantity”: https://www.gs1.org/1/gtinrules/en/rule/270/packcase-quantity
- GS1, “Logistic Label Guideline”: https://www.gs1.org/standards/gs1-logistic-label-guideline/1-3
- GS1, “Global Traceability Standard”: https://www.gs1.org/standards/gs1-global-traceability-standard/current-standard
The next practical step is simple: put the smallest pack, inner pack and case labels beside the purchase order and make every quantity relationship reconcile before the order ships.