RP Store Locator – Import File Guide

This knowledge base article explains how to import the RP Store Locator CSV file and provides a detailed description of every column in the import template.

Use this guide when preparing bulk location imports for Rose Perl–powered store locators.

File Format

File type: CSV (Comma-Separated Values)
Encoding: UTF-8 recommended
Header row: Not required, but strongly recommended. Column names do not need to match exactly, as you can map each column manually during the import step.

Column Reference

Below is a complete explanation of each column in the import file, in the order they appear.

Core Store Information

Boolean values: Unless otherwise stated, boolean fields must use 1 (true) or 0 (false).

title
Public-facing store or location name.
id
Optional unique identifier for the location. Useful for updates or re-imports. If omitted, the system will auto-generate one.
description
Short description of the location (services, notes, or additional context). Supports plain text.
priority
Numeric value used for sorting or featured locations. Higher numbers typically surface first.
status
Controls visibility of the location.
- 1 = active (visible)
- 0 = inactive (hidden)
Validation: Must be 0 or 1.

Contact Details

phone
Primary phone number for the location.
email
Contact email address associated with the location.
fax
Fax number (optional / legacy).
web
Website URL for the location (full URL recommended, including https://).
webdisplay
Display-friendly version of the website URL (used for UI labels).

Media & Branding

store_image
Primary image URL for the location (storefront, interior, or brand image).
secondary_image
Optional secondary image URL.
marker_image
Custom map marker image URL for this location.

Address & Geo Data

address
Primary street address.
address2
Secondary address line (suite, unit, floor, etc.).
city
City name.
state
State, province, or region.
zipcode
Postal or ZIP code.
country
Country name or ISO code.
latitude
Latitude coordinate. If provided, geocoding is skipped.
longitude
Longitude coordinate. If provided, geocoding is skipped.

Tip: If latitude and longitude are empty, the system will attempt to geocode the address.

Tags & Classification

tags
Comma-separated tags used for filtering and search (e.g. dealer, flagship, repair).
extrafield
Flexible metadata field for custom use cases (internal labels, legacy IDs, etc.).
is_dealer
Boolean flag indicating whether the location is a dealer.
- 1 = dealer
- 0 = not a dealer
Validation: Required. Must be 0 or 1.

Hours & Scheduling

schedule
Legacy or simple schedule text (optional).
operating_hours
Structured operating hours definition used by modern store locator UI components.
date_override_status
Enables or disables date-specific overrides.
date_overrides
JSON or structured data defining special hours (holidays, events, closures).

Sharing & Visibility

shareable
Boolean flag indicating whether the location has a public shareable page.
shareable_link
Custom or system-generated shareable URL for the location.

Large Imports (2,000+ Locations)

If you are importing more than 2,000 locations, additional Google Maps API configuration is required.

Required Google API Setting

To allow backend-based geocoding and bulk imports, you must add the following to your Google API key restrictions:

https://*.roseperl.com

This enables Rose Perl’s backend services to safely perform high-volume geocoding and import operations without client-side limits.

Failure to update this restriction may result in:

Partial imports
Geocoding failures
API quota or permission errors

Common Import Error: Required Columns Missing

🔴 Common Mistake (Promap Alert)
Missing required Store Name or Address fields
This is the most frequent reason imports fail. The system cannot create a store without a name and address.

If you see the error:

Column [Store Name] and [Store Address] are required

This means the import file does not contain all required information to create a store record.

Why this happens

Required fields were not provided in the CSV
Columns were not mapped correctly during the import step
The file structure does not match the Rose Perl Store Locator template

How to fix it

Download and use the sample template file (available on the import page)
Fill in the required fields exactly as shown in the example
Ensure all mandatory columns are present and populated

Required fields to create a store

At minimum, the following must be provided:

Store Name (title)
Store Address (address, city, state, zipcode, country)

Latitude and Longitude are not required. These values are automatically generated during import to create the map location.

Column Mapping During Import

🔴 Common Mistake (Promap Alert)
Incorrect column-to-field selection
Selecting the wrong field from the dropdown (or leaving required fields set to Ignore Column) will cause validation errors or incomplete stores.

When importing your file, you must map each column correctly using the dropdown selectors.

Match each column in your spreadsheet to the corresponding Rose Perl field
Columns that are not needed should be set to Ignore Column
Do not map extra or duplicate fields

Important: You do not need to select or provide Latitude and Longitude. These are automatically generated.

Import Mapping Example

UI Labels Explained (Exact Match)

When mapping columns during import, you will see the following dropdown labels exactly as shown in the interface:

Ignore column – Do not import this column
Store Name – Maps to title
Store Address – Maps to address
Store Address2 – Maps to address2
City
State
Zipcode
Country
Phone Number
Fax
Email
Website
Website Display As
Description
Priority
Tags
Schedule of Store
Store Image Url
Secondary Image Url
Marker Image Url

🔴 Common Mistake (Promap Alert)
Mapping address fields incorrectly
Make sure Store Address, City, State, Zipcode, and Country are each mapped to their matching CSV columns — do not combine them into one field.

The example below shows correct column-to-field mapping during import:

Field Reference Table

The table below lists each available field, a short description, and whether it is required to successfully create a store.

Field	Description	Required
title	Store or location name displayed publicly	Yes
id	Unique store identifier for updates or re-imports	No
description	Short description of the store	No
priority	Sorting weight for featured locations	No
status	Store visibility flag (`1` = active, `0` = inactive) Defaults to 1	No
phone	Primary store phone number	No
email	Store contact email address	No
fax	Store fax number	No
web	Store website URL	No
webdisplay	Display-friendly website label	No
store_image	Primary store image URL	No
secondary_image	Secondary store image URL	No
marker_image	Custom map marker image URL	No
address	Street address	Yes*
address2	Suite, unit, or secondary address	No
city	City name	No*
state	State or region	No*
zipcode	Postal or ZIP code	No*
country	Country name or ISO code	No*
latitude	Latitude coordinate	Conditional
longitude	Longitude coordinate	Conditional
tags	Comma-separated filter tags	No
extrafield	Custom metadata field	No
is_dealer	Dealer flag (`1` = dealer, `0` = not dealer)	No
schedule	Simple schedule text	No
operating_hours	Structured operating hours	No
date_override_status	Enable date overrides (`1` or `0`)	No
date_overrides	Special hours or closures (JSON)	No
shareable	Enable public share page (`1` or `0`)	No
shareable_link	Public shareable store URL	No

* Address fields are required unless both latitude and longitude are provided. City, State, Zip and Country are not required but strongly recommended.