Mobile cart reconciliation

Abstract

A method is disclosed in which a consumer employs a device associated with a user to scan a tag associated with an item to be purchased. The consumer can use the device associated with the user to pay for the item. A point of sale ("POS") terminal or other such device associated with a merchant scans the tag associated with the item, the item is associated with the user, and the item scanned by the device associated with the user is reconciled with the item scanned by the device associated with the merchant.

Description

[0001] Related applications

[0002] This application claims priority to U.S. Patent Application No. 16 / 363,062, filed April 2, 2019. The contents of the above application are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to point-of-sale systems and methods. Background Technology

[0004] Typical point-of-sale (POS) systems, such as those frequently used by retailers, require customers to wait in line for an available salesperson. The salesperson empties the items from the shopping cart and scans each purchased item one at a time (or once per type of item) at the checkout (POS) terminal. This process has several problems. Waiting for an available salesperson can lead to long lines, especially when staffing levels are insufficient. Scanning individual items is very time-consuming. Furthermore, customers may not know the total price of the items in their cart and may not have enough money to pay for them, causing them embarrassment. Summary of the Invention

[0005] The following is a simplified overview of exemplary embodiments to provide a basic understanding of some aspects of the exemplary embodiments. This overview is not a comprehensive summary of the exemplary embodiments. It is not intended to identify core or key elements of the exemplary embodiments, nor is it intended to define the scope of the appended claims. Its sole purpose is to present some concepts of the exemplary embodiments in a simplified form as a prelude to the more detailed description that follows.

[0006] According to an exemplary embodiment, a method is disclosed herein in which a consumer uses a device associated with a user to scan a tag associated with an item to be purchased. The consumer can use the device associated with the user to pay for the item. A point-of-sale (“POS”) terminal or other such device associated with a merchant scans the tag associated with the item, which is associated with the user, and reconciles the item scanned by the user-associated device with the item scanned by the merchant-associated device. Further embodiments include methods, apparatus, and computer-readable media with instructions for implementing the methods described herein. Attached Figure Description

[0007] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate exemplary embodiments.

[0008] Figure 1 This is a block diagram of a system that uses a mobile shopping cart and reconciles the mobile shopping cart with the physical shopping cart for purchasing items.

[0009] Figure 2This is a block diagram illustrating an example of a system for purchasing multiple items.

[0010] Figure 3 This is a block diagram illustrating an example of a system for purchasing multiple items, where the number of items purchased exceeds the number of specific items.

[0011] Figure 4 This is a block diagram showing a more detailed example of a system for reconciling mobile shopping carts.

[0012] Figure 5 This is a block diagram showing an example of a merchant's equipment.

[0013] Figure 6 This is a block diagram illustrating an example of a consumer device.

[0014] Figure 7 This is a block diagram illustrating an example of a user interface for consumer devices.

[0015] Figure 8 This is a block diagram showing an example of an item with a single tag scanned by both a consumer device and a merchant device.

[0016] Figure 9 This is a block diagram showing an example of an item with optical tags and radio frequency identification tags.

[0017] Figure 10 This is a block diagram showing an example of an item having a first label for scanning by a consumer device and a second label for scanning by a merchant device.

[0018] Figure 11 This is a block diagram illustrating a computer system on which exemplary embodiments can be implemented.

[0019] Figure 12 This is a block diagram illustrating a method for reconciling payments using a mobile shopping cart before checkout.

[0020] Figure 13 This is a diagram illustrating the process of reconciling payments via a mobile shopping cart after checkout.

[0021] Figure 14 This is a block diagram illustrating a method for mobile shopping cart reconciliation performed by a device (e.g., a mobile device) associated with a consumer, where payment is made before the mobile shopping cart is reconciled with the physical shopping cart.

[0022] Figure 15 This is a block diagram illustrating a method for mobile shopping cart reconciliation performed by a device (e.g., a mobile device) associated with a consumer, where payment is made after the mobile shopping cart is reconciled with the physical shopping cart.

[0023] Figure 16This is a block diagram illustrating a method for mobile shopping cart reconciliation performed by a point-of-sale system associated with a merchant, wherein payment is made before the mobile shopping cart is reconciled with the physical shopping cart.

[0024] Figure 17 This is a block diagram illustrating a method for mobile shopping cart reconciliation performed by a point-of-sale system associated with a merchant, wherein payment is made after the mobile shopping cart is reconciled with the physical shopping cart. Detailed Implementation

[0025] The examples provided in this specification are not intended to limit the scope of the appended claims. The accompanying drawings generally indicate features of the examples, and it should be understood and appreciated that the same reference numerals are used to refer to the same elements. References to “an embodiment” or “an embodiment” or “an exemplary embodiment” in the specification mean that a particular feature, structure, or characteristic described is included in at least one embodiment described herein, and do not imply that such feature, structure, or characteristic exists in all embodiments described herein.

[0026] Figure 1 This is a block diagram of a system 100 for purchasing item 102, employing a "mobile shopping cart" and reconciling the mobile shopping cart with a "physical shopping cart". A consumer (not shown) uses consumer device 104 to scan the tag 106 associated with item 102 to make a purchase. The consumer can use consumer device 104 to pay for the item. The consumer then proceeds to checkout. A merchant device 108 associated with the merchant scans the tag 106 associated with item 102. Merchant device logic 110 in merchant device 108 communicates with consumer device logic 112 in consumer device 104 to reconcile the item scanned by consumer device 104 with the item scanned by merchant device 108. If the item 102 scanned by consumer device 104 matches the item 102 scanned by merchant device 108, then merchant device 108 accepts payment from consumer device 104.

[0027] Items scanned by consumer device 104 may be referred to herein as a mobile shopping cart. Items scanned by merchant device 108 may be referred to herein as a physical shopping cart. In an exemplary embodiment, consumer device 104 is a mobile device associated with a consumer. For example, consumer device 104 may be a smartphone.

[0028] In an exemplary embodiment, consumer device 104 includes consumer device logic 112, scanner 118, and wireless transceiver 120. Consumer device logic 112 is operable to control the operation of the device and implement the functions described herein. As used herein, the term "logic" includes, but is not limited to, hardware, firmware, software, and / or combinations of each, to perform one or more functions or one or more actions and / or to result in a function or action from another component. For example, depending on the desired application or need, logic may include a software-controlled microprocessor, discrete logic such as an application-specific integrated circuit (ASIC), a programmable / programmable logic device, a memory device containing instructions, or combinational logic embodied in hardware. Logic may also be entirely embodied as software that performs the required functions when executed by a processor.

[0029] Scanner 118 is operable to scan tag 106 on article 102. In an exemplary embodiment, scanner 118 is an optical scanner. For example, scanner 118 may be operable to scan barcodes, or Quick Response (QR) codes, Universal Product Codes (UPCs), or any combination of two or more of barcodes, QR codes, and UPC codes. In another exemplary embodiment, scanner 118 is operable to scan infrared (IR) tags. In yet another exemplary embodiment, scanner 118 is a wireless scanner, such as a radio frequency identification (RFID) scanner. For example, scanner 118 is operable to employ contactless protocols such as Near Field Communication (NFC), personal area network protocols such as Bluetooth, wireless local area network protocols such as Wi-Fi, or combinations of two or more wireless protocols such as NFC, Bluetooth, and Wi-Fi. In a particular embodiment, scanner 118 is operable to scan two or more combinations of optical, IR, and RFID tags.

[0030] The wireless transceiver 120 can communicate with the merchant device 108 using wireless protocols such as Wi-Fi or cellular data. As will be described in more detail herein, the wireless transceiver 120 can be used by the consumer device logic 112 to obtain pricing information for the item 102, provide data representing the scanned item, and / or provide payment information.

[0031] Item 102 can be any item offered for sale by the merchant. Tag 104 can include any suitable tag that can be scanned, including but not limited to active, passive, semi-passive RFID, NFC, infrared tags, and optical tags (e.g., UPC). In an exemplary embodiment, the tag can include two or more types of tags (e.g., UPC tags and BLUETOOTH tags), which can be combined in one tag or implemented in two separate tags.

[0032] In an exemplary embodiment, each item 102 has a label 106 that is unique to that item. In another exemplary embodiment, similar items may have similar labels (e.g., a 12-ounce Lucky Charm box of cereal may have the same label that provides different data than the label on a 24-ounce Lucky Charm box of cereal or any other type of cereal).

[0033] In an exemplary embodiment, merchant device 108 is located in the checkout area 116 of a merchant establishment. Merchant device 108 includes merchant device (or point-of-sale “POS”) logic 110 for providing the functions described herein, a wireless transceiver 122 for communicating with consumer device 104, and a scanner 114. The wireless transceiver may employ any suitable protocol such as Wi-Fi. The scanner 114 may employ any suitable protocol for scanning item 102. For example, the scanner may suitably include any one or more of the optical, IR, and wireless scanners described herein.

[0034] Although not shown, it will be readily understood by those skilled in the art that merchant device 108 can be coupled to a device to indicate to a consumer whether a transaction has been approved or not. For example, the merchant device can be coupled to a door that opens when a transaction is approved. As another example, merchant device 108 can be coupled to one or more lights to indicate whether a transaction has been approved (e.g., yellow for in progress, green for approved, and red for unapproved or problematic).

[0035] In an exemplary embodiment, when a consumer wishes to purchase item 102, the consumer uses scanner 118 to scan the tag 106 associated with item 102 and obtain data representing item 102. Consumer device logic 112 determines the price of item 102 based on the data representing the item obtained from tag 106. In an exemplary embodiment, the price may be included in the data representing the item obtained by scanner 118 from tag 106. In another exemplary embodiment, consumer device logic 112 uses wireless transceiver 120 to communicate with merchant device 108 to obtain the price of the item. In an exemplary embodiment, when the consumer completes their purchase, consumer device logic 112 sends payment information to merchant device 108 via wireless transceiver 120. When the consumer enters checkout area 116, scanner 114 associated with merchant (or point-of-sale) device 108 scans the tag 106 of item 102. Merchant device 108 also obtains data representing item 102 and payment information from consumer device 104 via wireless interface 122.

[0036] Merchant device logic 110 verifies (reconciles) the data of representative items 102 scanned by a consumer device 104 (e.g., mobile) associated with a consumer (mobile shopping cart) and matches it with the data of representative items 102 scanned by a merchant device 108 (e.g., point-of-sale) associated with a merchant (physical shopping cart). If the mobile shopping cart and physical shopping cart do not match, merchant device logic 110 can prompt corrective action. For example, merchant device 108 may include a display that shows a comparison of the mobile and physical shopping carts to facilitate reconciliation. As another example, merchant device logic 110 may provide data representing the physical shopping cart to consumer device 104 so that the consumer can use consumer device 104 to reconcile the mobile and physical shopping carts. In a particular embodiment, merchant device logic 110 may notify merchant staff of the problem.

[0037] After successfully reconciling the mobile shopping cart with the physical shopping cart, the (point-of-sale) merchant device 108 accepts payment from the (mobile) consumer device 104 associated with the consumer. In an exemplary embodiment, the consumer device 104 may obtain payment information before the consumer approaches the checkout area 116 and / or before the merchant device 108 scans the label 106 of the item 102. Those skilled in the art will readily understand that obtaining payment information before the consumer approaches the checkout area 116 and / or before the merchant device 108 scans the label of the item 102 helps minimize the amount of time the consumer must remain in the checkout area 116. In a particular embodiment, the consumer device 104 may obtain payment after the mobile shopping cart has been reconciled with the physical shopping cart.

[0038] In an exemplary embodiment, consumer device logic 112 can acquire data representing a coupon held by a consumer via consumer device scanner 118. The coupon information can be presented to merchant device 108 as part of the payment for item 102.

[0039] Figure 2 This is a block diagram illustrating an example of a system 200 for purchasing multiple items 102A, 102B. In this example, the consumer has placed the items into a shopping cart 202. However, those skilled in the art will readily understand that the principles described herein apply to situations where the consumer does not use the shopping cart 202 (e.g., the consumer carries the items to the checkout area 116).

[0040] As in Figure 1In this example, the consumer uses a consumer device scanner 118 associated with consumer device 104 to scan labels 106A and 106B associated with items 102A and 102B, respectively. Although consumer device 104 is shown and described as separate from shopping cart 202 in this example, those skilled in the art will readily understand that in some embodiments, consumer device 104 may be incorporated into shopping cart 202.

[0041] In an exemplary embodiment, pricing information may be embodied in tags 106A and / or 106B. In an exemplary embodiment, where pricing information is not embodied in tags 106A and / or 106B, consumer device logic 112 may cause wireless transceiver 120 to communicate with wireless transceiver 122 (e.g., sending data representing the item obtained from the tag) to obtain the price of items 102A and / or 102B as shown in 204. Wireless transceiver 122 is associated with merchant device 108 or another device associated with a merchant. The merchant device (or other device associated with the merchant) responds with pricing information as shown in 206. In an exemplary embodiment where pricing information is included on tags 106A and / or 106B, consumer device logic 112 may communicate with merchant device 108 to verify the pricing information. For example, a consumer may be entitled to a discount (e.g., as a member of a loyalty program), which may not be presented on tags 106A and / or 106B. By communicating with merchant device 108, consumer device logic 112 can obtain data about the discount. In an exemplary embodiment, merchant device 108 determines whether a consumer is entitled to a discount and sends data representing any available discounts to consumer device 104.

[0042] When a consumer indicates that they have completed their purchase, consumer device 104 obtains payment information from the consumer (as described above, payment information may include coupon data). Similar to... Figure 1 In the example, a consumer can be scanned by scanner 114 at any time (e.g., before, during, or after) when the consumer approaches checkout area 116 and / or shopping cart (physical shopping cart) 202 to provide payment information.

[0043] Merchant device logic 110 verifies (reconciles) the data of representative items scanned by a consumer device 104 (e.g., mobile) associated with a consumer (mobile shopping cart) against the data of representative items 102A, 102B scanned by a merchant device 108 (e.g., point-of-sale) associated with a merchant (physical shopping cart). If the mobile shopping cart and physical shopping cart do not match, merchant device logic 110 can prompt corrective action. For example, merchant device 108 may include a display that shows a comparison of the mobile and physical shopping carts to facilitate reconciliation. As another example, merchant device logic 110 may provide data representing the physical shopping cart to consumer device 104 so that the consumer can use consumer device 104 to reconcile the mobile and physical shopping carts. In a particular embodiment, merchant device logic 110 may notify merchant staff of the problem.

[0044] After successfully reconciling the mobile shopping cart with the physical shopping cart, the (point-of-sale) merchant device 108 accepts payment from the (mobile) consumer device 104, as shown at 208, associated with the consumer. Those skilled in the art will readily understand that the payment process may require the exchange of one or more messages between the consumer device 104 and the merchant device 108. For example, the consumer device may send payment information to the merchant device 108, and the merchant device may send a signal to the consumer device 102 indicating whether the payment has been accepted. In an exemplary embodiment, the consumer device 104 may obtain payment information before the consumer approaches the checkout area and / or the merchant device 108 scans the tags 106A and 106B associated with items 102A and 102B, respectively; however, in certain embodiments, the consumer device 104 may obtain payment after the mobile shopping cart and the physical shopping cart have been reconciled.

[0045] In an exemplary embodiment, consumer device logic 112 can acquire data representing a coupon held by a consumer via consumer device scanner 118. The coupon information can be presented to merchant device 108 as part of the payment for item 102.

[0046] Although the example presented above illustrates the purchase of two items, it will be readily understood by those skilled in the art that the number of items chosen for this example is for illustrative purposes, and that the principles described herein can be applied to any number of items achievable in any entity. Therefore, the exemplary embodiments described herein should not be construed as being limited to the number of items provided in the examples described herein.

[0047] Figure 3This is a block diagram illustrating an example of a system 300 for purchasing multiple items, where more than one specific item is purchased. In the example shown, more than one item 102A, designated as 102A1 and 102A2, is purchased. In this example, the consumer has placed items 102A1, 102A2, and 102B into shopping cart 202. However, those skilled in the art will readily understand that the principles described herein apply to situations where the consumer does not use shopping cart 202 (e.g., the consumer takes the items to checkout area 116).

[0048] In an exemplary embodiment, the tags 106A1 and 106A2 for similar items (e.g., 102A1 and 102A2) are identical. Therefore, tags 106A1 and 106A2 provide the same data when scanned.

[0049] In an exemplary embodiment, each label 106A1, 106A2, and 106B has a unique code. For example, even if labels 106A1 and 106A2 are located on similar items (e.g., a hammer), the data on each label is different.

[0050] As in Figure 1 and Figure 2 In this example, the consumer uses consumer device 104 to scan tags 106A1, 106A2, and 106B associated with items 102A1, 102A2, and 102B, respectively. Although consumer device 104 is shown and described as separate from shopping cart 202 in this example, those skilled in the art will readily understand that in some embodiments, consumer device 104 may be incorporated into shopping cart 202.

[0051] In an exemplary embodiment, pricing information may be embodied in tags 102A1, 102A2, and / or 102B. In an exemplary embodiment, where pricing information is not embodied in tags 102A1, 102A2, and / or 102B, consumer device logic 112 may cause wireless transceiver 120 to communicate with wireless transceiver 122 (e.g., to send data representing the item obtained from the tag) to obtain the price of item 102A1, 102A2, and / or 102B as shown in 204. Wireless transceiver 122 is associated with merchant device 108 or another device associated with a merchant. The merchant device (or other device associated with the merchant) responds with pricing information as shown in 206. In an exemplary embodiment where pricing information is included in tags 106A1, 106A2, and / or 106B for item 102A1, 102A2, and / or 102B respectively, consumer device logic 112 may communicate with merchant device 108 to verify the pricing information. For example, a consumer may be entitled to a discount (e.g., as a member of a loyalty program), but this discount may not appear on labels 102A1, 102A2, and / or 102B. Consumer device logic 112 can obtain data about the discount by communicating with merchant device 108.

[0052] When a consumer indicates that they have completed their purchase, consumer device 104 obtains payment information from the consumer (as described above, payment information may include coupon data). Similar to... Figure 1 and Figure 2 In the example, a consumer can be scanned by scanner 114 at any time (e.g., before, during, or after) when the consumer approaches checkout area 116 and / or shopping cart (physical shopping cart) 202 to provide payment information.

[0053] Merchant device logic 110 verifies (reconciles) the data of representative items scanned by a consumer device 104 (e.g., mobile) associated with a consumer (mobile shopping cart) against the data of representative items 102A1, 102A2, and 102B scanned by a merchant device 108 (e.g., point-of-sale) associated with a merchant (physical shopping cart). If the mobile shopping cart and physical shopping cart do not match, merchant device logic 110 can prompt corrective action. For example, merchant device 108 may include a display that shows a comparison of the mobile and physical shopping carts to facilitate reconciliation. As another example, merchant device logic 110 may provide data representing the physical shopping cart to consumer device 104 so that the consumer can reconcile the mobile and physical shopping carts using consumer device 104. In a particular embodiment, merchant device logic 110 may notify merchant staff of the problem.

[0054] After successfully reconciling the mobile shopping cart with the physical shopping cart, the (point-of-sale) merchant device 108 accepts payment from the (mobile) consumer device 104 associated with the consumer. In an exemplary embodiment, the consumer device 104 may obtain payment information before the consumer approaches the checkout area and / or the merchant device 108 scans the tag 106 associated with the item 102; however, in a particular embodiment, the consumer device 104 may obtain payment after the mobile shopping cart and the physical shopping cart have been reconciled.

[0055] In an exemplary embodiment, consumer device logic 112 can acquire data representing a coupon held by a consumer via consumer device scanner 118. The coupon information can be presented to merchant device 108 as part of the payment for item 102.

[0056] Although the example presented above illustrates the purchase of two items, it will be readily understood by those skilled in the art that the number of items chosen for this example is for illustrative purposes, and that the principles described herein can be applied to the number of items achievable in any entity. Therefore, the exemplary embodiments described herein should not be construed as being limited to the number of items provided in the examples described herein.

[0057] Figure 4 This is a block diagram illustrating a more detailed example of a system 400 for providing reconciliation for mobile shopping carts. In this example, multiple merchant devices 108A and 108B are coupled to a network 402. A wireless access point (AP) 404 is coupled to the network 402, enabling the access point 404 and the merchant devices 108A and 108B to communicate with an additional merchant system 406. Some examples of the additional merchant system include, but are not limited to, a database 410 containing product pricing information categorized by label identification, consumer loyalty program data 412, logic 414 for verifying coupons, payment processing logic 416, and any other databases and logic that the merchant may employ. In an exemplary embodiment, one or more financial networks 408 are coupled to the network 402, which enables the payment processing logic 416 to contact the consumer's financial institution (e.g., a bank, credit card company, etc.) to verify the payment and deduct funds from the consumer's account.

[0058] In an exemplary embodiment, one or more wireless access points 404 are distributed throughout the merchant's premises to allow consumer device 104 to communicate with the merchant. Figure 4 As shown, this allows consumer device 104 to obtain item price information based on tag data. However, those skilled in the art will readily understand that one or more APs 404 can provide many other functions. For example, a merchant can send data representing special offers or discounts to consumer device 104.

[0059] In an exemplary embodiment, a consumer can choose either merchant device 108A or merchant device 108B to check out. The consumer simply approaches the checkout area 116A or 116 associated with the desired checkout 108A or 108B, respectively. As described herein, a scanner associated with the selected checkout area scans items 102A, 102B in shopping cart 202 (physical cart) and obtains data representing the items scanned by consumer device 104 (mobile cart). If the physical cart and mobile cart match (reconciliation), the selected merchant device obtains payment information from consumer device 104. Payment is processed by payment processing logic 416, which can communicate with financial network 408 to obtain payment from the consumer's account.

[0060] Figure 5 This is a block diagram illustrating an example of merchant device 108. In an exemplary embodiment, merchant device 108 includes merchant device logic 110, scanner 114, wireless transceiver 122, payment module 502, and user interface 504.

[0061] As described herein, scanner 114 may suitably include optical and / or RFID scanners. In an exemplary embodiment, scanner 114 is operable to scan UPC codes, barcodes, and / or two-dimensional barcodes (e.g., QR codes) on tags. In another example of this embodiment, scanner 114 is operable to scan infrared tags. In yet another exemplary embodiment, scanner 114 is operable to scan RFID tags using any suitable technology, including but not limited to wireless local area networks (“WLANs”) such as Wi-Fi, personal area networks (“PANs”) such as Bluetooth, and / or contactless protocols such as NFC. In certain embodiments, scanner 114 is operable to scan a combination of optical and / or wireless technologies.

[0062] In an exemplary embodiment, the wireless transceiver 122 is operable to communicate with a consumer device (e.g., consumer device 108). The wireless transceiver can use any suitable wireless technology, such as Wi-Fi or BlueTooth.

[0063] In an exemplary embodiment, payment module 502 is operable to acquire payment information for an item (or goods) scanned by scanner 114. Payment data can be acquired via wireless transceiver 122. In an exemplary embodiment, payment module 502 is connected via network 402 (…). Figure 4 Coupled to merchant payment logic 406 and / or financial network 408 to process payments.

[0064] In an exemplary embodiment, a user interface 504 is used to communicate information to the consumer. For example, when payment has been accepted, the payment module 502 can output a message (display and / or audio) indicating that the transaction is complete and the consumer can exit the checkout area. In another exemplary embodiment, if the mobile shopping cart and the physical shopping cart do not match, the user interface 504 can be used to assist with reconciliation. For example, the user interface can use a display to show the goods scanned by the scanner 114. In a particular embodiment, the display of the user interface 504 shows the goods scanned by the scanner 114 and the consumer device indicating the scanned items. In an exemplary embodiment, the user interface 504 includes a keyboard, a display, and / or a touchscreen, enabling the consumer to request assistance.

[0065] In an exemplary embodiment, the user interface also includes payment inputs, such as a card reader, cash receiver or recycler, check receiver, or a combination of inputs that may allow consumers to pay for items and / or pay for additional items (e.g., previously unpaid additional items identified during reconciliation) and / or request scanner 114 to rescan the physical shopping cart (e.g., after an item has been removed from or added to the cart).

[0066] In an exemplary embodiment, merchant device logic 110 acquires data representing an item from a label scanned by scanner 114 (a merchant, point-of-sale, or "POS"). Merchant device logic 110 receives a request to pay for the scanned item via scanner 114. The request includes data representing a payment amount. The merchant device determines the amount owed based on the data of the representative item scanned by scanner 114. Merchant device logic 110 compares the amount owed with the payment amount. Merchant device logic 110 accepts the payment request for the item scanned by scanner 114 in response to determining that the amount owed matches the payment amount. In an exemplary embodiment, merchant device logic 110 causes payment module 502 to process the payment in response to determining that the amount owed matches the payment amount.

[0067] In an exemplary embodiment, merchant device logic 110 rejects a first request for payment for an item scanned by scanner 114 in response to a mismatch between the item scanned by scanner 114 (the amount owed) and the payment amount. This could occur if the consumer may have unintentionally (or intentionally) not scanned an item being checked out (e.g., carried by the consumer and / or in their shopping cart).

[0068] If the amount owed does not match the payment amount, the consumer can determine whether the item scanned by scanner 114 was not scanned by their consumer (e.g., mobile) device. If the consumer determines that there is an item that was not scanned by their consumer device, the consumer can then scan the item with their consumer device and adjust the payment accordingly.

[0069] Alternatively, consumers can remove items from their shopping carts (either carried by the consumer or even items previously left in the checkout area by a customer). The consumer can then request a rescan of the items using their consumer device (which can be requested by the consumer via the consumer device, received by the wireless transceiver 122 or via the user interface 504), which will cause the scanner 114 to rescan the items. The outstanding amount is updated based on the rescanned items. If the payment equals the updated outstanding amount, the merchant device logic 110 will cause the payment module 502 to process the payment.

[0070] Figure 6 This is a block diagram illustrating an example of a consumer device 104. In an exemplary embodiment, the consumer device 104 includes consumer device logic 112, a scanner 118, a wireless transceiver 120, and a user interface 602.

[0071] As described herein, scanner 118 may suitably include optical and / or RFID scanners. In an exemplary embodiment, scanner 118 is operable to scan UPC codes, barcodes, and / or two-dimensional barcodes (e.g., QR codes) on tags. In another exemplary embodiment, scanner 118 is operable to scan IR tags. In yet another exemplary embodiment, scanner 118 is operable to scan RFID tags using any suitable technology, including but not limited to wireless local area networks (“WLANs”) such as Wi-Fi, personal area networks (“PANs”) such as Bluetooth, and / or contactless protocols such as NFC. In certain embodiments, scanner 118 is operable to scan combinations of optical and / or wireless technologies.

[0072] Consumer device logic 112 acquires tag data from scanner 118. Consumer device logic 112 maintains a list of items associated with the scanned tags. Item data can be acquired from the tags, or consumer device logic 112 can use wireless transceiver 120 to acquire data representing the items scanned by scanner 118.

[0073] In an exemplary embodiment, the consumer uses user interface 602 to provide payment information. The payment information may be pre-set (e.g., saved credit card or bank account information) and / or may be input by the consumer via user interface 602. In an exemplary embodiment, the consumer can obtain a transaction history and / or view scanned items for purchase via user interface 602.

[0074] In an exemplary embodiment, scanner 118 scans a tag for an item to be purchased, the tag providing data representing the item. Consumer device logic 112 maintains the current amount due for the scanned item (or items) to be purchased. Consumer device logic 112 obtains payment for the current amount due. As described herein, payment data may be preset and / or entered by the consumer when the purchase is completed. In an exemplary embodiment, a payment request is received from the merchant's computer system via wireless transceiver 120. Consumer device logic 112 provides payment to the merchant's computing system in response to the payment request via wireless transceiver 120. In a particular embodiment, consumer device logic 112 may automatically send payment information when consumer device 104 is detected in the checkout area. In yet another exemplary embodiment, the consumer uses user interface 602 to request payment to be sent to the merchant.

[0075] In an exemplary embodiment, scanner 118 scans tags for a plurality of items to be purchased, the tags providing data representing a plurality of corresponding items. Consumer device logic 112 maintains an updated current amount due in response to scanning each of the plurality of tags.

[0076] In an exemplary embodiment, a request is received to remove an item intended for purchase from a plurality of corresponding items. For example, a consumer may use user interface 602 to indicate that they are no longer interested in purchasing a specific item. The consumer uses scanner 112 to scan the tag associated with the item to be removed. Consumer device logic 112 updates the current amount due in response to scanning the tag associated with the item to be removed.

[0077] In an exemplary embodiment, consumer device logic 112 receives, via wireless transceiver 120, a signal indicating that the amount due indicated by the scanning of an item by the point-of-sale device does not match the current amount due. User interface 602 provides an interface that allows adjustment of the payment amount to match the amount due indicated by the point-of-sale device scan. In another exemplary embodiment, data of a representative item scanned by a merchant is received via wireless transceiver 120. User interface 602 outputs (visually or audibly) the item scanned by the merchant device. In yet another exemplary embodiment, the user interface provides an interface that allows the consumer to request assistance.

[0078] In an exemplary embodiment, consumer device logic 112 is operable to transmit data of a representative tag scanned by scanner 118 to a merchant computing system via wireless transceiver 120. Consumer device logic 112 receives data on the price of a representative item from the merchant's computer system in response to transmitting the data of the representative tag to the merchant computing system via wireless interface 120. In another exemplary embodiment, the data of a representative item obtained by scanner 118 from the tag includes the price of the item.

[0079] Figure 7 This is a block diagram illustrating an example of a user interface 700 for a consumer device. In an exemplary embodiment, the user interface 602 of the consumer device 104 employs the user interface 700. The user interface 700 may be implemented on a touchscreen interface or on a combination of a display and a keyboard.

[0080] In an exemplary embodiment, the user interface 700 includes a current total amount display 702, a scan new item input 704, a remove item input 706, a price check input 708, and a checkout / payment input 710. The current total amount display 702 maintains the total amount of the currently scanned items (mobile shopping cart) used for shopping. This allows consumers to determine if they have exceeded their budget. Consumers use the scan new item input 704 to add new items to the mobile shopping cart. Consumers use the remove item input 706 to remove items from the mobile shopping cart. For example, if a consumer decides not to purchase something and removes it from their cart, the consumer will use the remove item input 706 and then scan the tag associated with the item to remove it from the mobile shopping cart. The price check input 708 allows consumers to obtain the price of the item, which can help determine whether to purchase the item. The checkout / payment input 710 can be used by consumers to initiate checkout (e.g., scan the physical shopping cart) and / or provide payment information (e.g., account information).

[0081] Figure 8 This is a block diagram illustrating an example of an item with an RFID tag 106C, which is scanned by both consumer and merchant devices. For example, the RFID tag 106C can be scanned by a WLAN (e.g., Wi-Fi and / or PAN (e.g., Bluetooth)) scanner. Those skilled in the art will readily understand that the RFID tag 106C can employ any suitable wireless technology.

[0082] Figure 9 This is a block diagram illustrating an example of an article having an RFID tag 106C1 and an optical tag 106C2. For example, the optical tag 106C2 may be scanned by a consumer device scanner 118, while the RFID tag 106C1 may be scanned by a merchant device scanner 114. Examples of optical technologies that may be employed with tag 106C2 include, but are not limited to, UPC, barcode, QR code, IR, or combinations of optical technologies. Examples of RFID technologies that may be employed with tag 106C1 include, but are not limited to, WIFI, BLUETOOTH, or combinations of wireless technologies. Although tags 106C1 and 106C2 are shown as separate tags, it will be readily understood by those skilled in the art that this is merely for illustrative purposes, as in the exemplary embodiment, tags 106C1 and 106C2 are embodied on the same substrate.

[0083] Figure 10 This is a block diagram illustrating an example of an item 102 having a first RFID tag 106C3 for scanning by a consumer device and a second RFID tag 106C4 for scanning by a merchant device. Those skilled in the art will readily understand that tags 106C3 and 106C4 can employ different protocols. For example, tag 106C3 may include one or more of Wi-Fi, BlueTooth, and NFC, and tag 106C4 may include one or more of Wi-Fi or BlueTooth. For instance, a consumer may use NFC (Contactless Protocol) to scan the tag associated with an item when placing it in a mobile shopping cart, while a merchant device may use Wi-Fi (WLAN Protocol) to scan the tag associated with an item in a physical shopping cart. Although tags 106C3 and 106C4 are shown as separate tags, those skilled in the art will readily understand that this is merely for illustrative purposes, as in the exemplary embodiment, tags 106C3 and 106C4 are embodied on the same substrate.

[0084] While the above description relates to items having labels on them, those skilled in the art will readily understand that in some embodiments, the label may be separate from the item. For example, when purchasing a product, the item may be weighed and a “label” may be associated with the item, which may include a barcode or other data indicating the purchase amount (e.g., quantity, unit price, total price, or a combination thereof). Physical labels may be provided to be placed on items; however, in exemplary embodiments, as part of reconciliation processing, the consumer device may send data representing unlabeled items.

[0085] Figure 11 This is a block diagram illustrating a computer system 1100 on which exemplary embodiments can be implemented. The computer system 1100 can be used to implement merchant device logic 110 (…). Figures 1 to 5 Consumer device logic 112 ( Figures 1 to 4 and Figure 6 ) and / or payment module 502 ( Figure 5 ).

[0086] Computer system 1100 includes a bus 1102 or other communication mechanism for transmitting information and a processor 1104 coupled to the bus 1102 for processing information. Computer system 1100 also includes main memory 1106, such as random access memory (RAM) or other dynamic storage devices coupled to the bus 1102, for storing information and instructions to be executed by the processor 1104. Main memory 1106 can also be used to store temporary variables or other intermediate information during the execution of instructions executed by the processor 1104. Computer system 1100 also includes read-only memory (ROM) 1108 or other static storage devices coupled to the bus 1102 for storing static information and instructions of the processor 1104. A device 1110, such as a magnetic disk or optical disk, is provided and coupled to the bus 1102 for storing information and instructions.

[0087] Computer system 1100 may be coupled to display 1112, such as a cathode ray tube (CRT), liquid crystal display (LCD), or light-emitting diode (LED), via bus 1102 for displaying information to a computer user. Input device 1114, such as a keyboard including alphanumeric and other keys, is coupled to bus 1102 for transmitting information and command selections to processor 1104. Another type of user input device is cursor control 1116, such as a mouse, trackball, or arrow keys, for transmitting directional information and command selections to processor 1104 and for controlling cursor movement on display 1112. This input device typically has two degrees of freedom on two axes, a first axis (e.g., x) and a second axis (e.g., y), allowing the device to specify a position in a plane. In an exemplary embodiment, display 1112, input device 114, and / or cursor control 1116 may be integrated into a touchscreen display.

[0088] One aspect of the exemplary embodiments relates to the use of computer system 1100. According to the exemplary embodiments, computer system 1100 provides a mobile shopping cart reconciliation in response to processor 1104 executing one or more sequences of one or more instructions contained in main memory 1106. Such instructions may be read into main memory 1106 from another computer-readable medium, such as storage device 1110. Executing the sequence of instructions contained in main memory 1106 causes processor 1104 to perform the processing steps described herein. One or more processors in a multiprocessor arrangement may also be employed to execute the sequence of instructions contained in main memory 1106. In alternative embodiments, hardwired circuitry may be used instead of or in combination with software instructions to implement the exemplary embodiments. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.

[0089] As used herein, the term "computer-readable medium" refers to any medium that participates in providing instructions to processor 1104 for execution. Such media can take many forms, including but not limited to non-volatile media. Non-volatile media include, for example, optical discs or magnetic disks, such as storage device 1110. Common forms of computer-readable media include, for example, floppy disks, hard disks, magnetic cards, paper tape, any other physical media with a perforated pattern, RAM, PROM, EPROM, FLASHPROM, CD, DVD, or any other memory chip or cassette tape, or any other medium that a computer can read.

[0090] In an exemplary embodiment, the computer system 1100 also includes a communication interface 1118 coupled to the bus 1102. The communication interface 1118 provides bidirectional data communication that couples the computer system 1100 to a network link 1120 connected to a local network 1122. This enables the computer system 1100 to communicate with other external devices. For example, the communication interface 1118 may allow a consumer device 104 to communicate with a merchant device 108, and vice versa.

[0091] Network link 1120 typically provides data communication to other data devices via one or more networks. For example, network link 1120 may include one or more wireless and / or wireless links.

[0092] In view of the above structural and functional characteristics, referring to Figures 12 to 17 This will help to better understand the method illustrated in the exemplary embodiments. Meanwhile, for ease of explanation, Figures 12 to 17 The methods shown and illustrated are executed sequentially. It should be understood that the exemplary embodiments described herein are not limited to the order shown, as some aspects may occur in a different order and / or simultaneously with other aspects shown and illustrated herein. Furthermore, not all the illustrated features described herein may be required to implement the methods shown according to the exemplary embodiments. The methods described herein are suitable for implementation in hardware, software, or a combination thereof when executed by a processor.

[0093] Figure 12 This is a block diagram illustrating method 1200 for mobile shopping cart reconciliation before checkout. As described herein, part of method 1200 may be provided by merchant device logic 110 (… Figures 1 to 5 Consumer device logic 112 ( Figures 1 to 4 and Figure 6 ), Payment module 502 ( Figure 5 ) and / or computer system 1100 ( Figure 11 )implement.

[0094] At 1202, data representing the item is obtained by scanning a tag associated with the item by a device associated with the consumer (e.g., consumer device 104, such as a mobile device). As described herein, the tag can be any suitable type of tag. The data may include a description of the item (e.g., brand, model) and / or pricing information. For example, the tag may be an optical tag, such as a scanned barcode, a Quick Response (QR) code, a Universal Product Code (UPC), or, in a particular embodiment, a combination of two or more barcodes, QR codes, and UPC codes. In another exemplary embodiment, the tag is an infrared (IR) tag. In yet another exemplary embodiment, the tag is a radio frequency identification (RFID) scanner that can employ any suitable wireless protocol, such as a contactless protocol (e.g., NFC), a PAN protocol (e.g., BLUETOOTH), or a WLAN protocol (e.g., Wi-Fi).

[0095] In an exemplary embodiment, the data obtained from the labels of similar items (e.g., identical products) is the same. In another exemplary embodiment, each item, including similar items, has a unique label.

[0096] As shown in 1204, the consumer's (e.g., mobile) device tracks the items used for purchase (mobile shopping cart). If the consumer expects to purchase another item, measures 1202 and 1204 are repeated. Measures 1202 and 1204 can be repeated frequently based on the consumer's expectations. The consumer can purchase any practically achievable quantity of items.

[0097] At 1206, the consumer provides payment information. In an exemplary embodiment, the payment information is based on the sum of scanned and tracked items (mobile shopping cart). The payment information may include account information that can be debited by the merchant (e.g., credit, checks, etc.).

[0098] At 1208, the merchant device (e.g., merchant device 108 as described herein) scans items brought to the checkout area by the consumer (which may be brought to the checkout area or into the shopping cart) by scanning the tag associated with the item, and detects the item by a scanner associated with a point-of-sale device (e.g., a physical shopping cart) associated with the merchant.

[0099] At point 1210, the merchant device verifies (reconciles) whether the physical shopping cart matches the mobile shopping cart. If the physical shopping cart matches the mobile shopping cart (yes), payment is accepted and completed in method 1200 as indicated by 1212.

[0100] However, at 1210, if the mobile cart and physical cart do not match (no), corrective actions can be taken as indicated in 1214. For example, the mobile cart and physical cart can be compared to reconcile their accounts. If an item scanned in the physical cart is not present in the mobile cart, the consumer can choose to scan the tag associated with that item using consumer device 104 or scan to select discarding the item. The consumer can also choose to adjust payment as shown in 1206. As another example, if the consumer's physical cart displays fewer items than the mobile cart (e.g., the consumer might return an item to a shelf without indicating that it was returned in the mobile cart), the consumer can adjust the mobile cart.

[0101] After taking corrective action, scan the physical shopping cart again and reconcile it with the mobile shopping cart. If the mobile shopping cart matches the physical shopping cart (yes), then accept payment and complete the process as shown in 1212. Otherwise (no), take corrective action again as shown in 1214.

[0102] Figure 13 This is a block diagram illustrating method 1300 for reconciling payments via a mobile shopping cart after checkout. As described herein, part of method 1300 may be provided by merchant device logic 110 (… Figures 1 to 5 Consumer device logic 112 ( Figures 1 to 4 and Figure 6 ), Payment module 502 ( Figure 5 ) and / or computer system 1100 ( Figure 11 )implement.

[0103] At 1302, data representing the item is obtained by scanning a tag associated with the item by a device associated with the consumer (e.g., consumer device 104, such as a mobile device). As described herein, the tag can be any suitable type of tag. The data may include a description of the item (e.g., brand, model) and / or pricing information. For example, the tag may be an optical tag, such as a scanned barcode, a Quick Response (QR) code, a Universal Product Code (UPC), or, in a particular embodiment, two or more barcodes, QR codes, and UPC codes. In another exemplary embodiment, the tag is an infrared (IR) tag. In yet another exemplary embodiment, the tag is a radio frequency identification (RFID) scanner that can employ any suitable wireless protocol, such as a contactless protocol (e.g., NFC), a PAN protocol (e.g., BLUETOOTH), or a WLAN protocol (e.g., Wi-Fi).

[0104] In an exemplary embodiment, the data obtained from labels used for similar items (e.g., identical products) is the same. In another exemplary embodiment, each item, including similar items, has a unique label.

[0105] As shown in 1304, the consumer's (e.g., mobile) device tracks the items used for purchase (mobile shopping cart). If the consumer expects to purchase another item, measures 1302 and 1304 are repeated. Measures 1302 and 1304 can be repeated frequently based on the consumer's expectations. The consumer can purchase any practically achievable quantity of items.

[0106] At 1306, the merchant device (e.g., merchant device 108 described herein) scans items brought to the checkout area by the consumer (which may be taken to the checkout counter or into the shopping cart) by scanning the tag associated with the item, and detects the item by a scanner associated with a point-of-sale device (e.g., a physical shopping cart) associated with the merchant.

[0107] At point 1308, the merchant device verifies (reconciles) whether the physical shopping cart matches the mobile shopping cart. If the physical shopping cart matches the mobile shopping cart (yes), then at point 1310, the consumer provides payment information. In an exemplary embodiment, the payment information is based on the sum of the scanned and tracked items (mobile shopping cart). The payment information may include account information that can be debited by the merchant (e.g., credit, checks, etc.).

[0108] However, if at 1308 the mobile cart and physical cart do not match (no), corrective actions can be taken as indicated in 1312. For example, the mobile cart and physical cart can be compared to reconcile their contents. If an item scanned in the physical cart is not present in the mobile cart, the consumer can choose to scan the label associated with that item using consumer device 104 or scan to select discarding the item. As another example, if the consumer's physical cart displays fewer items than the mobile cart (e.g., the consumer may have returned an item to the shelf but forgot to indicate that it was returned in the mobile cart), the consumer can adjust the mobile cart.

[0109] After taking corrective action, scan the physical shopping cart again and reconcile it with the mobile shopping cart. If the mobile shopping cart matches the physical shopping cart (yes), proceed with payment at 1310; otherwise (no), take corrective action again as shown in 1312.

[0110] Figure 14This is a block diagram illustrating method 1400 for mobile shopping cart reconciliation performed by a device (e.g., a mobile device) associated with a consumer, wherein payment is made prior to reconciliation between the mobile shopping cart and the physical shopping cart. As described herein, method 1400 may be provided by consumer device logic 112 ( Figures 1 to 4 and Figure 6 ), Payment module 502 ( Figure 5 ) and / or computer system 1100 ( Figure 11 )implement.

[0111] At point 1402, launch the application for the consumer device (mobile shopping cart). If the application is already running, the mobile shopping cart may be reset.

[0112] At point 1404, the consumer initiates an action. This action can be any action involved in the purchase process. Figure 14 In the exemplary embodiments shown, the measures may include, but are not limited to, adding a new item to the mobile shopping cart, removing an item from the mobile shopping cart (and deducting the price), requesting a price check, or signaling that the purchase is complete and continuing to view.

[0113] At 1406, the label associated with the item is scanned. The label can be any suitable type, such as an optical label (e.g., a UPC code, barcode, and / or QR code) or an RFID label (e.g., NFC, WIFI, and / or BLUETOOTH). Once the label is scanned, the selected action is performed. For example, if the selected action is to add the item to the mobile cart (ADD), the item and its price are added to the mobile cart as shown at 1408 (which retains the current payable amount for the scanned item used for purchase). If the selected action is a price check, at 1410, the item's price is displayed on a display associated with the consumer device. If the selected action is to remove (or subtract) the item from the mobile cart, the item is removed from the mobile cart, and its price is subtracted from the total value of the items in the mobile cart. While as... Figure 14 Notes are provided, but as described herein, the tags do not contain the item's price; however, the consumer device can communicate with the merchant device to obtain the price. In an exemplary embodiment, the consumer device can scan multiple tags. Descriptions of the items associated with the tags and the current amount due are maintained by a mobile shopping cart.

[0114] If at point 1404, the consumer instructs them to complete their shopping (DONE), then at point 1414, the consumer device retrieves payment (current amount due) for the items in the mobile shopping cart. In one exemplary embodiment, the consumer enters the payment. In another exemplary embodiment, a payment is selected from a predefined account.

[0115] Optionally, at 1416, the consumer device can signal the merchant device to scan the mobile shopping cart (i.e., acquire the physical shopping cart). In another exemplary embodiment, the merchant device automatically detects when the mobile shopping cart moves to the checkout area to begin scanning the physical shopping cart.

[0116] At 1418, the consumer device receives a signal from the device associated with the merchant indicating whether the mobile shopping cart and the physical shopping cart match. If the mobile shopping cart and the physical shopping cart match (yes), the payment input at 1414 is sent to the merchant device, and the process is completed as indicated at 1420. In an exemplary embodiment, the merchant device sends a signal to the consumer device requesting payment, and the consumer device responds to the request by sending payment data to the merchant device.

[0117] If at point 1418 the mobile shopping cart and physical shopping cart do not match (No), processing returns to point 1404, where the consumer can take corrective action. In an exemplary embodiment, the consumer may be provided with a display of the mobile shopping cart, the physical shopping cart, or both to help the consumer reconcile the mobile and physical carts. For example, if a consumer returns an item to the shelf but forgets to remove it from the mobile shopping cart, the consumer can update the mobile shopping cart. As another example, if a consumer forgets to scan an item in the mobile shopping cart, the consumer can add that item to the mobile shopping cart. In a particular embodiment, a user interface is provided to the consumer that allows them to request assistance.

[0118] After reconciling the mobile and physical shopping carts, consumers can indicate again at step 1404 that they have completed their shopping. At step 1414, a changed payment can be entered (e.g., if the payment amount has changed), and at step 1416, the merchant's device rescans the physical shopping cart. Figure 14 The measures, including but not limited to measures 1404, 1414, 1416 and 1418, may be repeated once or multiple times to complete the transaction.

[0119] Figure 15 This is a block diagram illustrating method 1500 for mobile shopping cart reconciliation performed by a device (e.g., a mobile device) associated with a consumer, wherein payment is made after the mobile shopping cart is reconciled with the physical shopping cart. As described herein, part of method 1400 may be provided by consumer device logic 112 ( Figures 1 to 4 and Figure 6 ), Payment module 502 ( Figure 5 ) and / or computer system 1100 ( Figure 11 ) to be executed. As described herein, part of method 1400 may be executed by consumer device logic 112 ( Figures 1 to 4 and Figure 6 ), Payment module 502 ( Figure 5 ) and / or computer system 1100 ( Figure 11 )implement.

[0120] At point 1502, launch the application for the consumer device (mobile shopping cart). If the application is already running, the mobile shopping cart may be reset.

[0121] At point 1504, the consumer initiates an action. This action can be any action involved in the purchase process. Figure 15 In the exemplary embodiments shown, the measures may include, but are not limited to, adding a new item to the mobile shopping cart, removing an item from the mobile shopping cart (and deducting the price), requesting a price check, or signaling that the purchase is complete and continuing to view.

[0122] At 1506, the label associated with the item is scanned. The label can be any suitable type, such as an optical label (e.g., a UPC code, barcode, and / or QR code) or an RFID label (e.g., NFC, WIFI, and / or BLUETOOTH). Once the label is scanned, the selected action is performed. For example, if the selected action is to add the item to the mobile cart (ADD), the item and its price are added to the mobile cart as shown at 1408 (which retains the current payable amount for the scanned item used for purchase). If the selected action is a price check, at 1410, the item's price is displayed on a display associated with the consumer device. If the selected action is to remove (or subtract) the item from the mobile cart, the item is removed from the mobile cart, and its price is subtracted from the total value of the items in the mobile cart. Although as... Figure 14 Notes are provided, but as described herein, the tags do not contain the item's price; however, the consumer device can communicate with the merchant device to obtain the price. In an exemplary embodiment, the consumer device scans multiple tags. Descriptions of the items associated with the tags and the current amount due are maintained by a mobile shopping cart.

[0123] If at point 1504, the consumer instructs them to complete their shopping (DONE), optionally at point 1514, the consumer device can send a signal to the merchant device to scan the mobile shopping cart (i.e., acquire the physical shopping cart). In another exemplary embodiment, the merchant device automatically detects when the mobile shopping cart moves to the checkout area to begin scanning the physical shopping cart.

[0124] At point 1516, the consumer device receives a signal from the merchant's associated device indicating whether the mobile shopping cart and the physical shopping cart match. If the mobile shopping cart and the physical shopping cart match (yes), at point 1518 the consumer device retrieves the payment (current amount due) for the mobile shopping cart and provides it to the merchant device. In an exemplary embodiment, the consumer device receives a payment request signal from the merchant device, and the consumer device sends a payment in response to the signal. In an exemplary embodiment, the consumer enters the payment. In another exemplary embodiment, a payment is selected from a predefined account.

[0125] If at step 1516 the mobile shopping cart and physical shopping cart do not match (No), processing returns to step 1504, where the consumer can take corrective action. Optionally, the consumer may be provided with a display of the mobile shopping cart, physical shopping cart, or both to help them reconcile their accounts. For example, if a consumer returns an item to the shelf but forgets to remove it from the mobile shopping cart, they can update it. As another example, if a consumer forgets to scan an item in their mobile shopping cart, they can add that item back to it. In certain embodiments, a user interface is provided that allows the consumer to request assistance from the merchant.

[0126] When reconciling the mobile and physical shopping carts, consumers can indicate again at step 1504 that they have completed their purchase. At step 1514, the merchant device rescans the physical shopping cart. If the mobile and physical carts match (yes), the consumer device retrieves the payment at step 1518 and sends it to the merchant device. Figure 15 The measures, including but not limited to measures 1504, 1514 and 1516, may be repeated once or multiple times to complete the transaction.

[0127] Figure 16 This is a block diagram illustrating method 1600 for mobile shopping cart reconciliation performed by a point-of-sale (POS) system associated with a merchant, wherein payment is made prior to the reconciliation of the mobile shopping cart and the physical shopping cart. As described herein, method 1600 may be provided by merchant device logic 110 (… Figures 1 to 5 ) and / or computer system 1100 ( Figure 11 )implement.

[0128] At point 1602, data is received from a consumer device (mobile shopping cart) associated with the consumer. This data represents one or more items the consumer has requested to purchase. In an exemplary embodiment, the data includes the current amount due. In a particular embodiment, the data includes a description and price for each item in the mobile shopping cart.

[0129] At 1604, payment data is obtained from the consumer device. The payment data may include a financial account, such as a checking or credit card account, used to pay for items in the mobile shopping cart. In an exemplary embodiment, the merchant device may request the payment data. In a particular embodiment, the payment data is sent along with the mobile shopping cart data.

[0130] At point 1606, the merchant's device scans the items purchased by the consumer (physical shopping cart). In an exemplary embodiment, the items are contained within the shopping cart; however, those skilled in the art will readily understand that a shopping cart is not necessary, as the consumer can simply carry the items. In an exemplary embodiment, a signal is received from the consumer's device to prompt for scanning. In another exemplary embodiment, scanning is performed automatically in response to the detection of a consumer in a predefined area (e.g., checkout).

[0131] At step 1608, the merchant device compares the mobile shopping cart with the physical shopping cart (reconciliation). If the mobile cart matches the physical shopping cart (yes), the amount owed matches the payment amount, and the payment is accepted. Method 1600 is completed as shown in step 1612.

[0132] If at 1608 the physical shopping cart and mobile shopping cart do not match (no), payment for the item is not accepted (payment refused), and corrective action is taken as shown at 1610. In an exemplary embodiment, corrective action may include displaying the physical contents of the mobile and physical shopping carts to the user to facilitate reconciliation. In another exemplary embodiment, the merchant device sends data representing the physical shopping cart to the consumer device, which may allow the consumer device to assist with reconciliation. The consumer may choose to scan an item into the mobile shopping cart, which is in the physical shopping cart but not in the mobile shopping cart, or remove the item from the mobile shopping cart. The consumer may also choose to remove an item that is in the mobile shopping cart but not in the physical shopping cart (e.g., if the consumer scans an item into the mobile shopping cart, later decides not to purchase the item, but forgets to remove it from the mobile shopping cart). After corrective action is taken, payment information may be updated at 1604 (if the payment amount has changed), and the physical shopping cart may be scanned again at 1606. In an exemplary embodiment, the consumer device may send a signal requesting a rescan of the physical shopping cart. Those skilled in the art will readily understand that measures 1610, 1604, 1606 and 1608 can be repeated as many times as possible on any entity to complete the transaction.

[0133] Figure 17 This is a block diagram illustrating method 1700 for mobile shopping cart reconciliation performed by a POS system associated with a merchant, wherein payment is made after reconciliation of the mobile shopping cart and the physical shopping cart. As described herein, method 1700 may be provided by merchant device logic 110 (… Figures 1 to 5) and / or computer system 1100 ( Figure 11 )implement.

[0134] At point 1702, data is received from a consumer device (mobile shopping cart) associated with the consumer. This data represents one or more items the consumer has requested to purchase. In an exemplary embodiment, the data includes the current amount due. In a particular embodiment, the data includes a description and price for each item in the mobile shopping cart.

[0135] At point 1704, the merchant's device scans the items the consumer is purchasing (the physical shopping cart). In an exemplary embodiment, the items are contained within the shopping cart; however, those skilled in the art will readily understand that a shopping cart is not necessary, as the consumer can simply carry the items. In an exemplary embodiment, a signal is received from the consumer's device to prompt for scanning. In another exemplary embodiment, scanning is performed automatically in response to the detection of a consumer in a predefined area (e.g., checkout).

[0136] At 1706, the merchant device compares the mobile shopping cart with the physical shopping cart (reconciliation). If the mobile shopping cart matches the physical shopping cart (yes), then at 1710, payment data is retrieved from the consumer device. The payment data may include a financial account, such as a checking or credit card account, used to pay for the items in the mobile shopping cart. In an exemplary embodiment, the merchant device may request payment data.

[0137] If at 1706 the physical shopping cart does not match the mobile shopping cart (no), corrective action is taken as shown at 1708. In an exemplary embodiment, corrective action may include displaying the physical contents of the mobile and physical shopping carts to the user for reconciliation. In another exemplary embodiment, the merchant device sends data representing the physical shopping cart to the consumer device, which may allow the consumer device to assist with reconciliation. The consumer may choose to scan an item into the mobile shopping cart, which is in the physical shopping cart but not in the mobile shopping cart, or remove the item from the mobile shopping cart. The consumer may also choose to remove an item in the mobile shopping cart but not in the physical shopping cart (e.g., if the consumer scans an item into the mobile shopping cart, later decides not to purchase the item, but forgets to remove it from the mobile shopping cart). After corrective action is taken, the physical shopping cart is scanned again at 1704. In an exemplary embodiment, the consumer device may send a signal requesting a rescan of the physical shopping cart. Those skilled in the art will readily understand that measures 1706, 1708, and 1704 can be repeated any number of times physically possible to complete the transaction. Once the physical shopping cart and the mobile shopping cart are matched, payment will be processed as shown in 1710.

[0138] In the examples above, the payment is described as being received by the consumer device. However, those skilled in the art will readily understand that the payment can be received by the consumer device, the merchant device, or a portion of the payment can be received by both the consumer device and the merchant device. Therefore, the exemplary embodiments described herein should not be construed as limiting the scope to which device receives the payment.

[0139] The above description is an exemplary embodiment. It is certainly impossible to describe every possible combination of components or methods, but those skilled in the art will recognize that many further combinations and arrangements of the exemplary embodiments are possible. Therefore, this application is intended to include all such changes, modifications, and variations that fall within the spirit and scope of the appended claims, which should be interpreted fairly, legally, and impartially.

Claims

1. A method for self-checkout by a consumer from a merchant retail location, the consumer purchasing a plurality of items from the merchant, wherein, The consumer's mobile cart is reconciled with the merchant's physical cart, the method comprising: acquiring first data representative of a plurality of items by first individually scanning each of the plurality of items by an optical scanner associated with a mobile device associated with a consumer, a first tag associated with each of the plurality of items, wherein the first tag comprises an optical tag, and wherein each of the plurality of items comprises a second tag, the second tag comprising a wireless, non-optical tag, wherein the first data comprises a first total price for the plurality of items to be purchased; based on the first data, acquiring an offer for payment of the plurality of items by the mobile device associated with the consumer prior to approaching a predefined checkout area of the merchant, the mobile cart of the consumer comprising the plurality of items; detecting when the consumer is within the predefined checkout area of a point of sale device associated with the merchant, wherein a wireless, non-optical scanner is coupled to the point of sale device; acquiring second data representative of the plurality of items by the wireless, non-optical scanner by automatically scanning a physical cart containing the plurality of items first scanned by the consumer, the automatic scanning comprising a second collective scan of the plurality of items in the physical cart in a single scan in response to detecting the consumer in the predefined checkout area, the second collective scan acquiring the second data by scanning the second tag on each of the plurality of items, the second data comprising a second total price for the plurality of items to be purchased; acquiring, by the point of sale device, the first data representative of the plurality of items first scanned by the optical scanner associated with the mobile device from the mobile device, wherein the acquiring comprises acquiring the mobile cart of the consumer; verifying, by the point of sale device, whether the first data representative of the plurality of items first scanned by the mobile device associated with the consumer matches the second data representative of the plurality of items second scanned by the point of sale device associated with the merchant, wherein the verifying comprises comparing the mobile cart to the physical cart; in response to verifying that the first data representative of the plurality of items first scanned by the mobile device associated with the consumer matches the second data representative of the plurality of items second scanned by the point of sale device associated with the merchant, accepting payment from the mobile device associated with the consumer by the point of sale device associated with the merchant; in response to determining that the first data does not match the second data, reconciling the first data and the second data, wherein the reconciling comprises: rejecting the offer for payment of the plurality of items from the consumer; displaying to the consumer a graphical user interface on the mobile device associated with the consumer, the graphical user interface comparing a list of items in the mobile cart to a list of items in the physical cart; and allowing the consumer to take corrective action on the graphical user interface to adjust the list of items in the mobile cart until the list of items in the mobile cart matches the list of items in the physical cart; thirdly rescanning, by the point of sale device associated with the merchant, a plurality of the items in the physical cart; verifying that the mobile cart matches the physical cart; and accepting payment from the consumer for a plurality of the items.

2. The method of claim 1, wherein, the labels of similar items selected from a plurality of the items are identical.

3. The method of claim 1, wherein, each of the first plurality of labels and the second plurality of labels has a unique code.

4. The method of claim 1, wherein, the optical label includes a universal product code.

5. The method of claim 1, further comprising: determining, by the mobile device, that the consumer is entitled to a discount as a member of a loyalty program; determining, by the point of sale device, that the consumer is entitled to the discount; and verifying, by the point of sale device, that the first data representing the items scanned by the mobile device associated with the consumer a first time matches the second data representing the items scanned by the point of sale device associated with the merchant a second time, and if so, the payment from the consumer for a plurality of the items is subject to the discount. ​

Images