Patent Grant
8732013
The present invention relates generally to purchaser incentive and awards redemption programs, and more specifically, to the capture of retailer item identifiers from filtered merchants, and the matching of such retailer item identifiers with corresponding manufacturer item identifiers to facilitate, for example, data analysis and the provision of incentives and awards to consumers.
Incentive award programs have been developed in a variety of industries to promote customer loyalty. Generally, such programs reward customers for repeat business with the same merchant or service provider by accumulating reward points which can then be redeemed in a plurality of ways, including exchanging the reward points for additional goods and services that may be selected from an approved list or a redemption catalog for example. The reward points are usually calculated using a predetermined formula or ratio that relates a customer's purchase volume (i.e., in terms of money value or some other volume parameter) to a certain number of reward points. For example, reward points may be issued on a one-for-one basis with each dollar that a customer spends on particular goods and services.
One well-known example of a customer incentive program is a “frequent flyer” program which rewards airlines passengers with “mileage points” based upon the distances that the passengers fly with a particular airline. The mileage points may then be redeemed for free airfare or free car rentals. Other incentive award programs are designed to induce usage of particular financial instruments, such as credit cards or debit cards, by accumulating reward points or dollar value points based upon the volume of purchases made using the particular financial instrument. These types of programs maybe designed such that customers of the financial institution accumulate reward points which can be redeemed for selected goods or services or, alternatively, such that customers accumulate points which have a dollar value which can be applied toward a credit or debit balance, depending on whether the instrument is a credit or debit instrument, for example.
These and other similar incentive award programs are described in U.S. Pat. Nos. 5,774,870 and 6,009,412 issued to Thomas W. Storey and assigned to Netcentives, Inc., both of which are hereby incorporated by reference to the extent that they describe an automated rewards system. U.S. Pat. Nos. 5,689,100 and 5,956,695 issued to Carrithers et al. and assigned to Maritz, Inc., both of which are also incorporated by reference, further disclose incentive award programs wherein purchase data is filtered at the merchant level. For more information on loyalty systems, transaction systems, electronic commerce systems, and digital wallet systems, see, for example, the Shop AMEX™ system as disclosed in Ser. No. 60/230,190 filed Sep. 5, 2000; the MR as Currency™ and Loyalty Rewards Systems as disclosed in Ser. No. 60/197,296 filed on Apr. 14, 2000, Ser. No. 60/200,492 filed Apr. 28, 2000, and Ser. No. 60/201,114 filed May 2, 2000; a digital wallet system as disclosed in U.S. Ser. No. 09/652,899 filed Aug. 31, 2000; a stored value card as disclosed in Ser. No. 09/241,188 filed on Feb. 1, 1999; a system for facilitating transactions using secondary transaction numbers as disclosed in Ser. No. 09/800,461 filed on Mar. 7, 2001; and also in related provisional application Ser. No. 60/187,620 filed Mar. 7, 2000, Ser. No. 60/200,625 filed Apr. 28, 2000, and Ser. No. 60/213,323 filed May 22, 2000, all of which are herein incorporated by reference. Other examples of online membership reward systems are disclosed in U.S. Pat. No. 5,774,870, issued on Jun. 30, 1998, and U.S. Pat. No. 6,009,412, issued on Dec. 29, 1999, both of which are hereby incorporated by reference. A further example of a loyalty and reward program may be found at the AIR MILES® Web site (www.airmiles.ca), which describes a loyalty program offered by The Loyalty Group, a privately held division of Alliance Data Systems of Dallas, Tex., and which is hereby incorporated by reference. Additional information relating to smart card and smart card reader payment technology is disclosed in Ser. No. 60/232,040, filed on Sep. 12, 2000, and U.S. Pat. Nos. 5,742,845; 5,898,838 and 5,905,908, owned by Datascape; all of which are hereby incorporated by reference. Information on point-of-sale systems and the exploitation of point-of-sale data is disclosed in U.S. Pat. No. 5,832,457, issued on Nov. 3, 1998 to O'Brien et al., which is hereby incorporated by reference.
Portions of each of the above-described programs may be used to induce customer loyalty to particular merchants or service providers who directly provide goods or services to the consumer. In other words, these prior art frequency awards programs provide a means for retail businesses, financial institutions, and others in direct contact with the customers they service to provide incentives to their customers to encourage repeat and/or volume business. However, these programs do not sufficiently address the similar needs of businesses that are further up in the distribution chain (such as manufacturers) to promote volume purchases by customers based upon, for example, brand loyalty independent of the retail source for the purchase. Additionally, the prior art programs do not provide a means for monitoring, tracking, and/or analyzing consumer and product data across distribution channels for a particular manufacturer and/or the variety of goods which that manufacturer places into the stream of commerce for ultimate sale to consumers by a retailer.
Generally, before a product arrives at a retail establishment for sale to a consumer, the product travels through a distribution chain which originates with the manufacturer. The manufacturer typically sells its products to a wholesaler who in turn sells those products to various retailers. Most modern retailers implement some form of computerization or electronic technology in their day-to-day operations. This technology typically consists of using point-of-sale (POS) systems for automating checkout procedures, assisting sales personnel, and the like. POS systems generally include one or more automated check-out terminals which are capable of inputting or sensing and interpreting a symbol or other indicia related to the product, such as a Universal Product Code (UPC), generally comprising a machine-readable bar code coupled with a human-readable UPC number, that is printed on a label or tag which is placed on each item of merchandise to be purchased. The manufacturer may assign and mark each product that it sells with a UPC. Conventionally, once the product reaches the retailer, the retailer further identifies each product with a Stock Keeping Unit (SKU) number or code as well as other information for identifying a specific item or style of merchandise. The retailer's SKU number may be either an entirely different number used to identify each product (e.g., by style) or a modified version of the manufacturer's UPC number, derived, perhaps, by adding a SKU number to the UPC number for example.
A POS terminal, a kiosk terminal, or a sales person's hand-held terminal might be coupled to a store computer system, such as a network server or some other store platform host, which is able to recognize and process UPC and/or SKU information which has been manually keyed-in or sensed and interpreted by a device, such as a barcode reader, coupled to the terminal. The computer system typically includes a database which stores information relating to the retailer's product inventory, such as stocked merchandise, a UPC and/or SKU number for each item of merchandise, and various types of merchandise identification information, such as price, inventory, style, color, size, etc., which is associated with each UPC and/or SKU number. When a customer purchases an item of merchandise, store personnel frequently use an automated terminal to read the barcode markings which are attached to the item. A computer interprets the UPC and/or SKU number comprised by the barcode, accesses the database to determine the price for each item, and maintains a running total of the total transaction price.
One problem that results from the independent identification schemes of the manufacturer and the retailers is that there is no way for the manufacturer to track the quantity of any particular product that each retailer sold. For example, even if a manufacturer obtains all of the SKU numbers representing items purchased from Retailer 1 and Retailer 2 by consumers, the manufacturer has no means for determining which SKU number corresponds to the manufacturer's UPC, since the UPCs and SKU numbers of the various retailers are not tracked and matched.
Another problem specifically relates to prior art incentive or loyalty programs, wherein program participants are encouraged to purchase products and/or services from sponsoring merchants. While such loyalty programs enable participants to earn rewards based on purchases made from a designated merchant, they lack the ability to reward participants at various levels of the product distribution chain.
In view of the foregoing, a need exists for an incentive or loyalty program which overcomes the shortcomings of the prior art. Thus, there is a need for a system and method which provides a universal customer incentive program that networks various levels of the product distribution chain, such as manufacturers, wholesalers, and retailers, to provide incentives to consumers to purchase products not only from a particular merchant or group of merchants but also from particular manufacturers, regardless of the specific merchant who sells the manufacturer's products to the consumer. Additionally, a need exists for a system and method for gathering data which associates particular consumer purchasing behaviors and specific products or product criteria across a manufacturer's distribution channels.
The present invention provides a system for implementing a loyalty program on a network-wide level. The system associates merchant, UPC, and SKU data on a network level to reward consumers and/or to analyze the data for a variety of business purposes, such as market segmentation analyses and/or analyses relating to consumer spending behaviors or patterns, for example. In accordance with one aspect of the invention, the association of merchant, UPC, and SKU data by the system facilitates implementation of an incentive or loyalty program by providing universal rewards currency. This universal rewards currency may be “spent” by participants who have earned rewards and accepted by the other participants in the multi-tiered network created by the system.
The multi-tiered network may comprise any number of participants, including consumers, retailers (and any of their employees), manufacturers, third-party providers, and the like. In accordance with another aspect of the invention, the association of merchant, UPC, and SKU data by the system facilitates data analysis on a network level based upon several factors, including a consumer ID, consumer profile, retailer ID, merchant classification code, merchant consortium code, region code, SKU number, UPC, manufacturer ID, and/or the like. The system may receive, filter, and compile any of the above data across multiple entities for the purpose of issuing rewards and performing data analysis, such as analyses which may be employed in strategic planning and marketing for example.
In one embodiment, the invention provides a filtering module to process purchase transaction data received from a retailer POS. Information relating to the merchant is stored and/or received at a rewards server and may include, for example, a retailer identifier, a merchant classification code, merchant consortium code, merchant location code, and the like. Merchant information is used to filter purchase transactions by determining whether the purchase transaction qualifies an initiating purchaser for a reward. Rewards may be determined and calculated at any number of levels. Moreover, this filtering process may determine when a purchase transaction should be subject to data analysis on a network level.
More particularly, the merchant POS transmits purchase data from a merchant to a host, wherein the purchase data includes retailer data, transaction data and a retailer item identifier, and wherein the retailer item identifier enables the host to determine a manufacturer item identifier. The merchant POS then receives, from the host, a determination that the merchant is a qualifying merchant when the purchase data corresponds to the loyalty program data. The merchant POS then causes the host to issue loyalty awards based on the manufacturer item identifier and the loyalty program data.
A more complete understanding of the invention may be derived by referring to the detailed description and claims when considered in connection with the Figures, wherein like reference numbers refer to similar elements throughout the Figures, and:
The following disclosure presents and describes various exemplary embodiments in sufficient detail to enable those skilled in the art to practice the invention, and it should be understood that other embodiments may be realized without departing from the spirit and scope of the invention. Thus, the following detailed description is presented for purposes of illustration only, and not of limitation, and the scope of the invention is defined solely by the appended claims.
The present invention may be described herein in terms of functional block components and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the present invention may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, Java, COBOL, assembler, PERL, or the like, with the various algorithms being implemented with any combination of data structures, objects, processes, routines, or other programming elements. Further, it should be noted that the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. For a basic introduction to cryptography, please review a text written by Bruce Schneider which is entitled “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” published by John Wiley & Sons (second edition, 1996), which is hereby incorporated by reference.
It should be appreciated that the particular implementations shown and described herein are illustrative of the invention and its best mode and are not intended to otherwise limit the scope of the present invention in any way. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical incentive system implemented in accordance with the invention.
Communication between participants in the system of the present invention is accomplished through any suitable communication means, such as, for example, a telephone network, public switch telephone network, intranet, Internet, extranet, WAN, LAN, point of interaction device (e.g., point of sale device, personal digital assistant, cellular phone, kiosk terminal, automated teller machine (ATM), etc.), online communications, off-line communications, wireless communications, satellite communications, and/or the like. One skilled in the art will also appreciate that, for security reasons, any databases, systems, or components of the present invention may consist of any combination of databases or components at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, de-encryption, compression, decompression, and/or the like.
It further will be appreciated that users may interact with the system via any input device such as a keyboard, mouse, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®), cellular phone, and/or the like. Similarly, the invention could be used in conjunction with any type of personal computer, network computer, workstation, minicomputer, mainframe, or the like, running any operating system, such as any version of Windows, Windows NT, Windows 2000, Windows 98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, or the like. Moreover, although the invention may be described herein as being implemented with TCP/IP communications protocols, it will be readily understood that the invention could also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, or any number of existing or future protocols. Moreover, the system contemplates the use, sale, or distribution of any goods, services, or information over any network having similar functionality described herein.
Each participant or user of the system of the present invention, including purchasers, retailers, manufacturers, and a third-party providers, may be equipped with a suitable computing system to facilitate online communications and transactions with any other participant. For example, some or all participants may have access to a computing unit in the form of a personal computer, although other types of computing units may be used, including laptops, notebooks, handheld computers, set-top boxes, kiosk terminals, and the like. Additionally, other participants may have computing systems which may be implemented in the form of a computer-server, a PC server, a networked set of computers, or any other suitable implementations which are known in the art or may hereafter be devised.
The computing systems may be connected with each other via a data communications network as described more fully above. For example, the network may be a public network, which is assumed to be insecure and open to eavesdroppers. In one embodiment, the network is embodied as the Internet. In this context, the computers may or may not be connected to the Internet at all times. For instance, the consumer's computer may employ a modem to occasionally connect to the Internet, whereas the retailer computing system, the manufacturer computing system, and the central rewards mechanism might maintain a permanent connection to the Internet. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network.
The retailer's computer system may also be interconnected to a third-party provider via a second network, referred to as a payment network. The payment network represents existing proprietary networks that presently accommodate transactions for credit cards, debit cards, and other types of financial instruments or banking cards. The payment network is a closed network that is assumed to be secure from eavesdroppers. Examples of the payment network include the American Express®, VisaNet®, and the Veriphone® networks.
As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, aspects of the present invention may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, the present invention may take the form of a computer program product on a computer-readable storage medium having computer-readable program-code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.
The present invention is described below with reference to block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various aspects of the invention. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose, hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions.
As used herein, the terms “user” and “participant” shall interchangeably refer to any person, entity, charitable organization, machine, hardware, software, or business who accesses and uses the system of the invention, including consumers, retailers, manufacturers, and third-party providers. Participants in the system may interact with one another either online or off-line. As used herein, the term “online” refers to interactive communications that takes place between participants who are remotely located from one another, including communication through any of the networks or communications means described above or the like.
The term “manufacturer” shall include any person, entity, charitable organization, machine, software, hardware, and/or the like that manufactures, distributes, or originates a product or service which may ultimately be offered to a consumer directly or indirectly through a retailer. The term “manufacturer” may also include any party that generates and/or provides manufacturer item identifiers. The term “retailer” shall include any person, entity, charitable organization, machine, software, hardware, and/or the like that that offers a product or service to a consumer. As used herein, the term “retailer” is used interchangeably with the term “merchant”. Moreover, in this context, a retailer or merchant may offer or sell, either online or offline, products and/or services made or supplied by at least one manufacturer. As used herein, the phrases “network level” and “network-wide level” shall refer to a system that includes more than one retailer and at least one manufacturer.
As used herein, the terms “purchaser”, “customer”, “consumer”, “participant”, and “end-user” may be used interchangeably with each other, and each shall mean any person, entity, charitable organization, or business which uses a consumer ID to participate in the present system. A “consumer ID”, as used herein, includes any device, code, or other identifier suitably configured to allow the consumer to interact or communicate with the system, such as, for example, a rewards card, charge card, credit card, debit card, prepaid card, telephone card, smart card, magnetic stripe card, bar code card, authorization/access code, personal identification number (PIN), Internet code, other identification code, and/or the like. Additionally, a “consumer ID” may comprise any form of electronic, magnetic, and/or optical device capable of transmitting or downloading data from itself to a second device which is capable of interacting and communicating with such forms of consumer I.D.
A consumer may register to participate in the present system by any methods known and practiced in the art. For example, a consumer may be enrolled automatically (e.g. if the consumer holds an existing account with the system administrator), over the phone, at the point of sale through a paper application or verbal interview, through the mail, or through instant enrollment online. Consumer enrollment data may comprise any of the following: name; address; date of birth; social security number; email address; gender; the names of any household members; a credit card number for charging any fees that may be associated with participation in the system, survey data; interests, educational level, and/or any preferred brand names. Upon enrollment, the consumer receives a consumer ID. The consumer ID may be associated with a household account which specifies the consumer as a primary member and permits the identification of supplementary members associated with the consumer's household who may also earn reward points for the consumer.
A “consumer profile”, as used herein, shall refer to any data used to characterize a consumer and/or the behavior of a consumer. In the context of a commercial transaction, “a consumer profile” shall be understood to include, for example, the time and date of a particular purchase, the frequency of purchases, the volume/quantity of purchases, the transaction size (price), and/or the like. Additionally, in other transactional contexts, the term “consumer profile” shall also be understood to include non-purchase behaviors of a consumer, such as consumer enrollment data, visiting a Web site, referrals of prospective participants in the system, completion of a survey or other information gathering instrument, and/or the like. For instance, a participating online consumer may earn rewards points automatically through a triggering event, such as visiting a Web site, completing an online survey, or clicking on a banner advertisement for example. Offline, a participating consumer may earn rewards points by completing a task or showing their consumer ID to the cashier and triggering the cashier to provide a “behavior” ID which may be input (e.g., by scanning a bar code on a paper survey for example) into the POS terminal. Further, any aspects of the consumer profile may be used in the context of data analysis.
A “third-party provider” may comprise any additional provider of goods and/or services to a consumer. Specifically, a “third-party provider” includes any party other than the particular manufacturer and retailer who is involved in a transaction with a consumer. A third-party provider may include, for example, a financial institution, such as a bank or an issuer of a financial instrument (such as a credit card or a debit card). A third-party provider may also include a provider of goods and services which are offered as awards to consumers in exchange for a requisite number of reward points.
Though the invention may generically be described with reference to a series of transactions which transfer a good or service from an originating party to an intermediary party and a subsequent transaction which transfers the good or service from the intermediary party to an end-user of that good or service, for convenience and purposes of brevity and consistency, the present disclosure generally refers to the originating party as a manufacturer, the intermediary party as a retailer, the end-user as a consumer, and a good or service as a product or item. However, it will be recognized by those of ordinary skill in the art that the retailer need not provide a product or item to a consumer in exchange for monetary currency. While this often may be the case, the present disclosure is not so limited and includes transactions which may be gratuitous in nature, whereby the retailer transfers a product or item to a consumer without the consumer providing any currency or other value in exchange. It is further noted that additional participants, referred to as third-party providers, may be involved in some phases of the transaction, though these participants are not shown. Exemplary third-party providers may include financial institutions, such as banks, credit card companies, card sponsoring companies, or issuers of credit who may be under contract with financial institutions. It will be appreciated that any number of consumers, retailers, manufacturers, third-party providers, and the like may participate in the system of the present invention.
As used herein, the term “UPC” and the phrase “manufacturer item identifier” shall refer to any symbol or indicia which provides information and, in an exemplary embodiment, shall refer to any number, code, or identifier assigned by a manufacturer and associated with an item, including any type of goods and/or services, ultimately offered to a consumer or other end-user. Colloquially, a UPC is sometimes referred to as a SKU number. However, as used herein, the term “SKU” and the phrase “retailer item identifier” shall refer to any symbol or indicia which provides additional information and, in an exemplary embodiment, shall refer to any number, code, or identifier assigned by a retailer and associated with an item, including any type of goods and/or services, offered to a consumer or other end-user.
“Purchase data”, as used herein, comprises data relating to the sale, lease, rent, offer or other transaction involving any item (e.g., goods and/or services) to a consumer or other end-user. Purchase data may include any of the following exemplary data or information: an item purchased, an item price, a number of items purchased, a total transaction price, loyalty points used, loyalty points earned, loyalty points balance, discounts, a payment method, a date, a store identifier, an employee identifier, a retailer item identifier, a loyalty identifier, and/or the like.
“Retailer ID” or “merchant ID” as used herein, comprises any symbol, indicia, code, number, or other identifier that may be associated with a retailer of any type of items offered to a consumer or other end-user. A retailer ID may also include or be associated with a “store ID”, which designates the location of a particular store. For example, a retailer ID may directly, or through an associated store ID, identify a store by name, geographic location, mapping coordinates, district, postal code, street address, and any combination thereof. The store ID may be used to facilitate geographic or regional filtering for the purpose of issuing and/or redeeming of loyalty points or any other incentive. The store ID may be used to identify the location of a retailer or may itself be associated with another identifier such as a regional ID, for example. A store ID, or the like, may be used by the disclosed filtering module to determine if a retailer is located within defined boundaries for the purpose of issuing loyalty points to the retailer, manufacturer or the retailer's customers. In another embodiment, a retailer ID further includes or is associated with a merchant classification code, a merchant consortium code, a merchant location code, a region identifier, and the like.
A retailer ID may be associated with a “merchant classification code”, which defines a classification that serves as a general descriptor of the merchant type. A merchant classification code may serve to group retailers that share a common business line and/or sell common products or services. For example, a computer retailer may have a classification code identifying the retailer as an “electronics” merchant. A merchant classification code may be used by the disclosed filtering module to qualify a retailer, manufacturer and/or customer for rewards based on a purchase from a merchant of a defined type. According to one embodiment, the merchant classification code further includes or is associated with a retailer ID, a merchant consortium code, a region identifier, and the like.
Further, a retailer may be identified according to an affiliation with other merchants. A “merchant consortium code” identifies any group of retailers that are affiliated through agreement, common ownership, common retailer space, and the like. Further, a merchant consortium may comprise a group of retailers that identify and/or relate to one another in some manner (e.g., geography, common or related promotional efforts, common ownership, selling common goods and/or services, etc.). Such consortiums may enter into agreements to provide incentives to consumers based on purchase transactions consummated at any one of the retailers of the consortium, such that the consumer's patronage may benefit other members of the consortium either individually or as a whole. An example of a merchant consortium may include a particular shopping mall. According to one embodiment, the merchant consortium code further includes or is associated with a retailer ID, a merchant classification code, a region identifier, and the like.
A “merchant location code” identifies a retailer by a physical geographical location. The merchant location code enables, for example, filtering of retailers based on store location such that a promotion can be implemented with defined physical boundaries. A location code may denote a retailer's latitude and longitude, state, region, city, district, postal code, street address, and the like. According to one embodiment, the merchant location code further includes or is associated with a retailer ID, a merchant classification code, a merchant consortium code, and the like.
A “manufacturer ID” comprises any symbol, indicia, code, number, or other identifier that may be associated with a manufacturer of any type of goods and/or services ultimately offered to a consumer or other end-user.
An “award” or “reward” may comprise any quantity of products, services, coupons, gift certificates, rebates, reward points, bonus points, credits or debits to a financial instrument, any combination of these, and/or the like. “Data analysis”, as used herein, shall be understood to comprise quantitative and qualitative research, statistical modeling, regression analyses, market segmentation analyses, econometrics, and/or the like. Such analyses may be used to predict consumer behaviors and/or correlate consumer profiles, retailer data, manufacturer data, and/or product or service data.
One skilled in the art will appreciate that any earning or using of loyalty points, as discussed herein, may apply to (or involve) the retailer, manufacturer, customers, shippers, or any other entity or person involved in, or associated with, the distribution channel. Moreover, a customer, client, participant or consumer, as used herein, may also include the retailer, manufacturer, consortium or any other entity or person described herein.
According to one embodiment of the invention, a central rewards mechanism includes a filter component for determining whether a POS transaction meets predefined requirements. The filter module filters transactions at various levels based on, for example, merchant identifier, merchant classification code, merchant consortium identifier, and region identifier. While described extensively herein, the filter component processes transaction data to determine when a POS transaction qualifies a loyalty program participant to be awarded a number of loyalty points.
Practitioners will appreciate that the disclosed filtering processes may be applied to loyalty point redemption as well. For example, the filter module may receive a request from a retailer POS device when a card holder intends to apply a portion of a loyalty account balance toward a purchase. Based on the filtering of the request, the system may allow or decline the transaction.
The filter module receives loyalty program data from a rewards server in, for example, real-time or batch mode. The filter module further receives transaction data from a POS terminal by way of a payment gateway. The filter module compares the transaction data to the loyalty program data to determine if a correlation exists between one or more elements of each data set. Based on whether or not a correlation exists, the filter module may use the two data sets to calculate a reward, forward the transaction data to a processor for SKU/UPC matching, or both.
The system of the present invention associates or maps merchant data, manufacturer UPC data, and retailer SKU data on a network level to reward consumers and/or to analyze the data for a variety of business purposes, such as market segmentation analyses and/or analyses relating to consumer spending behaviors or patterns for example. Rather than simply capturing transactions at a Record of Charge (ROC) level, that is, recording consumer purchases in a general fashion by designating purchase categories (such as “clothing”, “electronics”, or “hardware” for example), the system identifies the merchant, particular item purchased (such as “jeans”, “stereo”, or “hammer” for example), as well as its corresponding manufacturer. By filtering transaction data from the retailer POS, the system links or associates the merchant to the retailer SKU. The system further links or associated the retailer SKU to a manufacturer UPC to permit the standardization of merchants, goods, and/or services codes at the network level. This standardization not only permits a record of both the specific item purchased and its manufacturer, regardless of the particular retailer involved in the transaction, but it permits the mapping of multiple consumers, multiple goods and/or services, multiple retailers, and/or multiple manufacturers to advantageously cross-market goods and services to consumers.
In accordance with one aspect of the invention, the association of merchant data, SKU data, and UPC data by the system facilitates implementation of an incentive or loyalty program by providing universal rewards currency which may be “spent” by participants who have earned rewards and accepted by the other participants in the multi-tiered network created by the system. For example, the system may issue universal rewards currency based on the identity of the merchant, the type of merchant, a group of merchants, the location of the merchant, and the like. Earned universal rewards currency may likewise be limited to a particular merchant, merchant type, group of merchants, and merchant location. Thus, a network is defined wherein universal rewards currency may be issued and redeemed.
The network may comprise any number of participants, including consumers, retailers (and any of their employees), manufacturers, third-party providers, and the like. Each of these categories of participants may be considered a tier in the network, and each participant within the various tiers may design and implement an independent rewards scheme within the context of the universal environment provided by the system. For example, Manufacturer 1 may produce and assign a UPC to Item X. Item X may subsequently be offered for sale by both Retailer 1 and Retailer 2. Retailer 1 and Retailer 2 may then each assign an independent SKU number to Item X to facilitate their own tracking, inventory, and pricing schemes. A consumer may then purchase Item X from both Retailer 1 and Retailer 2. Moreover, while Retailer 1 and Retailer 2 may each assign a separate SKU number to Item X, the filter module may map the two SKU numbers when a link or association is established, (e.g., merchant classification code, merchant consortium code, location code, etc.) between Retailer 1 and Retailer 2.
Since the system is capable of processing, associating, and quantifying a variety of data, including consumer data, employee data, retailer data, manufacturer data, SKU number data corresponding to Item X, and UPC data assigned by Manufacturer 1, for example, this data can then be used by the manufacturer, the retailer, the system administrator, and/or a third-party provider to provide rewards to consumers, employees, retailers, etc. For example, a manufacturer may provide frequency-based incentives, such as every 10th purchase of a particular item will be discounted by 50%, for example, independent of and/or in addition to any incentives offered by the specific retailer involved in the transaction. Additionally, the manufacturer may provide sales incentives to the employees of retailer's independent of and/or in addition to any employee incentive programs that the retailers may choose to implement.
Since rewards, which may be in the form of rewards points, may be earned across the various tiers in the network, rewards may also be used or spent across the various tiers in the network. Thus, any rewards points that an employee, for example, may earn by promoting a particular manufacturer's line of products, may be “spent” by that employee on goods or services provided by any participant in the network, not merely at the retailer who employs that employee. Likewise, any rewards points earned by a consumer may be spent on goods or services offered by any participant in the network.
In accordance with another aspect of the invention, the association of merchant data, UPC data, and SKU data by the system facilitates data analysis on a network level based upon several factors, including any of the following: consumer ID, consumer profile, retailer ID, merchant classification code, merchant consortium code, location code, SKU number, UPC, manufacturer ID, and/or the like. The system may compile any of the above data across multiple participants for the purpose of data analysis, such as analyses which may be employed in strategic planning and marketing for example. The system of the invention may be used to compile, analyze, and report data in a manner which would inform any or all network participants that, for example, a specific consumer (1) has made multiple purchases of particular manufacturers' products; (2) has spent Q dollars over a certain time period (3) at specific multiple retailers; and (4) of the purchases made, R dollars went towards the purchase of Product 1, S dollars went towards the purchase of Product 2, and T dollars went towards the purchase of Service 1. Moreover, the system may be used to compile, analyze, and report data that enable a retailer, a manufacturer, and/or a third-party provider to create a variety of targeted marketing promotions, such as, for example, (1) marketing Product 1 offered by Manufacturer 1 to consumers who purchase Product 2 offered by Manufacturer 2; (2) marketing Product 1 offered by Manufacturer 1 and sold by Retailer X to consumers who purchase Product 2 offered by Manufacturer 2 at Retailer Y; (3) marketing Product 1 offered by Manufacturer 1 and sold by Retailer X to consumers who purchase Product 2 offered by Manufacturer 2 at Retailer Y five times a year. It will be appreciated that these are but a few of the many possible applications for data gathered and generated by the system of the present invention.
In accordance with a further aspect of the invention, the system administrator may allocate rewards points to participants in the system. In one embodiment, participating retailers and/or manufacturers may purchase points from the system administrator and the points are then allocated to an account associated with the retailer and/or manufacturer. In an alternate embodiment, the system administrator may give or donate points to participating retailers and/or manufacturers. The system administrator maintains an account with each of the participating retailers and manufacturers and tracks available point balances and/or balances owing on a rolling basis. The points purchased by the retailers and/or manufacturers may then be earned by and issued to consumers in a manner that is predetermined by the retailer and/or manufacturer involved in the transaction with the consumer. For example, Retailer 1 may purchase 10,000 points from the system administrator and then offer consumers 1 point for every $10 dollars spent in Retailer 1's store or, perhaps, some number of points for every fifth transaction in the store. Moreover, Manufacturer 1, who produces the product offered by Retailer 1, may also purchase points from the system administrator. Thus, when a consumer purchases Manufacturer 1's product at Retailer 1, Manufacturer 1 may issue some number of points to the consumer. The issuance of points, either by retailers or manufacturers, may be based upon any selected criteria, including a points-for-dollars ratio, a defined quantity of points per item or per transaction, some combination of these, and/or the like.
The system administrator maintains an account for each participating consumer and apprises the consumer of the point totals and account activity. The consumer may review the total number of points in the account either online or off-line, such as through a periodic statement sent by the system administrator or through the use of a communications network, such as the Internet, for example. Points in the consumer's account are accumulated across the multiple retailers and/or manufacturers participating in the system. Thus, points earned by a consumer based upon transactions with different retailers and/or manufacturers are combined, resulting in a rapid accrual of points. The system administrator offers a catalog of products and services, which may be either online or off-line, from which consumers may select rewards in exchange for accrued points. In this manner, consumers advantageously earn points based upon their everyday purchases of products and services, these points are accrued across retailers and/or manufacturers, and point redemption takes place through a single, universal catalog of rewards.
In accordance with the present invention,
The central rewards mechanism 102 manages the incentive or loyalty program of the system 100. In an exemplary embodiment, central rewards mechanism 102 receives, processes, and stores manufacturer data, such as information regarding products and/or services and UPC data, transmitted by manufacturers 106 who have enrolled in the system 100. Central rewards mechanism further stores information relating to participating retailers. Such information may include, for example, SKU numbers, retailer ID, merchant classification code, merchant consortium code, location code, and the like. Manufacturers 106 and merchants 104 may transmit data to central rewards mechanism 102 in any form and by any means known in the art, including any of the communications means described above.
The manufacturer data is stored by the central rewards mechanism 102 in database 103. Database 103 may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Common database products that may be used to implement database 103 include DB2 by IBM (White Plains, N.Y.), any of the database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access by Microsoft Corporation (Redmond, Wash.), or any other database product. Database 103 may be organized in any suitable manner, including as data tables or lookup tables.
The central rewards mechanism 102 may receive and process consumer ID information and purchase data from any of the retailer systems 104. The central rewards mechanism 102 may also associate a particular consumer ID with the purchase data and a corresponding manufacturer item identifier. In one embodiment, a filter module of the central rewards mechanism 102 performs an analysis involving any of the following: a consumer ID, purchase data, a point ratio, a consumer profile, a retailer ID, merchant classification code, merchant consortium code, location code, and a manufacturer ID. The analysis may be dependent upon an association of the consumer ID, merchant data, purchase data, and the manufacturer item identifier. The analysis may further comprise, for example, a calculation of rewards points and/or other analyses for purposes of market segmentation, determining consumer spending behavior, correlating spending behavior and consumer demographics, and/or the like, as described in greater detail above.
In one exemplary embodiment, the central rewards mechanism 102 stores and/or informs a consumer of the rewards points that have been earned from a particular transaction as well as accumulated over time. The number of rewards points calculated and awarded by the central rewards mechanism 102 for a particular purchase may depend upon a predetermined rewards ratio. The rewards ratio may be determined by the retailer, the system administrator, the manufacturer of the purchased item, and/or any other suitable third-party. For example, if a participating consumer buys a product from a retailer for $100 and if the retailer rewards ratio is one reward point for each dollar of the purchase price (i.e., one-for-one), once the consumer's consumer ID is identified by the system, the consumer is credited with a suitable number of rewards points from the retailer, which, in this case, would be 100 points. In addition, the retailer may be linked to a consortium of merchants through a merchant consortium code. Thus, if the consortium agrees to issue reward points based on a purchase from a consortium member, then the consortium may select a point ratio that is different than the retailer's selected ratio. Further, if the manufacturer also chooses to issue rewards points for the item purchased, the manufacturer may select a point ratio that is different from the retailer's and/or the consortium's selected ratio. In the illustrated example, if the manufacturer's selected point ratio is two-for-one, then the consumer will be awarded an additional 200 points from the manufacturer for this single $100 purchase. If the consortium's point ratio is one half-for-one, then the consumer will be awarded an additional 50 points for the $100 purchase. Therefore, in all, the consumer would have earned a total of 350 points for the single $100 purchase.
The system may also provide a line of credit to advance loyalty points to any entity discussed herein, as set forth in, for example, U.S. Ser. No. 11/548,203, filed on Oct. 10, 2006 and entitled “A System And Method For Issuing And Using A Loyalty Point Advance” and U.S. Ser. No. 09/718,192, filed on Nov. 21, 2000 and entitled “System And Method For The Real-Time Transfer Of Loyalty Points Between Accounts”, which is hereby incorporated by reference.
In the manner described by way of example above, the system of the invention may provide “earn accelerators” through which consumers may accumulate rewards points at comparatively rapid rate. In other words, a single purchase may generate rewards points for a consumer from any or all of a retailer, merchant consortium, manufacturer, and/or any other third-party provider. The generated rewards points may be used as rewards currency by the consumer throughout the network established by the system of the invention.
In an exemplary embodiment, retailer system 104 comprises a retailer terminal 108 and a retailer processor 110 in communication with database 111. Retailer terminal 108 comprises any device capable of identifying a consumer ID. Exemplary devices for identifying a consumer ID may include a conventional card reader which recognizes a magnetic stripe or bar code associated with a consumer ID, a biometric device, a smart card reader which recognizes information stored on a microchip integrated with a consumer ID, and any device capable of receiving or uploading consumer ID data transmitted electronically, magnetically, optically, and/or the like. In one embodiment, retailer terminal 108 and retailer processor 110 are co-located at a retail store. In another embodiment, retail terminal 108 and retailer processor 110 are remote from each other.
In an exemplary embodiment, as illustrated in
In accordance with the exemplary embodiments illustrated in
Regardless of the location of retailer regional processor 114, retailer regional processor 114 receives and processes similar information from each of the retailer processors 110 associated with each of the retail stores owned by the same retailer. Whether the system 100 comprises a retailer regional processor 114 or a retailer national processor may be a function of the number of stores maintained by a particular retailer. That is, a larger retailer who has numerous stores throughout the country, for example, may choose to have a plurality of regional processors, while a smaller retailer with a few stores scattered across the country may be better served by a single, national processor. In exemplary embodiments, the retailer regional processors 114 and/or national processors communicate with a suitable database 115 or other storage device which is configured to store and maintain purchase data and any other suitable retailer information. In another exemplary embodiment, retailer regional processor 114 may receive, process, and store manufacturer data, such as information regarding products and/or services and UPC data, from manufacturers 106 who have enrolled in the system 100. The manufacturer data may be stored in any suitable form, including data tables or lookup tables.
With momentary reference to
In an exemplary embodiment, rewards terminal 116 operates in real-time. In this context, “real-time” means that reward points are immediately, or nearly immediately, updated at the time purchases are made and are therefore immediately redeemable by the consumer at the a point of sale. Thus, for example, a consumer may be informed by rewards terminal 116 at the point of sale that the item being purchased by the consumer may be purchased using the consumer's accumulated reward points, including points accumulated on a network level. Points accumulated on a network level enable consumers to accumulate points more rapidly than would be possible if only a single retailer or group of retailers were issuing the points. In one embodiment, rewards terminal 116 may update a consumer's rewards points in real-time and, in response to the consumer's particular points total, issue a coupon, a gift certificate, and/or additional bonus points to the consumer.
In another exemplary embodiment, the system may operate in batch mode, wherein points totals are calculated, stored, and periodically updated for access by the retailer terminal 108, including POS terminal 112 and/or rewards terminal 116. Thus in this embodiment, the consumer may be notified of available points sometime after a purchase, or a suggestive sale may take place after a purchase. The total point count or suggestive sale may take into account points generated and accumulated as the result of network-wide purchases.
In various alternate embodiments of the invention, retailer terminal 108 may include a rewards terminal 116 but not a POS terminal 112; a POS terminal 112 but not a rewards terminal 116; or a POS terminal 112 in communication with a rewards terminal 116. In alternate embodiments, where terminal 108 includes a POS terminal 112 and a rewards terminal 116, the two terminals 112 and 116 may be variously implemented as separate terminals, integrated terminals, or software within a device. In another embodiment, where terminal 108 comprises a rewards terminal 116 but not a POS terminal 112, terminal 108 may be a kiosk terminal located within a retail store or some other remote terminal which is capable of recognizing a consumer ID and communicating with the system 100. A consumer may use independent rewards terminal 116 to do, for example, any of the following: view accumulated reward points totals; view potential awards which the consumer may obtain in exchange for various numbers of points; select an award; redeem rewards points for a selected award; request and/or receive a reward points advisory statement; and/or view a directory of participating retailers, manufacturers, and third-party providers.
In another exemplary embodiment, system 100 further comprises a consumer terminal 118. Consumer terminal 118 is any remote terminal through which a consumer may access other aspects of the system 100. Consumer terminal 118 may comprise any of the input devices, computing units, or computing systems described above. Further, consumer terminal 118 communicates with the system 100-through any of the communications networks described above. In one embodiment, consumer terminal 118 permits a consumer to engage multiple facets of the system 100 in an interactive online communications environment. The interactive online environment made available through consumer terminal 118 is an extension of the network-level incentive award program and is implemented in conjunction with other aspects of the system 100. In this context, a consumer may uses consumer terminal 118 for a variety of purposes. In one embodiment, consumer terminal 118 may be used to communicate with and receive information from the central rewards mechanism 102. For example, a consumer may use consumer terminal 118 to do any of the following: enroll in the system; receive statements or reports regarding accumulated reward points totals; receive bonus details; view potential awards which the consumer may obtain in exchange for various numbers of points; select an award; receive redemption information; view points adjustments; redeem rewards points for a selected award; request and/or receive a reward points advisory statement; receive information regarding where and how points were earned and/or how points were redeemed; receive information regarding expiration dates for points earned; receive information relating to any applicable fees; receive information regarding marketing promotions; and/or view a directory of participating retailers, manufacturers, and/or third-party providers.
In another embodiment, consumer terminal 118 may be used to interact with and/or make purchases and generate rewards points from participating online retailers, as illustrated by the various phantom lines in
In accordance with a further aspect of the invention, the system 100 may comprise a rewards server 120 in communication with a database 121, as illustrated in
In an exemplary embodiment, rewards server 120 receives, processes, and stores both manufacturer data and retailer data. Manufacturer data may include descriptions of products and/or services and UPC data transmitted from manufacturers 106 who have enrolled in the system 100. The manufacturer data may be stored in any suitable form, including data tables or lookup tables. Retailer data may include descriptions of products and/or services, merchant classification codes, merchant consortium codes, location codes, and SKU data transmitted from retailers 104 who have enrolled in the system 100. The retailer data may be stored in any suitable form including, for example, data tables or lookup tables where it may be subsequently used for transaction filtering processes as will be described in greater detail in relation to
In an exemplary embodiment, the rewards server 120 performs a plurality of functions that might otherwise be performed by the central rewards mechanism 102. For example, since rewards calculations require significant processing and memory resources, performance of calculations processing by the rewards server 120 at the regional level lessens the processing load on the central rewards mechanism 102, thereby increasing the efficiency of the central rewards mechanism 102. In an exemplary embodiment, each retailer's region, which comprises a plurality of that retailer's stores or outlets, accesses a rewards server 120 which acts as an intermediary between the retailer regional processor 114 and the central rewards mechanism 102. This configuration relieves the processing, power, memory, and other requirements of the central rewards mechanism 102. Moreover, each retailer is but one of many retailers that may participate in the network level rewards structure. Accordingly, a plurality of rewards servers 120 may be in communication with the central rewards mechanism 102 as well as each of the participating retailer regional processors 114, further alleviating the processing burden and freeing up the resources of the central rewards mechanism 102.
Implementations which include at least one independent rewards server 120 are also advantageous because cost-effective communications links may be used to facilitate communications with the central rewards mechanism 102. Performance by the rewards server 120 of many of the “intelligence functions” of the system 100, permits transmission of only particular forms of purchaser information to the central rewards mechanism 102. In an exemplary embodiment, data sent from the rewards server 120 to the central rewards mechanism 102 may include the consumer ID and the total number of rewards points earned by a consumer in a particular transaction. In another exemplary embodiment, data transmitted by the rewards server 120 to the central rewards mechanism 102 may also include any pre-selected aspect of the consumer profile, any pre-selected aspect of the purchase data, and/or any other pre-selected data associated with a consumer, a retailer, a manufacturer, and/or a third-party provider. Pre-selection of the types of data transmitted by the rewards server 120 to the central rewards mechanism 102 may be conducted by the system administrator, a retailer, a manufacturer, and/or a third-party provider. Thus, data which may be useful for purposes of data analysis but unrelated to the rewards feature, such as the characteristics of the particular item purchased for example, may not need to be transmitted to the central rewards mechanism 102.
Exemplary functions performed by the rewards server 120 may include the association of merchant data, UPC data and SKU data; manipulation of the rewards criteria applicable in particular cases, which may further depend upon the retailer, manufacturer, and/or third-party provider involved in a specific transaction with a consumer; calculation of rewards benefits earned by the consumer; filtration functions for determining which data is transmitted from the rewards server 120 to the central rewards mechanism 102; and/or various types of data analyses, as described above. In an exemplary embodiment, the retailer system 104 houses, maintains, and updates the hardware and/or software of the rewards server 120. In another embodiment, rewards server 120 may be housed, maintained, and updated by the system administrator.
In accordance with another embodiment of the present invention, the system 100 permits an open payment system. Since the invention generally provides that consumer participation in the system is based upon a consumer ID, a purchaser may use any of multiple payment vehicles (such as cash, check, charge card, credit card, debit card, MasterCard®, Visa®, and/or the American Express® Card for example) to make purchases at the various retailers and still participate in the system. Thus, in one embodiment, the consumer ID is independent of any particular payment vehicle, such as a credit card for example.
However, alternate embodiments of the invention may be implemented which associate a consumer ID with a particular payment vehicle, such as a consumer's credit card account, charge card account, debit card account, and/or bank account for example. In this embodiment, the retailer conducting the transaction need only participate in the system to the extent that the retailer provides its SKU data to the system 100, such as to the rewards server 120. In other words, when a consumer ID is associated with an instrument (e.g., a credit card) from a third-party provider, the retailer need not provide a rewards terminal or other terminal capable of processing the consumer ID, since the third-party provider may process the consumer ID as part of the payment transaction. Thus, in this embodiment, rewards benefits may be earned by the consumer on a network-wide level without the retailer's direct participation in the rewards feature (notwithstanding the retailer's participation in transmitting SKU data to the system). Moreover, it will be appreciated that a single consumer ID may be associated with multiple third-party payment vehicles, thereby allowing a consumer to generate rewards points regardless of the particular payment vehicle selected for a particular purchase.
With reference to
Lastly, a storage device 420, such as a hard disk drive for example, preferably contains files or records which are accessed by the various software modules, such as enrollment module 412 and authentication module 414. In particular, consumer data 422 comprises information received from a consumer upon registration with the rewards mechanism 402. Consumer rewards 424 comprise data corresponding to each consumer's rewards account. Consumer rewards 424 may include cumulative rewards point totals as well as historical totals and rewards account activity over time. Retailer records 426 comprise information received from the various participating retailers. Manufacturer records 428 comprise information received from the various participating manufacturers. One skilled in the art will appreciate that the storage device 420 and, therefore, consumer data 422, consumer rewards 424, retailer records 426, and manufacturer records 428 may be co-located with the rewards mechanism 402 or may be remotely located with respect to the rewards mechanism 402. If the storage device 420 is remotely located with respect to the rewards mechanism 402, communication between storage device 420 and rewards mechanism 402 may be accomplished by any suitable communication link but is preferably accomplished through a private intranet or extranet.
Enrollment module 412 receives information from consumers, retailers, and/or manufacturers who wish to participate in the system. Enrollment module 412 accesses and stores information in storage device 420. Authentication and/or validation of the identity and status of participants, including any of the other system components, may be performed by the authentication module 414, which preferably has access to the records residing in storage device 420.
With reference to
Lastly, a storage device 524, such as a database as described above for example, preferably contains files or records which are accessed by the various software modules 512, 514, 516, and 518. In particular, manufacturer data 526 comprises information received from a manufacturer, such as descriptions or other information regarding the manufacturer's products and/or services as well as UPC data for example. Retailer data 528 comprises information received from a retailer, such as descriptions or other information regarding the retailer's products and/or services as well as SKU data for example. Consumer data 530 comprises information pertaining to a consumer, including a consumer ID, purchase data, a consumer profile, and/or the like. One skilled in the art will appreciate that the storage device 524 and, therefore, manufacturer data 526, retailer data 528, and consumer data 530 maybe co-located with the rewards server 502 or may be remotely located with respect to the rewards server 502. If the storage device 524 is remotely located with respect to the rewards server 502, communication between storage device 524 and rewards server 502 may be accomplished by any suitable communication link but is preferably accomplished through a private intranet or extranet.
Referring next to
The various transaction files may be consolidated by the retailer processor 110 and then forwarded to the retailer regional processor 114 (step 606) for further back-office and cumulative data analysis performed by retailer 104.
In an exemplary embodiment, the transaction file is transmitted by either of the retailer processor 110 or the retailer regional processor 114 to the rewards server 120 (step 608). Through a filtering process, SKU information for each item included in the transaction file is then matched to or associated with corresponding UPC information which identifies the related manufacturer 106. An exemplary association process is illustrated in the flowchart of
In an exemplary embodiment, database 121 receives and stores manufacturer data, including UPC data, from manufacturer 106 (step 702). Database 121 also receives and stores retailer data, including SKU numbers, from retailer 104 (step 704). In an exemplary implementation, database 121 stores manufacturer data in a separate manufacturer data table for each participating manufacturer 106. Each manufacturer data table may comprise a plurality of fields, such as “UPC” and “product description” for example, and a plurality of records, each of which corresponds to an item offered by the participating manufacturer 106.
In one embodiment, database 121 stores retailer data in a separate retailer data table for each participating retailer 104. Each retailer data table may comprise a plurality of fields, such as “retailer ID”, “merchant classification code”, merchant consortium code”, “location code”, “SKU”, and “product description” for example, and a plurality of records, each record corresponding to an item offered by a participating retailer 104.
Data from each of the manufacturer and the retailer data tables is then associated (step 706). The association step may be accomplished by a database merge function, for example, using a “key field” in each of the manufacturer and retailer data tables. A “key field” partitions the database according to the high-level class of objects defined by the key field. For example, a “product description” class may be designated as a key field in both the manufacturer data table and the retailer data table, and the two data tables may then be merged on the basis of the “product description” data in the key field. In this embodiment, the data corresponding to the key field in each of the merged data tables is preferably the same. That is, the product descriptions in the manufacturer data table match the product descriptions in the retailer data table. However, manufacturer and retailer data tables having similar, though not identical, data in the key fields may also be merged by using AGREP, for example. Accordingly, the data
The result of the data association step is the creation of a separate data table, such as a UPC/SKU lookup table for example (step 708). Thus, when the rewards server 120 receives the data (e.g., consumer ID and SKU data) captured by the POS terminal (step 710), the rewards server 120 may search the UPC/SKU lookup table for the appropriate SKU number and then match the SKU to the corresponding UPC data (step 712). In an exemplary embodiment, the “SKU” and “UPC” fields in the UPC/SKU data table may be linked by an appropriate pointer. That is, when the rewards server 120 searches the UPC/SKU table and locates the particular SKU that has been captured and transmitted by the POS terminal, the specifically identified SKU data field uses a pointer to direct the rewards server 120 to the UPC data field that corresponds to that SKU number. In an exemplary embodiment, the UPC data field may be linked by one or more additional pointers to other key fields, such as a consumer ID, a retailer ID, a manufacturer ID, and/or a third-party ID. These additional pointers may be used as means for compiling data which may be useful in any of the various data analyses performed by the rewards server 120. In this manner, the association of POS SKU numbers and UPC data may be used to create a context in which standardized, network-wide analyses may be conducted.
In an exemplary embodiment, the rewards server 120 utilizes the association information to calculate the rewards points generated by a consumer's purchase. For example, an appropriate series of pointers leading from a SKU to a UPC to a manufacturer ID may ultimately direct the rewards server 120 to employ a 2-for-1 manufacturer rewards ratio to award a consumer twice as many points as the dollar amount of the consumer's total transaction price. In another exemplary embodiment, an appropriate series of pointers may result in the calculation of rewards points based upon multiple rewards criteria, such as rewards criteria associated with the manufacturer of the item as well as rewards criteria associated with a third-party provider for example.
In a further embodiment, the rewards server 120 may use the association of UPC and SKU number data to analyze a variety of marketing variables across multiple manufacturers and retailers. For example, rewards server 120 may use a series of pointers leading from an SKU to a UPC and then to a “consumer profile” field or table to correlate, for instance, consumer spending behaviors, particular manufacturers, and/or specific products across multiple retailers for example.
In alternative embodiments, association of the UPC data and SKU number may take place at any of the rewards terminal 116, the retailer POS terminal 112, the retailer processor 110, the retailer regional processor 114 (or a retailer national processor), and/or the central rewards mechanism 102.
In one embodiment, the retailer 104 may offer an incentive or loyalty program that is independent from the program offered by the system 100. Alternatively, the retailer 104 may use the system's UPC data for its own internal purposes.
With momentary reference to
If the filtering module search on the rewards program database does not return any records or insufficient information (step 806), then the POS transaction does not qualify the initiating consumer for a reward program and the transaction is processed normally (step 810). However, if the search returns one or more records or sufficient information (step 806), then the POS transaction qualifies the initiating consumer for a reward program and the filtering module retrieves specific reward program data (step 812). In another embodiment, before or after qualifying an entity, the system may request additional information from the merchant, consumer and/or any other entity discussed herein. Based on the reward program data, the rewards server 120 calculates the reward (step 814) based on any number of conditions such as, for example, the location of the purchase, the time of the purchase, a customer identifier, and the like.
It should be noted that the calculation of a reward at the merchant level (step 812) is not necessary. The process flow described above may be incorporated to filter transactions to determine when a purchase transaction qualifies the initiating consumer for rewards based on SKU/UPC matching as described in reference to
In another embodiment, the filtering module requires only minimal information from the retailer POS because the retailer provides more detailed information in advance, which is stored within a database at the rewards server 120. With reference to
If a SKU is located in the retailer data that corresponds to the transaction SKU (step 906), then the filtering module retrieves stored retailer information corresponding to the SKU (step 912). Retailer information may include, for example, a retailer ID, merchant classification code, merchant consortium code, location code, and the like. Reward server 120 uses the retailer information to perform a search on a database storing reward program data (step 912). A retailer, group of retailers, or any other third-party may interact with the reward server to configure a reward program. The reward program may be based on an individual retailer (retailer ID), retailer type (merchant classification code), retailer grouping (merchant consortium), and retailer location (location code). For example, in an effort to attract more consumers to a shopping mall, a group of retailers within the shopping mall may form a consortium based on an agreement to issue reward points based purchases made within any of the stores within the consortium. As such, the consortium may configure a reward program with the reward server 120, wherein a merchant consortium code is provided and stored with other program details. Reward server 120 may further store information relating to each individual member of the consortium, such that when a transaction SKU is matched to a retailer (step 906), the retrieved retailer record (step 912) may include a consortium code that is used to retrieve reward program information (step 912).
If the filtering module does not locate reward program data based on the retailer information (step 914), then the transaction is subject to the SKU/UPC matching process described in reference to
Practitioners will appreciate that the systems and process steps described above are for explanation only and do not limit the scope of the invention. For example, the various processes may be executed in any order and filtering may occur prior to, during, or following transaction processing at a Card Authorization System (CAS). Moreover, the invention is not limited to the filtering elements as described above. The invention contemplates additional filtering elements and/or layers such as, for example, postal code of the retailer, postal code of the purchaser, a purchaser classification, purchaser demographics, purchase time periods, payment type, and the like. Further, the transaction filtering and matching processes, as described herein, may be used to calculate and issue rewards based on various payment instruments including, for example, credit cards, charge cards, debit cards, prepaid cards, stored value cards, gift cards, reward cards, etc.
According to one embodiment, the various system components and steps described above may be incorporated within a CAS in order to calculate rewards and provide transaction authorization for purchases made through a payment instrument. The payment instrument may include, for example, a credit card, debit card, gift card, gift certificate, rewards card, pre-paid credit card, and the like.
In the foregoing specification, the invention has been described with reference to specific embodiments. However, it will be appreciated that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. The specification and figures are to be regarded in an illustrative manner, rather than a restrictive one, and all such modifications are intended to be included within the scope of present invention. Accordingly, the scope of the invention should be determined by the appended claims and their legal equivalents, rather than by the examples given above. For example, the steps recited in any of the method or process claims may be executed in any order and are not limited to the order presented in the claims.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of any or all the claims. As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, no element described herein is required for the practice of the invention unless expressly described as “essential” or “critical”.
This application is a continuation of, and claims priority to, U.S. patent application Ser. No. 11/742,934, entitled “System and Method for Tiered Filtering of Purchase Transactions” filed on May 1, 2007. The '934 application continuation-in-part of, and claims priority to, U.S. Pat. No. 7,398,225 issued on Jul. 8, 2008 (aka U.S. patent application Ser. No. 09/836,213, entitled “System and Method for Networked Loyalty Program” and filed on Apr. 17, 2001). The '225 patent claims benefit to U.S. Provisional Application Ser. No. 60/279,817, entitled “System and Method for Networked Incentive Awards Program” and filed Mar. 29, 2001, which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4087660 | Sedley | May 1978 | A |
| 4358672 | Hyatt et al. | Nov 1982 | A |
| 4473825 | Walton | Sep 1984 | A |
| 4546241 | Walton | Oct 1985 | A |
| 4609812 | Drexler | Sep 1986 | A |
| 4634848 | Shinohara et al. | Jan 1987 | A |
| 4910672 | Off et al. | Mar 1990 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5056019 | Schultz et al. | Oct 1991 | A |
| 5117355 | McCarthy | May 1992 | A |
| 5128752 | Von Kohorn | Jul 1992 | A |
| 5173851 | Off et al. | Dec 1992 | A |
| 5200889 | Mori | Apr 1993 | A |
| 5201010 | Deaton et al. | Apr 1993 | A |
| 5202826 | McCarthy | Apr 1993 | A |
| 5233514 | Ayyoubi et al. | Aug 1993 | A |
| 5237620 | Deaton et al. | Aug 1993 | A |
| 5256863 | Ferguson et al. | Oct 1993 | A |
| 5287268 | McCarthy | Feb 1994 | A |
| 5305196 | Deaton et al. | Apr 1994 | A |
| 5327508 | Deaton et al. | Jul 1994 | A |
| 5353218 | DeLapa et al. | Oct 1994 | A |
| 5382779 | Gupta | Jan 1995 | A |
| 5388165 | Deaton et al. | Feb 1995 | A |
| 5424524 | Ruppert et al. | Jun 1995 | A |
| 5430644 | Deaton et al. | Jul 1995 | A |
| 5434394 | Roach et al. | Jul 1995 | A |
| 5448471 | Deaton et al. | Sep 1995 | A |
| 5467269 | Flaten | Nov 1995 | A |
| 5471669 | Lidman | Nov 1995 | A |
| 5477038 | Levine et al. | Dec 1995 | A |
| 5483444 | Heintzeman et al. | Jan 1996 | A |
| 5491326 | Marceau et al. | Feb 1996 | A |
| 5502636 | Clarke | Mar 1996 | A |
| 5513102 | Auriemma | Apr 1996 | A |
| 5535407 | Yanagawa et al. | Jul 1996 | A |
| 5537314 | Kanter | Jul 1996 | A |
| 5559313 | Claus et al. | Sep 1996 | A |
| 5592560 | Deaton et al. | Jan 1997 | A |
| 5612868 | Off et al. | Mar 1997 | A |
| 5621812 | Deaton et al. | Apr 1997 | A |
| 5638457 | Deaton et al. | Jun 1997 | A |
| 5642485 | Deaton et al. | Jun 1997 | A |
| 5644723 | Deaton et al. | Jul 1997 | A |
| 5649114 | Deaton et al. | Jul 1997 | A |
| 5649115 | Schrader et al. | Jul 1997 | A |
| 5659469 | Deaton et al. | Aug 1997 | A |
| 5673322 | Pepe et al. | Sep 1997 | A |
| 5675662 | Deaton et al. | Oct 1997 | A |
| 5677952 | Blakeley, III et al. | Oct 1997 | A |
| 5687322 | Deaton et al. | Nov 1997 | A |
| 5689100 | Carrithers et al. | Nov 1997 | A |
| 5708782 | Larson et al. | Jan 1998 | A |
| 5710886 | Christensen et al. | Jan 1998 | A |
| 5715399 | Bezoz | Feb 1998 | A |
| 5729693 | Holda-Fleck | Mar 1998 | A |
| 5734838 | Robinson et al. | Mar 1998 | A |
| 5742845 | Wagner | Apr 1998 | A |
| 5749075 | Toader et al. | May 1998 | A |
| 5761648 | Golden et al. | Jun 1998 | A |
| 5765141 | Spector | Jun 1998 | A |
| 5774868 | Cragun et al. | Jun 1998 | A |
| 5774869 | Toader | Jun 1998 | A |
| 5774870 | Storey | Jun 1998 | A |
| 5794230 | Horadan et al. | Aug 1998 | A |
| 5802275 | Blonder | Sep 1998 | A |
| 5806043 | Toader | Sep 1998 | A |
| 5806044 | Powell | Sep 1998 | A |
| 5806045 | Biorge et al. | Sep 1998 | A |
| 5814796 | Benson et al. | Sep 1998 | A |
| 5816918 | Kelly et al. | Oct 1998 | A |
| 5822230 | Kikinis et al. | Oct 1998 | A |
| 5832457 | O'Brien et al. | Nov 1998 | A |
| 5832458 | Jones | Nov 1998 | A |
| 5834748 | Litman | Nov 1998 | A |
| 5839117 | Cameron et al. | Nov 1998 | A |
| 5844230 | Lalonde | Dec 1998 | A |
| 5845259 | West et al. | Dec 1998 | A |
| 5848399 | Burke | Dec 1998 | A |
| 5855007 | Jovicic et al. | Dec 1998 | A |
| 5857175 | Day et al. | Jan 1999 | A |
| 5864822 | Baker, III | Jan 1999 | A |
| RE36116 | McCarthy | Feb 1999 | E |
| 5870722 | Albert et al. | Feb 1999 | A |
| 5884277 | Khosla | Mar 1999 | A |
| 5892827 | Beach et al. | Apr 1999 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5892905 | Brandt et al. | Apr 1999 | A |
| 5898838 | Wagner | Apr 1999 | A |
| 5903874 | Leonard et al. | May 1999 | A |
| 5903880 | Biffar | May 1999 | A |
| 5905246 | Fajkowski | May 1999 | A |
| 5905908 | Wagner | May 1999 | A |
| 5907830 | Engel et al. | May 1999 | A |
| 5907831 | Lotvin et al. | May 1999 | A |
| 5909023 | Ono et al. | Jun 1999 | A |
| 5913210 | Call | Jun 1999 | A |
| 5915007 | Klapka | Jun 1999 | A |
| 5915019 | Ginter et al. | Jun 1999 | A |
| 5915243 | Smolen | Jun 1999 | A |
| 5915244 | Jack et al. | Jun 1999 | A |
| 5918211 | Sloane | Jun 1999 | A |
| 5918213 | Bernard et al. | Jun 1999 | A |
| 5918214 | Perkowski | Jun 1999 | A |
| 5920847 | Kolling et al. | Jul 1999 | A |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5933811 | Angles et al. | Aug 1999 | A |
| 5937391 | Ikeda et al. | Aug 1999 | A |
| 5937394 | Wong et al. | Aug 1999 | A |
| 5938727 | Ikeda | Aug 1999 | A |
| 5940506 | Chang et al. | Aug 1999 | A |
| 5950173 | Perkowski | Sep 1999 | A |
| 5952638 | Demers et al. | Sep 1999 | A |
| 5953005 | Liu | Sep 1999 | A |
| 5956695 | Carrithers et al. | Sep 1999 | A |
| 5956700 | Landry | Sep 1999 | A |
| 5964830 | Durrett | Oct 1999 | A |
| 5970469 | Scroggie et al. | Oct 1999 | A |
| 5971277 | Cragun et al. | Oct 1999 | A |
| 5974398 | Hanson et al. | Oct 1999 | A |
| 5978777 | Garnier | Nov 1999 | A |
| 5979757 | Tracy et al. | Nov 1999 | A |
| 5982520 | Weiser et al. | Nov 1999 | A |
| 5983196 | Wendkos | Nov 1999 | A |
| 5983205 | Brams | Nov 1999 | A |
| 5984191 | Chapin, Jr. | Nov 1999 | A |
| 5988500 | Litman | Nov 1999 | A |
| 5991376 | Hennessy et al. | Nov 1999 | A |
| 5991736 | Ferguson et al. | Nov 1999 | A |
| 5992738 | Matsumoto et al. | Nov 1999 | A |
| 5992752 | Wilz, Sr. et al. | Nov 1999 | A |
| 5995942 | Smith et al. | Nov 1999 | A |
| 5999914 | Blinn et al. | Dec 1999 | A |
| 6000608 | Dorf | Dec 1999 | A |
| 6002771 | Nielsen | Dec 1999 | A |
| 6003013 | Boushy et al. | Dec 1999 | A |
| 6007426 | Kelly et al. | Dec 1999 | A |
| 6009411 | Kepecs | Dec 1999 | A |
| 6009412 | Storey | Dec 1999 | A |
| 6012038 | Powell | Jan 2000 | A |
| 6012039 | Hoffman et al. | Jan 2000 | A |
| 6012051 | Sammon, Jr. et al. | Jan 2000 | A |
| 6012636 | Smith | Jan 2000 | A |
| 6014634 | Scroggie et al. | Jan 2000 | A |
| 6014635 | Harris et al. | Jan 2000 | A |
| 6015344 | Kelly et al. | Jan 2000 | A |
| 6016476 | Maes et al. | Jan 2000 | A |
| 6018695 | Ahrens et al. | Jan 2000 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6018724 | Arent | Jan 2000 | A |
| 6021399 | Demers et al. | Feb 2000 | A |
| 6024640 | Walker et al. | Feb 2000 | A |
| 6026370 | Jermyn | Feb 2000 | A |
| 6026375 | Hall et al. | Feb 2000 | A |
| 6026377 | Burke | Feb 2000 | A |
| 6032133 | Hilt et al. | Feb 2000 | A |
| 6032136 | Brake, Jr. et al. | Feb 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6035281 | Crosskey et al. | Mar 2000 | A |
| 6038321 | Torigai et al. | Mar 2000 | A |
| 6039244 | Finsterwald | Mar 2000 | A |
| 6041308 | Walker et al. | Mar 2000 | A |
| 6041309 | Laor | Mar 2000 | A |
| 6044360 | Piccialio | Mar 2000 | A |
| 6047269 | Biffar | Apr 2000 | A |
| 6049778 | Walker et al. | Apr 2000 | A |
| 6049779 | Berkson | Apr 2000 | A |
| 6055573 | Gardenswartz et al. | Apr 2000 | A |
| 6058371 | Dijan | May 2000 | A |
| 6058482 | Liu | May 2000 | A |
| 6061660 | Eggleston et al. | May 2000 | A |
| 6064979 | Perkowski | May 2000 | A |
| 6065120 | Laursen et al. | May 2000 | A |
| 6072468 | Hocker et al. | Jun 2000 | A |
| 6073840 | Marion | Jun 2000 | A |
| 6075863 | Krishnan et al. | Jun 2000 | A |
| 6076101 | Kamakura et al. | Jun 2000 | A |
| 6078898 | Davis et al. | Jun 2000 | A |
| 6081900 | Subramaniam et al. | Jun 2000 | A |
| 6088730 | Kato et al. | Jul 2000 | A |
| 6092069 | Johnson et al. | Jul 2000 | A |
| 6092201 | Turnbull et al. | Jul 2000 | A |
| 6094486 | Marchant | Jul 2000 | A |
| 6101483 | Petrovich et al. | Aug 2000 | A |
| 6101484 | Halbert et al. | Aug 2000 | A |
| 6101485 | Fortenberry et al. | Aug 2000 | A |
| 6105001 | Masi et al. | Aug 2000 | A |
| 6105865 | Hardesty | Aug 2000 | A |
| 6115737 | Ely et al. | Sep 2000 | A |
| 6119230 | Carter | Sep 2000 | A |
| 6128599 | Walker et al. | Oct 2000 | A |
| 6128603 | Dent et al. | Oct 2000 | A |
| 6129274 | Suzuki | Oct 2000 | A |
| 6131810 | Weiss et al. | Oct 2000 | A |
| 6134318 | O'Neil | Oct 2000 | A |
| 6134548 | Gottsman et al. | Oct 2000 | A |
| 6138911 | Fredregill et al. | Oct 2000 | A |
| 6141161 | Sato et al. | Oct 2000 | A |
| 6145739 | Bertina et al. | Nov 2000 | A |
| 6148405 | Liao et al. | Nov 2000 | A |
| 6154214 | Uyehara et al. | Nov 2000 | A |
| 6161096 | Bell | Dec 2000 | A |
| 6164533 | Barton | Dec 2000 | A |
| 6173267 | Cairns | Jan 2001 | B1 |
| 6178407 | Lotvin et al. | Jan 2001 | B1 |
| 6178408 | Copple et al. | Jan 2001 | B1 |
| 6182894 | Hackett et al. | Feb 2001 | B1 |
| 6185541 | Scroggie et al. | Feb 2001 | B1 |
| 6189103 | Nevarez et al. | Feb 2001 | B1 |
| 6195677 | Utsumi | Feb 2001 | B1 |
| 6196458 | Walker et al. | Mar 2001 | B1 |
| 6199099 | Gershman et al. | Mar 2001 | B1 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6222914 | McMullin | Apr 2001 | B1 |
| 6236978 | Tuzhilin | May 2001 | B1 |
| 6243688 | Kalina | Jun 2001 | B1 |
| 6249772 | Walker et al. | Jun 2001 | B1 |
| 6249773 | Allard et al. | Jun 2001 | B1 |
| 6251017 | Leason et al. | Jun 2001 | B1 |
| 6267672 | Vance | Jul 2001 | B1 |
| 6289322 | Kitchen et al. | Sep 2001 | B1 |
| 6292786 | Deaton et al. | Sep 2001 | B1 |
| 6298335 | Bernstein | Oct 2001 | B1 |
| 6332126 | Pierce et al. | Dec 2001 | B1 |
| 6332157 | Mighdoli et al. | Dec 2001 | B1 |
| 6334111 | Carrott | Dec 2001 | B1 |
| 6336098 | Fortenberry et al. | Jan 2002 | B1 |
| 6363362 | Burfield et al. | Mar 2002 | B1 |
| 6386444 | Sullivan | May 2002 | B1 |
| 6402029 | Gangi | Jun 2002 | B1 |
| 6408284 | Hilt et al. | Jun 2002 | B1 |
| 6438527 | Powar | Aug 2002 | B1 |
| 6450407 | Freeman et al. | Sep 2002 | B1 |
| 6452498 | Stewart | Sep 2002 | B2 |
| 6484147 | Brizendine et al. | Nov 2002 | B1 |
| 6484940 | Dilday et al. | Nov 2002 | B1 |
| 6486768 | French et al. | Nov 2002 | B1 |
| 6510998 | Stanford et al. | Jan 2003 | B1 |
| 6522889 | Aarnio | Feb 2003 | B1 |
| 6532448 | Higginson et al. | Mar 2003 | B1 |
| 6578015 | Haseltine et al. | Jun 2003 | B1 |
| 6594640 | Postrel | Jul 2003 | B1 |
| 6609150 | Lee et al. | Aug 2003 | B2 |
| 6631358 | Ogilvie | Oct 2003 | B1 |
| 6631849 | Blossom | Oct 2003 | B2 |
| 6687679 | Van Luchene et al. | Feb 2004 | B1 |
| 6721743 | Sakakibara | Apr 2004 | B1 |
| 6748365 | Quinlan et al. | Jun 2004 | B1 |
| 6820061 | Postrel | Nov 2004 | B2 |
| 6826594 | Pettersen | Nov 2004 | B1 |
| 6829586 | Postrel | Dec 2004 | B2 |
| 6842739 | Postrel | Jan 2005 | B2 |
| 6856976 | Bible et al. | Feb 2005 | B2 |
| 6898570 | Tedesco et al. | May 2005 | B1 |
| 6931538 | Sawaguchi | Aug 2005 | B1 |
| 6947898 | Postrel | Sep 2005 | B2 |
| 6985876 | Lee | Jan 2006 | B1 |
| 7025674 | Adams et al. | Apr 2006 | B2 |
| 7043752 | Royer et al. | May 2006 | B2 |
| 7096190 | Postrel | Aug 2006 | B2 |
| 7127414 | Awadallah et al. | Oct 2006 | B1 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7249197 | Roestenburg et al. | Jul 2007 | B1 |
| 7289970 | Siegel | Oct 2007 | B1 |
| 7290061 | Lentini et al. | Oct 2007 | B2 |
| 7321901 | Blinn et al. | Jan 2008 | B1 |
| 7349867 | Rollins et al. | Mar 2008 | B2 |
| 20010032137 | Bennett et al. | Oct 2001 | A1 |
| 20010032182 | Kumar et al. | Oct 2001 | A1 |
| 20010032183 | Landry | Oct 2001 | A1 |
| 20010034653 | Yamamoto | Oct 2001 | A1 |
| 20010034720 | Armes | Oct 2001 | A1 |
| 20010037295 | Olsen | Nov 2001 | A1 |
| 20010047342 | Cuervo | Nov 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020013728 | Wilkman | Jan 2002 | A1 |
| 20020016734 | McGill et al. | Feb 2002 | A1 |
| 20020026348 | Fowler et al. | Feb 2002 | A1 |
| 20020046110 | Gallagher | Apr 2002 | A1 |
| 20020049631 | Williams | Apr 2002 | A1 |
| 20020052940 | Myers et al. | May 2002 | A1 |
| 20020055874 | Cohen | May 2002 | A1 |
| 20020056044 | Andersson | May 2002 | A1 |
| 20020062253 | Dosh, Jr. et al. | May 2002 | A1 |
| 20020069109 | Wendkos | Jun 2002 | A1 |
| 20020069150 | Ni | Jun 2002 | A1 |
| 20020075844 | Hagen | Jun 2002 | A1 |
| 20020077890 | LaPointe et al. | Jun 2002 | A1 |
| 20020077978 | OLeary et al. | Jun 2002 | A1 |
| 20020082918 | Warwick | Jun 2002 | A1 |
| 20020082920 | Austin et al. | Jun 2002 | A1 |
| 20020082990 | Jones | Jun 2002 | A1 |
| 20020087468 | Ganesan et al. | Jul 2002 | A1 |
| 20020091593 | Fowler | Jul 2002 | A1 |
| 20020095365 | Slavin et al. | Jul 2002 | A1 |
| 20020107733 | Liu et al. | Aug 2002 | A1 |
| 20020111919 | Weller et al. | Aug 2002 | A1 |
| 20020120513 | Webb et al. | Aug 2002 | A1 |
| 20020123949 | VanLeeuwen | Sep 2002 | A1 |
| 20020143614 | MacLean et al. | Oct 2002 | A1 |
| 20020146018 | Kailamaki et al. | Oct 2002 | A1 |
| 20020152116 | Yan et al. | Oct 2002 | A1 |
| 20020161630 | Kern et al. | Oct 2002 | A1 |
| 20020194069 | Thakur et al. | Dec 2002 | A1 |
| 20030004802 | Callegari | Jan 2003 | A1 |
| 20030004808 | Elhaoussine et al. | Jan 2003 | A1 |
| 20030009379 | Narasimhan et al. | Jan 2003 | A1 |
| 20030013438 | Darby | Jan 2003 | A1 |
| 20030036425 | Kaminkow et al. | Feb 2003 | A1 |
| 20030040964 | Lacek | Feb 2003 | A1 |
| 20030055722 | Perreault et al. | Mar 2003 | A1 |
| 20030061097 | Walker et al. | Mar 2003 | A1 |
| 20030069787 | Tendon et al. | Apr 2003 | A1 |
| 20030069842 | Kight et al. | Apr 2003 | A1 |
| 20030074311 | Saylors et al. | Apr 2003 | A1 |
| 20030087650 | Aarnio | May 2003 | A1 |
| 20030101131 | Warren et al. | May 2003 | A1 |
| 20030115456 | Kapoor | Jun 2003 | A1 |
| 20030130948 | Algiene et al. | Jul 2003 | A1 |
| 20030163425 | Cannon, Jr. | Aug 2003 | A1 |
| 20030187762 | Coyle | Oct 2003 | A1 |
| 20030200142 | Hicks et al. | Oct 2003 | A1 |
| 20030200144 | Antonucci et al. | Oct 2003 | A1 |
| 20030208445 | Compiano | Nov 2003 | A1 |
| 20030216960 | Postrel | Nov 2003 | A1 |
| 20030216967 | Williams | Nov 2003 | A1 |
| 20030229584 | Brown | Dec 2003 | A1 |
| 20040015438 | Compiano et al. | Jan 2004 | A1 |
| 20040019522 | Bortolin et al. | Jan 2004 | A1 |
| 20040019560 | Evans et al. | Jan 2004 | A1 |
| 20040035923 | Kahr | Feb 2004 | A1 |
| 20040039644 | Postrel | Feb 2004 | A1 |
| 20040039692 | Shields et al. | Feb 2004 | A1 |
| 20040049439 | Johnston et al. | Mar 2004 | A1 |
| 20040068438 | Mitchell et al. | Apr 2004 | A1 |
| 20040078273 | Loeb et al. | Apr 2004 | A1 |
| 20040097287 | Postrel | May 2004 | A1 |
| 20040098317 | Postrel | May 2004 | A1 |
| 20040107140 | Postrel | Jun 2004 | A1 |
| 20040128197 | Bam et al. | Jul 2004 | A1 |
| 20040215505 | Sullivan | Oct 2004 | A1 |
| 20040220854 | Postrel | Nov 2004 | A1 |
| 20040262381 | Mesaros | Dec 2004 | A1 |
| 20050021399 | Postrel | Jan 2005 | A1 |
| 20050021400 | Postrel | Jan 2005 | A1 |
| 20050021401 | Postrel | Jan 2005 | A1 |
| 20050021457 | Johnson et al. | Jan 2005 | A1 |
| 20050060225 | Postrel | Mar 2005 | A1 |
| 20050080727 | Postrel | Apr 2005 | A1 |
| 20050149394 | Postrel | Jul 2005 | A1 |
| 20050240472 | Postrel | Oct 2005 | A1 |
| 20060004629 | Neemann et al. | Jan 2006 | A1 |
| 20060020511 | Postrel | Jan 2006 | A1 |
| 20070239523 | Yi | Oct 2007 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 308 224 | Mar 1989 | EP |
| 0308224 | Mar 1989 | EP |
| 8235276 | Sep 1996 | JP |
| 2003132224 | May 2003 | JP |
| WO9923176 | May 1999 | WO |
| WO9926176 | May 1999 | WO |
| WO9930256 | Jun 1999 | WO |
| WO9952051 | Oct 1999 | WO |
| WO9960503 | Nov 1999 | WO |
| WO0014665 | Mar 2000 | WO |
| WO0033159 | Jun 2000 | WO |
| WO0033222 | Jun 2000 | WO |
| WO0101282 | Jan 2001 | WO |
| WO0152078 | Jul 2001 | WO |
| Entry |
|---|
| Fallon: “UK Retailers' Loyal Customer ‘Card Wars’ Prove Costly (Most major retailers in the UK have grown their sales over the past 2 years by launching loyalty-card programs)”; Supermarket News, May 5, 1997; vol. 47, No. 18, p. 57. |
| Dialog file 9, #001824832 “UK Retailers loyal Customers' card Wars' Prove Costly” Supermarket News, V47, N18, p. 57+, May 5, 1997. |
| Visa International, New Technologies [online]. 2000 [retrieved on Jun. 19, 2008]. Retrieved from Internet: <URL:http://web.archive.org/web/20000605185829/visa.com/nt/chip/main.html>. |
| WAP WTLS: Wireless Application Protocol Wireless Transport Layer Security Specification, Wireless Applications Forum, Limited, Apr. 30, 1998. [Retrieved on Jan. 19, 2009]. Retrieved from the Internet <Oct. 7, 2008>. |
| Non-Final Office Action mailed Sep. 10, 2008 in U.S. Appl. No. 10/708,570. |
| Non-Final Office Action mailed Sep. 9, 2008 in U.S. Appl. No. 10/708,568. |
| Non-Final Office Action mailed Nov. 29, 2004 in U.S. Appl. No. 09/834,478. |
| Final Office Action mailed May 11, 2005 in U.S. Appl. No. 09/834,478. |
| Advisory Action mailed Jan. 9, 2006 in U.S. Appl. No. 09/834,478. |
| Non-Final Office Action mailed May 9, 2006 in U.S. Appl. No. 09/834,478. |
| Final Rejection mailed Dec. 28, 2006 in U.S. Appl. No. 09/834,478. |
| Advisory Action mailed Mar. 2, 2007 in U.S. Appl. No. 09/834,478. |
| Non-Final Office Action mailed May 10, 2007 in U.S. Appl. No. 09/834,478. |
| Final Office Action mailed Nov. 7, 2007 in U.S. Appl. No. 09/834,478. |
| Advisory Action mailed Feb. 25, 2008 in U.S. Appl. No. 09/834,478. |
| Non-Final Office Action mailed Jun. 2, 2008 in U.S. Appl. No. 09/834,478. |
| Final Office Action mailed Dec. 29, 2008 in U.S. Appl. No. 09/834,478. |
| Notice of Allowance mailed Feb. 5, 2008 in U.S. Appl. No. 09/836,213. |
| Notice of Allowance mailed Jun. 17, 2008 in U.S. Appl. No. 11/619,512. |
| Notice of Allowance mailed Oct. 22, 2008 in U.S. Appl. No. 11/619,523. |
| Requirement for Restriction mailed Dec. 8, 2008 in U.S. Appl. No. 11/276,800. |
| Non-Final Office Action mailed Dec. 31, 2008 in U.S. Appl. No. 11/276,800. |
| Non-Final Office Action mailed Aug. 8, 2007 in U.S. Appl. No. 11/695,911. |
| Final Office Action mailed Jan. 24, 2008 in U.S. Appl. No. 11/695,911. |
| Advisory Action mailed Mar. 27, 2008 in U.S. Appl. No. 11/695,911. |
| Non-Final Office Action mailed Jul. 15, 2008 in U.S. Appl. No. 11/695,911. |
| Final Office Action mailed Jan. 28, 2009 in U.S. Appl. No. 11/695,911. |
| Requirement for Restriction mailed Sep. 25, 2006 in U.S. Appl. No. 10/027,984. |
| Non-Final Office Action mailed Jan. 30, 2007 in U.S. Appl. No. 10/027,984. |
| Final Office Action mailed Aug. 9, 2007 in U.S. Appl. No. 10/027,984. |
| Non-Final Office Action mailed Apr. 3, 2008 in U.S. Appl. No. 10/027,984. |
| Non-Final Office Action mailed Oct. 17, 2008 in U.S. Appl. No. 10/027,984. |
| Notice of Allowance mailed Feb. 5, 2008 in U.S. Appl. No. 10/010,947. |
| Non-Final Office Action mailed Jun. 27, 2008 in U.S. Appl. No. 11/458,019. |
| Final Office Action mailed Jan. 7, 2009 in U.S. Appl. No. 11/458,019. |
| Non-Final Office Action mailed Jun. 20, 2007 in U.S. Appl. No. 10/304,251. |
| Final Office Action mailed Nov. 15, 2007 in U.S. Appl. No. 10/304,251. |
| Advisory Action mailed Mar. 17, 2008 in U.S. Appl. No. 10/304,251. |
| Non-Final Office Action mailed Jun. 13, 2008 in U.S. Appl. No. 10/304,251. |
| Final Office Action mailed Dec. 4, 2008 in U.S. Appl. No. 10/304,251. |
| Notice of Allowance mailed Aug. 22, 2008 in U.S. Appl. No. 10/378,456. |
| Non-Final Office Action mailed Aug. 18, 2008 in U.S. Appl. No. 11/548,203. |
| ISR and Written Opinion mailed Jan. 10, 2002 in PCT/US01/012219. |
| ISR and Written Opinion mailed Oct. 2, 2002 in PCT/US02/008408. |
| Notice of Allowance mailed Apr. 5, 2007 in U.S. Appl. No. 10/084,744. |
| ISR and Written Opinion mailed Jan. 12, 2005 in PCT/US04/04457. |
| ISR and Written Opinion mailed Mar. 23, 2000 in PCT/US05/30792. |
| ISR and Written Opinion mailed Jul. 16, 2008 in PCT/US07/78253. |
| Dialog reference. File 9 # 01824832 UK Retailers Loyal customers ‘Card Wars’ Prove costly Supermarket News, V 47, n 18 p. 57+. |
| Fallon: UK Retailers' Loyal Customer ‘Card Wars’ Prove Costly (Most major retailers in the UK have grown their sales over the past 2 years by launching loyalty-card programs); Supermarket News May 5, 1997; vol. 47, No. 18, p. 57. |
| USPTO; Office Action dated Aug. 18, 2010 in U.S. Appl. No. 11/742,934. |
| USPTO; Final Office Action dated Oct. 29, 2010 in U.S. Appl. No. 11/742,934. |
| USPTO; Notice of Allowance dated Nov. 17, 2010 in U.S. Appl. No. 11/742,934. |
| USPTO; All Office Actions (Non-Final, Final, Advisory Actions, Restrictions/Elections, etc.), Notices of Allowance, 892s, 1449s and SB/08As from U.S. Appl. Nos. 09/836,213; U.S. Appl. No. 10/708,568; U.S. Appl. No. 10/708,570; U.S. Appl. No. 11/864,241; U.S. Appl. No. 12/609,384; U.S. Appl. No. 10/010,947; U.S. Appl. No. 10/027,984; U.S. Appl. No. 11/619,523; U.S. Appl. No. 11/619,512; U.S. Appl. No. 10/304,251; U.S. Appl. No. 10/710,779; U.S. Appl. No. 11/161,906; U.S. Appl. No. 11/458,019; U.S. Appl. No. 12/851,470; U.S. Appl. No. 12/852,074; U.S. Appl. No. 12/852, 122; U.S. Appl. No. 12/852,141; U.S. Appl. No. 12/852,224; U.S. Appl. No. 12/852,246; U.S. Appl. No. 12/852,272; U.S. Appl. No. 12/909,709; U.S. Appl. No. 10/378,458; U.S. Appl. No. 10/907,882; U.S. Appl. No. 11/276,800; U.S. Appl. No. 11/695,911; U.S. Appl. No. 11/742,934; U.S. Appl. No. 11/752,675; U.S. Appl. No. 11/752,685; U.S. Appl. No. 11/382638; U.S. Appl. No. 12/270,198; U.S. Appl. No. 12/332,248; U.S. Appl. No. 12/354,324; and U.S. Appl. No. 12/541,330. |
| Number | Date | Country | |
|---|---|---|---|
| 20110078011 A1 | Mar 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60279817 | Mar 2001 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11742934 | May 2007 | US |
| Child | 12955773 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09836213 | Apr 2001 | US |
| Child | 11742934 | US |
