How to: Prepare Imports for bulk edits/additions to Hierarchy

The location importer is an internal tool that Zenput uses to help manage customer's hierarchies. In order to accomplish this a .CSV template is utilized that follows a consistent structure so that data is not overwritten and duplicate locations are not created.

There are a couple of unique reasons why you may want to utilize the bulk importer:

  • Adding a list of 10+ locations
  • Changing the information of locations that exist in your account in bulk (email, phone number, name of the location, or General Attributes associated with a location)
  • Adding/Updating Users to multiple locations at once
  • Moving locations and/or users from different teams
  • Removing a list of locations from your account at once
  • Adding Regions to existing locations to enable the use of Location attributes

To gather this information for your existing locations to provide to support, please see this article How to: Export Locations . 


In order to do this, we separate location and user information into different templates. Below you will find the Templates & information on the necessary column titles that are required for uploading information.

Location Template

  • Name (Column A) (Required)

    • The exact name the location will be called in Zenput
    • If already exists will need the exact name of the Location. 

  • Address (Column B) (Required)

    • The street address of the location in Zenput, This is ONLY the street address, do not include city, state, zip. (EX. 123 example st.)

  • City (Column C) (Required)

    • The city the location is in.

  • State (Column D) (Required)

    • The state the location is in (can also be the region if no state exists i.e locations outside the U.S.)

  • Country (Column E) (Required)

  • Zip (Column F) (Required)

    • Zip or postal code of location

  • Region (Column G) (Recommended)

    • To allow the use of Location Attributes, this column must be included here. 

  • Email (Column H) (Not Required)

    • The email address of the location. Can be more than 1. 
      • Useful if you want to send completed submissions to a location directly.

  • Phone(Column I) (Not Required)

    • Phone number of location
      • Useful if they want to receive text notifications from Zenput.
        (Landlines Can NOT receive notifications) 

  • External Key (Column J) (IMPORTANT(Required)

    • Every location must include/have an external key that is unique. This can be any combination of numbers and/or letters that you prefer, however, each individual location MUST have a unique key in the company.
      • This is how we overwrite existing locations with new information if we upload a list of locations with the same external key as a location that already exists in your account it will overwrite the previous location and all data from the past will be attributed to the newly uploaded location.
    • If you want to make sure that the external key you are using is unique from other locations in your account, simply go to (Locations) and hit the "export" button in the top right of the screen, you will be emailed a list of your locations that will show you all location external keys. Here is a more thorough article on how to do this How to: Export Locations. 

  • Active (Column K) (Not Required)

    • If you want to deactivate a current list of your locations, add this column.
    • The options for this column are (blank=no change; 0=deactivate; 1=activate)
      • Recommended to only use if you want to deactivate a list of your existing locations

  • Lat (Column L) (Not Required)

    • Latitude of the location
    • NOTE: IF LAT AND LON ARE PRESENT, address, city, state, country, and zip are no longer required.

  • Lon (Column M) (Not Required)

    • Longitude of the location
    • NOTE: IF LAT AND LON ARE PRESENT, address, city, state, country, and zip are no longer required.

  • Team0 (Column N) (Not Required)

    • Is a four-digit Team ID that the system creates, this is used only for bulk editing locations into different teams. 
    • If there is no change to teams, this column is not required. 

  • Team Action (Column O) (Not Required)

    • The options for this column are (blank=no change; 0=deactivate; 1=activate)
      • Recommended to only use if you want to deactivate Teams. 

  • General Attributes/Tag(s) (Column P & Q) (Not Required)

    • You can have as many or as few general attributes as you want, all attributes must be in a separate column with the headers tag1, tag2, tag3 and so on.

  • Tag Action (Column R ) (Required when General Attributes (tags) are present)
    The action we need to perform to the General attribute .
    • Update - Adds general attributes to the location's existing set of general attributes, it does not overwrite the tags that may already be associated with an existing location / Creates general attributes for a NEW location
    • Replace - Removes existing general attributes from an existing location and replaces with what is being uploaded
    • Delete - Deletes the general attributes you are uploading from the existing location

Here is an example of a filled out location template where we are adding new locations to an account. Location Template here

User Template

  • first name (Column A) (Required)

    • The exact name the user should be assigned
      • Often "Store" if location level user (submitter) or first name for users above location level users (managers). 

  • last name (Column B) (Required) 

    • The exact name the user should be assigned
      • Often "456"(location number) if location level user (submitter) or last name for the users above location level users (managers).

  • Email (Column C) (Required)

    • Unique email for each user account is required
      • In most cases, location level users (submitters) share login information.
      • Users above location level users (managers) have unique emails

  • Permission (Column E) (Required)

  • Role (Column D) (Required)

    • The role the user should be assigned (must be an existing role in your company)
      • The role is often used for assigning projects & reporting, every user should have a role. 
  • Team Name (Column F) (Required)

    • The exact name of the team, as it appears in the UI (User interface), where the user is being added to. 

  • External Key (Column G) (Optional)

    • Only necessary if adding users to existing locations. 

Here is an example of a filled out user import template User Template here 

If you have questions or are unsure of how to do something, please contact 


Below are csv. files of a Location and User Import Template that you can download by clicking below. 

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.