Name ten locations without typing ten records
Configure the pattern inside the warehouse already selected
The builder starts from the current ShipOS warehouse. A freeform prefix plus rack, shelf, and bin coordinates produces each location name; global settings can cover a shelf while individual bins keep their own exceptions.
The naming coordinates organize this builder only. Cybership creates no separate zone, aisle, rack, or shelf hierarchy from them.
Shelf Builder
Configure racks, shelves, and bins for Test Main Warehouse
9-SB-01
6 locations
Shelf
01Bins:
4Location Type
Pick Face
Shelf
02Bins:
2Individual Bin Configuration
1 selectedBin 01
Overflow
PickableSellableBin 02
Overflow
PickableSellable
9-SB-02
4 locations
Shelf
01Bins:
4Location Type
Pick Face
The plan currently expands to 10 location records.
See every location before the first record is created
Preview uses the same rack-and-shelf tree operators see in the product. Each bin reveals its generated name, location type, and pickable or sellable state; the Overflow shelf stays visibly different from the two Pick Face shelves.
Preview itself makes no server request. Conflict checks run only after Create All Locations is submitted, when duplicate generated names, existing names in the selected warehouse, and the 1,000-location limit are enforced.
Location Preview
Total locations to be created: 10
Location tree
Hover any bin to inspect the generated location.
9-SB-01
(6 locations)01 (4 bins)
Pick Face0102030402 (2 bins)
0102
9-SB-02
(4 locations)01 (4 bins)
Pick Face01020304
Review the tree for Test Main Warehouse, then create the batch.
Carry saved locations into labels and mobile scanning
A successful run redirects to Inventory → Locations and reports the created count. If the first merged PDF is available, it opens immediately; operators can later select the saved rows, choose any published LOCATION template, and queue another label job.
After conflict checks, locations are inserted sequentially, so a later create error can leave earlier rows saved. PDF rendering runs afterward as a separate best-effort step and cannot remove successfully created records.
Confirm the saved warehouse locations
Test Main Warehouse · Successfully created 10 locations
| Location | Location type | On hand | Pickable | Sellable |
|---|---|---|---|---|
| 9-SB-01-01-01 | Pick Face | 0 | Yes | Yes |
| 9-SB-01-01-02 | Pick Face | 0 | Yes | Yes |
| 9-SB-01-01-03 | Pick Face | 0 | Yes | Yes |
| 9-SB-01-01-04 | Pick Face | 0 | Yes | Yes |
| 9-SB-01-02-01 | Overflow | 0 | No | Yes |
| 9-SB-01-02-02 | Overflow | 0 | No | Yes |
| 9-SB-02-01-01 | Pick Face | 0 | Yes | Yes |
| 9-SB-02-01-02 | Pick Face | 0 | Yes | Yes |
| 9-SB-02-01-03 | Pick Face | 0 | Yes | Yes |
| 9-SB-02-01-04 | Pick Face | 0 | Yes | Yes |
Regenerate labels from the saved records
Records remain available after creation. Label rendering is separate, so operators can rerun the published template without rebuilding the shelf plan.
- 01
Open Inventory → Locations
- 02
Select the created locations
- 03
Choose Merge Location Labels
- 04
Choose a LOCATION template and start the merge job
- Job type
- Location
- Operation
- Merge PDFs
- Items
- 10
Default Location Label
Published location template
9-SB-01-01-01
Pick Face
Resolve the same record from a floor scan
The universal mobile scanner uses the generated barcode to open location details and current inventory.
Scanned barcode
73120458
Resolved location
9-SB-01-01-01
- Priority
- Priority 1
- Location type
- Pick Face
- Total stock
- 0 eaches
- Location kind
- STATIC
Products in location
0 products · inventory is empty until stock is placed here.
Keep the digital slot honest
The builder removes repetitive setup without pretending the naming plan is a warehouse hierarchy, the create loop is atomic, or the first PDF attempt is the record itself.
- 1–99 bins
- Validated states
- Sequential creates
- Recoverable labels
- What does the builder submit?
- Each name, location type ID, pickable and sellable state, and priority for the current warehouse. Creation defaults supply the STATIC kind and no parent.
- How are location exceptions handled?
- A shelf can share one location type plus pickable and sellable values, or expose those settings for each bin. The current builder does not show a priority control.
- Can a non-sellable bin stay pickable?
- No. Batch validation rejects any generated location where sellable is false and pickable is true, so those inventory states cannot be submitted together.
- Is the create operation all-or-nothing?
- Conflict checks run before creation. After that, locations are inserted sequentially, so an unexpected failure on a later row can leave earlier rows saved.
- What survives a missing label file?
- Every successfully created location and stored barcode. Operators can select those rows in Locations, choose a published LOCATION template, and queue another merged document.
See it in your operation
Bring us the warehouse slots your team still names by hand
Show us the prefix, shelf pattern, pick faces, overflow exceptions, and physical labels you need. We’ll map the generated records and recovery path against your floor.
No sales call is required to get sandbox access.
Continue exploring
Related workflows
Cycle Count
Inventory
Schedule scoped counts, omit expected quantities from mobile, and require a matching recount before correction.
Inventory Management
Inventory
Connect Product Stock and availability to the counts, replenishment work, and history operators use to keep inventory accurate and pickable.
Replenishment
Inventory
Calculate Restock and Break tasks from effective levels, pickable stock, open demand, and available source inventory.
Putaway Lists
Inventory
Create a Putaway List from scanned source stock, compare destination evidence, and keep remaining quantity visible after partial moves.