Publishing

Static maps for store locators

Export a ready-to-use locator for kiosks, stores, events, and external servers with fewer dependencies on API calls.

Export ready for external hosting
Fewer API calls on public usage
More stability in low connectivity
AI search included or excluded as needed
Illustration of a static map export panel with data, theme, and AI search options.
Static exportChoose data, theme, and AI

The export packages locations, layout, and selected features for an external server, CDN, or local device.

Illustration of an in-store kiosk using a static locator during low connectivity.
Offline kioskLocator available at the service point

In-store, event, and showroom experiences stay fast and reliable even when connectivity is limited.

Overview

Bring your locator into environments where connectivity is not guaranteed

Static maps let teams publish a packaged locator version with selected data, theme, and features. It is useful for in-store kiosks, event terminals, internal networks, external servers, and operations that need to reduce real-time API dependency.

Predictable performance

Static files load quickly from CDNs, simple servers, and local devices, reducing latency caused by dynamic calls.

Higher reliability

The locator remains available in stores, kiosks, and low-connectivity environments even when the network is unstable.

Offline operation

Teams can prepare experiences for fairs, showrooms, reception desks, and service points where internet access can fail.

Feature control

The export lets administrators decide what enters the package, including theme, data, media, and whether AI search is available.

Export options

Choose the right package for each environment

Administrators can generate a lightweight static map for simple directories or a more complete package for in-store and kiosk experiences.

Data and content

  • Published locations with name, address, categories, and coordinates
  • Description, opening hours, links, phone numbers, and contact information
  • Pins, promoted logos, and public images when configured
  • Filters and fields needed for local navigation

Theme and layout

  • Locator colors, typography, spacing, and borders
  • Desktop and mobile layouts defined in the visual editor
  • Custom pins and promoted pins
  • Option to include or hide header, filters, list, and details based on theme settings

Search and intelligence

  • Local text search for stores and categories
  • Optional AI search when the target environment can make external calls
  • AI exclusion for offline kiosks or controlled environments
  • Filter-based fallback when connectivity is limited

Publishing

  • Exportable package for an external server, CDN, or local device
  • Files ready for review before distribution
  • Manual versioning to publish a new export when data changes
  • Use on public pages, intranets, kiosks, and temporary installations
Where to use it

From the public website to the store counter

The same location base can support very different experiences. Static export reduces operational dependencies without forcing the business to rebuild its locator from scratch.

Kiosks and stores

  • Self-service terminals to find departments, dealers, or service points
  • Sales tablets with a catalog of branches and partners
  • Showrooms that need to work despite unstable Wi-Fi
  • Events and trade shows with shared or limited networks

External servers

  • Hosting on owned or partner infrastructure
  • CDN delivery to reduce global latency
  • Integration into corporate sites with strict network rules
  • Environments where direct calls to the public API are not desired

Low connectivity

  • Regions with unstable mobile connections
  • Stores in malls, warehouses, or locations with weak signal
  • Operations that need a consistent experience during traffic spikes
  • Contingency plans for important campaigns and launches
How to generate it

Export a static version in six steps

The workflow stays simple: review data, choose features, generate the package, and publish it where it makes sense for your business.

1

Review published locations

Confirm entries, coordinates, categories, hours, contacts, and links are up to date before generating the package.

2

Adjust the public theme

Use the visual editor to validate desktop and mobile layout, pins, colors, filters, cards, and header behavior included in the static version.

3

Open static export

In the locator admin panel, open the publishing or export area and choose to generate a static map.

4

Choose included features

Select data, images, filters, and search behavior. Include AI search only when the target environment can make external calls.

5

Generate and test the package

Download or publish the export, open it on desktop and mobile, and test search, filters, pins, and location details before distribution.

6

Host and update when needed

Upload files to an external server, CDN, intranet, or local device. Generate a new version whenever locations, theme, or search rules change.

Use cases

Consistent experiences for companies of any size

Static maps help small teams that need a simple directory and larger operations that require control, scale, and contingency.

Retail and franchises

Offer store, service, or pickup search on kiosks and tablets inside the physical store.

Events and tourism

Publish maps of points, booths, attractions, and partners in environments with shared networks or limited access.

Industry and distribution

Deliver distributor and reseller directories on partner servers without relying on real-time integration.

Healthcare, education, and services

Create local lookup experiences for branches, campuses, clinics, or service points with high operational availability.

Keep exploring

Related features

Visual theme editor

Customize layout, map, and pins before generating the static version.

Learn more →

Analytics

Analyze online usage to decide what to optimize in the export.

Learn more →
Get started

Publish your hosted locator in minutes.