Method and system for gathering and analyzing consumer purchasing information based on product and consumer clustering relationships5974396Abstract A method and system for gathering and analyzing customer and purchasing information permits a retailer or retail chain to process transactional information involving large numbers of consumers and consumer products. Product information is gathered that uniquely identifies a specific product by type and manufacturer and grouped into generic product clusters. Consumers are similarly grouped into consumer clusters based on common consumer demographics and other characteristics. Consumer retail transactions are analyzed in terms of product and/or consumer clusters to determine relationships between the consumers and the products. Product, consumer, and transactional data are maintained in a relational database. Targeting of specific consumers with marketing and other promotional literature is based on consumer buying habits, needs, demographics, etc. A retailer queries the database using selected criteria, accumulates data from the database in response to that query, and makes prudent business and marketing decisions based on that response. Queried information from the database may be communicated to a printing subsystem for printing promotional literature directed to particular customers based on cluster information stored in the database. Claims What is claimed is: Description BACKGROUND AND SUMMARY OF THE INVENTION
______________________________________
UPC CLUSTER PRODUCT
UPC PRODUCTS ASSOCIATION CLUSTERS
______________________________________
10086302145 Heintz
Ketchup 8 oz. 10086302145 01
01 General
' ' '
' ' '
______________________________________
Consumer clusters are defined as follows. Consumer group criteria are established when a query or report is to be executed. Consequently, consumer clusters are not hard coded and can be established and modified as needed. For example, a report can be run specifying the following criteria which define the consumer cluster. income: $0-25,000 household size: 1-3 people Head of household between 20-35 yrs. old The households that meet this criteria will be selected at execution time based on the demographic information contained in the database. Database queries can be run in the same manner, specifying the criteria that defines a particular consumer cluster. Exemplary software programs and data structures required for each of the subsystems of the present invention will now be described in terms of various process data flow diagrams and data models. An overall process data flow diagram for the frequent shopper system according to the present invention is illustrated in FIG. 7. Those of ordinary skill in the art will appreciate that based on the data process flows and data models provided below, queries, data structures, programs, etc. for implementing the present invention may be readily generated. Any suitable language and specific coding for implementing the process flows and data models may be used. With respect to FIG. 7, data flow relationships are indicated and labelled by arrows between the various subsystems of the present invention and entities. These relationships define what and how information will be stored in the database. The symbols and flow connections used in FIG. 7 are described in the table set forth below.
______________________________________
Identifier Type Definition
______________________________________
POINT OF Data Process
Point of sale system
SALES SYSTEM functioning within the
actual retail outlet
environment. Includes
scanners, registers, and
in-store concentrators.
RETAIL SHOPPER
External Entity
The consumer of the
retailer. Each consumer
is also associated into a
household which is tracked
as a single entity.
CONSUMER Data Process
Subsystem providing a
APPLICATION means for capturing
information about a store
consumer. Consumer
characteristic and
demographic information
entered on an application
form and subsequently
entered into a data file.
PRINT External Entity
Site of actual print
FACILITIES production and
manufacturing that is
computer interfaced with a
data-system generated by
the database in response
to a query.
MARKETING External Entity
Functional group
FUNCTION responsible for the
definition of direct
marketing programs and
products and for the
direct support of
retailers.
DIRECT MAILING
External Entity
Facility that receives
printed promotional and
advertising materials and
distributes those
materials to targeted
consumers.
FSDB Data Store Main repository for
consumer characteristics
and transactional purchase
history.
CONSUMER Data Process
Main repository of
PURCHASE consumer information and
REPOSITORY purchase history.
Contains product cluster
definition, organizational
structure, and other
definitional information.
PRINT SYSTEMS
Data Process
Set of functions driving
ANALYSIS the format and setup of
the final printed
product. Analyzes
consumer data against
defined print product
formats to determine
resultant printing
instructions.
PRINT Data Store Respository of information
INTELLIGENCE describing and defining
DATABASE the relationship between
consumer behavior and the
format of the printed
product.
USER INTERFACE
Data Process
Set of reports, queries,
and extracts providing
value-added analysis and
formatting of information
contained in the consumer
purchase repository. May
function on a both
scheduled and as needed
basis.
REPOSITORY Data Process
Facility for the
ADMINISTRATION administration of the
consumer purchase
respository. Provides
access to the
organizational and
structural information in
the repository such as
product clusters.
RETAILER External Entity
Retailer business entity.
FLOW CONNECTIONS:
PURCHASE Data Flow The actual transaction
between a retail grocer and
one of their consumers.
DEMOGRAPHIC Data Flow Information provided by the
INFORMATION retail grocer's consumer on
the sign-up application.
Includes demographic and
psychographic data such as
age, number of people in
family, income, specific
consumer products used in
household, etc.
TRANSACTION Data Flow A set of transactions
SESSION representing the total
"check-out" interaction
between the retail grocer and
one of their consumers at one
time. Includes purchases,
voids, and all other activity
conducted at the POS
workstation.
REPOSITORY Data Flow Updates made by database
CHANGES information administrator to
the database via the retailer
interface.
CONSUMER PROFILE
Data Flow The interface to the database
containing the consumer
demographic and psycho-
graphic information
aggregated by the consumer
application subsystem.
CONSUMER Data Flow Summarization of consumer
BEHAVIOR household buying behavior.
SUMMARY
PRINT SYSTEM Data Flow A set of parameters defining
INSTRUCTIONS the actions and decisions to
be taken by the Print Systems
Analysis Subsystem.
CONSUMER Data Flow Summarization of consumer
PURCHASE EXTRACT household buying behavior
based on predefined sets of
extract criteria such as
consumer cluster definitions.
CONSUMER Data Flow A set of value added,
MARKETING summarized reports and/or
INFORMATION graphs depicting consumer
buying behavior for a
specified set of criteria.
PRINTER Data Flow Detailed instructions
INTELLIGENCE defining the format of a
mailing piece for a specific
consumer.
ENVIRONMENTAL
Data Flow Specific changes and new
CHANGES information to be applied to
the database via User
Interface.
CONSUMER Data Flow The actual components of
CHARACTERISTICS consumer demographic and
psychographic information
added to the database.
ENVIRONMENT Data Flow Set of instructions and
PARAMETERS parameters defining the
printing environment relating
format to print content for
consumer clusters.
CONSUMER Data Flow Set of standard reports
BEHAVIOR REPORTS showing consumer buying
behavior across time
intervals, store sites,
product clusters,
departments, and within
consumer clusters.
______________________________________
FIG. 8 is a data model showing the manner in which data in the frequent shopper database are associated and interrelated. Each of the codes used in FIG. 8 are defined in the following table:
__________________________________________________________________________
Identifier Definition Description
__________________________________________________________________________
APPL.sub.-- CODES
APPLICATION Coded list of potential
CODES appliances a consumer
household may own.
DIET.sub.-- CODES
DIETARY CODES
A coded list of
potential dietary
requirements for a
consumer household.
PROD.sub.-- VENDOR
PRODUCT VENDOR
The supplier of a
product; not necessarily
the manufacturer.
Includes name and
address.
PROMO.sub.-- CODES
PROMOTION CODES
A coded user
classification of
promotions with
description.
HH.sub.-- APPL
HOUSEHOLD A list of codes
APPLIANCES indicating the
appliances a consumer
household claims to own.
HH.sub.-- DIET
HOUSEHOLD A list of codes
DIETARY indicating the dietary
REQUIREMENTS
preferences of the
consumer household.
PROD.sub.-- MFR
PRODUCT Name and address of a
MANUFACTURER
product's manufacturer.
PROD.sub.-- PROMO
PRODUCT A definition of a
PROMOTION product promotion,
including the start and
end dates of the
promotion ("flight
time"). Also
establishes a tracking
period to allow for
before, during and after
sales figures.
HH.sub.-- PURCH-TOTALS
HOUSEHOLD A cumulative total of a
PURCHASE TOTALS
consumer household's
purchases.
HH.sub.-- PROMO.sub.-- PURCH
HOUSEHOLD The cumulative amount of
PROMOTION a consumer household's
PURCHASES purchase on a specific
promotion item.
HH.sub.-- DEMO
HOUSEHOLD Names, addresses, ages,
DEMOGRAPHICS
and other demographic
features that help
uniquely identify the
consumer household.
INCOME.sub.-- CODES
INCOME CODES
A codes list of consumer
household income ranges.
HH.sub.-- CLUSTER.sub.-- PURCH
HOUSEHOLD A cumulative total of a
CLUSTER specific product cluster
PURCHASES associated with the
consumer household.
UPC.sub.-- PRODUCT
UPC PRODUCT A descriptive definition
of a specific product.
STORE.sub.-- INFO
STORE Information about a
INFORMATION specific store in the
retail chain.
CARD.sub.-- MEMBER
CARD MEMBER Descriptive
characteristics of an
individual card member
within a consumer
household.
HH.sub.-- PURCH.sub.-- HISTORY
HOUSEHOLD A trail of data and
PURCHASE total amount of a
HISTORY consumer household's
purchases.
CONS.sub.-- GROUP
CONSUMER GROUP
A specific consumer
cluster defined by a set
of demographic and/or
buyer behavior criteria.
PROD.sub.-- CLUSTER
PRODUCT CLUSTER
A list of predefined
product clusters and
their descriptions.
UPC.sub.-- CLUSTER
UPC CLUSTER A member of a product
cluster connecting a
product to a product
cluster.
CARD.sub.-- CODES
CARD CODES Coded categories of the
type of cards issued to
consumers such as
"check-cashing", etc.
DISTRICT.sub.-- INFO
DISTRICT A definition of an
INFORMATION operational district
within a retail chain.
__________________________________________________________________________
Each particular object indentifier is structured as a table with a number of component names being included in each table. A list of potential components in each object indentifier table is included below.
______________________________________
Object Identifier Component Names
______________________________________
APPL.sub.-- CODES = APPL.sub.-- CODE
+APPL.sub.-- DESC
CARD.sub.-- CODES = CARD.sub.-- CODE
+CARD.sub.-- DESC
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
CARD.sub.-- MEMBER
= CARD.sub.-- NUM
+CARD.sub.-- SEQ.sub.-- NUM
+APPLIC.sub.-- DATE
+ISSUE.sub.-- DATE
+LAST.sub.-- NAME
+FIRST.sub.-- NAME
+MID.sub.-- INITIAL
+BIRTH.sub.-- DATE
+SOC.sub.-- SEC.sub.-- NUM
+DRV.sub.-- LIC.sub.-- NUM
+DRV.sub.-- LIC.sub.-- STATE
+EMPL.sub.-- NAME
+EMPL.sub.-- ADDR1
+EMPL.sub.-- ADDR2
+EMPL.sub.-- CITY
+EMPL.sub.-- STATE
+EMPL.sub.-- ZIP
+EMPL.sub.-- PHONE
+BANK.sub.-- NAME
+CHK.sub.-- ACCT.sub.-- NUM
+CARD.sub.-- CODE
+STORE.sub.-- ID
+DISTRICT.sub.-- ID
CONS.sub.-- GROUP = GROUP.sub.-- ID
+BEG.sub.-- AGE.sub.-- DATE
+END.sub.-- AGE.sub.-- DATE
+BEG.sub.-- AGE.sub.-- NUM
+END.sub.-- AGE.sub.-- NUM
+BEG.sub.-- HH.sub.-- NUM
+END.sub.-- HH.sub.-- NUM
+INCOME.sub.-- CODE
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
DIET.sub.-- CODES = DIET.sub.-- CODE
+DIET.sub.-- DESC
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
DISTRICT.sub.-- INFO
= DISTRICT.sub.-- ID
+DISTRICT.sub.-- DESC
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
HH.sub.-- APPL = CARD.sub.-- NUM
+APPL.sub.-- CODE
HH.sub.-- CLUSTER.sub.-- PURCH
= CARD.sub.-- NUM
+CLUSTER.sub.-- ID
+TOT.sub.-- CLUS.sub.-- QTY
+TOT.sub.-- DIS.sub.-- AMT
+TOT.sub.-- PURCH.sub.-- AMT
+PURCH.sub.-- DATE1
+PURCH.sub.-- DATE2
+PURCH.sub.-- DATE3
+PURCH.sub.-- DATE4
+PURCH.sub.-- DATE5
+STORE.sub.-- ID
+DISTRICT.sub.-- ID
HH.sub.-- DEMO = CARD.sub.-- NUM
+LAST.sub.-- NAME
+HH.sub.-- ADDR1
+HH.sub.-- ADDR2
+HH.sub.-- CITY
+HH.sub.-- STATE
+HH.sub.-- ZIP
+HH.sub.-- PHONE
+MAIL.sub.-- IND
+HH.sub.-- NUM
+CHILD.sub.-- NUM
+CHILD1.sub.-- BDATE
+CHILD2.sub.-- BDATE
+CHILD3.sub.-- BDATE
+CHILD4.sub.-- BDATE
+CHILD5.sub.-- BDATE
+INCOME.sub.-- CODE
+BIRTH.sub.-- DATE
+STORE.sub.-- ID
+DISTRICT.sub.-- ID
HH.sub.-- DIET = CARD.sub.-- NUM
+DIET.sub.-- CODE
HH.sub.-- PROMO.sub.-- PURCH
= CARD.sub.-- NUM
+PROMO.sub.-- ID
+TOT.sub.-- PROMO.sub.-- QTY
+TOT.sub.-- DIS.sub.-- AMT
+TOT.sub.-- PURCH.sub.-- AMT
+PERIOD.sub.-- START.sub.-- DATE
+PERIOD.sub.-- END.sub.-- DATE
HH.sub.-- PURCH.sub.-- HISTORY
= CARD.sub.-- NUM
+PURCH.sub.-- DATE
+PURCH.sub.-- AMT
+STORE.sub.-- ID
+DISTRICT.sub.-- ID
HH.sub.-- PURCH.sub.-- TOTALS
= CARD.sub.-- NUM
+TOT.sub.-- DIS.sub.-- AMT
+TOT.sub.-- TAX.sub.-- AMT
+TOT.sub.-- PURCH.sub.-- AMT
+TOT.sub.-- VISIT.sub.-- NUM
INCOME CODES = INCOME.sub.-- CODE
+INC.sub.-- BEG.sub.-- AMT
+INC.sub.-- END.sub.-- AMT
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
PROD.sub.-- CLUSTER
= CLUSTER.sub.-- ID
+CLUSTER.sub.-- DESC
+CLUSTER.sub.-- TYPE
+STORE.sub.-- ID
+DISTRICT.sub.-- ID
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
PROD.sub.-- MFR = MFR.sub.-- CODE
+VENDOR.sub.-- ID
+MFR.sub.-- NAME
+MFR.sub.-- ADD1
+MFR.sub.-- ADD2
+MFR.sub.-- CITY
+MFR.sub.-- STATE
+MFR.sub.-- ZIP
+MFR.sub.-- PHONE
PROD.sub.-- PROMO = UPC.sub.-- CODE
+PROMO.sub.-- ID
+PROMO.sub.-- CODE
+PROMO.sub.-- AMT
+START.sub.-- DATE
+END.sub.-- DATE
+TRACK.sub.-- START.sub.-- DATE
+TRACK.sub.-- END.sub.-- DATE
+TOT.sub.-- SOLD.sub.-- NUM
+STORE.sub.-- ID
+DISTRICT.sub.-- ID
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
PROD.sub.-- VENDER
= VENDOR.sub.-- ID
+VEND.sub.-- NAME
+VEND.sub.-- ADDR1
+VEND.sub.-- ADDR2
+VEND.sub.-- CITY
+VEND.sub.-- STATE
+VEND.sub.-- ZIP
+VEND.sub.-- PHONE
PROMO.sub.-- CODES
= PROMO.sub.-- CODES
+PROMO.sub.-- DESC
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
STORE.sub.-- INFO = STORE.sub.-- ID
+DISTRICT.sub.-- ID
+STORE.sub.-- NAME
+STORE.sub.-- ADDR1
+STORE.sub.-- ADDR2
+STORE.sub.-- CITY
+STORE.sub.-- STATE
+STORE.sub.-- ZIP
+STORE.sub.-- PHONE
+STORE.sub.-- MGR
+CREATE.sub.-- DATE
+CREATE.sub.-- USER
UPC.sub.-- CLUSTER
= UPC.sub.-- CODE
+DISTRICT.sub.-- ID
+STORE.sub.-- ID
+CLUSTER.sub.-- ID
UPC.sub.-- PRODUCT
= UPC.sub.-- CODE
+MFR.sub.-- CODE
+PROD.sub.-- CODE
+PROD.sub.-- NAME
+PROD.sub.-- DESC
+PROD.sub.-- AMT
______________________________________
The element structure definitions indicating the field length and type of each object identifer are provided in the table below.
______________________________________
Object
Identifier Field Length Type
______________________________________
APPLIC.sub.-- DATE
7 DATE
APPL.sub.-- CODE
2 CHAR
APPL.sub.-- DESC
30 CHAR
BANK.sub.-- NAME
30 CHAR
BEG.sub.-- AGE.sub.-- DATE
7 DATE
BEG.sub.-- AGE.sub.-- NUM NUMBER
BEG.sub.-- HH.sub.-- NUM NUMBER
BIRTH .sub.-- DATE
7 DATE
CARD.sub.-- CODE
2 CHAR
CARD.sub.-- DESC
30 CHAR
CARD.sub.-- NUM 16 CHAR
CARD.sub.-- SEQ.sub.-- NUM
1 CHAR
CHILD1.sub.-- BDATE
7 DATE
CHILD2.sub.-- BDATE
7 DATE
CHILD3.sub.-- BDATE
7 DATE
CHILD4.sub.-- BDATE
7 DATE
CHILD5.sub.-- BDATE
7 DATE
CHILD.sub.-- NUM NUMBER
CHK.sub.-- ACCT.sub.-- NUM
15 CHAR
CLUSTER.sub.-- DESC
30 CHAR
CLUSTER.sub.-- ID
10 CHAR
CLUSTER.sub.-- TYPE
2 CHAR
CREATE.sub.-- DATE
7 DATE
CREATE.sub.-- USER
10 CHAR
DIET.sub.-- CODE
2 CHAR
DIET.sub.-- DESC
30 CHAR
DISTRICT.sub.-- DESC
30 CHAR
DISTRICT.sub.-- ID
10 CHAR
DRV.sub.-- LIC.sub.-- NUM
20 CHAR
DRV.sub.-- LIC.sub.-- STATE
2 CHAR
EMPL.sub.-- ADDR1
30 CHAR
EMPL.sub.-- ADDR2
30 CHAR
EMPL.sub.-- CITY
20 CHAR
EMPL.sub.-- NAME
30 CHAR
EMPL.sub.-- PHONE
16 CHAR
EMPL.sub.-- STATE
2 CHAR
EMPL.sub.-- ZIP 10 CHAR
END.sub.-- AGE.sub.-- DATE
7 DATE
END.sub.-- AGE.sub.-- NUM NUMBER
END.sub.-- DATE 7 DATE
END.sub.-- HH.sub.-- NUM NUMBER
FIRST.sub.-- NAME
15 CHAR
GROUP.sub.-- ID 10 CHAR
HH.sub.-- ADDR1 30 CHAR
HH.sub.-- ADDR2 30 CHAR
HH.sub.-- CITY 20 CHAR
HH.sub.-- NUM NUMBER
HH.sub.-- PHONE 16 CHAR
HH.sub.-- STATE 2 CHAR
HH.sub.-- ZIP 10 CHAR
INCOME.sub.-- CODE
2 CHAR
INC.sub.-- BEG.sub.-- AMT NUMBER
INC.sub.-- END.sub.-- AMT NUMBER
ISSUE.sub.-- DATE
7 DATE
LAST.sub.-- NAME
20 CHAR
MAIL.sub.-- IND 1 CHAR
MFR.sub.-- ADDR1
30 CHAR
MFR.sub.-- ADDR2
30 CHAR
MFR.sub.-- CITY 20 CHAR
MFR.sub.-- CODE 6 CHAR
MFR.sub.-- NAME 30 CHAR
MFR.sub.-- PHONE
16 CHAR
MFR.sub.-- STATE
2 CHAR
MFR.sub.-- ZIP 10 CHAR
MID.sub.-- INITIAL
1 CHAR
PERIOD.sub.-- END.sub.-- DATE
7 DATE
PERIOD.sub.-- START.sub.-- DATE
7 DATE
PROD.sub.-- AMT 5 NUMBER
PROD.sub.-- CODE
6 CHAR
PROD.sub.-- DESC
30 CHAR
PROD.sub.-- NAME
20 CHAR
PROMO.sub.-- AMT
5 NUMBER
PROMO.sub.-- CODE
2 CHAR
PROMO.sub.-- DESC
30 CHAR
PROMO.sub.-- ID 10 CHAR
PURCH.sub.-- AMT
7 NUMBER
PURCH.sub.-- DATE
7 DATE
PURCH.sub.-- DATE1
7 DATE
PURCH.sub.-- DATE2
7 DATE
PURCH.sub.-- DATE3
7 DATE
PURCH.sub.-- DATE4
7 DATE
PURCH.sub.-- DATE5
7 DATE
SOC.sub.-- SEC.sub.-- NUM
9 CHAR
START.sub.-- DATE
7 DATE
STORE.sub.-- ADDR1
30 CHAR
STORE.sub.-- ADDR2
30 CHAR
STORE.sub.-- CITY
20 CHAR
STORE.sub.-- ID 10 CHAR
STORE.sub.-- MGR
30 CHAR
STORE.sub.-- NAME
30 CHAR
STORE.sub.-- PHONE
16 CHAR
STORE.sub.-- STATE
2 CHAR
STORE.sub.-- ZIP
10 CHAR
TOT.sub.-- CLUS.sub.-- QTY NUMBER
TOT.sub.-- DIS.sub.-- AMT
9 NUMBER
TOT.sub.-- PROMO.sub.-- QTY NUMBER
TOT.sub.-- PURCH.sub.-- AMT
9 NUMBER
TOT.sub.-- SOLD.sub.-- NUM NUMBER
TOT.sub.-- TAX.sub.-- AMT
9 NUMBER
TOT.sub.-- VISIT.sub.-- NUM NUMBER
TRACK.sub.-- END.sub.-- DATE
7 DATE
TRACK.sub.-- START.sub.-- DATE
7 DATE
UPC.sub.-- CODE 12 CHAR
VENDOR.sub.-- ID
10 CHAR
VEND.sub.-- ADDR1
30 CHAR
VEND.sub.-- ADDR2
30 CHAR
VEND.sub.-- CITY
20 CHAR
VEND.sub.-- NAME
30 CHAR
VEND.sub.-- PHONE
16 CHAR
VEND.sub.-- STATE
2 CHAR
VEND.sub.-- ZIP 10 CHAR
______________________________________
The retail point of sale system 20 software is symbolically illustrated in the data process flow diagram FIG. 9. Each symbol identifier is defined in the table below.
______________________________________
Identifier Type Definition
______________________________________
FIG. 9 Split/Merge
Breakdown of purchase
transaction into purchase item
components to generate
transaction records.
TRANS LOG Data Store
Collection of all Transaction
Sessions for a given store.
CAPTURE Data Process
Receive the scanned data from
CONSUMER the consumer's membership card
IDENTIFIER and format for the session log.
LOG ITEM Data Process
Receive scanned data for
PURCHASE product purchase and format for
the session log.
LOG ITEM Data Process
Receive nonitem purchase
ADJUSTMENTS scanner data, e.g. coupons, and
format for the session log.
AGGREGATE Data Process
Gather and concentrate all
SESSION session logs accumulated for a
LOGS time period, e.g. a 24 day.
Format to a single data file.
CONCEN- Data Process
Gather all session logs into one
TRATE transaction log data file.
TRANS-
ACTION LOGS
SESSION LOG Data Store
FLOW CONNECTIONS:
PURCHASE Data Flow The actual transaction between
a Retail Grocer and one of
their consumers.
TRANSACTION Data Flow A set of transactions
SESSION representing the total
"check-out" interaction
between the Retail Grocer and
one of their consumers at one
time. Includes purchases,
voids, and all other activity
conducted at the POS
workstation.
CONSUMER CARD
Data Flow Information scanned from
DATA consumer membership card.
Usually just the card member
number.
CONSUMER ID Data Flow The card member number (MIN)
originating from the consumer
membership card.
ITEM PURCHASE
Data Flow Information related to a
purchased item such as an item
number, selling price, and
quantity.
ITEM LOG Data Flow A consumer's item purchase
represented in the session log.
ITEM ADJUSTMENTS
Data Flow Consumer transactions other
than an item purchase, such as
voids, coupons, etc.
ADJUSTMENT LOG
Data Flow A nonitem purchase transaction
represented in the session log.
SESSION ITEMS
Data Flow Each unit of a session log
representing product purchase
and other transactions.
SESSION GROUP
Data Flow All sessions within a logical
grouping such as for a given
store over a day or week.
Generally sorted by POS
terminal and time.
TRANS LOG GROUP
Data Flow Group of Session Groups
usually for a given store over
a day or week. Exists as a
data file.
______________________________________
The consumer application system software is outlined in the data flow diagram of FIG. 10. The definition of each symbol identifier and each flow connection is provided in the table set forth below.
______________________________________
Identifier Type Definition
______________________________________
RECORD CARD Data Process
Enter consumer identifying,
MEMBER demographic, and
INFORMATION psychographic data from the
sign-up application
subsystem into database.
CONSUMER Data Store Data entry repository for
APPLICATIONS new consumer applicant's
data.
COMPLETE Data Process
The consumer, along with
CARD store assistant completes
APPLICATION the sign-up application and
assigns unique MIN.
CARD External Entity
The facility that produces
MANUFACTURER the physical card and mailer
to provide the consumer with
the membership package.
PRODUCE CARD
Data Process
Extract the information
required to produce and
deliver consumer a
membership card.
EXTRACT Data Process
Extract all identifying
CONSUMER demographic, and
INFORMATION psychographic information
and format into an interface
file for communication/
delivery to the Frequent
Shopper Database. Can
optionally provide complete
database for new consumers.
DISTRIBUTE Data Process
Receive the completed new
CARD consumer membership set
(including card) and send to
consumer.
CONSUMER External Entity
The Retailer's consumer.
FLOW CONNECTIONS:
CARD DETAILS
Data Flow Data items required to
produce the consumer
membership package
including the card.
APPLICATION Data Flow All data items included on
DATA the consumer sign-up
application form.
CONSUMER Data Flow The interface to the
PROFILE database containing the
consumer demographic and
psychographic information
aggregated in the Consumer
Applications subsystem.
CONSUMER Data Flow Consumer sign-up information
INFORMATION data as required by the
entry process to the
consumer applications
subsystem.
DEMOGRAPHIC Data Flow Information provided by the
INFORMATION Retailer's consumer on the
sign-up application.
Includes demographic and
psychographic data.
______________________________________
FIG. 11 shows a process data flow for transactions with the consumer product purchase repository. Definitions for the symbol and flow connection identifiers are provided in the table below.
______________________________________
Identifier Type Definition
______________________________________
RETAILER External Entity
Retailer business entity.
VALIDATE Data Process
Receive transaction
TRANSACTION session log from POS
system and validate the
session.
PENDING TRANS Data Store Transaction log session
LOG that is invalid. Held
for correction, then
released for posting.
CORRECT ERRORS
Data Process
Make necessary
corrections to rejected
transaction log session.
Usually a problem with
consumer card number.
POST CONSUMER Data Process
Scan valid transaction
PURCHASES log session, determine
product cluster purchases
and post to database.
ADD NEW Data Process
Accept new application
CONSUMER consumer information from
consumer application
subsystem and add to
database.
FREQUENT Data Store Main repository for
SHOPPER DATA consumer characteristics
BASE and product purchase
history. Relational
database serving as
repository for consumer
and product information.
EXTRACT Data Process
Extracts information
CONSUMER required by the print
CLUSTER SUMMARY analysis subsystem.
FLOW CONNECTIONS:
INVALID TRANS Data Flow
LOG SESSION
VALID TRANS LOG
Data Flow
SESSION
TRANSACTION Data Flow
SESSION
VALID CARD Data Flow
NUMBER
CONSUMER PROFILE
Data Flow
CONSUMER Data Flow
BEHAVIOR SUMMARY
PROD CLUSTER Data Flow
PURCHASE
PENDING TRANS Data Flow
LOG SESSION
CORRECTED TRANS
Data Flow
LOG SESSION
VALID UPC Data Flow
TRANS LOG ERRORS
Data Flow
NEW CONSUMER Data Flow
CONSUMER Data Flow
CLUSTER SUMMARY
______________________________________
FIGS. 12(a)-12(i) are self-explanatory illustrating various kinds of repository administration reports, activities, and functions that may be performed using the present invention. A process flow diagram for user interface between a retailer and the frequent shopper database is illustrated in FIG. 13. Definitions of the symbols and flow connections are provided in the table set forth below.
______________________________________
Definition Identifier Type
______________________________________
RETAILER External Entity
Retailer
business
entity.
EVALUATE QUERY Data Process
Parse,
analyze, and
format query
request from
user.
FORMAT QUERY Data Process
Receives
resultant data
from query and
presents to
user.
EXECUTE Data Process
Takes query
QUERY criteria and
accesses
database for
required
information.
FREQUENT Data Store Main
SHOPPER repository for
DATABASE consumer
characteris-
tics and
product
purchase
history.
______________________________________
Identifier Type
______________________________________
FLOW CONNECTIONS:
CONSUMER Data Flow
MARKETING
INFORMATION --
QUERY
QUERY Data Flow
SELECTION
CRITERIA
QUERY REPORT Data Flow
RESOLVED QUERY Data Flow
CRITERIA
RESULTANT QUERY Data Flow
______________________________________
While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. Moreover, while various examples have been described in the retail grocery context, the present invention may be employed in any retail, wholesale, or consumer service or sales environment.
|
Same subclass Same class Consider this |
||||||||||
