Why Salesforce

Field execution that works with your Salesforce investment.

FieldKo is installed in your own Salesforce org from AppExchange. Managers and admins work in Salesforce, reps use the FieldKo Atlas app, and field data syncs into the same org as the rest of your customer data.

Book a Demo See FieldKo on AppExchange

The problem

A separate field app means a separate system to run.

Another set of logins.Standalone field apps need their own users, permissions and security review.

Customer data in two places.Accounts live in Salesforce while store visits live somewhere else, so someone has to reconcile them.

An integration to maintain.Every change to accounts, products or territories has to be copied across.

What it does

What you get by staying in Salesforce.

Salesforce security reviewEvery solution listed on AppExchange must pass a security review by Salesforce before it can be listed.

Managed packagesInstalled and upgraded as managed packages, with a namespace that keeps FieldKo's objects and fields separate from yours.

No hit to your org limitsPublicly listed AppExchange packages don't count against your edition's limits for apps, objects and tabs.

Sandbox firstInstall and test FieldKo in a Salesforce sandbox before you roll it out in production.

Field data in your orgVisits, photos, answers and orders become Salesforce records in your org when the device syncs.

Salesforce loginReps log in with their Salesforce account, so your org's login policies apply.

Your permission modelAccess follows your profiles, permission sets and sharing, including account teams.

Native reports and automationFieldKo records work with Salesforce reports, dashboards, Chatter, flows and APIs.

Client portals on Experience CloudGive brand partners their own view of visits, photos and survey answers through a Salesforce Experience Cloud portal.

Configurable where possibleMenus, visit actions, task types, surveys and labels are set from Salesforce. When your process needs more, we scope the extension with you.

What you'll see

Installed in Setup. Controlled from Salesforce.

In Salesforce

Installed packagesSetup · Installed Packages

Managed

FieldKoRetail Field Management: data model, Salesforce screens, permission sets

FieldKo NativeSync and metadata services, mobile settings, sync logs, attendance

FieldKo Manager Permission SetFieldKo Native Permission Set

Two managed packages: FieldKo for the data model and Salesforce screens, and FieldKo Native for sync and mobile settings.

From Salesforce to the app

How changes reach repsFieldKo in Salesforce → FieldKo Atlas

Menus, visit actions, sync settingsAny sync

Labels and translationsManual Sync

Objects, fields and layoutsMetadata Collector, then Reset Sync

Records, sharing, call cyclesAny sync

Admins change what reps see from Salesforce settings. Each kind of change reaches devices on a set kind of sync.

Questions

Common questions

Does FieldKo replace Salesforce?

No. FieldKo runs inside your Salesforce org. Your accounts, users and reports stay in Salesforce, and FieldKo adds the field app and the screens managers use to plan and review store work.

Can FieldKo work with our existing Salesforce setup?

Yes. FieldKo installs into your existing Salesforce org. We review your data model, permissions and workflows with you and agree the setup and project scope.

Where is our field data stored?

In your own Salesforce org. Until a rep's device syncs, their work is held in an encrypted database on the device. Who can see it follows your Salesforce permissions.

Can we give clients or brand partners their own view?

Yes. FieldKo supports client portals built on Salesforce Experience Cloud, so each partner sees the visits, photos and survey answers shared with them.

Can we test it first?

Yes. Install and test FieldKo in a Salesforce sandbox before you roll it out in production.

Best practices

Related best practices.

Performance & AnalyticsMake field data trustworthy across large retail teamsSet governance for store, product, campaign and visit data so reporting remains useful across regions.3 min read Strategy & LeadershipThe retail execution maturity modelAssess whether your organization merely records visits or consistently turns store observations into improvements.3 min read Retail Execution ExcellenceRetail execution: a practical operating modelTurn field activity into reliable in-store outcomes through a repeatable plan, execute, verify and improve cycle.5 min read

Browse all best practices →

See FieldKo running in a Salesforce org.

We'll show you the packages, permission sets and settings your admin works with, and the app your reps use.

Book a Demo