System and apparatus for dispensing coupons having selectively printed borders around preferred products5926795Abstract Apparatus and a corresponding method for creating a coupon or other like incentive in response to a transaction. A record pertaining to the details of the transaction is examined to determine whether the transaction is intended to trigger the creation of a coupon or other like incentive having a border. The non-existence of a certain detail of the transaction examined will result in creation of a coupon or other like incentive having a border. Also, the existence of a certain detail of the transaction examined will result in the creation of a coupon or other like incentive having a border. Transactions that do not trigger the creation of a coupon or other like incentive having a border may result in creation of coupons or other like incentives not having borders or in creation of a transaction receipt not having a border. Claims What is claimed as new and desired to be secured by letters patent of the United States is: Description BACKGROUND OF THE INVENTION
______________________________________
F1 (hexadecimal)
coupon creation
F2 redemption,
F3 store support procedure
entry
The flags field has the following meanings
30 (hexadecimal)
free coupon,
40 no-sale redemption,
20 continuity linked (if creation), or
coupon value entered manually (if redemption),
10 voided redemption,
OF reason code.
______________________________________
The low four bits of the flag field are used to record a reason for non-printing or misredemption of a coupon. The various reasons can, for instance, be as follows, where the four-digit value represents the binary state of the field.
______________________________________
A Coupon printing:
0000 printed,
1000 print inhibited store-wide
1001 print inhibited at this lane,
1010 print inhibited for this CLU#,
1011 print inhibited for this item,
0100 unable to access coupon index record,
0101 unable to access coupon deal record,
0010 transaction below threshold,
0001 duplicate CLU#,
1100 printing disabled by operator.
B. Misredemption:
0000 normal redemption,
0001 item not in order,
0010 expiration date exceeded
0100 match only in manufacturer number,
1000 accepted (validation disabled).
______________________________________
The date/time of the transaction are recorded in the form MMDDHH, where MM is the month, DD the day of the month, and HH the hour of the day. The CPN# field is used to record the entire set of data read from a printed coupon, and the UPC# field records (1) the triggering product code in the case of coupon creations and (2) the purchased product code in the case of redemptions. Hardware and Software Overview The hardware used in this invention is conventional for point-of-sale systems. Various manufacturers supply point-of-sale equipment, and the invention is not limited to any particular configuration. By way of example, the invention is presently implemented using the International Business Machines Corporation (IBM) 4690 Store Program. The store controller 10 is an IBM 4690, and the terminals 12 are IBM 4693 terminals. The IBM 4693 terminal incorporates a customer receipt station which can be used to print the aforesaid coupon or incentive designs and receipts. IBM supplies a software operating system for use in controlling operations in the hardware described. The operating system is referred to as the IBM 4690 Store System. The IBM 4690 Store System is a general purpose machine which can be used in many retail environments. In this particular environment the IBM 4690 Store System operates according to a specific software application, namely, the IBM 4690 Supermarket Application. Communication between the terminals and the store controller is accomplished using a number of communication protocols such as ethernet, token ring or store loop. All of these aspects of the invention hardware and software are well known and well defined in trade literature and IBM technical literature. For further information, a useful starting point is the publication "IBM 4690 Store System Programming Guide," (SC30-3517-04) published by IBM, Dept. E35, P.O. Box 12195, Research Triangle Park, N.C. 27709. The printer hardware used in this invention can be any conventional printer capable of thermally activating heat sensitive paper. The thermally capable printer 24 includes a fixed segmented printing head which contains individual heating segments. The fixed segmented printing head spans the width of the paper. Each heating segment can be independently heated so as to be able to heat activate the chemicals or dyes present in the paper. Data from the coupon deal record is used to format the fixed segmented printing head of the thermally capable printer. Heating segments of the fixed segmented printing head of the thermally capable printer 24 located in a central region of the printing head print the details of the particular coupon or incentive deal from the coupon deal record 42. Heating segments located near the outer edges of the fixed segmented printing head print the border of the coupon. Such printer hardware is manufactured, for instance, by IBM model number 4116 thermal printer. The paper which is used to create the coupon contains a thermally activated dye or chemical which, when subjected to the heat of the thermal printer, changes the color of the paper from the original, base color of the paper. In such a case the details of the coupon and the color of the border are the same color. Typically, such paper is embedded with one chemical to produce one color upon activation. Using such paper the coupon 94 can have a border 95 as shown in FIG. 5a. Depending on the formatting of the printer the coupon 94 can have a border 106 as shown in FIG. 5b. The coupon 94 as shown in FIG. 5b can only be created when a single chemical or dye is embedded in the paper, since the border encompasses the text of the coupon and is thus activated by the same chemical dye. Incentives 97 printed according to the method are shown in FIGS. 7a and 7b having borders 107, 108, respectively. A different chemical or dye can be impregnated in the border region of the paper so that the resulting coupon has a border of one color and the details of the coupon are of another color. The color of the border may be any color. Typically, the color of the activated dye or chemical producing the details of the coupon is the color black, and the color of the activated dye or chemical producing the border is the color red. Use of such paper results in coupons 94 as shown in FIG. 5a and incentives 97 as shown in FIG. 7a. Such paper is manufactured, for instance, by Ludlow Technical and designated CMC II thermal roll. Conventional software is used to control the printer. Coupon Creation The coupon creation functions performed by the terminals 12 and the controller 10 are shown in FIGS. 3, 4a and 4b. FIG. 3 illustrates a "general wait state" of the terminal, wherein the terminal software cyclically checks to determine whether any processing is required. Once processing is initiated to a certain stage, a return is made to the general wait state, as will be further explained below. However, the printing of coupons may precede the printing of the receipt, or the printing of the receipt may precede the printing of the coupons. Coupon creation as described below is of a preferred embodiment, but the invention in not limited to such an embodiment. The first illustrated block of the general wait state poses the question whether there is any input data to process, as indicated at 50. The input data typically takes the form of bar code scanner input, but may also include keyboard input from the terminal operator. If there is input data to process, the terminal departs from the general wait state and enters an input program sequence, as indicated at 51. If there is currently no input data to process, the next test, posed in block 52, is whether a requested response has been received from the controller 10. As will be described below, each of the terminals 12 frequently makes requests to the controller 10 for file access. The requesting program returns control to the general wait state, to await arrival of the response. If a response has been received, control is transferred to a response return point, as indicated at 53. The response return point sequentially follows the point in the program from which the file access request was made to the controller. If no response has been received from the controller 10, the next question posed in the general wait state is whether a preselected time-out is complete, as indicated at 54. As will be described, a time-out is initiated after each coupon printing request, to ensure that the coupon printing function does not totally occupy the time of the terminal printer. In the equipment presently employed to implement the invention, coupons are printed at a separate station of the printer, but employing a print head shared by other print stations. In this manner, separate printed documents can be generated at the separate stations, but the single print head behaves in effect like a single printer. Printing of too many coupons can preclude or limit printing of a customer receipt. When the time-out is completed, return is made to the program that initiated the time-out, as indicated at 55. If the time-out is not yet complete, control is transferred back to the beginning of the general wait state loop. In the input processing steps, shown in FIG. 4a, only the purchase and coupon creation functions are shown. If the input involves coupon redemption, as determined in block 58, control is transferred to the redemption processing functions (not shown). Otherwise, the first step of input processing is to obtain the product code input to the terminal, as indicated in block 60. Then a request is made to the controller 10 for the item record corresponding to the input product code. The request for this record, indicated at 61, is one of a number of such requests made to the controller during the input process. In each case, after the request is transmitted to the controller 10, a return is made to the general wait state shown in FIG. 3, to await the return of the response from the controller. When the response is received, the wait state loop of FIG. 3 transfers control back to the input sequence, at a point immediately following block 61. Next, as shown at 62, a print request is issued to initiate printing of a line on the customer receipt. The print request results in the storing of printable data in a print queue. One unction of the system software associated with the terminal is (1) to take printable information from the print queue on a first-in-first-out basis, and (2) to print it using the terminal printer. Up to this point in the input processing, the functions performed are conventional ones that take place regardless of whether any coupon creation is to occur. In the next step, shown at 63, a check is made to determine whether the trigger flag is set in the item record being processed. If the trigger flag is set, a request is made to the controller 10 for the corresponding coupon index record, as indicated at 64. If this is a normal triggering arrangement, as described in U.S. Pat. No. 4,723,212, the coupon look-up number or numbers (which is or are stored in the coupon index record) is or are placed as a coupon request in a coupon queue, as indicated at 65, together with the flags associated with each coupon look-up number in the coupon index record. If the item is one product in a multiple-trigger coupon deal, and if the item is not also the subject of a separate normal triggering arrangement, the step of storing a coupon request in the coupon queue will be bypassed. Regardless of whether this is a "normal" triggering product, a "negative" coupon trigger, or one of multiple triggers, the occurrence of the triggering product is saved in trigger item list for this transaction, for use at the end of the transaction in processing the negative and multiple triggers so that a coupon (either a coupon having a border or a coupon not having a border) will be printed. One of the flags associated with the coupon index record is, of course, the printing priority flag, and this determines the position in which the coupon request will be placed in the coupon queue. High priority coupons are entered behind any already queued high-priority coupons and ahead of any low-priority items, while low-priority items are entered at the bottom or end of the coupon queue. After entry of a coupon request in the coupon queue, return is made to the general wait state, as indicated at 66. If a product being processed has no coupon trigger flag, as determined in the block 63, there is still a possibility that a coupon should be printed during the current transaction. The store has the option of printing a default coupon having no border if no other coupons are printed in a transaction--usually also provided that a minimum purchase requirement is met. Also, negative and multiple-trigger coupons having borders have to be processed at the end of the transaction. First, a check is made, in the block 67, to determine whether the transaction has advanced to the point where the balance due has been registered on the terminal--i.e., where all items have been input and processed. If the balance-due point has not been reached, control is transferred to the block 66, to return to the general wait state. If the balance-due point has been reached, control is next transferred to a supplementary processing program 67.1 illustrated in FIG. 4c. This supplementary processing program, to be discussed below, handles negative coupons and multiple-trigger coupons. When the supplementary processing is complete, return is made to the block 68, which poses the question whether any coupons at all have been printed during the entire transaction. If not, a store default coupon having no border is stored in the coupon queue, as indicated at block 69, before a return is made to the general wait state. Input processing proceeds in the manner shown in FIG. 4a, with coupon requests being placed in the coupon queue as corresponding triggering items are detected in the transaction. The process by which coupon requests are removed from the coupon queue is shown in FIG. 4b. The supplementary processing of triggering items is shown functionally in FIG. 4c. First, as shown at block 70.1, access is obtained to a list of triggering items recorded for this particular transaction. Then the question is posed, as indicted in block 70.2, whether any negative coupon deal is in effect. If so, the list of triggering items is examined, in block 70.3, to determine whether any negative trigger item was not purchased during this particular transaction. The absence of a negative triggering item from the list results in the storing of a coupon request, in block 70.4. If no negative coupon deals are in effect, as determined in block 70.2, or if the terms of a negative trigger deal are not satisfied, as determined in block 70.3, or following the storing of a coupon request, in block 70.4, control is transferred to block 70.5, which determines whether there are any multiple-trigger deals in effect. If there are none, an exit is made from this processing program, as indicated at 70.6. If there is at least one multiple-trigger deal in effect, the terms of the deal are examined, as indicated in block 70.7, which is expanded in FIG. 4d. If the terms of the deal are satisfied, a coupon request is stored in the coupon queue, as shown in block 70.8, and control is transferred back to the block 70.5 to check for additional multiple-trigger coupon deals. If the terms of the multiple-trigger coupon deal are not satisfied, the block 70.8 is bypassed. It will be understood that there may be a number of multiple-trigger coupon deals in effect at the same time in a particular store. This will require multiple passes through the logic of FIG. 4c. In other words, exit from the processing program, at 70.6, is made only after returning to block 70.5 to determine whether any further multiple-trigger deals remain to be processed. In determining whether the terms of a multiple-trigger deal have been satisfied, it is first determined, in block 71.1 (FIG. 4d), whether a trade event deal is in effect. If so, the trigger item list for this transaction is scanned for compliance with the deal conditions. A trade event deal may involve the purchase of any predetermined number of items in a predefined trade group of products. If the terms of the trade event deal are satisfied, as indicated in block 71.3, the affirmative exit is taken from the processing program, as indicated at 71.4. If not, the negative exit from the program is taken, as indicated at 71.5. If no trade event deal is in effect, it is assumed that a simpler form of a multiple-trigger coupon is in effect. The trigger item list is scanned, in block 71.6, to accumulate a count of the number of trigger items purchased, or the total dollar amount purchased, as desired. If the requirements are met, as determined in block 71.7, the affirmative exit is taken (71.4). Otherwise, the negative exit (71.5) is taken. After completion of input processing, as described with reference to FIGS. 4a, 4c, and 4d, a return is always made to the general wait state, as indicated at 66 in FIG. 4a. Processing of the coupon queue proceeds in accordance with the flow chart of FIG. 4b. After a return from a time-out, from the general wait state, the coupon queue is first checked, as shown at 72, to determine whether there are any coupon requests waiting to be processed. If there are, the next question posed, in block 73, is whether the balance-due point has been reached in the transaction. If it has not, the only coupons eligible for printing are high priority coupons. This is determined in block 74. If there are no items in the coupon queue, or if there are only low-priority items and the balance-due point has not been reached, control is transferred to block 75, which selects a zero or near-zero time-out period. Then, in block 76, the time-out is initiated and a return is made to the general wait state. Control will very soon pass back again from the general wait state, to check the condition of the coupon queue once more. If the balance-due point has been reached, as determined in block 73, the next test, in block 77, is to determine whether the end of the transaction has been reached--that is, whether the terminal operator has received payment for the sale and has closed out the transaction in preparation for beginning a new one. If this has not occurred, control is passed to the next step, at block 78, to select the next unprocessed item in the coupon queue. If the end of the transaction has been reached, however, a log-only flag is set, in block 79, before passing to block 78. Control also passes to block 78 if a high priority coupon creation request is detected in block 74. At this point, a coupon creating candidate has been selected from the coupon queue, but it is still subject to a number of further tests before an actual print request is made to print the coupon. First, in block 80, a check is made to determine if the same coupon has already been printed in this transaction. Only one coupon of the same coupon look-up number is normally permitted for each transaction. Next, if there have been no previous coupons of the same kind, a check is made in block 81 to determine whether a minimum purchase threshold has been reached. For each coupon deal, there is an option to prevent printing of the coupon if a designated (storewide) total purchase minimum is not reached. If the answer obtained from block 81 is negative, control is transferred to block 75, to exit to the general wait state, but without removing the coupon request from the coupon queue. The next time the coupon is processed, the total purchase amount is again checked. If the coupon is never printed, because the threshold purchase amount is not reached by the end of the transaction, a log record is created for the coupon. In block 82, a check is made on the total count of coupons printed for this transaction. If the number exceeds a maximum set for this particular checkout terminal, no further printing of coupons is permitted. In addition, printing is not permitted if a print inhibit flag has been set, as determined in block 83. If printing is inhibited, or if the maximum coupon count is reached, or if the coupon has been printed already, then the log-only flag is set, as indicated in block 84, before advancing to the step shown in block 85, in which the complete coupon deal record, corresponding to the currently processed coupon queue entry, is requested from the controller 10. Next, if the log-only flag is not set, as determined in block 86, a determination is made, in block 86.1, whether the coupon deal calls for an instant redemption--i.e., the application of a discount without the printing of a coupon. If no instant redemption is called for, the coupon is formatted for printing, as indicated in block 87, using the information obtained from the coupon deal record. Then a print request is issued, as indicated in block 88, to place in the print queue the printable data that is to appear on the coupon. This data will include bar code data that will result in the printing of a coupon with pertinent information encoded in bar code form. If instant redemption is called for, as determined in block 86.1, a discount is applied directly to the customer's bill, as indicated in block 88.1, and blocks 87 and 88 are bypassed to avoid printing a coupon. The amount of the discount may depend on the number of trigger items (in multiple-trigger coupon deals) or on other factors predefined for the coupon deal. Data from the coupon deal record (such as the flag, as described earlier) is used to format the thermally capable printer 24 to print a border 95 around the preferred coupon 94 as shown in FIG. 5. Preferably, the border 95 of the coupon having a border 94 is colored red so as to catch the eye of the consumer. The flag of the coupon deal record activates the thermal capabilities of the thermally capable printer 24 so as to create the border 95 around the coupon. Other coupons printed by the thermally capable printer 24 do not have a border and appear as coupon 96, as shown in FIG. 6. The coupon 96 is printed due to the request made at block 69 of FIG. 4a. As such, the block 69 does not transmit the necessary formatting information to the thermally capable printer 24 so as to print a border around the coupon. The thermally capable printer 24 is able to print a border around the preferred coupon 94 because the printer paper contains a thermally activated dye or chemical border which changes color upon the selective application of heat to produce a border around the coupon 94 of preferred products. The next step, shown at block 89, is to prepare a log record of the coupon creation, or in the case of log-only situations, to create a log record of a coupon request that did not result in printing of a coupon. The log-only flag is checked again in block 90, after the logging step of block 89. If the log-only flag is set, control is transferred to block 75, to set a zero time-out and then to return to the general wait state. If the log-only flat is not set (i.e., coupon is to be printed), a short (e.g., six-second) delay or time-out is selected, in block 92, before returning to the general wait state through block 76. The time-out ensures that the printer will not be totally occupied with the coupon printing function, but will be free for the next period of time to print other material, such as portions of the customer receipt. An important aspect of coupon creation is that one of the fields printed on the coupon in bar code form is a trigger item sequence number, obtained from the coupon index record flags. This number identifies the triggering product or item, and it can be used to compile statistics relating the printed coupon to the items that triggered its printing. The other fields of data printed on the coupon in bar code form include the coupon value, the expiration date, the manufacturer's code, and the product family code to which the coupon deal applies. Printed on the coupon in human-readable form are the offer description and the advertising message, as well as some of the information also printed in bar code form. File Maintenance Maintenance of the controller files used in coupon creation and redemption is effected by means of a sequential maintenance file, which may be prepared at a site remote from the store, and then processed at the store controller to effect the desired changes in the files. The maintenance functions include (1) adding, deleting, or replacing coupon deal records and coupon index records, (2) enabling and disabling coupon triggering by item, (3) enabling and disabling coupon printing by item, (4) copying the coupon by file, and (5) retrieving the coupon counts. Other functions include (1) reorganizing the coupon-look-up file, (2) clearing the file before a reload, and (3) adding or replacing system configuration data. The latter function includes (1) enabling or disabling coupon creation by coupon deal, (2) enabling or disabling printing by store or checkout lane, (3) enabling or disabling coupon validation but continuing to log redemptions and misredemptions, (4) updating a per-transaction coupon maximum, by checkout lane, and (5) updating a transaction threshold. The format of the maintenance file can, for instance, be as follows:
______________________________________
Command 1 (one byte)
Data
. . .
Data
Data
End-of-data record
Command 2
Data
. . .
. . .
End-of-data record
. . .
. . .
End-of document record
______________________________________
Four commands do not require accompanying data. These are commands to reorganize the coupon look-up file, create a report log, report all coupon counts, and clear the coupon look-up file for a reload. The specific formats for effecting these maintenance commands is not critical to the present invention. Any desired programing approach may be employed to make changes to the controller files as desired. In another form of the invention, as shown in FIG. 10, the components consist of at least a single stand-alone transaction device 104. The transaction device 104 contains a thermally capable printer, a transaction reading device such as a bar type code reader and/or credit card reader, and associated files and controllers similar to the first embodiment so as to compare the details of a transaction to stored triggering values so as to command the thermally capable printer to print a coupon or other like incentive having a border or not having a border. As in the previous embodiment the coupon 94 can have a border as shown in FIGS. 5a and 5b and the incentive 97 can have borders as shown in FIGS. 7a and 7b. FIG. 6 shows a coupon 96 not having a border. FIG. 8 shows a coupon 98 having a border and a watermark. FIG. 9 shows a coupon 101 having multiple borders. The colored borders can be of any color, however, the colored border of the coupon as shown in FIG. 5b and the incentive as shown in FIG. 7b are limited to the same color as the text of the coupon or incentive, respectively. The transaction device 104 compares the details of the transaction to the stored triggering values. For example, a bordered coupon or like incentive can be printed in response to: a product purchased or not purchased, the dollar amount of the transaction, the number of products purchased, the form of payment (such as cash, a credit card, a debit card, or a frequent shopper card), and what the source of a credit card or a debit card is, etc. The thermally capable printer of the transaction device 104 also prints the receipt 105, which does not have a border. The printer paper, as in the previous embodiment, contains at least one thermally activated dye or chemical which changes color upon the selective application of heat to produce a border of at least one color around the coupon or other like incentive. The border can be any color. Multiple borders 102, 103 can be used as shown in FIG. 9. Additionally, a watermark 100 can be included with the border 99 on the coupon 98. Obviously, numerous modifications and variations of the present invention are possible in light of the above teachings. It is therefore to be understood that, within the scope of the appended claims, the invention may be practiced otherwise than as specifically described herein.
|
Same subclass Same class Consider this |
||||||||||
