top of page
Search

Avoid GTIN Mixups: Case Pack vs Eaches for Fulfillment Pros

17 hours ago
9 min read

Medical supply case, inner pack, and eaches

An each is the single sellable unit with its own barcode, the thing a customer actually receives, while a case pack is the fixed count of those eaches inside one shipping carton and the conversion factor you apply across inventory, shipping, and receiving. The practical rule: stock and ship by eaches when a channel demands flexibility, like direct-to-consumer orders, and lean on case packs when wholesale efficiency or retailer mandates take priority. Get the pack count wrong across your product data, labels, and advance ship notices, and you invite receiving errors and chargebacks.

 

TL;DR:  
  • Accurate unit management requires matching case pack GTINs to actual contents whenever the pack size changes, to prevent receipt and chargeback errors.

  • Different packaging levels must use distinct identifiers: eaches with UPC or GTIN-12, cases with GTIN-14, and pallets with SSCC, to avoid warehouse misreceipts.

  • Converting between cases and eaches must be consistent, with key figures like units per case and change dates properly audited to ensure inventory accuracy.

  • Handling costs favor case packs for high-volume retailers, while eaches offer greater flexibility suitable for direct-to-consumer channels with lower weekly demand.

  • Proper packing, labeling, and adherence to retailer-specific requirements help prevent reconciliation issues and streamline shipment processing.

 



Table of Contents

 

 

What Counts as an Each, an Inner Pack, and a Case Pack

 

An each is the smallest unit a buyer can purchase on its own, carrying its own UPC or GTIN-12. A case pack is the number of those eaches packed into one master shipping carton, and it becomes the multiplier you use whenever you move between selling units and shipping units. Between the two sits the inner pack, sometimes called a warehouse pack: a bundle of eaches grouped inside the case but smaller than the full case, built so a store or distribution center can break bulk without tearing open the whole carton.

 

The math only works when everyone uses the same numbers. Say a case pack holds 24 eaches, as in one common example from GS1 pack-count conventions: a pallet of 48 cases then contains 1,152 eaches. That single multiplier, 24, has to appear identically in your product master, on the case label, and in every purchase order line that references the item.


Case pack multiplication from cases to eaches

Retailers and distributors routinely place purchase orders in case quantities, while your sales reports, POS feeds, and consumption data run in eaches. Skip the conversion step and your reconciliation breaks immediately; a buyer who orders 10 cases expecting 240 units but receives a system record showing “10 units” will flag a shortage that never existed.

 

Keep these three levels distinct in your own records:

 

  • Each: the individual sellable unit with its own barcode.

  • Inner pack: a sub-case bundle of eaches, used to break bulk without opening the master carton.

  • Case pack (master carton): the full shipping container, holding either loose eaches or several inner packs, and the unit most purchase orders reference.

 

Barcodes, GTINs, and Trade-Item Hierarchies

 

Every packaging level needs its own identifier, and mixing them up is one of the most common causes of warehouse receiving errors. The each carries a UPC or GTIN-12. The case carries a GTIN-14 (sometimes printed as an ITF-14 barcode or encoded in GS1-128), a separate number from the each-level code. Pallets carry an SSCC, a serial shipping container code that ties the physical load to its advance ship notice.

 

GS1’s GTIN management guidelines are explicit on when a new case-level GTIN is required: any change to the quantity inside a case, say a shift from 8 units to 12, forces a new GTIN at that packaging level. The each-level code generally stays the same since the consumer unit hasn’t changed, but the case identity has, and systems downstream need to see that difference to avoid pulling stale pack-count data.


Barcodes, GTINs, and Trade-Item Hierarchies — overview diagram

A pallet of 48 cases at 24 eaches per case works out to 1,152 individual units, a figure that only holds true as long as the case-level GTIN still matches a 24-unit pack. Change the case contents without issuing a new GTIN and every downstream system, from your WMS to the retailer’s receiving dock, is working off a number that no longer reflects reality.

 

Common mistakes that cause real damage:

 

  • Printing the each-level UPC on the outer case instead of a distinct case GTIN.

  • Zero-padding a UPC and reusing it as a case identifier rather than assigning a true GTIN-14.

  • Failing to update the case GTIN after a pack-count change, so the ASN and the physical carton disagree.

 

Any of these can trigger a chargeback or a misreceipt at a retailer’s dock, since the barcode scanned on arrival won’t match what the purchase order expected.

 

Case Packs, Eaches, and the Reconciliation Problem

 

The most frequent inventory error in wholesale happens when one team records transactions in cases and another records them in eaches, and nobody applies the conversion consistently. According to practitioner guidance on case-pack reconciliation, this mismatch in units of measure is the root cause behind most of the off-by-multiples errors that show up in sell-through and velocity reports.

 

The fix is mechanical once you see it. If a purchase order shows 50 cases at a 24-unit case pack, that’s 1,200 eaches entering inventory, and every sell-through calculation after that needs to reference eaches, not cases, or the numbers drift. Our guide on inventory turnover for medical supplies walks through weeks-of-cover math using the same each-level basis.

 

A quick worked example: say a SKU sells 180 eaches a week, you hold 720 eaches on hand, and the case pack is 24. That’s 4 weeks of cover, and a reorder point set at 2 weeks of cover means triggering a new order once stock drops to 360 eaches, which rounds to 15 full cases.

 

Four fields in your product master deserve a dedicated audit, not a one-time entry:

 

  1. Units per case: the core multiplier for every conversion.

  2. Units per inner pack: needed when a case contains sub-bundles.

  3. Cases per pallet: required for freight and storage planning.

  4. Pack-change effective date: flags exactly when a new case GTIN takes effect so historical records aren’t misread.

 

Pro Tip: Lock the units-per-case field at the SKU level in your ERP and require a dated revision log whenever a supplier changes case contents, so old purchase orders don’t get reconciled against the wrong multiplier.

 

Packing, Labeling, and Channel Requirements

 

Retailers and fulfillment partners enforce their own rules for how case-packed inventory arrives, and most of those rules exist to prevent exactly the reconciliation errors described above. Operational guidance on pack hierarchy points to a consistent pattern: case contents must match what the label and ASN declare, every case in a shipment should hold the same quantity unless clearly marked otherwise, and pallet labels need an SSCC that lines up with the shipment’s advance ship notice.

 

Typical channel-level expectations include:

 

  • Equal unit counts across all cases in a single shipment, unless cases are explicitly marked as mixed.

  • A “packed by manufacturer” designation on cases that shouldn’t be broken down before resale.

  • Do-not-separate labeling on inner packs meant to stay bundled through to the shelf.

  • FNSKU labeling and ASN data that match the physical case count for channels like Amazon’s FBA program.

 

Inner packs earn their keep in 3PL and retail environments because they let a warehouse pull a smaller bundle for replenishment without cracking open a full master carton, which case-pack configuration research describes as a deliberate compromise, often a vendor pack of 48 split into warehouse packs of 12. Breaking a sealed case that wasn’t designed to be split adds labor time and repackaging cost that a well-planned inner-pack structure avoids.

 

Before shipping inbound: confirm barcode placement on each case face, verify the barcode type matches what the receiving partner scans, and make sure the ASN states the case-pack count explicitly rather than assuming the receiver will infer it.

 

Deciding Between Case Pack and Eaches for a Given SKU

 

Choosing a pack configuration per SKU comes down to weighing handling cost against order flexibility, and the right answer changes by channel and by product.

 

Run each SKU through this checklist:

 

  1. Sales velocity per location: high-velocity locations often justify case-level replenishment; low-velocity ones favor eaches.

  2. SKU variation and return rate: frequent returns push toward eaches so partial cases aren’t wasted.

  3. Retailer mandates: some buyers require case-pack shipping regardless of your preference.

  4. MOQ and sterilization constraints: medical and sterile products often tie minimum order quantities to batch runs, as practitioner notes on medical MOQs describe, though MOQ is a commercial policy, not a physical packaging rule.

  5. Labeling and serialization needs: items under traceability requirements add complexity to any pack change.

  6. Storage density: cases stack and store more efficiently than loose eaches.

  7. Pick-pack labor: each-level picking costs more labor per unit shipped than case-level picking.

 

At a glance: eaches win on flexibility and lose on handling cost per unit; case packs win on handling efficiency and lose on order flexibility; labeling complexity tends to rise with serialized or regulated products regardless of which pack level you choose.

 

A direct-to-consumer seller generally wants eaches available even when case packs exist upstream. A big-box retailer will often mandate case-level shipping outright. A healthcare or sterile-product buyer needs to check MOQ against case pack size before assuming they can order below it, something our piece on retail versus wholesale medical supply differences covers in more depth.

 

Pro Tip: When a product carries both a sterilization-driven MOQ and a standard case pack, confirm in writing whether the MOQ equals one case or several, since suppliers sometimes quote MOQ as a multiple of case pack rather than the case pack itself.

 

How We Handle Pack-Level Logistics for Medical Supplies

 

Across our catalog of medical equipment, wound care, respiratory, urology, and disposable supplies, we list pack-level details on individual product pages so buyers can see unit counts before ordering. We work with both individual medical professionals placing smaller orders and larger purchasing organizations that need wholesale case quantities, and our customer service team fields questions on MOQ and case-pack specifics directly. When a buyer needs a custom pack configuration or label requirement that isn’t listed on a product page, we recommend reaching out to our sales team before placing the order so expectations match what ships.

 

An Ops Lead’s Short Take

 

If a SKU moves fewer than a handful of units a week at a given location, stock it in eaches; once weekly demand per location climbs past a full case, switch to case-level replenishment and never look back. The real risk isn’t picking the wrong pack level once, it’s a supplier changing case contents without telling anyone and nobody updating the GTIN or the dated revision log to match.

 

— QB

 

Get Pack-Level Support From Queens Surgical

 

Ordering medical consumables shouldn’t mean guessing whether a listed quantity means one unit or a full case. We supply gloves, wound care, respiratory, urology, PPE, and instrument lines in pack sizes that fit both single-clinic orders and larger wholesale purchases, and our medical supply categories show pack details on the product page itself.


Queenssurgical

 

If your procurement team is still deciding between stocking by the case or by the each, start by checking current pack sizes on our category pages and reach out with your specific volume needs.

 

FAQ

 

What is a case pack in retail?

 

A case pack is the fixed number of individual sellable units, or eaches, packed into one master shipping carton, and retailers often use it as the standard quantity for purchase orders. It’s set by the manufacturer or supplier and typically stays fixed until a pack-count change triggers a new case-level identifier.

 

What does “packaging” mean in this context?

 

Packaging refers to the hierarchy of containers holding a product as it moves from manufacturer to shelf: the each, the inner pack, the case, and the pallet. Each level typically carries its own identifier, since GTIN management rules require pack-level barcodes to reflect what’s actually inside.

 

What is the difference between an inner pack and a master carton?

 

An inner pack is a smaller bundle of eaches nested inside the master carton, letting a warehouse or retailer break bulk without opening the full case. The master carton, or case pack, is the complete shipping unit and the one most purchase orders reference directly.

 

What are the four typical packaging levels?

 

The common hierarchy runs each, inner pack, case (master carton), and pallet, with each level carrying a distinct barcode such as a UPC on the each and an SSCC on the pallet. Not every product uses all four; smaller SKUs sometimes skip the inner-pack level entirely.

 

How do I calculate eaches from a case pack count?

 

Multiply the number of cases by the units-per-case figure listed in the product master or on the case label. A shipment of 48 cases at 24 units per case works out to 1,152 eaches, and that same multiplier should carry through to every sell-through and reorder calculation afterward.

 

Sources

 

Recommended

 

 
 
 

Comments


bottom of page