Managing Stores Updated 2026-02-22

Using custom fields for store locations

What this article helps you do

Add custom fields (e.g. “Wi-Fi password”, “Parking info”, “Specialist”) to your stores and display them on the list view, popup, or both.

Before you start

  • Mapstore is set up with at least one store
  • You can have up to 5 custom fields per shop

Step-by-step instructions

1. Define custom fields

  1. In Mapstore, go to Custom fields (from the main nav or via Stores -> Add store or edit a store).
  2. Click Add custom field.
  3. Enter a Field name (e.g. “Parking” or “Wi-Fi”).
  4. Choose the Field type: Text (plain text) or Link (URL).
  5. Choose Visibility position: show in List view, Popup, or both.
  6. Click Create field.
  7. Repeat for more fields (up to 5 total).

2. Add values to stores

  1. Go to Stores and open a store (or create one).
  2. Scroll to the Custom fields section.
  3. Fill in the values for each custom field you defined.
  4. Save the store.

3. Include custom fields in CSV or Google Sheets (optional)

If you import from CSV or Google Sheets, use custom field headers in this format:

  • cf_text_FieldName for text fields
  • cf_link_FieldName for link fields

Examples:

  • cf_text_Parking
  • cf_link_Booking_URL

You can also control where a field shows:

  • cf_text_l_FieldName (list only)
  • cf_text_p_FieldName (popup only)
  • cf_text_lp_FieldName (list and popup)

How to verify it worked

  1. View your store locator on the storefront.
  2. Check the list view and the store popup - your custom field labels and values should appear where you set visibility.
  3. Edit a store and change a custom field value; the change should show on the storefront after saving.

Common issues and fixes

IssueFix
”Define more” or “Add custom field” is missingYou’ve reached the limit of 5 custom fields. Remove or edit an existing one before adding another.
Custom field doesn’t appear on storefrontCheck that the field’s visibility includes List view and/or Popup, and that you’ve saved values for that store.
”This name conflicts with an existing CSV header key”Pick a different field name that doesn’t match a built-in column (e.g. avoid “name”, “address”, “phone”).
Column from CSV not mapped to custom fieldUse the cf_text_FieldName or cf_link_FieldName format. Plain column names are not mapped as custom fields.