Common Location-Based Use Cases
Multi-location dealer group
Scenario: Your organization has multiple stores.
Common setup:
- Create one Location document per store.
- Connect each Location to its Place record so address details are available.
- Create one location detail route per Location (for example, /locations/downtown).
- Use a Locations section on a global page (such as the homepage) to show all stores as cards.
Service-only location
Scenario: You have a location that should focus on service, not vehicle inventory.
Common setup:
- Hide the inventory CTA on the location detail page.
- Exclude the location from selectors that should not apply (for example, trade-in and finance application).
- Keep the location available in selectors that should apply (for example, service scheduling and contact).
Location-filtered reviews on a landing page
Scenario: You want a landing page that highlights reviews for specific stores.
Common setup:
- Add a Reviews section to a content page.
- Enable location-specific mode.
- Select the locations you want to feature.
- Set the initial and expanded review counts based on the page length and design.
Custom pricing or CTA labels for one location
Scenario: You want different wording for a label or CTA at a specific store.
Common setup:
- Add a label override on the Location.
- Provide the replacement text.
Keep a location detail page but hide a location from forms
Scenario: A location should have a public page, but should not be selectable in specific form flows.
Common setup:
- Keep location page visibility enabled.
- Remove the location from the form selectors where it should not appear.
New location with no address yet
Scenario: You want to start setup, but the address record is not available.
Common setup:
- Have an admin create the Place record first.
- Connect the Location to that Place.
- Finish configuring the Location after the Place is connected, since many fields depend on that connection.