Batch Generate won't create the locations

In short

The Layout Rules must give every level one set of codes, for at most 5,000 locations. No new code may already be used in the zone. Fix the rule the message names, then check the total again.

What you see

This warehouse has no zones. Create a zone first, then generate locations.

No Aisle rule is given.

No Rack rule covers Aisle [aisles].

No Shelf rule covers Rack [racks].

No Location rule covers Shelf [shelves].

Rules [number] and [number] both give the Aisle codes.

Rules [number] and [number] both apply to Aisle [aisles].

Rules [number] and [number] both apply to Rack [racks].

Rules [number] and [number] both apply to Shelf [shelves].

This layout has [number] Locations, more than the 5,000 allowed in one batch.

This layout has at least [number] Locations, more than the 5,000 allowed in one batch.

Rule [number]: the end is below the start.

Rule [number]: the start and end must both be numbers or both be letters.

Rule [number]: the list has no codes.

The end is below the start.

The start and end must both be numbers or both be letters.

The list has no codes.

[level] ranges must be [letters or numbers] in this code style.

Resolve the conflicts before creating Locations: a conflicting row would duplicate a Location Code in this zone.

The generation plan has [number] conflicting Location Codes. Resolve the conflicts before creating Locations.

The plan changed since you reviewed it

The warehouse has no zones

Batch Generate needs a zone to put the locations in. Add the zone first, then start Batch Generate again.

A level has no rule

Every level needs a rule: aisles, racks, shelves and locations, and every parent needs a rule for the level below it. The message names the parents left out, such as aisle B with no rack rule. Select Add layout rule and choose the level. Leave Applies to empty to cover every parent, or name the missing ones, such as B.

Two rules cover the same place

Each parent takes its codes from one rule. The message names the two rules, such as two rack rules that both name aisle A, or both cover every aisle. Delete one rule, or change Applies to so each parent is named once. A rule that names a parent always wins over one for every parent, so that pair is fine.

The layout is too big

One batch makes 5,000 locations at most. Split the zone into batches, such as aisles A to C, then D to F. A later batch reuses the aisles, racks and shelves already there, and skips the locations that exist.

A rule's codes don't make sense

The end is below the start: swap them, such as 1 to 10, not 10 to 1.
Numbers and letters are mixed: a range is 1 to 10 or A to F, never 1 to F.
The list has no codes: enter them with commas, such as A, B, D.
The range doesn't match the code style: in Custom, each level's Codes setting says letters or numbers. Change the range, or the setting on the Target step.

Some codes conflict

A Conflict row in the Generation Plan would repeat a code already in use. Its Reason says whether the zone has the Location Code, or the team has the Full Location Code. Change the rule's codes or prefix so they are new, then check the plan again. Rows marked Skipped (already exists) are fine: those locations already exist in the same place.

The plan changed

Locations in the zone were created or changed after Stockist made the plan you checked, so nothing was created. Check the new Generation Plan, then select Create Locations again.