This guide is especially relevant for enterprise asset operations teams managing assets across multiple sites, regions, and business units, where structured location hierarchies are critical for visibility and control.
Asset tracking software can help you quickly make sense of all the locations and sublocations associated with your business equipment. You can import all these helpful details into EZO using our handy import wizard. Read on to find out more.
In enterprise environments, accurate location data forms the backbone of asset visibility, enabling better tracking, reporting, and operational coordination across distributed teams.
Before you start, it would be helpful to go through this quick guide on importing basics.
1. Importing New Locations
To begin importing new locations into EZO, go to Locations โ Import Locations โ Add New Locations.
You can now choose a spreadsheet with all your location details and click Upload. An example of a location spreadsheet is given below, with a simple header row and a list of all the locations with corresponding values:
For enterprise teams, bulk imports like this enable rapid onboarding of large location datasets without manual entry, ensuring scalability from day one.
You can now map the columns from your CSV to columns found in EZO. You can also edit a column at any time, or skip it entirely:
It is important to note that each column must either be skipped or mapped before the import can start.
You may ask the system to skip the header row โ that is, titles such as โCityโ or โCountry Codeโ โ in your CSV when importing. To do this, select the checkbox โIgnore header row in Excelโ.
When youโre done mapping all your columns, click โPreviewโ to get things going:
The system shows you a preview of all the details that are going to be imported. If everything looks good, click โImportโ.
Your locations have been imported successfully! You can also expand the parent locations to see the nested locations under them:
This hierarchical structure is particularly important in enterprise environments where assets must be tracked across layered location models (region โ site โ facility โ sub-location).
2. Updating Existing Locations
You can update existing locations en masse using a CSV import. Simply go toย Locations โ Import Locations โ Update Existing Locations. Please note that using the โAdd New Locationsโ button for this will create duplicate locations!
After youโve clicked โUpdate Existing Locationโ, follow the same steps you would when adding a new location. This time, rather than creating those locations afresh, EZO will simply update the values associated with them in the system.
For enterprise operations, this ensures that location data remains accurate and up-to-date without requiring time-consuming manual corrections.
3. Importing Sublocations
You can import sublocations into the system right when youโre adding or updating locations! As an example, say you have a Head Office with two Warehouses (1 and 2), with the first warehouse also having an aisle called Rack 1. This set of associations is shown below:
The associations under โHead Officeโ can all be added through a CSV as follows:
Use the โNest Location Underโ field to create a simple Parent > Child association (such as โWarehouse 1โ being nested under โHead Officeโ). For adding further associations to sublocations, useย the / symbol. In the example above, โRack 1โ is nested under โHead Office/Warehouse 1โ, meaning Rack 1 is present in Warehouse 1, which in turn is located in the Head Office.
Note: You cannot use the โNested Under Locationโ field to create locations. This field will only create associations. To create a location, simply add it separately to the CSV as we have done above.
Such structured hierarchies are essential for enterprise asset operations, enabling precise tracking, reporting, and accountability across complex location networks.
And thatโs it, youโre on your way to adding hundreds of locations to EZO in moments!
