Skip to main content
Retail execution metrics turn what reps record in the FieldKo Atlas app into numbers you can manage: whether stores get visited, whether the work gets done, and whether the shelf looks the way it should. Use this page to see what each metric measures, how to calculate it, and which FieldKo data feeds it. Each metric links to a report recipe with step-by-step instructions. Every visit, task, survey answer, ranging, order, pack-out, and attendance record that reps sync from the app is a Salesforce record, so you build these metrics with standard Salesforce reports and dashboards. FieldKo includes report types, but no ready-made reports. To see which report types come with FieldKo, see Report Types and What They Include.

Metrics at a Glance

Select a metric to open its report recipe.

What Each Metric Tells You

Coverage and Visit Frequency

Coverage tells you whether your team reaches the stores it’s responsible for. A store that isn’t visited can’t be fixed, so low coverage usually explains poor results in every other metric. Visit frequency adds rhythm: high-value stores often need weekly visits, and smaller stores monthly. FieldKo records each store’s Last Check-Out when a visit is completed, and if your company uses recurrence patterns, flags each store’s Next Visit Due as Past Due or Due in Future.

Call Compliance and Strike Rate

Call compliance compares the visits in the plan with the visits reps completed. It shows whether the call plan is realistic and whether reps follow it. Strike rate shows how often a completed visit turns into an order, which measures selling effectiveness rather than activity.

Time in Store

Time in store shows whether reps spend enough time to do the job, and whether visits run long. FieldKo calculates Actual Time Spent (Mins) from each visit’s check-in and check-out, so you can compare it with Planned Time Spent (Mins).

On-Shelf Availability, Out of Stock, and Distribution

These come from core ranging. Each time a rep records ranging, FieldKo saves one ranging line item for every product in the store’s product set, marked present or not present. OSA is the share marked present; the out-of-stock rate is the share not present. Numeric distribution looks at one product across stores: the percentage of stores where it’s on the shelf. These metrics matter because a shopper can’t buy what isn’t there.

Share of Shelf and Planogram Compliance

Share of shelf compares your facings with the whole category. Planogram compliance checks whether products are in the agreed positions. FieldKo doesn’t have dedicated facings or planogram fields, so you capture these with survey questions. To make those answers reportable, see Design Surveys and Tasks for Reporting.

Promotion Compliance

Promotion compliance shows whether a promotion, display, or price point is in place in the stores that should have it. In FieldKo, you roll out the work with a field campaign, and reps confirm execution with survey questions on the campaign’s tasks.

Order Value per Visit and Pack-Out Rate

Order value per visit links field activity to revenue. Pack-out rate measures how quickly reps or merchandisers stock product: FieldKo calculates Pack Out Rate (minutes) as the minutes spent per case packed out, so a lower number is faster.

Perfect Store Score

A perfect store score combines several metrics into one number per store, weighted by what matters most to your business, for example availability 40%, planogram 30%, promotion 20%, and pricing 10%. Agree on the weights before you build it, and keep them stable so scores are comparable over time.
Start with coverage, call compliance, and OSA. They use data FieldKo captures on every visit, so you can report on them without any survey changes.

Before You Build Reports

  • Ask for the report types you need. Some recipes need a report type that FieldKo doesn’t include, such as one with Visits as the only object, or one for Attendance or Pack Outs. Each recipe says what to ask your admin for. Admins can follow Report Folders, Sharing, and Custom Report Types.
  • Plan survey questions for reporting. Survey answers are stored as text, so you can’t add up or average them in a report. Scored questions, which store points in number fields, are reportable. See Design Surveys and Tasks for Reporting.
  • Data appears after reps sync. Work done offline shows up in reports when the rep syncs. See Understand Offline Work and Sync.

See Also

Last modified on October 20, 2026