Square, Inc.

Cynthia Lobb

John Joseph LaBanca, Jr

Roger Reyelts

Travis Schmeisser

Roshan Jhunja

Christopher Woodyard

Brad Seiler

Noah Batterson

This disclosure describes, in part, techniques for integrating functionality across multiple applications. For instance, an electronic device may operate an application in a first mode of operation, wherein the first mode of operation is associated with a first type of business. Based at least in part on operating the application in the first mode of operation, the electronic device may provide a first user interface that includes one or more first input options associated with the first type of business. The electronic device may then receive input associated with operating the application in a second mode operation, wherein the second mode of operation is associated with a second type of business. Based on the input, the electronic device may operate the application in the second mode of operation, which includes providing a second user interface that includes one or more second input options associated with the second type of business.

Integrating functionality across multiple applications

This disclosure describes, in part, techniques for analyzing and updating merchants' data structures. For instance, a payment service may store data structures associated with merchants, where each data structure indicates items that a respective merchant offers for acquisition. The payment service may then analyze at least a first data structure to determine first items offered for acquisition by a first merchant and a second data structure to determine second items offered for acquisition by a second merchant. Based on the first items and the second items, the payment service may determine an item to recommend to the second merchant. The payment service may then generate and send a message to a merchant device of the second merchant, where the message recommends that the second merchant offer the item for acquisition. In some instances, the first merchant and the second merchant are each associated with a specific type of business.

Systems for analyzing and updating data structures

This disclosure describes techniques for performing intelligent rebalancing of items between physical locations of merchants and replenishment of items for physical locations of merchants. The techniques include the use of a payment service that provides various services for merchants and obtains information associated with transactions of the merchants, employees of the merchants, and vendors of the merchants. Harnessing the information and knowledge associated with the variety of merchants, the payment service may intelligently automate the rebalancing items between physical locations, such as by moving items from a physical location of the merchant with a lower rate of sale to another physical location of the merchant with a higher rate of sale. Similarly, the payment service may intelligently automate replenishment of items by generating orders to have vendors fulfill needed quantities of items at locations of merchants.

Intelligent inventory management

Techniques for effectuating a rollback to a previous version of a database (e.g., a catalog or inventoy database) associated with an entity are described. A payment processing service may receive instructions to modify a database. The payment processing service may modify the database based at least partly on the instructions and add an entry to a modification log. Each entry in the modification log may correspond to a previous version of the database and the entry may correspond to a new version of the database after the modification to the database. The payment processing service may determine that the modification to the database is likely to warrant a rollback and may effectuate the rollback by determining a previous entry of the modification log that precedes the entry and adding a new entry to the modification log that corresponds to the previous version of the database associated with the previous entry.

Version recall for computerized database management

Techniques for effectuating a rollback to a previous version of a catalog associated with an entity are described. A payment processing service may receive instructions to modify a catalog associated with an entity. The payment processing service may modify the catalog based at least partly on the instructions and add an entry to a modification log. Each entry in the modification log may correspond to a previous version of the catalog and the entry may correspond to a new version of the catalog after the modification to the catalog. The payment processing service may determine that the modification to the catalog is likely to warrant a rollback and may effectuate the rollback by determining a previous entry of the modification log that precedes the entry and adding a new entry to the modification log that corresponds to the previous version of the catalog associated with the previous entry.

Growing community of inventors

Marietta, GA, United States of America

Cynthia Lobb