Skip to main content
All CollectionsImport/Export
Importing Locations
Importing Locations
Paul Sullivan avatar
Written by Paul Sullivan
Updated over 2 months ago

In this article

Objective

Use Import/Export to add Locations in bulk to your instance of Coconut or perform a mass update on existing Locations records.

Steps

To perform a Locations import, download the .csv template file, complete the file as indicated, and import it into your instance of Coconut.

NOTE: Coconut currently supports an import limit of up to ~500 Locations records.

Import_Locations.gif

Download the .csv template file

  1. From the navigation menu, click Import/Export

  2. From Data Type, select Locations

  3. Click Export Data to download a template in the supported format to use for the Locations import

    • NOTE: If you have not added a Location to your instance of Coconut, the download will include only the column headers

When Export Data is clicked, an audit operation is performed on the Locations data that exists in your instance of Coconut. If this is not the first time you are adding Locations to your instance of Coconut and you have received an error message, skip ahead to Resolve formatting errors.

Complete the .csv file

For a sample Locations CSV, jump to the end of the article.

  1. Navigate to where the downloaded .csv template is located on your device

  2. Save the .csv template file to your desired location, based on your organization’s best practices and/or policies

  3. Open the .csv file and complete based on the following parameters:

    • NOTE: Your .csv template may include additional fields depending on your Coconut package and what add-ons (if any) are included; furthermore, values included in the table below may or may not apply to your instance of Coconut, depending on your package

Field

Description

Required/Optional

external_id

A unique identifier that represents the Location outside of your instance of Coconut

Required

new_external_id

Used to update the external_id to a new value (leave blank if no update required)

Optional

name

The name of the Location

Required

slug

An identifier (for example, the Location’s name); the slug is what is appended to booking shortcut links instead of the Location’s ID

Optional

virtual

A code that indicates whether the Location is virtual or physical

0 = Physical Location

1 = Virtual Location

Required

address

The street address of the Location

Required (if Physical Location)

city

The city of the Location

Required (if Physical Location)

prov_state

The 2-character province or state code for where the Location is located (for example, ON = Ontario, NY = New York)

Required (if Physical Location)

country

The 2-character country code for where the Location is located (for example, CA = Canada, US = United States)

Required (if Physical Location)

postal_zip

The postal code or zip code for where the Location is located

Required (if Physical Location)

timezone

The Location’s timezone (enter in PHP format; for reference: https://www.php.net/manual/en/timezones.php)

Optional

lang

A 2-character code indicating the primary language used at the Location (EN, FR, and ES are available for English, French, and Spanish respectively)

Required

email

The email address where communication sent to the Location will be forwarded

Optional

phone

The phone number that will be associated with the Location

Optional

cell_phone

The cell phone number that will be associated with the Location (digits only)

Optional

phone_ext

The extension that is associated with the Location’s phone number

Optional

visibility

A code that indicates if the Location is an option for booking appointments

0 = Public (Location displays as part of online booking experience)

1 = Private (Location is only available for staff to schedule appointments)

2 = Invite Only (Location is only available to be booked through a shortcut)

Required

sunday_open

The time the Location opens on that specific day, using HH:MM:SS formatting (for example, 09:00:00);

repeat for each day of the week

Optional

sunday_closed

The time the Location closes on that specific day, using HH:MM:SS formatting (for example, 17:30:00);

repeat for each day of the week

Optional

Import the .csv file

  1. From the navigation menu, click Import/Export

  2. From Data Type, select Locations

  3. Do one of the following:

    • Drag and drop the completed .csv file onto the upload target

    • Click or select from your computer to upload the .csv file

  4. Verify the .csv file is without errors by reviewing the confirmation message that displays upon upload

    • NOTE: If the Import button does not activate, it indicates there are errors in the .csv file; click Show Errors to review a list of row items in the .csv file that require correction, correct the errors, and re-upload the corrected .csv file (review Resolve formatting errors for more info)

    • NOTE: If the Import button activates, it indicates that the .csv file is formatted correctly; details of what will be imported display for your review

  5. Click Import

The Locations are imported, and can be accessed by navigating to Locations.

Resolve formatting errors

For tips to resolve the most common formatting errors, please visit this article.

  1. From the error message, click Show All

  2. A details list displays; review the details to confirm what updates are required to which Locations

  3. Complete the required updates by navigating to the existing Locations and updating required fields or updating within the .csv file

The following demonstrates resolving formatting errors by reviewing the errors and updating a revised .csv file. While the example shows a Staff import, the same steps apply.

Resolve_formatting_errors.gif

Resolve external_id errors

An external_id is required for each Location. This identifier enables a database restore should any error occur during the import process. If the error message notes that external_ids are missing, they can be added by either auto-generating an ID or manually inputting an ID.

Auto-generate an external_id

  1. From the error message that displays, click Generate external IDs

  2. An external_id is automatically generated for each item missing the field

    • Example of an auto-generated external_id: coco_loc_da62fc03-986a-4184-a8aa-c44ccf108871

Locations_External_IDs.gif

You can now continue with the import process.

Manually generate an external_id

  1. From the error message that displays, click Show All

  2. Note the Location(s) where an external_id is required

  3. From the navigation menu, click Locations

  4. Navigate to a Location that requires updating

    • Click the More Actions () icon

    • Click Edit

    • Navigate to the External ID field and click the Lock (🔒) icon to unlock the field

    • Click OK

    • Enter your desired External ID

  5. Click Save

  6. Repeat steps 4 and 5 for each Location that requires updating

You can now continue with the import process.

A note on access and visibility

Admin users can import/export Locations.

Did this answer your question?