Abstract: A first identifier associated with a brick-and-mortar store of a merchant and a second identifier associated with a designated physical area within the brick-and-mortar store can be accessed to generate a third identifier that is an identification code scannable by a computing device of a customer. The identification code can be received from the computing device of the customer and a menu of items associated with the merchant can be caused to be presented via the computing device of the customer. An indication of an order for an item of the menu of items associated with the third identifier is received from the computing device of the customer. Payment data associated with a payment instrument of the customer is received from the computing device of the customer, and payment for the order of the item is processed based at least in part on the payment data.

Abstract: Customer-device application sites (e.g., content presented via a progressive web applications) that are accessible via merchant-managed identifiers (e.g., identification codes) are described. An identification of a physical location associated with a merchant can be associated with an identification code. The identification code can be received from a computing device of a customer and, based at least in part on receiving the identification code, merchant data associated with the merchant can be caused to be presented via a web browser of the computing device of the customer. In an example, the merchant data can be presented via the web browser by a progressive web application downloaded onto the computing device of the customer via the web browser. An indication of an input received via the progressive web application can be received by the computing device of the customer and an operation based at least in part on the input can be performed.

Abstract: Techniques described herein are directed to centralized brand asset management. In an example, a first computing device associated with a first point-of-sale (POS) service can receive an instruction to update a web page of a merchant, wherein the instruction to update the web page of the merchant changes a brand asset of the merchant. The first computing device can send a request to update the brand asset of the merchant to a centralized data storage storing one or more brand assets of one or more merchants. The centralized data storage can update the brand asset to an updated brand asset, which can be available to at least a second computing device associated with a second POS service. The second POS service can update a respective POS service feature based on the updated brand asset.

Abstract: Techniques described herein are directed to centralized brand asset management. In an example, a first computing device associated with a first point-of-sale (POS) service can receive an instruction to update a web page of a merchant, wherein the instruction to update the web page of the merchant changes a brand asset of the merchant. The first computing device can send a request to update the brand asset of the merchant to a centralized data storage storing one or more brand assets of one or more merchants. The centralized data storage can update the brand asset to an updated brand asset, which can be available to at least a second computing device associated with a second POS service. The second POS service can update a respective POS service feature based on the updated brand asset.

Abstract: Customer-device application sites (e.g., content presented via a progressive web applications) that are accessible via merchant-managed identifiers (e.g., identification codes) are described. An identification of a physical location associated with a merchant can be associated with an identification code. The identification code can be received from a computing device of a customer and, based at least in part on receiving the identification code, merchant data associated with the merchant can be caused to be presented via a web browser of the computing device of the customer. In an example, the merchant data can be presented via the web browser by a progressive web application downloaded onto the computing device of the customer via the web browser. An indication of an input received via the progressive web application can be received by the computing device of the customer and an operation based at least in part on the input can be performed.

Abstract: Using combined eCommerce and brick-and-mortar data to produce intelligent recommendations for web page operation is described. In an example, a request to access an eCommerce GUI presented on behalf of a merchant can be received from a device operable by a viewer. Brick-and-mortar point-of-sale (POS) transaction data associated with one or more customers that transact with the merchant or one or more other merchants that utilize the payment processing service to process brick-and-mortar POS transactions can be used to determine a variation of the eCommerce GUI presented on behalf of the merchant to present to the viewer. Instructions for rendering the variation of eCommerce GUI can be sent to the device operable by the viewer.

Abstract: Techniques described herein are directed to centralized brand asset management. In an example, a first computing device associated with a first point-of-sale (POS) service can receive an instruction to update a web page of a merchant, wherein the instruction to update the web page of the merchant changes a brand asset of the merchant. The first computing device can send a request to update the brand asset of the merchant to a centralized data storage storing one or more brand assets of one or more merchants. The centralized data storage can update the brand asset to an updated brand asset, which can be available to at least a second computing device associated with a second POS service. The second POS service can update a respective POS service feature based on the updated brand asset.

Abstract: Customized web page development based on brick-and-mortar point-of-sale (POS) information is described. In an example, transaction data associated with POS transaction(s) between a merchant and customers can be received. The POS transaction(s) can be completed via a POS device at a brick-and-mortar store of the merchant. A request to create a web page associated with an online store of the merchant can be received, and creation of the web page can be customized based at least in part on the transaction data associated with the POS transactions between the merchant and the customers. That is, brick-and-mortar POS transaction data can be used to customize creation of the web page.

Abstract: Using combined eCommerce and brick-and-mortar data to produce intelligent recommendations for web page operation is described. In an example, a request to access an eCommerce GUI presented on behalf of a merchant can be received from a device operable by a viewer. Brick-and-mortar point-of-sale (POS) transaction data associated with one or more customers that transact with the merchant or one or more other merchants that utilize the payment processing service to process brick-and-mortar POS transactions can be used to determine a variation of the eCommerce GUI presented on behalf of the merchant to present to the viewer. Instructions for rendering the variation of eCommerce GUI can be sent to the device operable by the viewer.

Abstract: Using combined eCommerce and brick-and-mortar data to produce intelligent recommendations for website editing is described. In an example, brick-and-mortar transaction data associated with a first merchant and second merchant(s) can be compared to identify a subset of the second merchant(s) that are similar to the first merchant. Performance metrics associated with eCommerce graphical user interfaces (GUIs) presented on behalf of the subset of the second merchant(s) can be determined based on aggregated transaction data associated with eCommerce point-of-sale (POS) transactions associated with the subset of the second merchant(s) and a recommendation based on content, a layout, and/or a design of at least a portion of the eCommerce GUIs can be generated. The recommendation can be sent to a computing device operable by the first merchant for use in creating or editing an eCommerce GUI to be presented on behalf of the first merchant.