# US 2020/0394635 A1 · Data Structure Analytics for Real-time Recommendations > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2020/0394635 A1 - Document ID: US20200394635A1 - Status: Published application - Kind: A1 - Application number: 17/008,530 - Filed: 2020-08-31 - Published: 2020-12-17 - Earliest claimed: 2015-09-30 - Assignees: Square, Inc. - Applicants: Square, Inc. - Inventors: Mathew Wilson; Derrick Huhn; Jonathan Andrew Wolter; Ryder Moody; Dan Simms - Web page: https://patentgrep.com/patent/US20200394635A1 ## CPC - G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit} - G06Q 20/102: {Bill distribution or payments} - G06Q 20/12: specially adapted for electronic shopping systems - G06Q 20/20: Point-of-sale [POS] network systems - G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction} - G06Q 20/4016: {involving fraud or risk level assessment in transaction processing} - G06Q 20/405: {Establishing or using transaction specific rules} - G06Q 30/0631: {Recommending goods or services} - G06Q 30/0635: {replenishment orders; recurring orders} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Techniques and arrangements for analyzing previous tickets of a customer at different merchants—specifying interactions of the customer at the different merchants—to determine subsequent recommendations to send to a particular merchant in real-time when the customer is located at the particular merchant. Other techniques and arrangements facilitate annotation of merchant tickets by the merchants to enrich the data maintained by the tickets and, in some instances, to enhance the described real-time recommendations. Still other techniques and arrangements create a merchant ticket for recording interactions between a merchant and customer upon the customer creating a reservation at the merchant for a specified future time, or being added to a waitlist of the merchant. Upon the customer arriving at the merchant proximate to the specified future time, the merchant may use the created ticket to track items ordered by the merchants, track tenders used to pay for items, and the like. ## Claims ### Claim at position 1 1-20. (canceled) ### Claim 21 A method comprising: obtaining, by one or more servers associated with a payment service and at a first time, a first data structure generated in association with a first engagement between a customer and a merchant to track one or more interactions between the customer and the merchant, obtaining, by the one or more servers and at a second time subsequent to the first time, an indication that a second data structure has been generated in association with a second engagement between the customer and one of the merchant or another merchant; analyzing, by the one or more servers, the first data structure and the second data structure; generating, by the one or more servers, one or more recommendations based on the analyzing; and surfacing, by the one or more servers, the one or more recommendations. ### Claim 22 (depends on 21) The method as claim 21 recites, wherein the first data structure is obtained from a first point-of-sale (POS) device associated with the merchant and the second data structure is received from a second POS device of the merchant, wherein the first POS device is located in a first section of a restaurant associated with the merchant and the second POS device is located in a second section of the restaurant. ### Claim 23 (depends on 22) The method as claim 22 recites, wherein the second data structure comprises a synchronized data structure created from data received from the first POS device and the second POS device. ### Claim 24 (depends on 21) The method as claim 21 recites, wherein the first data structure indicates that the customer has been added at a first time to a reservation associated with the merchant, wherein the second data structure indicates that the customer has ordered, at a second time, items or services from the other merchant, wherein an application executing on a device associated with a customer displays a limited set of a plurality of items and services available at the other merchant from which to order, and wherein the one or more recommendations include a recommendation that a first payment associated with the first data structure and a second payment associated with the second data structure be aggregated. ### Claim 25 (depends on 21) The method as claim 21 recites, wherein the first data structure is obtained from a merchant device of the merchant and indicates that the customer has been added at a first time to a waitlist of the merchant, wherein the second data structure is obtained from another merchant device of the other merchant remote from the first merchant device and indicates that the customer has ordered, at a second time, at least one first item from a limited set of items available at the second merchant, and wherein the one or more recommendations include a recommendation that the customer order at least one second item of a set of second items, wherein the set of second items comprises a limited set of a plurality of items available at the merchant. ### Claim 26 A system comprising: one or more processors; one or more non-transitory computer-readable media storing instructions executable by the one or more processors, wherein the instructions program the one or more processors to perform actions comprising: receiving, by one or more servers associated with a payment processing service and from a first point-of-sale (POS) device of a first merchant, a first data structure for recording first interactions between a customer and the first merchant, wherein the first data structure indicates that the customer has been added at a first time to a waitlist associated with the first merchant; receiving, by the one or more servers associated with the payment processing service and from a second POS device, a second data structure, wherein the second data structure indicates that the customer has ordered, at a second time, items or services; analyzing, by the one or more servers, the first data structure and the second data structure; generating, by the one or more servers, a recommendation that a first payment associated with the first data structure and a second payment associated with the second data structure be aggregated; and surfacing, by the one or more servers, the recommendation on at least one of the first POS device or the second POS device. ### Claim 27 (depends on 26) The system as claim 26 recites, wherein the second POS device comprises a second POS device of the first merchant in a same merchant establishment as the first POS device. ### Claim 28 (depends on 27) The system as claim 27 recites, wherein the first merchant comprises a restaurant, and wherein the second POS device is located at a bar within the restaurant. ### Claim 29 (depends on 26) The system as claim 26 recites, wherein the second POS device is associated with a second merchant, wherein the recommendation comprises a first recommendation, and the operations further comprising: responsive to receiving the first data structure, generating, by the one or more servers, a second recommendation that the customer visit an establishment of the second merchant while waiting. ### Claim 30 (depends on 29) The system as claim 29 recites, wherein the second recommendation is based at least in part on determining, by the one or more servers, a location of the first merchant and a location of the second merchant. ### Claim 31 A method comprising: receiving, by one or more servers associated with a payment service and from a first merchant device associated with a first merchant, a first data structure for recording first interactions between a customer and the first merchant, wherein the first data structure indicates that the customer has been added at a first time to a reservation of the first merchant; receiving, by the one or more servers and from a second merchant device remote from the first merchant device, a second data structure for recording second interactions of the customer during a transaction of the customer, wherein the second data structure indicates that the customer has ordered, at a second time, at least one first item of a limited set of first items available at the second merchant; analyzing, by the one or more servers, the first data structure and the second data structure; generating, by the one or more servers, a recommendation that the customer order at least one second item of a limited set of second items, wherein the limited set of second items comprises a subset of a plurality of items offered for sale by the first merchant; and surfacing, by the one or more servers, the recommendation on the second merchant device. ### Claim 32 (depends on 31) The method as claim 31 recites, wherein the second data structure further indicates content of a free-form note documenting a verbal exchange that occurred between an employee and the customer during the transaction, wherein the recommendation comprises a first recommendation, and the method further comprising: generating, by the one or more servers, a second recommendation based at least in part on the content of the free-form note. ### Claim 33 (depends on 32) The method as claim 32 recites, wherein the free-form note indicates a sentiment of the customer as perceived by the employee associated with the transaction. ### Claim 34 (depends on 31) The method as claim 31 recites, wherein the second merchant device is associated with the first merchant, and wherein the transaction occurs at a same establishment at which the first merchant device is located. ### Claim 35 (depends on 34) The method as claim 34 recites, wherein the first merchant comprises a restaurant, and wherein the second merchant device is located at a bar within the restaurant. ### Claim 36 (depends on 31) The method as claim 31 recites, further comprising: receiving, by the one or more servers, an updated second data structure indicating user input selecting at least one second item to order; and transmitting, by the one or more servers to a kitchen display system associated with the first merchant and before the customer has been seated at the first merchant, instructions regarding preparation of the at least one second item. ### Claim 37 (depends on 31) The method as claim 31 recites, wherein generating the recommendation is based at least in part on one or more historical data structures associated with the customer. ### Claim 38 (depends on 31) The method as claim 31 recites, wherein generating the recommendation is based at least in part on at least one of the first time or the second time. ### Claim 39 (depends on 31) The method as claim 31 recites, further comprising: providing, by the one or more servers to the second merchant device, multiple predefined tags in a merchant application executing on the second merchant device, each tag indicating a particular interaction with the customer, wherein the second data structure further indicates a tag of the multiple predefined tags, and wherein generating the recommendation is based at least in part on the tag. ### Claim 40 (depends on 31) The method as claim 31 recites, further comprising: receiving, by the one or more servers, an updated second data structure indicating user input representing a selection of at least one second item to order; and transmitting, by the one or more servers to the first merchant, an indication of the user input selecting the at least one second item.