Overview
Luminous has two separate import tools for warehouse locations, found under Tools → Imports in the Inventory & Warehouse section. They serve different purposes and have different templates:
| Import name | What it does |
|---|---|
| Warehouse Locations | Creates or updates the bin/location names inside a warehouse |
| Locations | Assigns SKUs to those existing bins (this is where the SKU columns appear) |
You typically run Warehouse Locations first (to create the bins), then Locations (to assign products to them).
1. Warehouse Locations import — creating bins
Tools → Imports → Warehouse Locations
This import creates or updates location (bin) records inside a warehouse. It does not have SKU columns.
Steps
- Go to Tools → Imports.
- Under the Inventory Operations, click Warehouse Locations.
- Select the target warehouse from the dropdown.
- Click Download Warehouse Locations Template to get the Excel file.
- Fill in the template, then upload it.
Template columns
| Column | Required? | What to enter |
|---|---|---|
Location | Yes | The name of the bin/location (e.g. A-01-01). If the name already exists in the warehouse it will be updated; if not, a new bin is created. |
IS_PICK_LOCATION | No | Controls whether this bin is flagged as a picking location for auto-depletion workflows. Leave blank, or enter 1 (yes) or 0 (no). |
2. Locations import — assigning SKUs to bins
Tools → Imports → Locations
This import links your SKUs to specific bins within a warehouse. This is the template that contains the SKU columns.
Steps
- Go to Tools → Imports.
- Under the Inventory Operation, click Locations.
- Choose your import mode (see Options below).
- Select the target warehouse from the dropdown.
- Click Download Locations Template to get the Excel file.
- Fill in the template and upload it.
Template columns
| Column | Required? | What to enter |
|---|---|---|
Location | Yes | Must exactly match an existing bin name in the selected warehouse. |
IS_PICK_LOCATION | No | 1 to mark this bin as a picking location, 0 to unmark it. Leave blank to leave the setting unchanged. |
SKU1 | No | An internal SKU to assign to this location. |
SKU2 | No | A second SKU to assign to the same location. |
SKU3, SKU4, … | No | As many additional SKU columns as you need. |
What do SKU1, SKU2, etc. mean?
Each SKU column holds one product SKU that should be associated with the location on that row. There is no fixed limit — you can add as many SKU columns as needed, as long as each column header contains the word SKU (e.g. SKU1, SKU2, SKU3). Luminous recognises any column whose header includes SKU and will process each one.
- Each row = one location. All SKU columns on the same row are all assigned to that single bin.
- Values must be internal SKUs that already exist in Luminous. Any SKU that is not found will be flagged as an error in the post-import report.
- Empty SKU cells are skipped — you do not need to fill every SKU column on every row.
Import options
| Option | Behaviour |
|---|---|
| Overwrite location (default) | Replaces any existing SKU–bin assignments for the affected SKUs with the new ones from the file. |
| Append location | Adds the new assignments without removing any existing ones. |
| Include All SKU Variant checkbox | When checked, assigning a master SKU also assigns all of its variant child SKUs to the same bin automatically. |
Tips
- Run the Warehouse Locations import before the Locations import. The Locations import requires bin names to already exist in the system.
- Each SKU should ideally have only one picking location per warehouse to avoid inventory tracking discrepancies.
- After uploading, Luminous shows a preview of your data before you confirm. Any rows with errors (unrecognised locations or SKUs) are highlighted so you can fix them before committing.