> ## Documentation Index
> Fetch the complete documentation index at: https://support.fieldko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a New Store

> Create a store account that FieldKo can plan, map, and sync to the right rep.

In FieldKo, a store is a Salesforce account. To appear in planning tools, on maps, and in a rep's app, the account needs the right record type, coordinates, and an owner or account team member who's a rep. Use this checklist each time you open a new store, so it's ready for its first visit.

## User Permissions Needed

| To do this | You need |
| - | - |
| Create accounts | Create permission on accounts |
| Assign default visit templates and edit account sets | FieldKo Manager Permission Set |

## Before You Begin

* Check which record types FieldKo plans visits for. On the **FieldKo Configuration** tab, click **Basic**, and look at **Account Record Types for Visit Planning**. After install, it's `Store`.
* Make sure your own Google Maps key is on the **FieldKo Configuration** tab, under **Calendar and Map**. See [Google Maps Key](/admin/installation#google-maps-key).
* Know which rep covers the store.

## Add the Store

Complete these steps in order. Each step links to the full instructions.

<Steps>
  <Step title="Create the Account with the Right Record Type">
    Create the account, and select a record type that's in **Account Record Types for Visit Planning**. The **Visit Calendar**, **Call Planning**, and other planning tools show only accounts with those record types.

    If an account is saved without a record type, FieldKo gives it the user's default account record type, or `Store` if there isn't one. To bring in many stores at once, see [Import and Update Data](/platform/data/import).
  </Step>

  <Step title="Enter the Shipping Address">
    Enter the store's full shipping address. FieldKo looks up coordinates from the shipping address, not the billing address.
  </Step>

  <Step title="Add Coordinates">
    On the account, click **Update Geolocation**. FieldKo looks up the shipping address with your Google Maps key and saves the shipping latitude and longitude. Run it again whenever the shipping address changes.

    Coordinates put the store on the **Visit Planner** and **Account Map**, and let the app check the rep's distance at check-in. If your org stores coordinates in its own fields, see [Where Account Coordinates Come From](/admin/call-cycles-and-visits#where-account-coordinates-come-from).
  </Step>

  <Step title="Assign the Owner or Account Team">
    Make the rep the **Account Owner**, or add them to the account team. The app syncs only accounts a rep owns or shares through an account team. If your org uses the **Public Group** user reporting hierarchy, share the account with the rep's public group instead. See [Accounts in Scope](/admin/offline-data#accounts-in-scope).
  </Step>

  <Step title="Optional: Add the Store to Account Sets and Brands">
    To include the store in field campaigns and recurring visits that use an account set, open the set on the **Account Set** tab, and add the store. See [Create and Edit Account Sets](/managers/field-campaigns#create-and-edit-account-sets).

    If **Enabled** is selected on the **Branding** custom setting's **Brands** record, link the store to its brand in the brand account's **BrandAccounts** related list. Reps receive only stores linked to their brands.
  </Step>

  <Step title="Optional: Set Up Ordering and Ranging">
    If reps take orders or record core ranging at the store, add a **FieldKo Contract** for its price book and a **Ranging Contract** for its product set. See [Link Price Books to Accounts](/admin/products-ordering-ranging#link-price-books-to-accounts) and [Core Ranging](/admin/products-ordering-ranging#core-ranging).
  </Step>

  <Step title="Optional: Assign a Default Visit Template">
    To create visits for the store with the same tasks every time, open the visit template, click **Assign to Accounts**, and select the store. FieldKo sets the store's **Default Visit Template**. See [Assign Default Templates to Accounts](/admin/call-cycles-and-visits#assign-default-templates-to-accounts).
  </Step>

  <Step title="Plan the First Visits">
    Plan visits on the **Visit Calendar**, or set a visit frequency with a recurrence pattern or recurring visits. The rep needs an active call cycle that covers the visit dates. See [Plan Visits in Salesforce](/managers/plan-visits) and [Set Up Recurrence Patterns](/managers/field-campaigns#set-up-recurrence-patterns).
  </Step>
</Steps>

**To confirm:** The store appears when you search for it on the **Visit Calendar** with its rep selected, and its pin appears on the **Account Map**. After the rep syncs, the store and its first visit appear in the rep's app.

<Tip>
  If a rep doesn't see a new store after syncing, check the owner or account team first, and then the store's record type. See [Rep Has No Visits, or Records Are Missing](/admin/support-diagnostics#rep-has-no-visits-or-records-are-missing).
</Tip>

## See Also

* [Set Up Call Cycles, Tasks, and Visit Templates](/admin/call-cycles-and-visits)
* [Plan Visits in Salesforce](/managers/plan-visits)
* [Record Types and Validation Rules](/platform/customize/record-types-and-validation-rules)
* [Keep Data Clean](/platform/data/data-quality)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.