Driving Intelligent Field Activity

We deliver software and services purpose-built for consumer goods companies.

Driving Intelligent Field

ActivityUsing POS / Syndicated data in AFS Retail Execution & DSD

CONFIDENTIAL – PROPRIETARY - AFS TECHNOLOGIES

Retail Sales Data 101 – the big picture

• A lot of things can happen from the shipment of a product to the actual consumer purchase

• New Retail Execution focuses on the consumer:

• What price they paid?

• When did they bought?

• What influenced the sale?

• However, shopper focused data is scarce and has limited reach –instead, most audits focus on aggregations at the store level

Retail Link


How can this data affect my business?

• Quick identification of exceptions and disruptions on the supply chain

• Inaccurate inventories – virtual stocks

• Alterations on the average demand

• Out of Stocks

• Trend analysis to know what to do next

• Prepare for seasonal activities

• Push products in certain stores

• Along with other data sources, provide a view of the final consumer shopping habits and experience

But… am I making the most of my Retail Sales Data???


POS Data-driven actions at a store• Regardless of the source, AFS has managed to isolate common data

patterns on the Retail Sales Data.

• Placeholders for this data are available in the customer / customer product profile and can be refreshed as often as the data becomes available.

• Key idea is to use the data as enabler for actions in the store – from simple descriptive facts to insights and actions automatically generated.

• How it has been achieved?

• Generation of customer fact sheets that can be queried at any time withthe most up to date information

• Our “Perfect Store” Module enhanced to create KPIs based on the data

• Our Mobile application automatically generates action suggestionsbased on KPI exceptions

Load external

data into AFS RE

Define

conditions for data

Analyze data

based on

conditions

Generate action

suggestions


How to Achieve this on AFS RE/DSD?


Configuring the data - GenInfos• General Info module (i.e. GenInfo) is used when existing information of

particular object (e.g. customer, contact person, product, activity, etc.) cannot be stored within standard fields. For example: customer account group, number of counters in shop, date of first opening of the shop, loyalty level, family status of contact person, etc.. Based on the setup of particular GenInfo, it is possible to view or edit it on Frontend.

Object / Module Example of General information

Activity Reasons for not ordering goods, degustation, leaflet promotion, etc.

Contact Name of the contact person's wife, birthday, etc.

Customer Opening hours, floor space, number of cash registers, etc.

Product Color modifications, expiration, packaging material etc.


GenInfo – Product At Customer

• There is a special type of GenInfo that stores Product at Customer data

• The set of fields available works in multiple ways, e.g.:

• Storing target facings per product

• Setting minimum inventory levels

• Establishing targets of execution at the product level

• … and of course, storing the POS/Syndicated data

• GenInfos can be easily created and configured through the administration console of our system.


Data in ActionPerfect Store, Automatic Targets and much more


Perfect store & Custom KPIs

• Custom KPIs based on the external data defined directly from console

• Possibility to import custom KPI by loading of customization file

Manual KPI definition XML file based definition


Perfect store & Custom KPI

• Define all basic parameters of KPI directly via Console UI

• Macros are supported for label to support dynamic description of KPI on frontend


Perfect store & Custom KPI

• KPI calculated based on user defined condition. In calculation, values defined in Product at customer general info (or Customer general info) are compared against another geninfo or static value

• General info of type Numeric and Logical are supported for now

Condition definition


Exception• For items that do not pass the

condition, the exception is raised.

• Application support two types of exception actions:

• NEW Automatic suggestion –suggestions for actions are automatically generated on frontend on the activity start

• Task proposals –prescriptions of the tasks that can user manually created from perfect store module (existing functionality of perfect store)

Automatic suggestion

definitionTask proposal definition


Definition of exception

• Prescription of the suggestion that is generated on the frontend in case that any exception raised from the defined KPI


Action suggestions on frontend

• Suggestions generated from the KPI are displayed as last group in the list of steps


Action suggestion detail

• Suggestions are one time tasks that are automatically generated by frontend

• Suggestions are not visible in list of tasks

• User can change the status of the suggestion in the same way as on task


List of suggestions on console

• Status of the suggestions can be checked on the console in the Tasks module

• By default are not visible in list of tasks

• Suggestions can be displayed from More menu in task module


Thank you for joining us on this presentation!For more information, visit us at:

https://re.afsi.com

Or contact us:

Andres Jejen

VP of Product Management

AFS RE/DSD

[email protected] Questions?

Documents

Driving Intelligent Field Activity