GenFrontier homeScope a project
Menu
Reader questionHow should we number aisles, bays, levels and bins so that pickers, scanners and the WMS all read locations the same way?

Designing a warehouse location numbering scheme

Warehouse location numbering rules that keep pickers, scanners and the WMS in step: fixed-width segments, walk-order sorting, check digits and GS1 GLNs.

field-notes / inventory-control / warehouse-location-numbering
A honeycomb frame held up to the light, its cells empty except for one cell capped with red wax.

Number warehouse locations as fixed-width segments that run from the largest area to the smallest (zone, aisle, bay, level, position), so that a plain text sort of the codes puts them in the order a picker walks. Leave gaps for racking you will add, keep out characters that look or sound alike, and keep the location’s type and rules in the WMS location profile, not in the code. Print exactly the same string in the barcode and in large human-readable text, add a separate check code for voice or keyed confirmation and change it from time to time. Use a GS1 Global Location Number (GLN) with an extension component, AI (254), only for places a trading partner also has to identify.

This field note is for warehouse managers, WMS administrators and implementation leads who are planning a re-slot, a new building or a new WMS. It covers the rules that software cares about, which many layout guides leave out.

What a location code has to do

A location code is read by three different readers: a person walking the floor, a scanner or voice terminal confirming the place, and a database that sorts, joins and filters on it. A good scheme gives all three the same answer without anyone translating.

The ASCM Supply Chain Dictionary defines a location tag as “A bar-coded sign situated at a warehouse location. The location number can be read or scanned.”

It defines a location audit as “A methodical verification of the location records for an item or group of items in inventory to ensure that when the record shows an item’s location, it is, in fact, in that location.” Both definitions assume one thing: that the number on the sign and the number in the record are the same number.

The three readers and what each needs

Reader What it does with the code What breaks it
Picker or put-away driver Finds the place by walking the hierarchy: aisle, then bay, then level Codes that skip around, labels at the wrong height, look-alike characters
Scanner or voice terminal Confirms the worker is at the right place Barcode content that differs from the record, check codes people have memorized
WMS, ERP and reports Sorts pick lists, groups counts, joins history Variable widths, mixed case, spaces, values that spreadsheets convert

Why this matters for inventory accuracy

The ASCM definition of inventory accuracy notes that “For logistical operations (location management) purposes, it is sometimes measured as the number of storage locations with errors divided by the total number of storage locations.” A location scheme that people misread produces location errors directly. When those errors show up in a count, the time goes into investigating cycle count variances that are really put-away mistakes.

The anatomy of a location code

Use one segment per physical level of the hierarchy, from largest to smallest, with a fixed width for each. A common shape for racked storage is aisle, bay, level and position. Add a zone segment only if the building has separate areas that pickers treat as different places.

Microsoft’s article on inventory locations in Dynamics 365 gives this kind of example: “01-02-03-4 represents aisle 1, rack 2, shelf 3, and bin 4.” The words vary by vendor and by site. What matters is that each segment means one thing everywhere in the building.

One location code, read segment by segment 14 - 03 - C - 2 Aisle 14 2 digits, 01 to 99 numbered in walk order Bay 03 2 digits, odd on the left, even on the right Level C 1 letter, A at floor, skip I and O Position 2 1 digit, numbered left to right Nine characters with separators. A plain text sort of these codes lists locations in the order a picker walks them.
Example format recommended in this field note, not a standard. The level segment is shown in red because it is the only letter segment.

Segments, widths and what each one means

Segment Meaning in this note Example width Numbering rule
Zone (optional) A separate area or building that pickers treat as a different place 1 letter Only if the site has several areas with their own aisles
Aisle The travel lane, and by convention the racks facing it 2 digits In walk order from the main cross-aisle
Bay The section of rack between two uprights 2 digits Odd numbers on one side, even on the other
Level The beam level, counted from the floor 1 letter A at floor level, upward
Position The slot within a bay level, such as pallet position or shelf bin 1 digit Left to right as you face the rack

Deep racks and drive-in lanes

In double-deep racking, drive-in lanes and push-back systems, a bay level holds pallets one behind another as well as side by side. Decide which segment carries depth before you print anything. A common choice is to let the position digit count from the aisle face backward, so position 1 is always the pallet a driver can reach first, and to record the rack type in the location profile.

Whatever you choose, write it down with a drawing. A driver who cannot tell whether position 2 is beside or behind position 1 will put pallets away by guesswork, and the count will find them in the wrong slot.

Keep the site out of the code

Keep the warehouse or site out of the code. Every WMS and ERP already stores the warehouse in its own field, and repeating it in the location code adds characters without adding meaning.

Floor, shelving and special locations

Not every location is a rack slot. Floor-stacked lanes, carton flow, shelving, dock doors, staging lanes and the returns cage all need codes. Give them the same number of segments and the same widths where you can, with a zone value that marks the area: for example, a floor lane might use the bay segment for the lane and the level segment for the depth position.

Where a place does not fit the pattern at all, such as a dock door or a quality hold cage, use a short readable name of the same total width and keep it in a separate zone. The point is that every location sorts, filters and prints the same way.

Rule 1: fix the width of every segment

Pad every numeric segment with leading zeros to a fixed width, use uppercase only, and never use spaces. Fixed width is what makes a plain text sort match the physical order, and it is what keeps the code intact when it passes through spreadsheets, label software and interfaces.

Why the sort breaks without padding

Databases, spreadsheets and most reports sort location codes as text. Text sorting compares character by character, so “2” comes after “10”.

Codes without padding, sorted as text Codes with padding, sorted as text
1-1-A-1 01-01-A-1
1-10-A-1 01-02-A-1
1-2-A-1 01-03-A-1
1-3-A-1 01-10-A-1
10-1-A-1 02-01-A-1
2-1-A-1 10-01-A-1

On the left, bay 10 lands between bays 1 and 2, and aisle 10 lands between aisles 1 and 2. A pick list sorted that way sends the picker back and forth. On the right, the text sort and the walk agree.

Size the widths for the building you will have

Pick each width for the largest number that segment will ever need, not the number you have today. If you have 18 aisles and the lease allows an expansion to 30, two digits is right. If a long aisle could reach 50 or more bays per side, the bay segment needs three digits, because odd and even numbering doubles the highest bay number.

Check the length limits of every system the code will pass through before you decide. Microsoft’s guide to configuring locations in a WMS-enabled warehouse says of Dynamics 365 location formats: “The total length of all segments and separators can’t exceed 10 characters.” Label templates, voice systems and carrier or 3PL interfaces have their own limits.

Decide about separators once

Separators make codes readable to people and keep letters such as E from sitting between digits. Choose one separator character, use it between every segment, and decide whether it is part of the stored code. Whatever you decide, the barcode must encode exactly the string the WMS stores, so the scan matches without any translation logic.

Spreadsheets will change your codes

Location lists travel through spreadsheets during every re-slot, count and cutover. Microsoft’s support article on keeping leading zeros and large numbers lists what Excel does to such data by default, including “Removing leading zeros from numerical text and converting to a number,” “Converting numerical data surrounding the letter “E” to scientific notation,” and “Converting a continuous string of letters and numbers to a date.”

Example (fictional). A site stores codes without separators and letters its levels A to F, so aisle 14, bay 03, level E, position 2 is 1403E2. Its staging lanes use digits only, such as 090101. A planner opens the location export in Excel to plan a re-slot.

Excel reads 1403E2 as 1,403 times 10 to the power 2 and shows 1.40E+05, and 090101 becomes the number 90101. The re-slot file goes back to the WMS with hundreds of codes that no longer match any location. Importing the column as text would have prevented both problems.

Separators are not a complete defense. Microsoft’s article on stopping numbers from changing to dates gives the example of 12/2 changing to 2-Dec, and an all-digit code with separators, such as 01-02-03, is exposed to the same date guessing. Keep a letter in every code, or make import as text the rule for every file that carries locations.

Rule 2: make the sort order match the travel path

Number aisles in the order people walk them from the main cross-aisle, and number bays so that a text sort of the codes in one aisle follows the direction of travel. Where travel direction changes by process, keep the walk order in a separate pick sequence field instead of forcing it into the code.

Odd and even sides

Put odd bay numbers on one side of the aisle and even on the other, both counting up from the same end. A picker walking down the aisle then sees 01 and 02 facing each other, then 03 and 04, and a text sort of the aisle’s codes interleaves the two sides in the order they are passed. People find the place by the parity of the number without having to read every label.

Serpentine and one-way paths

In a serpentine path the picker walks up one aisle and down the next. If every aisle is numbered from the front, the codes in the second aisle sort in the opposite direction to the walk.

Bay numbers that follow a serpentine pick path 01-0101-0301-0501-07 01-0201-0401-0601-08 02-0102-0302-0502-07 02-0202-0402-0602-08 03-0103-0303-0503-07 03-0203-0403-0603-08 Aisle 01Aisle 02Aisle 03 Main cross-aisle and start of the path at the front (bottom). Back cross-aisle at the top. Codes show aisle and bay only. Red line: pick path.
Fictional layout for illustration. Option shown: bays in aisle 02 are numbered from the back, so a text sort of the codes equals the walk.

You have two ways to deal with it:

  1. Number alternate aisles from the opposite end, as in the figure, so the text sort of the codes still equals the walk. One field does the work, but people must learn that bay 01 is at the back of even aisles.
  2. Number every aisle from the same end and store a pick sequence for each location. People always find bay 01 at the front, and the WMS sorts pick lists by the sequence field instead of the code.

Microsoft’s inventory locations article describes the second approach in Dynamics 365: “Sort codes can be specified by the aisle and other coordinates, or assigned manually for the location.” Choose option 2 if you expect the pick path to change, for example when you add a mezzanine or reverse one-way aisles for a new forklift route. Renumbering locations is far more work than recalculating a sequence field.

Levels from the floor up

Count levels from the floor, starting at A or 1, so that level A is always the floor or the first beam everywhere in the building. When racks of different heights stand side by side, level A still means the same height in each, and only the highest letter varies.

Put-away and replenishment walk differently

Put-away drivers and replenishment teams often work from reserve to pick faces in a different order from pickers. Do not try to make one code serve every travel pattern. Keep the code stable, and let each work type use its own sequence or directive in the WMS.

Counting by code range

A scheme whose text sort follows the building also makes counting easier to plan. A cycle count task can be defined as a range of codes, such as aisle 14, bays 01 to 20, and the counter walks it in order without doubling back.

Empty-location checks work the same way. A count of every location in a range, including those the system says are empty, is a direct way to find stock that was put away to the wrong code. The cycle count planner helps size how many locations a team can cover per day once ranges are set.

Rule 3: leave gaps for growth and never reuse a code

Reserve numbers for the aisles, bays and levels you may add, so that a new rack run does not force you to renumber the ones around it. When a location is removed, retire its code instead of giving it to a different place, because history, audit trails and old documents still point to it.

Where to leave gaps

  • Aisles. If the building has room for more aisles on one side, start numbering far enough in to leave those numbers free, or decide now that new aisles get the next numbers at the end.
  • Bays. If a run may be extended, the new bays get the next numbers. Avoid layouts where a new bay would have to sit between 03 and 05 on the same side.
  • Levels. Adding a beam level to existing racks changes every level above it. Letter levels so that a new beam can take the next letter at the top, or accept that a beam change means relabeling that bay.
  • Positions. If a pallet bay may be converted to carton shelving, size the position segment for the shelving, not the pallets.

What renumbering costs

Renumbering is not just a label job. It touches every record that refers to a location:

  • Labels, placards and any floor markings.
  • Fixed pick locations, minimum and maximum quantities and replenishment rules.
  • Location directives, zones and pick sequences.
  • Open work, open counts and any license plates in transit.
  • Reports, saved filters and spreadsheets people rely on.
  • Habits. People have learned where 14-03 is.

If a renumbering cannot be avoided, treat it as a cutover: a mapping table from old code to new, a frozen window, and counts afterward. The method is the same as in moving inventory balances into a new WMS.

Retired codes stay retired

A location code is a key that history depends on. If code 14-03-C-2 is removed in a re-slot and later assigned to a place in a new mezzanine, old transactions, count results and adjustment records now point to the wrong place.

GS1 follows a similar principle for its own location numbers. The GS1 GLN Allocation Rules Standard includes an example of a building remodel in which a GLN “was discontinued as the result of a building remodel,” the extension components under it were made inactive, and the shelf slots that remained relevant were reassociated with a new GLN. Apply the same discipline to internal codes: deactivate, do not reuse.

Rule 4: use characters nobody can confuse

Use digits for every segment except one, and if a segment uses letters, leave out the letters that look like digits or sound like each other. Test the full character set with your scanners, your label printer and, if you use voice, your voice system in the actual noise of the building.

Look-alike characters

On a worn label read from a reach truck, O and 0, I and 1, S and 5, Z and 2 and B and 8 are easy to confuse. The safest scheme keeps letters to the level segment and skips I and O there. If you need more than 24 letters for levels, your levels should be numbers.

Sound-alike characters

Voice-directed picking reads location codes aloud and asks the worker to speak a confirmation. Letters that rhyme, such as B, D, P and T, or that differ by one sound, such as M and N, are easy to mishear in a noisy aisle. If voice is in scope, prefer digits throughout, or keep letters to a short list you have tested with the headsets.

Lowercase, spaces and symbols

Keep everything uppercase so that a case-sensitive comparison never treats “c” and “C” as different places. Never use spaces: they are invisible on a label and easy to lose or double when files are exported and edited. Avoid symbols other than your one separator, because label software, barcode symbologies and interfaces handle them differently.

Rule 5: keep the location type in the profile, not in the code

The code should say where a place is. What the place is for, such as pick face, reserve, floor lane, staging or quarantine, belongs in the location’s profile or type in the WMS. Uses change with every re-slot, and a code that encodes the use would have to change with them.

How a WMS holds location rules

Dynamics 365 is a clear example of this design. Microsoft’s guide to creating a location profile says: “The location profile defines the properties and rules for that location, such as whether the location allows mixed items, which inventory dimensions it tracks, and how it participates in replenishment.”

The same guide lists settings such as license plate tracking, whether mixed items are allowed and whether to generate a check digit. Separately, location types such as STAGE, SHIP, BULK or PICK categorize locations for use as filters in warehouse processes. None of that needs to be in the code.

What goes wrong when the code carries the type

Suppose, for example, that a site prefixes pick faces with P and reserve locations with R. During a re-slot, the bottom two levels of an aisle become pick faces. Either every affected code changes, with all the renumbering costs above, or the prefix stops telling the truth.

After a year of re-slots, nobody trusts the prefix.

Keep a short list of attributes on the location record instead: type, zone, profile, dimensions and status. Reports and directives filter on those fields, and the code stays the same for the life of the rack.

Zones are for grouping, not for addressing

WMS zones group locations for work and replenishment: a cold zone, a high-value cage, a fast-mover pick module. A zone can cross aisle boundaries and change when you re-slot. Keep zone membership in the WMS and use the code’s optional zone segment only for areas that are physically separate places, such as a second building or a mezzanine.

Labels and check digits: confirming the right place

The label must carry the code in large human-readable text and a barcode that encodes exactly the same string. For voice or keyed confirmation, add a separate check code that is not derived from the location code, place it where it can only be read at the location, and change it from time to time so that pickers cannot recite it from memory.

What a location label carries

Element Rule
Human-readable code Largest text on the label, with the segment a picker needs most (often the bay) visually emphasized
Barcode Encodes exactly the stored code, including separators if they are stored
Level indicator An arrow pointing to the beam level the label belongs to, where several labels share one beam or upright
Check code Printed apart from the code, small enough that it is read only at the location
Nothing else No item numbers or descriptions on location labels: items move, locations do not

Where labels go

Put each label where the worker’s eyes and scanner already are when they reach the location. For pallet racking, that usually means a label on the beam at each level, centered under the position it names, with the level arrow pointing up or down to the pallet it belongs to.

Floor-level positions often have no beam below them, so their label goes on the first beam with a downward arrow, or on the upright. Labels on high levels need to be readable and scannable from where the driver actually is. Test the reading distance with the scanners you own before you choose label size, and consider a placard at the end of each bay that lists every level of that bay for drivers working from the floor.

Location check digits are not GS1 check digits

The ASCM dictionary defines a check digit as “A digit added to each number in a coding system that allows for detection of errors in the recording of the code numbers,” calculated with “a predetermined mathematical formula.” GS1 identifiers such as the 13-digit GLN carry that kind of check digit, which catches keying and scanning errors.

The “check digits” printed on location labels for voice picking do a different job. They prove the worker is standing at the location. If they could be calculated from the location code, a worker could say them without being there, so they are assigned instead; the patent discussed below describes them as “generated randomly.”

Microsoft’s location profile guide describes a Dynamics 365 setting called Generate check digit: “Set to Yes to automatically generate a check digit for the locations that use this profile. Workers scan or enter the check digit to confirm that they’re at the correct location during mobile device transactions.”

The older inventory locations article mentions “check text” that “can be used in online systems to verify that the operator has selected the correct location for a specific item.”

Memorization and duplicates

A US patent on generating and updating location check digits (US 8,868,519 B2, filed 2011, granted 2014) describes the two failure modes. It states that “check digit memorization by a user due to task repetition remains a problem,” because workers who visit the same locations day after day learn the digits and may “speak the check digits before they actually arrive at the location.”

It also describes duplication: if two adjacent slots are “randomly assigned matching check digits,” this “significantly increases the chance of the incorrect item being picked.” The patent’s background names changing the check digits on a regular basis as the main remedy, and notes that this “involves considerable effort and expense.” The patent itself claims a particular method for generating new digits, so ask your WMS or voice vendor how its own rotation works.

A practical rotation policy

  1. Assign check codes at random, and reject any code that matches a neighbor on the same level, the bay opposite, or the same bay and level in the next aisle.
  2. Rotate codes for the busiest pick faces on a schedule, for example quarterly, and for all locations when a picker reports codes being recited.
  3. Print new labels in batches by aisle, and update the WMS only when the aisle’s labels are hung, so that the floor and the system change together.
  4. Watch confirmation errors by location in the WMS. A location where confirmations never fail may have a memorized code; a location where they often fail may have a damaged label.

Locations outside your walls: GLN and AI (254)

Your internal location codes are enough as long as only your people and systems use them. When a trading partner must identify a place in your building, such as a dock door in an appointment system or a storage area a 3PL reports to its client, GS1 offers two options: a GLN for the place, or the building’s GLN plus a GLN extension component.

What GS1 allows

GS1’s page on physical locations lists examples including a distribution centre, a dock door, cold storage within a warehouse and a shelf. It says that “A physical location within another physical location can be allocated its own GLN,” and that “A physical location must be allocated its own GLN when its access address is different from other physical locations and there is a business need to identify the physical location across organisations.”

For places inside a location, the GLN extension component page says: “When internal to an organisation, sub-locations may be identified by a GLN or by a GLN with a GLN extension component.” It adds that a GLN “SHALL be used in open value chains where the complete set of trading partners is not known in advance,” while a GLN with an extension “may be exchanged, by mutual agreement, between two or more parties when the standard being used supports GLN extension component.”

Which identifier to use for a place in your building
Who must identify the placeIdentifierHow it is encoded
Only your own staff and systemsYour WMS location codeYour own barcode on the location label
You and named partners, by mutual agreement, where the standard you exchange supports itThe building's GLN plus a GLN extension componentAI (414) for the GLN with AI (254) for the extension, up to 20 characters
Partners not known in advance (an open value chain)The place's own GLNAI (414), a 13-digit GLN with check digit
Source: GS1 GLN extension component and physical location pages; GS1 GLN Allocation Rules Standard, Release 3.0.2, section 2.1.2.1; GS1 Application Identifier reference for AI (254) and AI (414). Checked November 2026.

The format of AI (254)

GS1’s Application Identifier reference lists AI (254), “Global Location Number (GLN) extension component,” with the format N3+X..20: the three-digit AI followed by up to 20 characters from the GS1 character set. It must be used with AI (414), the GLN of the physical location, and it needs a separator character when other data follows it in a barcode.

The GS1 rules add an important limit: “A GLN extension component SHALL only be used in conjunction with a GLN identifying a physical location.” In practice, your internal code can become the extension component if it fits the character set and length, which a fixed-width, uppercase, no-space code usually does. That is one more reason to follow Rules 1 and 4.

The same GS1 reference lists AI (414) as a primary key in a GS1 Digital Link URI, with AI (254) as one of its qualifiers. A partner that reads GS1 web URIs can therefore receive the building’s GLN and your internal code in a single identifier, if both sides agree to use it.

When this is worth doing

If no partner needs to see your sub-locations, internal codes are enough. GS1 identifiers become worth the effort when a partner’s system records events at your sub-locations, such as a retailer’s or 3PL client’s system that needs to know which door or which storage area, or when an interface standard you already exchange carries location identifiers. Confirm with the partner that both systems support the extension component before you print anything, as GS1’s own page says companies must.

Rolling out a new scheme: re-slot or new WMS

Design the scheme on paper, write it down as rules the WMS can enforce, generate and test the location list before any label is printed, and cut over aisle by aisle or in one frozen window with counts afterward.

Step by step

  1. Walk the building with a drawing and record every place stock can sit, including floor lanes, cages, staging and the trailer at the door.
  2. Draw the travel paths for picking, put-away and replenishment, and decide whether the code or a sequence field will carry the walk order.
  3. Write the rules as numbered requirements: segments, widths, character set, separator, numbering direction, gaps, check code policy and retirement of codes. In our engagements we start with written requirements like these, each with an acceptance test, before any configuration.
  4. Generate the location list from the rules rather than typing it. Microsoft’s guide describes a location setup wizard that “creates locations by combining each segment’s range of values”; its example of four segments, each from 1 to 3, produces 81 locations.
  5. Test the list. Sort it as text and walk the result on the drawing, import and export it through every spreadsheet and interface, and scan test labels with every scanner model.
  6. Assign profiles and types to each location: pick face, reserve, staging, hold, with the right stocking and mixing rules.
  7. Print and hang labels aisle by aisle, and check each aisle by scanning every label against the list.
  8. Map old codes to new, move open work and balances in a frozen window, and count the affected locations after the change.
  9. Train pickers and drivers on the hierarchy and the odd and even sides, with the drawing posted at the cross-aisles.

Example (fictional). A distribution center has 18 aisles, up to 46 bays per aisle counting both sides, a floor level plus five beam levels and up to three pallet positions per bay level. The lease allows expansion to 30 aisles.

The team chooses aisle 2 digits, bay 2 digits, level 1 letter from A to F (skipping nothing yet, since I and O are not needed), and position 1 digit, with hyphens stored. The format AA-BB-L-P is nine characters, within the 10-character limit of its WMS. A text sort of the generated list matches the serpentine pick path because even aisles are numbered from the back, and the location profile, not the code, marks levels A and B as pick faces.

Who may create a location

A scheme stays clean only if location creation is controlled. Write the rules into a short location standard, name one owner, usually the WMS administrator or inventory control lead, and restrict the permission to create, rename or deactivate locations to that role.

New locations should come from a request that states the physical place, the profile and the code the rules produce. A supervisor who keys a location called OVERFLOW2 on a busy night creates a code that sorts in the wrong place, matches no pattern and will still be there in five years.

Checklist

  • Every segment has a fixed width sized for the largest future value.
  • Codes are uppercase, have no spaces and use one separator, and fit every system’s field length.
  • A text sort of the codes equals the walk, or a sequence field carries the walk.
  • Gaps are reserved for planned growth, and retired codes are never reused.
  • Letters are limited to one segment and exclude look-alike and sound-alike characters.
  • Location type, zone and rules live in the profile, not in the code.
  • Barcodes encode exactly the stored code, and check codes are random, non-duplicated and rotated.
  • GLNs or GLN extensions are used only where a partner needs them, by agreement.

Location codes feed everything downstream: counts, accuracy reports and the item and location data a new WMS loads at go-live. Item master data readiness covers the item side, including the dimensions that decide which items fit which locations. For the labels themselves, our barcode, RFID and labeling work covers location labels as well as product and pallet labels; the pallet side is covered in SSCC pallet labels.

GenFrontier is a Kansas City firm that builds inventory and shipment-tracking software around your existing ERP, WMS and TMS. If a re-slot or a new WMS needs a location model and the software around it, our inventory management software page describes that work, and you can scope a project with us.

Working on this problem?

If this field note describes a process you need to fix or build software around, tell us about it. We start with your process, your systems and your deadline.