JP7452126B2 - Label verification device, label verification method, program, and label issuing device - Google Patents

Description

The present disclosure relates to a verification device and the like.

At retail stores such as supermarkets and convenience stores, when a customer has purchased only a small number of items, or when plastic bags are not required, they can attach designated tapes or stickers to the purchased items and take them out of the store. It has been verified that the product has been accounted for. However, such tapes and stickers may be used fraudulently, such as by removing the tape or sticker from an item that has already been paid for and replacing it with another item that has not been paid for. Furthermore, if such tapes and stickers are prepared near self-checkout registers, fraud may occur, such as pasting them on items that have not yet been paid for, making it appear as though items that have not been paid for have already been paid for. There is a possibility that it will happen.

In order to solve the above-mentioned problem, Patent Document 1 discloses that a paid-for item is affixed with a paid-out sticker on which the date and time of purchase, the name of the product, and the name of the store of purchase are written on the purchased item.

Patent No. 6217121

In Patent Document 1, in order to confirm whether the checkout sticker has been properly affixed, the clerk has to read the characters printed on the label and confirm the purchase date and time, product name, and purchase store name. arise.

One of the objects of the present disclosure is to provide a label verification device, a label verification method, a program, and a label issuing device that can easily confirm the validity of a label indicating that a transaction has been completed.

The label matching device according to the present disclosure is configured to collect accounting information obtained from a label attached to a target product on which accounting information, which is information related to accounting for the product, is printed, and information regarding the validity of the label. It includes a collation means for collating certain collation target information and an output means for outputting the collation result.

A label issuing device according to the present disclosure includes a label issuing means for issuing a label that is attached to a target product and has accounting information printed thereon, which is information related to accounting for the product, and the accounting information is a label that is attached to a target product. The identifier of the product for which the transaction has been completed, which includes the identifier of the completed product and is included in the accounting information, is compared with the identifier of the target product indicated by the code acquired from the target product by a label matching device.

The label verification method according to the present disclosure uses accounting information obtained from a label attached to a target product on which accounting information, which is information related to accounting for the product, is printed, and information regarding the validity of the label. Matches against certain matching target information and outputs the matching result.

The program according to the present disclosure causes a computer to acquire accounting information obtained from a label attached to a target product on which accounting information, which is information related to accounting for the product, is printed, and information regarding the validity of the label. A matching process for matching the matching target information with the matching target information, and an output process for outputting the matching result are executed.

An effect of the present disclosure is that the validity of the label indicating that payment has been completed can be easily confirmed.

1 is a block diagram schematically illustrating the configuration of a product management system 1 according to a first embodiment. FIG. FIG. 2 is a block diagram illustrating the configuration of a POS device 200 according to a first embodiment. It is a figure showing an example of registered product data concerning a 1st embodiment. It is a figure showing an example of sales history data concerning a 1st embodiment. FIG. 1 is a block diagram illustrating the configuration of a label matching device 100 according to a first embodiment. FIG. 3 is a diagram showing an example of accounting information and verification target information according to the first embodiment. It is a flowchart showing product registration/accounting processing in the POS device 200 according to the first embodiment. It is a flowchart showing the verification process in the label verification device 100 according to the first embodiment. FIG. 3 is a diagram showing an example of a verification result screen according to the first embodiment. It is a figure which shows the example of the label pasting position instruction screen based on the modification of 1st Embodiment. FIG. 7 is a diagram illustrating an example of accounting information and verification target information according to a modification of the first embodiment. FIG. 7 is a diagram illustrating an example of accounting information and verification target information according to the second embodiment. FIG. 7 is a diagram illustrating an example of a verification result screen according to the second embodiment. FIG. 7 is a diagram illustrating an example of accounting information and verification target information according to a third embodiment. It is a block diagram illustrating the outline of composition of product management system 2 concerning a 4th embodiment. FIG. 11 is a block diagram illustrating the configuration of a label matching device 100A according to a fifth embodiment. It is a flowchart which shows the collation process in label collation device 100A concerning a 5th embodiment. It is a block diagram which illustrates the structure of 200 A of label issuing apparatuses based on 6th Embodiment. It is a flowchart which shows label issuing processing in label issuing device 200A concerning a 6th embodiment. 5 is a block diagram showing an example of the hardware configuration of a computer 500. FIG.

In this disclosure, it is assumed that a label, sticker, tape, or sticker serving as proof of purchase is affixed to each purchased product at the end of the transaction. These stickers, tapes, and stickers are collectively referred to as labels. Embodiments of the present disclosure will be described below with reference to the drawings.

[First embodiment]
[composition]
FIG. 1 is a block diagram schematically illustrating the configuration of a product management system 1 according to the first embodiment. The product management system 1 includes N POS (Point of Sales) systems 20 (N is an integer of 1 or more), a management server 400, a reader 110, and a label matching device 100. The POS system 20 and the management server 400 are connected by wire or wirelessly to enable data communication. The reader 110 and the label verification device 100 are also connected to enable data communication by wire or wirelessly. The POS system 20 and the management server 400 are installed in a store, for example. The reader 110 and the label matching device 100 are used, for example, by a store clerk inside the store or outside the store.

(POS system 20)
Each POS system 20 includes a POS device 200, a reader 210, a printer 220, and a display device 230. The POS device 200 registers products to be sold and performs accounting. The POS device 200 can be configured such that a customer registers and pays for the product, or a store clerk registers and pays for the product, or a store clerk registers the product and performs the checkout for the product when purchasing the product. It may be any of the items operated by the customer. The POS system 20 is an embodiment of the label issuing device of the present disclosure.

Reader 210 is used to register products to be sold. The reader 210 optically reads a code attached to a product (hereinafter also referred to as a product assignment code) and transmits a product identifier indicated by the product assignment code to the POS device 200. The product provision code may be a barcode or a two-dimensional code. It is preferable that the product assignment code is attached to the product in such a way that it cannot be easily removed, such as by being printed on the product itself or the packaging of the product when the product is shipped.

In the example of FIG. 1, a product allocation code is attached to a purchased product using a barcode.

The printer 220 prints and issues a label to be attached to the product when the checkout for the product is completed. The label may be affixed to the product by a customer or may be affixed to the product by a store employee. A code (hereinafter also referred to as a label assignment code) indicating accounting information, which is information regarding the completion of the transaction, is printed on the label. Accounting information will be described later. The labeling code may be a barcode or a two-dimensional code. Printer 220 receives data indicating a labeling code from POS device 200.

In the example of FIG. 1, the labeling code is printed as a two-dimensional code on the label attached to the purchased product.

The display device 230 displays various information related to product registration and accounting (for example, how to operate the device, the amount of the product to be registered, etc.). The display device 230 is an embodiment of an output means included in the label issuing device of the present disclosure.

FIG. 2 is a block diagram illustrating the configuration of the POS device 200 according to the first embodiment. The POS device 200 includes a registration section 201, an accounting section 202, and a label information generation section 203.

The registration unit 201 registers products to be sold. Specifically, the registration unit 201 generates registered product data indicating the product identifier read from the product assignment code by the reader 210. The products included in the registered product data are also described as registered products. FIG. 3 is a diagram showing an example of registered product data according to the first embodiment. In FIG. 3, the product registration data includes a product identifier for one registered product.

The accounting section 202 performs accounting processing for registered products registered by the registration section 201. When the accounting process is completed, the accounting unit 202 generates sales history data indicating that accounting for the registered product has been completed. Accounting department 202 transmits sales history data to management server 400 and label information generation section 203. Products included in the sales history data are also described as accounted products. FIG. 4 is a diagram showing an example of sales history data according to the first embodiment. In FIG. 4, the sales history data includes an accounting identifier, a product identifier for one item that has been purchased (hereinafter also referred to as a completed item identifier), an identifier of the store where the transaction was made (hereinafter also referred to as a sales store identifier), and date and time (hereinafter also referred to as accounting date and time). The accounting identifier is an identifier that identifies each accounting process. The accounting identifier may be printed on the receipt issued when the accounting is completed. The accounted-for product identifier may be the product name of the item for which the transaction has been completed. The sales store identifier may be the store name of the store where the transaction was made.

The label information generation unit 203 generates accounting information to be printed on a label based on the sales history data and sends it to the printer 220. Specifically, the label information generation unit 203 converts the accounting information including the accounting identifier, the purchased product identifier, the sales store identifier, and the accounting date and time into a labeling code, and transmits the code to the printer 220 .

(Management server 400)
The management server 400 manages various data used by the POS device 200. The management server 400 stores a product data file as such data, and distributes the product data file to the POS device 200 as appropriate. Items such as a product identifier, product name, price, etc. are set for each product in the product data file. The management server 400 also receives sales history data from the POS device 200 and stores the received sales history data.

(Reader 110)
The reader 110 is connected to the label verification device 100. The reader 110 optically reads the product assignment code from the product to be verified (hereinafter also referred to as the target product), and transmits the product identifier (hereinafter also referred to as the target product identifier) indicated by the product assignment code to the label verification device 100. Send to. Further, the reader 110 optically reads the labeling code from the label attached to the target product, and transmits the accounted product information indicated by the labeling code to the label matching device 100. The target product is, for example, a product that the customer owns inside the store or outside the store. The target product may be a product that the customer is trying to take out of the store.

(Label verification device 100)
FIG. 5 is a block diagram illustrating the configuration of the label matching device 100 according to the first embodiment. The label matching device 100 includes a matching section 101, an output section 102, and an information acquisition section 103.

The information acquisition unit 103 acquires the target product identifier from the reader 110 as verification target information. The verification target information is, for example, information that is a comparison target for determining the validity of a label. Furthermore, the information acquisition unit 103 acquires accounting information from the reader 110.

The collation unit 101 collates the verification target information acquired by the information acquisition unit 103 and accounting information. Specifically, the matching unit 101 matches the target product identifier with the accounted product identifier included in the accounting information. FIG. 6 is a diagram illustrating an example of accounting information and verification target information according to the first embodiment. If the label is properly affixed, that is, if the label is issued when the checkout for the target product is completed and is affixed to the target product, the target product identifier and the paid product identifier match.

The output unit 102 outputs the results of the verification performed by the verification unit 101.

[motion]
Hereinafter, the operation of the system in the first embodiment will be explained using figures. FIG. 7 is a flowchart showing product registration and accounting processing in the POS device 200 according to the first embodiment. Product registration/accounting processing is performed, for example, when a customer purchases a product.

The registration unit 201 receives the product identifier read from the product assignment code from the reader 210, and performs product registration processing to generate registered product data (step S201). For example, the registration unit 201 generates registered product data as shown in FIG.

The accounting unit 202 performs accounting processing for the registered products registered by the registration unit 201 (step S202).

When the customer pays, the accounting department 202 generates sales history data and transmits it to the management server 400 and the label information generation section 203 (step S203). For example, the accounting department 202 generates sales history data as shown in FIG.

The label information generation unit 203 generates accounting information to be printed on the label based on the sales history data, and transmits it to the printer 220 (step S204).

The printer 220 prints a labeling code indicating accounting information on a label and issues it. For example, the printer 220 issues a label on which a labeling code indicating accounting information as shown in FIG. 6 is printed. The customer or store clerk attaches the issued label to the purchased product.

FIG. 8 is a flowchart showing the matching process in the label matching device 100 according to the first embodiment. The verification process is executed, for example, when a store clerk verifies a label affixed to a target product owned by a customer.

The information acquisition unit 103 instructs the store clerk to read the product provision code of the target product via the output unit 102 or the like. The store clerk causes the reader 110 to read the product provision code of the target product. The information acquisition unit 103 acquires the target product identifier indicated by the product assignment code from the reader 110 as verification target information (step S101). For example, the information acquisition unit 103 acquires matching target information as shown in FIG.

The information acquisition unit 103 instructs the store clerk to read the labeling code via the output unit 102 or the like. The store clerk causes the reader 110 to read the labeling code on the label affixed to the target product. The information acquisition unit 103 acquires accounting information indicated by the labeling code from the reader 110 (step S102). For example, the information acquisition unit 103 acquires accounting information as shown in FIG.

The order of step S101 and step S102 may be switched.

The collation unit 101 collates the verification target information acquired by the information acquisition unit 103 and accounting information (step S103). Here, the matching unit 101 matches the target product identifier with the accounted-for product identifier included in the accounting information.

As shown in FIG. 6, when the target product identifier and the paid-in product identifier match, the matching unit 101 determines that the paid-in label attached to the target product is correct. Furthermore, if the target product identifier and the paid-in product identifier do not match, the matching unit 101 determines that the paid-in label attached to the target product is incorrect. The output unit 102 outputs the results of the comparison performed by the comparison unit 101 (step S104).

FIG. 9 is a diagram showing an example of a verification result screen according to the first embodiment. If the verification result is correct, the output unit 102 outputs a verification result screen as shown in screen (a), for example. On the other hand, if the verification result is incorrect, the output unit 102 outputs a verification result screen as shown in screen (b), for example.

[effect]
According to the first embodiment, it is possible to easily confirm whether the paid-out label affixed to the target product is the one issued for the target product, as the validity of the checked-out label. The reason for this is that the label matching device 100 matches the accounted product identifier acquired from the label attached to the target product with the target product identifier indicated by the product allocation code acquired from the target product.

[Modified example]
<About the reader>
In the first embodiment, a case has been described in which the reader 110 optically reads the product assignment code or the label assignment code, but the reader 110 may be a camera that captures an image of the target product. When the reader 110 is a camera, the reader 110 detects the product assignment code and the label assignment code using known image recognition technology or image analysis technology, and specifies the information indicated by these codes. The reader 110 transmits information indicated by these codes to the information acquisition unit 103. Furthermore, the reader 110 may identify the product identifier of the target product from the appearance of the target product using image recognition technology or image analysis technology based on AI (Artificial Intelligence), without using the product assignment code.

Similarly to the case where the reader 110 is a camera, the reader 210 may also specify a product identifier based on a captured image of the product to be registered and transmit it to the registration unit 201.

<About the label>
The labeling code printed on the label is not limited to a two-dimensional code, but may be a one-dimensional code, text, color, pattern, image, etc. The color and pattern of the label may be changed for each store so that store staff can identify it at a glance. Furthermore, the type of label may be changed depending on the date or time when the label is issued. The label may be of the type that can be peeled off from a backing paper, or it may be a backing-less label whose adhesive surface is sensitive to heat. The printer 220 may automatically cut and output the rolled label.

<About the label attachment position>
If the label is pasted over the product assignment code, the label verification device 100 will not be able to perform verification. Furthermore, depending on the shape of the product, it may be difficult to find the label depending on the affixing position, making verification by the label verification device 100 difficult. Further, when the label attachment position is close to the position where the product assignment code is attached, the label comparison device 100 can efficiently perform the comparison. Therefore, the display device 230 may display a screen that instructs the appropriate position to attach the label on which accounting information is printed.

In this case, for example, the product data file stored by the management server 400 includes appropriate label attachment positions for each product. The label attachment position is determined in advance based on the position of the product assignment code and the shape of the product. The label information generation unit 203 refers to the product data file, determines the label affixing position of the purchased product, and outputs the label affixing position to the display device 230.

Furthermore, instead of using the predetermined label attachment position in the product data file, the label information generation unit 203 may determine the label attachment position based on the result of recognizing the shape of the product and the position of the product assignment code. good. In this case, the label information generation unit 203 receives the result of recognizing the shape of the product and the position of the product assignment code from the reader 210, which is a camera, for example. The label information generation unit 203 determines the position around the product assignment code as the attachment position, and outputs the label attachment position to the display device 230.

FIG. 10 is a diagram showing an example of a label pasting position instruction screen according to a modification of the first embodiment. Based on the label pasting position determined by the label information generation unit 203, the display device 230 outputs a label pasting position instruction screen in which the label pasting position is superimposed on an image of the product, as shown in FIG. 10, for example.

When affixing the issued label to the purchased product, the customer or store clerk affixes the label to the position specified on the label affixing position instruction screen.

<About checking multiple products>
When a customer purchases multiple products, the accounting unit 202 generates sales history data including the multiple purchased products. The label information generation unit 203 generates accounting information to be printed on a label attached to each product based on the sales history data, and outputs it to the printer 220. The printer 220 prints the same number of labels as the number of products sold in the same transaction.

FIG. 11 is a diagram illustrating an example of accounting information and verification target information according to a modification of the first embodiment. FIG. 11 is an example where two products are sold in the same transaction. Processing of the label matching device 100 will be explained using FIG. 11. Accounting information printed on one label includes, for example, product identifiers of all products sold under the same accounting.

In step S101 described above, the information acquisition unit 103 instructs to read the product provision codes of a plurality of target products. The store clerk causes the reader 110 to read the product provision codes of a plurality of target products. As shown in FIG. 11, the information acquisition unit 103 acquires a set of target product identifiers {P1, P2} indicated by the product assignment code as verification target information.

Furthermore, the information acquisition unit 103 instructs reading of labeling codes of a plurality of target products in step S102 described above. The store clerk causes the reader 110 to read the labeling codes of the plurality of target products. In this case, the set of accounted product identifiers included in the accounting information indicated by the labeling code is the same among the plurality of target products. The information acquisition unit 103 acquires a set of accounted product identifiers {P1, P2} included in the accounting information indicated by the labeling code of the target product. Note that the information acquisition unit 103 may acquire the product assignment code and label assignment code of one product, and then acquire the product assignment code and label assignment code of another product.

In step S103 described above, the collation unit 101 collates the set of target product identifiers and the set of paid-for product identifiers, as shown in FIG.

Note that the accounting information printed on one label may include an accounted-for product identifier for one product. In this case, in step S102 described above, the information acquisition unit 103 collects a set of accounted product identifiers from the accounted for item identifiers "P1" and "P2" acquired from the labels affixed to each of the plurality of target products, for example. Get {P1, P2}.

Furthermore, the accounting information printed on the label is not limited to product identifiers of products sold at the same transaction, but may include, for example, product identifiers of products sold at different transactions on the same day.

[Second embodiment]
In the second embodiment, the store identifier of the store where the verification process is performed (hereinafter also referred to as the verification store identifier) and the date and time (hereinafter also referred to as the verification date and time) are used as verification target information, and the sales included in the accounting information are used. This embodiment differs from the first embodiment in that the store identifier and checkout date and time are verified against the verification store identifier and verification date and time.

In the second embodiment, in step S101 described above, the information acquisition unit 103 acquires the verification store identifier and the verification date and time as verification target information. The verification store identifier (store identifier of the store where the label verification device 100 is used) is stored in advance in a storage unit (not shown), for example.

FIG. 12 is a diagram illustrating an example of accounting information and verification target information according to the second embodiment. The verification target information includes a verification store identifier and a verification date and time.

In step S103 described above, the collation unit 101 collates the verification target information acquired by the information acquisition unit 103 and accounting information. Specifically, the matching unit 101 matches the matching store identifier with the sales store identifier included in the accounting information. Further, the matching unit 101 matches the matching date and time with the accounting date and time included in the accounting information. Here, the verification unit 101 determines whether the verification date and time is within a predetermined time period after the accounting date and time. For example, the verification unit 101 determines whether the verification date and time is within three hours after the accounting date and time.

As shown in FIG. 12, if the verification store identifier and the sales store identifier match, and the verification date and time is within a predetermined time after the payment date and time, the verification unit 101 determines that the payment completed label affixed to the target product is correct. It is determined that In addition, if the verification store identifier and the sales store identifier do not match, or if the verification date and time are not within a predetermined time after the checkout date and time, the verification unit 101 determines that the checkout label attached to the target product is incorrect.

In step S104 described above, the output unit 102 outputs the result of the comparison by the comparison unit 101.

FIG. 13 is a diagram showing an example of a matching result screen according to the second embodiment. If the verification result is correct, the output unit 102 outputs a verification result screen as shown in screen (a) in FIG. 13, for example. On the other hand, if the verification result is incorrect, the output unit 102 outputs a verification result screen such as screen (b) or screen (c) in FIG. 13, for example.

Note that when comparing the verification date and time with the accounting date and time, the verification unit 101 may determine only whether the dates match.

[effect]
According to the second embodiment, it is possible to easily confirm, as the validity of the checked-out label, that the checked-out label affixed to the target product was issued at the store performing the checking and on the date and time of checking. . The reason is that the label verification device 100 verifies the sales store and checkout date and time of the purchased product obtained from the label affixed to the target product, the verification store, and the verification date and time, respectively.

[Third embodiment]
In the third embodiment, the accounting identifier printed on the receipt (hereinafter also referred to as receipt identifier) is used as verification target information, and the accounting identifier included in the accounting information and the receipt identifier are verified. and different from the second embodiment.

In the third embodiment, in step S204 described above, the printer 220 of the POS system 20 further prints accounting information including the receipt identifier described above on the receipt handed to the customer. The printer 220 that prints receipts and the printer 220 that prints labels may be the same or may be provided separately.

In step S101 described above, the information acquisition unit 103 instructs the store clerk, via the output unit 102 or the like, to read the receipt identifier printed on the receipt presented by the customer in possession of the target product. The clerk causes the reader 110 to read the receipt identifier. The information acquisition unit 103 acquires from the reader 110 a receipt identifier printed on a receipt presented by a customer who owns the target product, as verification target information.

FIG. 14 is a diagram illustrating an example of accounting information and verification target information according to the third embodiment. The verification target information includes a receipt identifier.

In step S103 described above, the collation unit 101 collates the verification target information acquired by the information acquisition unit 103 and accounting information. Specifically, the matching unit 101 matches the receipt identifier with the accounting identifier included in the accounting information.

As shown in FIG. 14, when the receipt identifier and the checkout identifier match, the matching unit 101 determines that the checkout label affixed to the target product is correct. Furthermore, if the receipt identifier and the checkout identifier do not match, the matching unit 101 determines that the checkout label attached to the target product is incorrect.

[effect]
According to the third embodiment, it is possible to easily confirm that the checkout label attached to the target product corresponds to the receipt presented by the customer, as the validity of the checkout label. The reason for this is that the label matching device 100 matches the accounting identifier included in the accounting information printed on the label with the receipt identifier obtained from the receipt presented by the customer in possession of the target product.

[Fourth embodiment]
The fourth embodiment differs from the first to third embodiments in that sales history data is used as verification target information and accounting information and sales history data are verified.

[composition]
FIG. 15 is a block diagram schematically illustrating the configuration of a product management system 2 according to the fourth embodiment. The product management system 2 differs from the product management system 1 according to the first embodiment in that the label matching device 100 performs data communication with the management server 400. Description of the same configuration as in the first embodiment will be omitted.

[motion]
In step S101 described above, the information acquisition unit 103 of the label verification device 100 acquires sales history data from the management server 400 as verification target information.

In step S103 described above, the collation unit 101 collates the verification target information acquired by the information acquisition unit 103 and accounting information. Specifically, the matching unit 101 determines whether the accounting date and time included in the accounting information and the accounted product identifier are included in the sales history data.

When the transaction date and time and the transaction completed product identifier are included in the sales history data, the verification unit 101 determines that the transaction completed label attached to the target product is correct. Furthermore, when the transaction date and time and the transaction completed product identifier are not included in the sales history data, the verification unit 101 determines that the transaction completed label attached to the target product is incorrect.

Note that the collation unit 101 included in the label collation device 100 may transmit the accounting date and time and the accounted product identifier included in the accounting information acquired by the information acquisition unit 103 to the management server 400. In this case, the management server 400 may search the sales history data for the accounting date and time and the accounted product identifier transmitted from the matching unit 101 and send the results to the matching unit 101. The matching unit 101 determines whether the paid label is correct based on the search results.

Additionally, the collation unit 101 may transmit the accounting identifier included in the accounting information acquired by the information acquisition unit 103 and/or the receipt identifier printed on the receipt presented by the customer to the management server 400. In this case, the verification unit 101 performs verification with the accounting identifier included in the sales history data.

[effect]
According to the fourth embodiment, it is possible to easily confirm that the accounting information of the accounting label affixed to the target product is in the sales history data stored in the management server 400 as the validity of the accounting label. The reason is that the label matching device 100 receives sales history data from the management server 400, and the accounting date and time and the accounted product identifier included in the accounting information acquired from the label affixed to the target product are not included in the sales history data. This is to determine whether it is included in As a result, even a checkout label forged using the product identifier of the target product and an arbitrary date and time can be detected as a fraudulent checkout label.

[Fifth embodiment]
[composition]
FIG. 16 is a block diagram illustrating the configuration of a label matching device 100A according to the fifth embodiment. The label verification device 100A includes a verification section 101 and an output section 102. The collation unit 101 and the output unit 102 are an embodiment of a collation unit and an output unit of the present disclosure.

The verification unit 101 collects accounting information obtained from a label attached to a target product on which accounting information, which is information related to the product's accounting, is printed, and verification target information, which is information regarding the validity of the label. Verify. The output unit 102 outputs the matching result obtained by the matching unit 101.

[motion]
FIG. 17 is a flowchart showing the matching process in the label matching device 100A according to the fifth embodiment. The collation unit 101 collates the accounting information acquired from the label on which the accounting information is printed with the verification target information, which is information regarding the validity of the label (step S501). The output unit receives the matching result from the matching unit 101 and outputs it (step S502).

[effect]
According to the fifth embodiment, the validity of the paid label can be easily confirmed. The reason is that the label matching device 100A acquires accounting information from a label attached to the target product, which is printed with accounting information that is information related to the accounting when the accounting for the item is completed. This is to check the information to be checked, which is information regarding the validity of the label.

[Sixth embodiment]
[composition]
FIG. 18 is a block diagram illustrating the configuration of a label issuing device 200A according to the sixth embodiment. The label issuing device 200A includes a label issuing unit 204 that issues a label that is attached to a target product and prints accounting information that is information related to the transaction when the transaction for the product is completed.

Accounting information includes identifiers of products for which accounting has been completed. The identifier of the product for which the checkout has been completed, which is included in the accounting information, and the identifier of the target product indicated by the code acquired from the target product are compared by a label matching device.

The label issuing device 200A may be included in the POS device 200 according to the first embodiment.

[motion]
FIG. 19 is a flowchart showing label issuing processing in the label issuing device 200A according to the sixth embodiment. The label issuing unit 204 acquires accounting information that is information related to accounting (step S601). Next, the label issuing unit 204 issues a label (step S602).

[effect]
According to the sixth embodiment, the validity of the paid label can be easily confirmed. This is because the label issuing device 200A issues a label on which accounting information including the identifier of the product for which accounting has been completed is printed.

(Hardware configuration)
In each embodiment described above, each component of each device (label verification device 100, POS device 200, management server 400, etc.) represents a functional unit block. A part or all of each component of each device may be realized by any combination of the computer 500 and a program.

FIG. 20 is a block diagram showing an example of the hardware configuration of computer 500. Referring to FIG. 20, the computer 500 includes, for example, a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, a program 504, a storage device 505, a drive device 507, and a communication interface 508. , an input device 509, an input/output interface 511, and a bus 512.

The program 504 includes instructions for implementing each function of each device. The program 504 is stored in advance in the ROM 502, RAM 503, or storage device 505. The CPU 501 realizes each function of each device by executing instructions included in the program 504. For example, the CPU 501 of the label matching device 100 executes instructions included in the program 504 to realize the functions of the matching section 101, the output section 102, and the information acquisition section 103. Further, the RAM 503 may store data processed in each function of each device. For example, the RAM 503 of the management server 400 may store registered product data.

A drive device 507 reads from and writes to the recording medium 506. Communication interface 508 provides an interface with a communication network. The input device 509 is, for example, a mouse, a keyboard, or the like, and receives information input from an administrator or the like. The output device 510 is, for example, a display, and outputs (displays) information to an administrator or the like. The input/output interface 511 provides an interface with peripheral devices. In the case of the label matching device 100, the above-mentioned reader 110 is connected to the input/output interface 511. A bus 512 connects each of these hardware components. Note that the program 504 may be supplied to the CPU 501 via a communication network, or may be stored in the recording medium 506 in advance, read by the drive device 507, and supplied to the CPU 501.

Note that the hardware configuration shown in FIG. 20 is an example, and components other than these may be added, or some components may not be included.

There are various variations in how each device is implemented. For example, each device may be realized by an arbitrary combination of a computer and a program, each of which is different for each component. Further, the plurality of components included in each device may be realized by an arbitrary combination of one computer and a program.

Further, a part or all of each component of each device may be realized by a general-purpose or dedicated circuit including a processor or the like, or a combination thereof. These circuits may be configured by a single chip or multiple chips connected via a bus. A part or all of each component of each device may be realized by a combination of the circuits and the like described above and a program.

Further, when a part or all of each component of each device is realized by a plurality of computers, circuits, etc., the plurality of computers, circuits, etc. may be centrally arranged or distributed.

Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above embodiments. Various changes can be made to the structure and details of the present disclosure that can be understood by those skilled in the art within the scope of the present disclosure. Further, the configurations in each embodiment can be combined with each other without departing from the scope of the present disclosure.

For example, as the matching target information, the matching target information in the first to fourth embodiments described above may be used in combination as appropriate. Specifically, the target product identifier of the first embodiment, the collation store, and the collation date and time of the second embodiment may be used as the collation target information. In this case, the matching unit 101 determines, for example, that the target product identifier matches the checked-out product identifier, the matching store identifier matches the sales store identifier, and the matching date and time is within a predetermined time after the accounting date and time. In certain cases, it is determined that the checkout label attached to the target product is correct. Furthermore, the verification store and verification date and time of the second embodiment, and the receipt identifier of the third embodiment may be used as the verification target information.

1, 2 Product management system 100, 100A Label verification device 101 Verification section 102 Output section 103 Information acquisition section 110 Reader 20 POS system 200A Label issuing device 200 POS device 201 Registration section 202 Accounting department 203 Label information generation section 210 Reader 220 Printer 230 Display device 400 Management server 500 Computer

Claims (13)

Verification of the accounting information obtained from the label attached to the target product, on which accounting information, which is information related to the product's accounting, is printed, and the verification target information, which is information regarding the validity of the label. means and
an output means for outputting the matching results;
Equipped with
The verification means compares the date and time when the verification is performed and the store identifier as the verification target information with the date and time when the transaction was completed and the store identifier included in the accounting information.
Label verification device. The output means outputs a screen indicating that the date and time of the verification is not within a predetermined time after the date and time when the checkout is completed, or that the store identifiers do not match.
The label verification device according to claim 1. Verification of the accounting information obtained from the label attached to the target product, on which accounting information, which is information related to the product's accounting, is printed, and the verification target information, which is information regarding the validity of the label. means and
an output means for outputting the matching results;
Equipped with
The verification means uses, as the verification target information, a transaction identifier obtained from a receipt presented by a customer who owns the target product, and collates it with the transaction identifier included in the transaction information.
Label verification device. Verification of the accounting information obtained from the label attached to the target product on which accounting information, which is information related to the product's accounting, is printed, and the verification target information, which is information regarding the validity of the label. means and
an output means for outputting the matching results;
Equipped with
The verification means uses the accounting date and time of the product included in the sales history and the identifier of the product as the verification target information, and the date and time when the accounting was completed included in the accounting information, and the date and time when the accounting was completed in the accounting. Match with product identifier,
Label verification device. comprising information acquisition means for instructing a store clerk to read the label and acquiring the accounting information read from the label;
A label matching device according to any one of claims 1 to 4. a label issuing unit that issues a label attached to the target product, on which accounting information, which is information related to accounting for the product, is printed when the accounting is completed ;
comprising an output means for outputting a screen showing the affixing position of the label on the product according to the position of the code attached to the product ,
The accounting information includes an identifier of the product for which the accounting has been completed,
The identifier of the product for which the transaction has been completed included in the accounting information and the identifier of the target product indicated by the code obtained from the target product are collated by a label matching device.
Label printing device. The label issuing means issues the same number of labels as the number of products sold at the accounting.
The label issuing device according to claim 6. The computer is
Comparing the accounting information obtained from a label attached to the target product on which accounting information, which is information related to the product's accounting, is printed, and verification target information, which is information regarding the validity of the label,
Output the matching results ,
In the verification, the date and time when the verification is performed and the store identifier are used as the verification target information, and the verification is verified with the date and time when the transaction was completed and the store identifier included in the accounting information.
Label matching method. The computer is
Comparing the accounting information obtained from a label attached to the target product on which accounting information, which is information related to the product's accounting, is printed, and verification target information, which is information regarding the validity of the label,
Output the matching results ,
In the verification, an accounting identifier obtained from a receipt presented by a customer who owns the target product is used as the verification target information, and is compared with the accounting identifier included in the accounting information.
Label matching method. The computer is
Comparing the accounting information obtained from a label attached to the target product on which accounting information, which is information related to the product's accounting, is printed, and verification target information, which is information regarding the validity of the label,
Output the matching results ,
In the verification, the accounting date and time of the product included in the sales history and the identifier of the product are used as the verification target information, and the date and time that the accounting was completed included in the accounting information, and the products for which accounting was completed in the accounting , which matches the identifier of
Label matching method. to the computer,
Verification of the accounting information obtained from the label attached to the target product, on which accounting information, which is information related to the product's accounting, is printed, and the verification target information, which is information regarding the validity of the label. processing and
Output processing that outputs the matching results,
run the
In the matching process, a program that executes a process of matching the date and time when the matching is performed and the store identifier as the matching target information with the date and time when the checkout was completed and the store identifier included in the accounting information . to the computer,
Verification of the accounting information obtained from the label attached to the target product, on which accounting information, which is information related to the product's accounting, is printed, and the verification target information, which is information regarding the validity of the label. processing and
Output processing that outputs the matching results,
run the
In the verification process, a program causes a transaction identifier obtained from a receipt presented by a customer who owns the target product to be used as the verification target information to perform a process of comparing the transaction identifier included in the accounting information. to the computer,
Verification of the accounting information obtained from the label attached to the target product, on which accounting information, which is information related to the product's accounting, is printed, and the verification target information, which is information regarding the validity of the label. processing and
Output processing that outputs the matching results,
run the
In the matching process, using the accounting date and time of the product included in the sales history and the identifier of the product as the verification target information, the date and time when the accounting was completed included in the accounting information, and the date and time when the accounting was completed in the accounting A program that executes the process of matching product identifiers .

Images