Warehouse labels
How to Create Barcode Labels for Warehouse Bins and Shelves
A warehouse location barcode identifies a place, not the product currently sitting there. A good bin or shelf label uses a stable location code that your WMS or inventory system understands, remains readable to people and scans reliably from the distance staff actually work at.
Updated 18 October 2026
Create a short, stable location ID such as A-04-C-12, encode that exact value in a format your warehouse scanners support—often Code 128 for a new internal system—print the same ID as human-readable text, and test the final label on the real rack or bin. Do not encode the product GTIN as the location barcode because products can move while the location identity should remain stable.
A practical example
For example, A-03-02 can mean aisle A, rack 03, bin 02 in a private warehouse system. This example is a naming convention, not a GS1 identifier. A location barcode should select that bin record; a product barcode should select the product record.
Test a receiving task that scans the product and then the destination bin. Confirm the application records both the correct item and location. Also test the highest shelf from its actual working distance before printing every location label.
Step 1: Define a location ID that will not change when stock moves
A location code should identify the physical slot: zone, aisle, rack, level, shelf or bin. The exact hierarchy is yours, but it should be unique and consistent. Examples include A-04-C-12 or PICK-07-03.
Keep product identity separate. The item in a location may change tomorrow; the location barcode should still resolve to the same physical place.
Step 2: Choose the barcode your scanners support
For an internal warehouse location code, Code 128 is usually a practical 1D starting point because it handles alphanumeric identifiers efficiently. Code 39 can be correct in an established legacy workflow. QR can work with 2D scanners or phones, but using a richer symbol is unnecessary if the job is simply to return one location ID.
If you are implementing a GS1 logistics specification, follow the required GS1 carrier and Application Identifier rules instead of substituting generic Code 128.
Step 3: Design for the scan distance, not just the sticker size
- Print the location code in large readable text so staff can recover when scanning fails.
- Keep clear space around the barcode and avoid borders or graphics crowding the symbol.
- Use durable material appropriate for dust, abrasion, cold or cleaning chemicals in the location.
- Place the label where the scanner has a clear line of sight and staff do not need to bend or twist unnecessarily.
- Test the label at the real scan angle and distance before producing the full warehouse set.
Step 4: Generate many warehouse location labels from a spreadsheet
Warehouse locations are usually already listed in a WMS export or spreadsheet. Put one location ID per row, preserve the exact text and generate the barcodes in bulk. BarcoBatch Excel Bulk can generate Code 128 images from an XLSX without sending the workbook to a server.
Step 5: Test the complete put-away and picking workflow
A barcode that scans in isolation can still fail operationally if the WMS expects a different location token or workers scan the wrong label first. Test receiving, put-away, replenishment and picking with real devices before treating the location-label design as final.
Distinguish a location tag from a retail shelf-price label
A location tag identifies a place, such as aisleA, bay 03 and bin 02. A price label identifies the product offered at that position and shows a current commercial price. Keep these purposes separate even when the labels sit next to each other. Moving stock need not change a stable location key; changing the product displayed on a shelf can require a new price label. A scan that selects the bin record is not proof that the displayed product and price are correct.
Build a price-label source with an explicit product key
For an illustrative shelf label, keep the approved product reference, product name, package description and displayed price together in your own source. The barcode contains the agreed identifier, not automatically the visible price. A price such as 125.00 is a display example, not a price encoded by an ordinary product GTIN. Confirm the receiving checkout or stock system uses that identifier. Do not create a new product code every time the displayed price changes.
Check Turkish display conventions without altering the barcode
If preparing labels for a Türkiye store, decide how the visible currency and decimal separator should appear, then confirm the actual print. That is a display decision, separate from the identifier string. Long descriptions and accented characters need a real sample, and any required price-label information must be checked through the business’s applicable process. This guide explains the barcode/layout workflow, not a complete legal price-label compliance template. Preserve supplier product codes exactly while editing human-facing text.
Plan replacement and shelf checks as an operational task
When replacing a label, compare the shelf position, physical product, visible description and received code. Remove superseded prices and prevent two labels from competing for the same slot. For adjustable shelf strips, test fit after insertion because a lip can cover digits or the lower bars. Use the existing label or bulk-label workflow for supported designs; it does not synchronize prices with a till database. A versioned source and a brief shelf walk are more useful than assuming image export completed the price change.
Common questions
Frequently asked questions
Should the shelf barcode identify the location or the product?
Use the identifier required by the action. A bin scan and a product-price scan can select different records, so label and test them as distinct purposes.
Does changing the visible price require a new GTIN?
Do not improvise product-number changes from a price edit. Follow the relevant identity rules and business process; keep display text and the approved product identifier distinct.
Will these tools update my checkout prices?
No. They generate browser-local artwork and files. Update the authoritative pricing system through its own workflow and separately verify that the displayed shelf information matches it.
What should I check after inserting a shelf label?
Check the actual product, position, description, visible price and scan result. Make sure the shelf holder does not cover bars, quiet zones or readable digits.
Sources & standards
Technical claims in this guide are checked against primary or official documentation where available.