Installation

Requirements, install, and the three steps from a fresh install to a working locator.

Location groups

What a group carries — field layout, per-site URLs and templates — and why there can be more than one.

Addresses, coordinates you can trust, and opening hours that are right at midnight and in the shop's own timezone.

When Fold asks a provider for coordinates, when it doesn't, and why every answer — misses included — is cached.

A bounding box, then a haversine, in one query — and the three answers a search can give.

craft.fold, the location query and its parameters, search results, and everything a location exposes.

The ready-made locator, progressive enhancement taken literally, the three map providers, and changing the markup.

GET /fold/search.json — parameters, the response shape, and the field that tells "not found" from "nothing near".

Link a location to a Commerce inventory location and answer "which shop near me has this in stock". Pro.

CSV in, CSV or JSON out, and a round trip through a spreadsheet that updates rather than duplicates. Pro.

Getting several hundred shops in, geocoded and back out again — without a browser timing out.

Every setting, its default, and the two worth changing before launch.

Who can see, edit and delete locations — and why groups and settings are admin-only.

What Lite does, what Pro adds, and why a lapsed licence still shows a map.

Missing pins, empty searches, a 429 from the endpoint, and opening times that are hours out.

How Fold compares to WP Store Locator, what it costs, and the questions worth asking before you install it.