Main focus

Add storage locations from Excel or CSV to an existing inventory. Imported locations become available for products, entries, counts, filters, and reports.

Applies to

  • Android
  • iOS
  • Web

Before you start

  • Prepare an Excel (.xls, .xlsx) or CSV (.csv) file with one row per location.
  • Use one column for the value you will map to Location name.
  • Use one clean, unique location name per row. Remove blanks, test rows, and duplicates before importing.
  • For Android or iOS imports, do not leave a header row in the import range unless you want that header imported as a location.
  • For Web imports, use clear headers such as Name and Observations so Map Location Fields can match the columns automatically.
  • For Excel files, keep the location data on the first sheet.
  • If the inventory already has live stock activity, duplicate it and test the import there first.

Clean duplicate names before importing

Importing adds rows to the existing location list; it does not replace the list with only the file contents. Clean duplicate names first so entries, counts, filters, and reports stay readable.

Watch the steps

Pause the walkthrough on Match fields to check the mapped location columns.

Quick path

Follow these steps

  1. Open the inventory that should receive the locations.
  2. Open the side menu and choose Locations.
  3. Tap Import.
  4. Select the Excel or CSV file.
  5. On Match fields, map Location name and any optional fields you use.
  6. Tap Proceed with the import.

Use clean names before importing

Renaming locations after products or entries use them creates follow-up review work.

Watch the Web steps

Open an existing inventory in the Web app, go to Locations, upload the file, check Map Location Fields, then review the imported rows.

Sample column expectations

ColumnRequiredHow Mobile Inventory uses it
Location name valuesRequiredMap this column to Location name. Each non-empty row creates a location available in lists, entries, counts, filters, and reports.
Manager or ownerOptional when your app version shows a matching fieldMap this only when a matching field is available. Otherwise leave it unmapped, or store the note in an observations/details column.
Observations or DetailsOptionalStores extra notes, such as access instructions, zone details, or internal comments.
Parent, Zone, Aisle, Shelf, BinOptional only when your app version shows matching fieldsIf hierarchy fields are not shown during Match fields, put the full path in Location name, for example Warehouse A / Aisle 3 / Shelf 2.

Key screens

Open Locations from the inventory side menu.
Choose the Excel or CSV file from local storage, Drive, Dropbox, or the import-code flow.
Map the location-name column and any optional notes fields.
Return to Locations and check that the imported names look right.

Web key screens

Upload the CSV or Excel file from Locations.
Review the automatic field matches before importing.
Check the imported rows after the import finishes.

What this does not do

  • It does not delete locations that already exist but are not present in the file.
  • It does not create nested hierarchy unless the app shows hierarchy fields during mapping.
  • It does not merge duplicate names automatically.
  • It does not change product quantities or stock entries. It only creates locations for later use.

Next step

After importing, open the Locations list and confirm that the names and optional details are ready for daily stock work.