New inventory added regularly   •   Bulk, closeout & take-all opportunities

How to Build a SKU and Bin Location System for Wholesale Inventory

Wholesale inventory becomes difficult to control when several products look similar, cartons are stored in different places, or the same merchandise is offered through more than one sales channel.

A retailer may know that 500 units arrived but still be unable to answer basic questions quickly:

  • Which variation is this?
  • How many sellable units remain?
  • Where is the product stored?
  • Which listing is connected to it?
  • Which units are damaged, reserved, or waiting for inspection?
  • What did the product cost after freight and receiving expenses?

A practical SKU and bin location system creates one reliable identity and one documented location for each inventory item. It can be used by discount stores, independent retailers, eBay sellers, Walmart Marketplace sellers, Whatnot sellers, exporters, and businesses that sell through several channels.

The system does not need to be expensive or complicated. It does need to be consistent.

What Is a Wholesale Inventory SKU System?

A stock keeping unit, commonly called a SKU, is an internal code that a business assigns to a specific product or product variation.

A wholesale inventory SKU system connects that code with the information needed to receive, store, sell, count, and analyze the item. The record may include:

  • Product name
  • Brand
  • Model or style
  • UPC, EAN, or GTIN
  • Color, size, scent, pack count, or other variation
  • Condition
  • Internal SKU
  • Quantity received
  • Sellable quantity
  • Reserved quantity
  • Damaged or quarantined quantity
  • Bin location
  • Acquisition date
  • Unit and landed cost
  • Lot code or expiration date when applicable
  • Sales channel listing identifiers

The SKU identifies the item in the buyer’s own system. The bin location identifies where that inventory is stored.

Understand the Difference Between a SKU, GTIN, UPC, and Barcode

These terms are related, but they are not interchangeable.

SKU

A SKU is created by the retailer for internal use. Two retailers can sell the same product while using different internal SKUs.

GTIN and UPC

A Global Trade Item Number, or GTIN, is a standardized product identifier. A UPC is a common barcode format that carries a GTIN for retail scanning in the United States and Canada.

GS1 US states that each product variation requires a unique barcode. Its example shows that a shirt offered in three sizes and three colors requires nine product identifiers. GS1 US barcode guidance

Barcode

A barcode is the machine-readable symbol that represents data. A manufacturer UPC barcode can identify the retail product. A business can also print an internal barcode that represents its own SKU or location code.

Do not replace or alter a manufacturer’s product identifier merely to fit an internal system. Record the manufacturer’s identifier in a separate field and connect it to the internal SKU.

1. Decide What One Inventory Record Represents

Before creating codes, decide what differences require separate inventory records.

Create a separate SKU when a difference affects how the product is stored, priced, described, sold, or counted. Differences may include:

  • Model number
  • UPC or GTIN
  • Size
  • Color
  • Scent or flavor
  • Pack count
  • Bundle configuration
  • Country or market version
  • Packaging condition
  • Product condition
  • Expiration window

For example, a single unit and a six pack should not share a SKU. A sealed product and the same product with damaged retail packaging should not share a sellable inventory record if they will be described or priced differently.

The objective is not to create as many SKUs as possible. It is to prevent materially different inventory from being combined under one number.

2. Create a Short and Consistent SKU Format

A SKU should be unique, readable, and easy to enter. Avoid codes that are so detailed that employees cannot use them consistently.

One possible structure is:

Category – Brand – Item – Variation

Example:

TOY-HAS-0142-BLU

This could represent:

  • TOY: category
  • HAS: brand abbreviation
  • 0142: internal item sequence
  • BLU: blue variation

Another product could use:

HOU-CUI-0088-12P

This could represent a housewares item, a brand abbreviation, an internal sequence, and a 12-piece pack.

Use rules that work across the systems the business actually uses:

  • Keep the format reasonably short.
  • Use the same field order every time.
  • Avoid spaces and unnecessary punctuation.
  • Avoid easily confused characters such as the letter O and number 0 when possible.
  • Give each variation its own code.
  • Never assign one SKU to two active products.
  • Do not recycle a discontinued SKU for a different product.
  • Document every abbreviation in a code dictionary.

A SKU does not need to contain every product fact. The complete product record should hold the full description, identifiers, costs, dates, and notes.

3. Keep Location Codes Separate From Product SKUs

Do not build the current shelf location permanently into the product SKU. Products move. The identity of the product should remain stable when its location changes.

Use a separate location structure such as:

Zone – Aisle – Bay – Shelf – Bin

Example:

A-03-02-B-04

This could mean:

  • Zone A
  • Aisle 03
  • Bay 02
  • Shelf B
  • Bin 04

For pallet storage, a shorter code may be enough:

P-04-12

This could identify pallet zone 4, position 12.

Use signs that can be read from the normal picking path. The physical label and the inventory record must use the same exact format.

4. Create Status Locations for Inventory That Is Not Ready to Sell

Not every received unit should immediately enter sellable stock.

Create separate locations or statuses for:

  • Receiving inspection
  • Damaged merchandise
  • Packaging damage
  • Customer returns
  • Recall hold
  • Expiration review
  • Missing accessories
  • Testing or grading
  • Reserved orders
  • Export documentation hold

Example codes could include:

  • REC-01: awaiting receiving inspection
  • Q-01: quarantine
  • DMG-01: damaged inventory
  • RET-01: customer returns
  • HOLD-01: reserved or compliance hold

Separating these units prevents the business from listing or promising inventory that is not available for normal sale.

5. Build a Master Product Record

Every active SKU should have one master record. A spreadsheet can work for a smaller operation, while a point of sale, warehouse, or inventory system may be more appropriate as volume increases.

At minimum, include:

Field Purpose
Internal SKU Stable identifier created by the business
Product name Clear description used by staff
Brand Brand shown on the product
Model or style Exact variation reference
UPC, EAN, or GTIN Manufacturer or standardized product identifier
Pack count Number of sellable units in the package
Condition New, open box, packaging damage, or other documented state
Primary location Normal picking location
Overflow location Additional stock location when used
Quantity on hand Physical units recorded in the system
Reserved quantity Units committed but not yet deducted
Hold quantity Units unavailable for normal sale
Available quantity Units that can be offered for sale
Unit cost Merchandise cost before additional expenses
Landed cost Allocated cost after applicable inbound expenses
Acquisition date Date the inventory was received or accepted
Lot or date code Used when relevant to the product
Channel identifiers Listing or offer references used by each sales channel

The IRS explains that good records can show which items are selling and help a business prepare financial statements and tax returns. It also states that supporting inventory documents should show the amount paid and that the purchase was for inventory. IRS Publication 583

Consult a qualified accounting or tax professional regarding the records and valuation method required for the business.

6. Calculate Available Inventory Correctly

The number physically present is not always the number available to sell.

Use a formula such as:

Available quantity = on-hand quantity – reserved quantity – hold quantity

Example:

  • Quantity on hand: 600
  • Reserved for open orders: 45
  • Damaged or awaiting inspection: 18

600 – 45 – 18 = 537 available units

If the business sells through several channels, the 537 units represent the shared available pool. Do not give every channel a separate quantity of 537 unless each channel has dedicated physical inventory.

A safety buffer can reduce overselling when systems do not synchronize immediately:

Channel-available quantity = available quantity – safety buffer

If the safety buffer is 12 units:

537 – 12 = 525 channel-available units

The correct buffer depends on sales velocity, system synchronization, cancellation exposure, and the speed of physical picking.

7. Connect Every Sales Listing to the Internal SKU

The internal SKU should be the common reference across the business, even when sales channels assign their own listing or item numbers.

Maintain a channel map with fields such as:

Internal SKU Channel Listing or item ID Quantity rule Status
TOY-HAS-0142-BLU Retail store POS-4381 Shared pool Active
TOY-HAS-0142-BLU eBay Listing ID Shared pool Active
TOY-HAS-0142-BLU Walmart Marketplace Item ID Shared pool Active
TOY-HAS-0142-BLU Whatnot Listing reference Event allocation Active

Marketplace fields and requirements can change. Review the current rules in each seller account before uploading or editing inventory.

Avoid creating a different internal identity for the same physical product on every channel. That makes it difficult to understand total exposure and can create duplicate inventory counts.

An exception may be appropriate when inventory is physically separated or committed to one channel. Document the allocation and transfer process so units are not counted twice.

8. Label Products, Cartons, Pallets, and Locations Clearly

The right label depends on the picking unit.

Product or inner-pack label

Consider including:

  • Internal SKU
  • Scannable internal barcode
  • Short product description
  • Variation
  • Pack count
  • Condition when it is not standard

Carton label

Consider including:

  • Internal SKU
  • Units per carton
  • Carton count
  • Lot or expiration information when applicable
  • Receiving date

Pallet label

Consider including:

  • Purchase or receiving reference
  • SKU or mixed-pallet indicator
  • Carton and unit count
  • Pallet number
  • Status
  • Destination location

Location label

Use large text and a scannable code. Place the label where staff can scan it without moving merchandise or entering an unsafe area.

Do not cover legally required product information, expiration dates, lot codes, serial numbers, or manufacturer barcodes with an internal label.

9. Make the SKU System Part of Receiving

The inventory record should begin while the shipment is being received, not days later from memory.

Use this workflow:

  1. Match the shipment to the purchase record and bill of lading.
  2. Count pallets, cartons, and units as appropriate.
  3. Confirm product identity and manufacturer identifiers.
  4. Separate variations and conditions.
  5. Record shortages, overages, and visible damage.
  6. Assign or confirm the internal SKU.
  7. Record the receiving date and source documents.
  8. Place questionable units in a hold location.
  9. Apply product, carton, pallet, and location labels as needed.
  10. Enter the final sellable, reserved, and hold quantities.

Use NexDeal’s wholesale inventory receiving checklist to document pallet counts, carton counts, condition, barcodes, shortages, and adjusted sellable yield.

10. Record Every Inventory Movement

An inventory system becomes unreliable when products are moved without updating their location.

Each movement record should identify:

  • Date and time
  • SKU
  • Quantity
  • From location
  • To location
  • Reason
  • Employee or user
  • Related order, count, return, or adjustment reference

Useful movement reasons include:

  • Received
  • Put away
  • Picked
  • Packed
  • Reserved
  • Order canceled
  • Returned
  • Damaged
  • Transferred
  • Count correction
  • Disposal approved

Do not solve a mismatch by changing the number without a reason. The adjustment history should explain what happened.

11. Use Cycle Counts Instead of Waiting for One Annual Count

A cycle count checks selected inventory on a repeating schedule. It helps identify errors while the related activity is still recent.

A simple schedule may be:

  • Fast-moving or high-value SKUs: weekly
  • Moderate-volume SKUs: monthly
  • Slow-moving SKUs: quarterly
  • Hold and damage locations: monthly
  • Random exception count: weekly

During a count:

  1. Pause or control movement for the selected location.
  2. Count physical units without relying only on the displayed quantity.
  3. Compare the result with the system.
  4. Research open orders, transfers, returns, and receiving documents.
  5. Record the adjustment and reason.
  6. Look for a repeated process failure.

Use accuracy as an operating measurement:

Inventory accuracy rate = correctly counted records ÷ records counted × 100

If 96 of 100 counted SKUs match:

96 ÷ 100 × 100 = 96% inventory accuracy

The four errors still require investigation. A percentage alone does not explain whether the problem came from receiving, picking, returns, channel synchronization, or an unrecorded move.

12. Audit the System for Duplicate and Incomplete Records

Review the master file regularly for:

  • Duplicate SKUs
  • One SKU assigned to multiple products
  • One product entered under several SKUs without a reason
  • Missing UPC, GTIN, model, or variation data
  • Negative available quantities
  • Inventory stored in an unknown location
  • Active listings with no available stock
  • Discontinued listings still reserving quantity
  • Products in hold locations for too long
  • Old SKUs reused for new merchandise
  • Costs or pack counts entered in inconsistent units

Correct the source record before copying data to additional channels. Otherwise, the same error spreads into listings, counts, purchase decisions, and financial reports.

A Complete Example

Suppose a retailer receives 720 units from a NexDeal order:

  • 360 blue units
  • 360 black units
  • 24 units have packaging damage
  • 12 units require additional inspection
  • 60 sellable units are reserved for an existing wholesale customer

The retailer creates:

  • ELE-BRA-0215-BLU for blue
  • ELE-BRA-0215-BLK for black

The sellable quantity is:

720 – 24 – 12 = 684 sellable units

After reserving 60 units:

684 – 60 = 624 available units

The physical locations are recorded as:

  • Blue sellable stock: A-02-01-A
  • Black sellable stock: A-02-02-A
  • Packaging damage: DMG-01
  • Inspection hold: Q-01
  • Reserved stock: HOLD-01

Each sales listing maps back to the blue or black internal SKU. The manufacturer identifier remains in its own field. If the sellable products move to another aisle, the location changes but the SKU remains the same.

Applying the System to a NexDeal Order

Start by reviewing NexDeal’s Newest Daily Deals and the specific offer. Record the exact product, condition, MOQ, available quantity, price, and displayed identifiers.

Review How NexDeal Works before ordering. As reviewed September 17, 2026, NexDeal states that product availability can change quickly, that it confirms the order and final quantity before payment, and that the buyer arranges the carrier and sends the bill of lading.

After the inventory arrives:

  1. Complete the receiving inspection.
  2. Separate products by exact variation and condition.
  3. Record existing UPC, EAN, GTIN, model, and lot information.
  4. Assign one internal SKU to each distinct inventory record.
  5. Separate sellable, damaged, reserved, and inspection-hold quantities.
  6. Assign and label the storage locations.
  7. Map active sales listings to the internal SKU.
  8. Add the SKU to the business’s aging and cycle-count schedules.

New buyers can complete the NexDeal customer application before reviewing available opportunities.

Wholesale Inventory SKU System Checklist

Before the inventory is offered for sale, confirm:

  • Does every distinct product variation have one unique internal SKU?
  • Is the manufacturer’s UPC, EAN, or GTIN stored separately?
  • Are pack count and condition clearly recorded?
  • Does every SKU have a physical location?
  • Are sellable, damaged, reserved, and hold quantities separated?
  • Is available quantity calculated from the shared inventory pool?
  • Does every channel listing map back to the internal SKU?
  • Are labels readable and scannable?
  • Are receiving and purchase documents connected to the record?
  • Are movements recorded with a reason?
  • Is the SKU included in a cycle-count schedule?
  • Can another employee locate and identify the product without guessing?

A good SKU and bin location system should make the correct action easier. Staff should be able to identify the product, locate it, count it, pick it, and explain its status using the same record.

Frequently Asked Questions

Is a SKU the same as a UPC?

No. A SKU is an internal identifier created by a business. A UPC carries a standardized product identifier used across retail systems. Keep both in the product record when available.

Should the warehouse location be part of the SKU?

Usually no. Store the bin location in a separate field so the product can move without changing its identity.

Do different colors or sizes need different SKUs?

Yes when the variation must be counted, priced, described, or sold separately. GS1 also states that each product variation needs a unique barcode when standardized identifiers are being assigned.

Can I use the manufacturer’s UPC as my internal SKU?

Some businesses do, but a separate internal SKU can provide more control over condition, pack count, bundles, and channel mapping. Do not alter or invent manufacturer identifiers.

How do I avoid overselling across several channels?

Use one master available quantity, subtract reserved and hold units, maintain a safety buffer when appropriate, and synchronize or reconcile channel quantities frequently.

How often should inventory be counted?

Count frequency should reflect value, sales velocity, error history, and risk. Fast-moving or high-value items generally deserve more frequent cycle counts than slow-moving merchandise.

This article provides general business information and does not constitute accounting, tax, legal, regulatory, or financial advice.

Sources Used