Generating an online storefront

Information

  • Patent Grant
  • 12147958
  • Patent Number
    12,147,958
  • Date Filed
    Monday, February 14, 2022
    2 years ago
  • Date Issued
    Tuesday, November 19, 2024
    a month ago
Abstract
Method, systems, and apparatus for generating an online storefront for a merchant, comprising receiving, by an inventory management system (IMS) and from a point of sale (POS) device, an indication of a user input to a first graphical user interface (GUI) representing a merchant request to generate the online storefront comprising one or more second GUIs; generating and activating the online storefront; retrieving inventory data associated with the merchant; transmitting, to a customer device, a second GUI that includes item information; receiving a customer request to purchase an item; transmitting, to a payment service system (PSS) that manages the IMS, the customer request; receiving an indication that the payment has been processed by the PSS; receiving a command from the PSS to update the inventory data; receiving a request from the POS device to deactivate the online storefront; and removing the customer device's access to the online storefront.
Description
TECHNICAL FIELD

This disclosure relates to generating an online storefront for merchants.


BACKGROUND

A merchant operating a brick and mortar store can service customers using a point of sale (POS) system. The POS system can include a physical electronic cash register or dedicated POS hardware. When customers want to purchase items for sale from the store, the merchant uses the POS system to record and complete the transaction. The POS system can also manage inventory for the store, e.g., track quantities of items for sale.


In a conventional point-of-sale electronic credit card transaction, the transaction is authorized and captured over a network connection. In the authorization stage, a physical credit card with a magnetic stripe is swiped through a merchant's magnetic card reader, e.g., as part of a point-of-sale device. A payment request is sent electronically from the magnetic card reader to a credit card processor. The credit card processor routes the payment request to a card network, e.g., Visa or Mastercard, which in turn routes the payment request to the card issuer, e.g., a bank. Assuming the card issuer approves the transaction, the approval is then routed back to the merchant. In the capture stage, the approved transaction is again routed from the merchant to the credit card processor, card network and card issuer, and the payment request can include the cardholder's signature (if appropriate). The capture stage can trigger the financial transaction between the card issuer and the merchant, and optionally creates a receipt. There can also be other entities, e.g., the card acquirer, in the route of the transaction. Debit card transactions have a different routing, but also require swiping of the card.


Occasionally, the merchant chooses to operate an online ecommerce store in addition to the brick and mortar store. The merchant can create a commerce web site and manually enter inventory data from the brick and mortar store. The merchant can program the web site to process online payment transactions.


SUMMARY

A merchant can operate a brick and mortar store through a point of sale system. The point of sale system provides an interface for the merchant to manage inventory, e.g., add, modify, or remove items for sale. The interface can provide an option to generate an online storefront based on the existing inventory data through a single action, e.g., checking a box. For example, the merchant can check a button that causes the point of sale system to generate an online storefront. Customers can conduct transactions from the online storefront, and the merchant can be notified of the transactions through the point of sale system.


In one aspect, a method of generating a storefront for a merchant, comprising: receiving a single indication to generate an online storefront for a point of sale system of the merchant, where the point of sale system includes inventory data of a plurality of items for sale; identifying the plurality of items for sale from the inventory data from point of sale system; and generating one or more resources for each item of the plurality of items for sale, where the one or more resources include details of the item, where the details are obtained from the inventory data, where the one or more resources are accessible from a web domain.


Implementations can include one or more of the following features. The details of the item include one or more of the following: a price, a description, a quantity, or a title. The one or more resources include executable instructions that enable the customer to interact with the item through the web domain. The executable instructions enable the customer to reserve or purchase the item. The instructions, when executed on a device, comprise the following operations: receiving user input at the device from the customer, where the user input selects one or more items for sale, and where the user input includes payment information for the one or more items; submitting, to a payment processing system, a request for a transaction that includes the payment information; receiving an authentication of the transaction from the payment processing system; and in response to receiving the authentication, presenting an indication of the authentication on a display of the device. Upon receiving the authentication, the inventory data at the point of sale system is updated. In response to receiving the authentication, further comprising: determining, at the payment processing system, an address of the customer; and processing, at the payment processing system, the transaction based on the address. Processing the transaction based on the address comprises sending the address to a third party fulfillment service, which sends the one or more items to the address. In response to receiving the authentication, further comprising: determining a quantity of the one or more items is under a limit in the inventory data of the point of sale system; notifying the merchant of the determination. The instructions, when executed, display an option for the item to be picked up in store or to be delivered. The single indication is received through a selected button that is displayed on a user interface, where the user interface is running on a device of the customer or the merchant. The instructions, when executed, display suggestions for popular inventory based on transactions with the point of sale system.


Advantages may include one or more of the following. A merchant can create an online storefront based on existing inventory data with a single action. The online storefront can provide a complete checkout process for each item in the inventory data. The merchant can sell to online customers as well as customers in the brick and mortar store, which can create a new revenue stream. Inventory data can be synchronized across both the online storefront and the brick and mortar store. Therefore, the merchant does not have to separately maintain inventory data for the online storefront and the brick and mortar store.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic illustration of an example payment system architecture of a point of sale system.



FIG. 2 is a schematic illustration of an example user interface for generating an online storefront.



FIG. 3 is a flow chart of an example process of generating an online storefront.



FIGS. 4A-B are schematic illustrations of example user interfaces of a generated online storefront.



FIG. 5 is a block diagram of an exemplary architecture of a mobile device capable of serving as a point of sale.





Like reference numbers and designations in the various drawings indicate like elements.


DETAILED DESCRIPTION


FIG. 1 is a schematic illustration of the architecture of an example point of sale system 100. The overall system 100 includes a merchant device 104, e.g., a mobile device or a point of sale system, connected to a network, e.g., the Internet 106. The mobile device is a mobile computing device, i.e., a hand-held computing device, capable of running a customer or a merchant application. For example, the mobile device can be a smartphone, tablet, a desktop computer, a laptop computer, dedicated point of sale hardware, or other data processing apparatus.


A payment processor operates a payment service system 108. The payment processor processes transactions conducted at the merchant device 104. The merchant device 104 can receive card information, e.g., through a card swipe, for the transaction at a card reader 103. The merchant device 104 communicates with the payment service system 108 using the network 106. The payment service system 108 includes one or more servers 112, at least some of which can handle secure transactions (e.g., using a secure server), to process all transactions with the merchant device 104. In general, servers 112 can store public merchant information such as the merchant's address or phone number. The servers 112 also handle secure information such as credit card numbers, debit card numbers, bank accounts, user accounts, user identifying information or other sensitive information.


The payment service system 108 can communicate with a computer system 116 of a card payment network, e.g., Visa or MasterCard. The payment service system 108 can communicate with a computer system 116 over the same network 106 used to communicate with the mobile device 104, or over a different network. The computer system 116 of the card payment network can communicate in turn with a computer system 118 of a card issuer, e.g., a bank. There can also be computer systems of other entities, e.g., the card acquirer, between the payment service system 108 and the card issuer.


Eventually, in order to receive funds from the transaction, the merchant will need to enter financial account information into the payment service system sufficient to receive funds. For example, in the case of a bank account, the merchant can enter the bank account number and routing number. The merchant's financial account can also be associated with a credit card account or another third party financial account. In addition, in some implementations, if the merchant has not entered the financial account information, the payment service system 108 can hold the received funds until the financial account information is provided.


Although FIG. 1 describes communicating with a card payment network using a payment card, the customer and the merchant can conduct a transaction using another form of payment, e.g., automated clearing house (ACH) payments, gift cards, loyalty purchases, or other payment mechanisms from a third party.


The payment service system 108 can also include an inventory management system 120. The inventory management system 120 manages items for sale by the merchant, e.g., using one or more databases. For example, the inventory management system 120 can store details for each item. The details can include a title, a price, a picture, quantity, a category, or a description of the item. In some implementations, the inventory management system 120 stores whether the item is available in store only, online only, or both. Therefore, the payment service system 108 can not only process financial transactions but can also manage inventory data for the merchant.


Through the inventory management system 120, the merchant can add, remove, or modify the inventory data. The merchant can use merchant device 104 or another device, e.g., a desktop device connected to the inventory management system 120. For example, the merchant can execute a merchant application on the merchant's mobile device. The merchant can add an item to the inventory data through an interface of the merchant application. The merchant application can send, e.g., through the Internet 106, the added item to the inventory management system 120, which stores the added item in one or more databases. In some other implementations, the merchant accesses, e.g., using a desktop computer, a web site that is hosted by the payment service system 108 and the merchant manages the inventory data through the web site.


The system can also include a customer device 110. The customer device 110 can interface with the payment service system 108 through the Internet 106. The customer device 110 can be a mobile device, a desktop device, or other data processing apparatus. For example, the customer device 110 can be used by a customer at home to make an online purchase using the payment service system 108.



FIG. 2 is a schematic illustration 200 of an example user interface 202 for generating an online storefront. A merchant can use the user interface 202 to configure settings of its inventory management system, e.g., the inventory management system 120 described above in reference to FIG. 1. The user interface 202 can be presented by a mobile device, e.g., the mobile device described above in reference to FIG. 1, or another electronic device. For example, the user interface 202 can display a single button 204 that, when activated, e.g., is “ON,” generates an online storefront for the merchant. This will be described further below in reference to FIG. 3.


The user interface 202 can also present other settings 206 of the merchant. For example, the merchant can access support links, view or edit items for sale in the inventory, view or edit the merchant's address, and view past sales made to different customers.



FIG. 3 is a flow chart 300 of an example process of generating an online storefront. For convenience, the process will be described with respect to a system, e.g., the inventory management system as described above in reference to FIG. 1, having one or more computing devices that perform the process.


The system receives a single indication to generate an online storefront (step 302). The single indication can be one activated button, e.g., as described above in reference to FIG. 2. In some implementations, the single indication is a user selection, e.g., input from a merchant, of a button that is displayed on a user interface of a merchant's mobile device. In particular, the button can be a check-box with “Enable Virtual Storefront” as corresponding text. The mobile device can send an indication of the user selection to an inventory management system. As described above, the single indication can be received from a merchant application running on a merchant's point of sale device, e.g., an iPad used to conduct financial transactions, or a separate device that accesses inventory data of a merchant.


The system identifies the inventory from the point of sale system (step 304). For example, the system accesses an internal database of the point of sale system that stores the inventory data of the merchant. In particular, a merchant can be logged into the merchant application running on the mobile device. The mobile device can send, to the inventory management system, a login identification of the merchant along with the single indication. The inventory management system can identify the merchant's inventory based on the login identification of the merchant.


The system generates one or more resources for each item in the merchant's inventory (step 306). The system can also generate resources for groupings of items, e.g., a home page resource, a resource of most frequently purchased items, and/or a resource of items within a category. Categories can either be available online exclusively, in store exclusively, both online and in store, or only to a manager. Each resource can be accessible from a web domain. For example, the inventory management system can create, publish, and manage the web domain. The web domain can be a subdomain of a domain owned by the inventory management system. A customer can access the resource, e.g., through an Internet browser, from any device having an Internet connection.


Each generated resource includes details of one or more items in the inventory. The details can be obtained from the internal database that stores the merchant inventory data. The resource can also include executable instructions that enable the advertised item to be purchased by a customer. For example, the resource can be generated from a template including code that can process transactions based on user input, e.g., the instructions can submit financial information entered by a customer to a payment processing system. An example resource is described further below in reference to FIGS. 4A-B.


Each generated resource can also include a standard design that displays the details of the one or more items. For example, the resources can be generated from a template including style sheets, e.g., Cascading Style Sheets, or other design code.


After generating the resources, the merchant can customize the online storefront. For example, the system can provide an interface to customize appearance of the generated resources. The merchant can change background color, font types, font colors, design themes, or other design elements specified in the resources. The system can also provide an interface to display or hide one or more items or categories of the inventory data.


In some implementations, inventory data is modified after the online storefront is generated. For example, the merchant can add a new item using the merchant application to the inventory data after generating the online storefront. In this case, the system, upon receiving instructions to add the new item, e.g., through the merchant application, generates a new resource for the new item and publishes the new resource on the Internet. Therefore, items in the online storefront are synchronized with items in the inventory data.


In some implementations, the system receives a separate indication to deactivate the online storefront. For example, the merchant can deactivate the button described above in reference to FIG. 2. The system then removes public access to the online storefront, e.g., by removing the merchant's subdomain. In some implementations, the system maintains the storefront even though the storefront is not online, e.g., the system generates resources based on the inventory data but does not publish the resources. Therefore, a merchant can quickly republish the online storefront if desired.



FIG. 4A is an example user interface of a home page 400 of a merchant's online storefront. The storefront can display a name 402, an image 408, and contact information 402 of the merchant. The storefront can also display items in a shopping cart 406, 410. For example, the home page can display multiple items in the inventory of the merchant, e.g., recommended items 412, and a description for each item, e.g., description 414. The multiple items can be sorted by popularity. The popularity can be tracked by the inventory management system. For example, if one or more items sell more quickly than other items, the inventory management system can promote the one or more popular items on the online storefront. The home page can be displayed through a browser running on a computing device. A customer browsing the home page can access particular listings, e.g., by clicking on a link.



FIG. 4B is an example user interface 416 of a listing of an item in the merchant's inventory. The listing is a resource generated from the inventory management system. For example, the listing can display a picture 422, a title 420, a price 418, and a description 424 of the item. The listing can also display a remaining quantity 426 as stored in the inventory. A customer can view the listing through a computing device. The customer can purchase the item through the listing using purchase links displayed on the listing, e.g., the “Add to Cart” button 410. After adding to a cart, the customer can checkout and enter his or her financial information, e.g., a credit card number, through form inputs. In some implementations, the financial information is auto-filled by the payment service system. For example, the payment service system can already have stored the customer's financial information. The customer can also select whether the item will be picked up at the merchant store or delivered to the customer. Upon receiving user input to purchase the item, the computing device can submit the input to a payment processing system. The payment processing system can send an authentication of the transaction to the computing device. The computing device can display an indication of the authentication to the customer, e.g., display a successful purchase message. In some implementations, in addition to providing the item for purchase, the system provides the item for reservation.


In some implementations, after the payment processing system sends the authentication of the transaction to the computing device, the payment processing system updates inventory data of the merchant through the inventory management system. For example, the payment processing system can send, to the inventory management system, a command to decrement a stock quantity of the item after successfully processing payment information from the customer. As a result, the merchant's inventory is up to date. The inventory can be properly reflected in the merchant's brick and mortar store and the online storefront because both pull inventory data from the inventory management system. In some implementations, the payment processing system determines stock of the item is under a predetermined limit in the inventory and notifies the merchant of the low stock, e.g., through an email or in a dashboard of the merchant application.


In some implementations, after the customer purchases the item, the payment processing system determines an address of the customer. The customer could have entered his or her address before paying for it. Or, the customer can have an account with the payment processing system, and the account can be associated with the customer's address. For example, if the customer is known to the payment processing system during checkout, e.g., through a login, the payment processing system can then use the customer's stored financial information and address for delivery. In another example, the payment processing system can determine an address that is closest to the customer's current physical position, e.g., by receiving a Global Positioning Satellite (GPS) location from the customer device. The payment processing system can process the transaction based on the address. For example, the payment processing system can send the address to a third party fulfillment service, which sends the purchased item to the customer. Therefore, the merchant will not have access to the customer's address, thereby allowing the customer to maintain privacy. In some implementations, the payment processing system notifies the third party fulfillment service if one or more items are low in stock.


In some implementations, the customer can choose to share the address with the merchant, e.g., the customer shares the address through a setting in an account profile. The payment processing system can then forward the customer's address to the merchant upon successfully processing the customer's payment information.



FIG. 5 is a block diagram of an exemplary architecture of a mobile device capable of serving as a point of sale. Architecture 500 can be implemented in any device for generating the features described in reference to FIGS. 1-4, including but not limited to portable or desktop computers, smart phones and electronic tablets, television systems, game consoles, kiosks and the like. Architecture 500 can include memory interface 502, data processor(s), image processor(s) or central processing unit(s) 504, and peripherals interface 506. Memory interface 502, processor(s) 504 or peripherals interface 506 can be separate components or can be integrated in one or more integrated circuits. The various components can be coupled by one or more communication buses or signal lines.


Sensors, devices, and subsystems can be coupled to peripherals interface 506 to facilitate multiple functionalities. For example, motion sensor 510, light sensor 512, and proximity sensor 514 can be coupled to peripherals interface 506 to facilitate orientation, lighting, and proximity functions of the device. For example, in some implementations, light sensor 512 can be utilized to facilitate adjusting the brightness of touch surface 546. In some implementations, motion sensor 510 (e.g., an accelerometer, gyros) can be utilized to detect movement and orientation of the device. Accordingly, display objects or media can be presented according to a detected orientation (e.g., portrait or landscape).


Other sensors can also be connected to peripherals interface 506, such as a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities.


Location processor 515 (e.g., GPS receiver) can be connected to peripherals interface 506 to provide geo-positioning. Electronic magnetometer 516 (e.g., an integrated circuit chip) can also be connected to peripherals interface 506 to provide data that can be used to determine the direction of magnetic North. Thus, electronic magnetometer 516 can be used as an electronic compass.


Camera subsystem 520 and an optical sensor 522, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips.


Communication functions can be facilitated through one or more communication subsystems 524. Communication subsystem(s) 524 can include one or more wireless communication subsystems. Wireless communication subsystems 524 can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. Wired communication system can include a port device, e.g., a Universal Serial Bus (USB) port or some other wired port connection that can be used to establish a wired connection to other computing devices, such as other communication devices, network access devices, a personal computer, a printer, a display screen, or other processing devices capable of receiving or transmitting data. The specific design and implementation of the communication subsystem 524 can depend on the communication network(s) or medium(s) over which the device is intended to operate. For example, a device may include wireless communication subsystems designed to operate over a global system for mobile communications (GSM) network, a GPRS network, an enhanced data GSM environment (EDGE) network, 802.x communication networks (e.g., WiFi, WiMax, or 3G networks), code division multiple access (CDMA) networks, and a Bluetooth™ network. Communication subsystems 524 may include hosting protocols such that the device may be configured as a base station for other wireless devices. As another example, the communication subsystems can allow the device to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP protocol, HTTP protocol, UDP protocol, and any other known protocol.


Audio subsystem 526 can be coupled to a speaker 528 and one or more microphones 530 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.


I/O subsystem 540 can include touch controller 542 and/or other input controller(s) 544. Touch controller 542 can be coupled to a touch surface 546. Touch surface 546 and touch controller 542 can, for example, detect contact and movement or break thereof using any of a number of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch surface 546. In one implementation, touch surface 546 can display virtual or soft buttons and a virtual keyboard, which can be used as an input/output device by the user.


Other input controller(s) 544 can be coupled to other input/control devices 548, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of speaker 528 and/or microphone 530.


In some implementations, device 500 can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, device 500 can include the functionality of an MP3 player and may include a pin connector for tethering to other devices. Other input/output and control devices can be used.


Memory interface 502 can be coupled to memory 550. Memory 550 can include high-speed random access memory or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, or flash memory (e.g., NAND, NOR). Memory 550 can store operating system 552, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. Operating system 552 may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system 552 can include a kernel (e.g., UNIX kernel).


Memory 550 may also store communication instructions 554 to facilitate communicating with one or more additional devices, one or more computers or servers. Communication instructions 554 can also be used to select an operational mode or communication medium for use by the device, based on a geographic location (obtained by the GPS/Navigation instructions 568) of the device. Memory 550 may include graphical user interface instructions 556 to facilitate graphic user interface processing; sensor processing instructions 558 to facilitate sensor-related processing and functions; phone instructions 560 to facilitate phone-related processes and functions; electronic messaging instructions 562 to facilitate electronic-messaging related processes and functions; web browsing instructions 564 to facilitate web browsing-related processes and functions and display GUIs; media processing instructions 566 to facilitate media processing-related processes and functions; GPS/Navigation instructions 568 to facilitate GPS and navigation-related processes; camera instructions 570 to facilitate camera-related processes and functions; and instructions 572 for serving as a point of sale. The memory 550 may also store other software instructions for facilitating other processes, features and applications, such as applications related to navigation, social networking, location-based services or map displays.


Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory 550 can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.


Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a non-transitory computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).


The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.


The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.


A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language resource), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.


The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).


Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.


To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending resources to and receiving resources from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.


Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.


The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.


A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.


While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.


Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.


In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

Claims
  • 1. A server computing device associated with an inventory management system, the server computing device comprising: one or more processors managed by the inventory management system; andone or more non-transitory computer-readable media coupled to the one or more processors having instructions stored thereon, which, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, at the inventory management system and from a point-of-sale (POS) device of a merchant via a merchant application executing on the POS device, an indication of a first single user input to a toggle switch of a first graphical user interface (GUI) of the merchant application presented on a display of the POS device, wherein the first single user input comprises a first merchant request to generate an online storefront comprising one or more second GUIs through which online transactions with customers can be conducted;responsive to receiving the indication of the first single user input: generating and activating the online storefront comprising at least one of the one or more second GUIs; andretrieving, from a database associated with the inventory management system, inventory data associated with the merchant, the inventory data indicating one or more items available to an ecommerce customer during an ecommerce transaction with the merchant;responsive to retrieving the inventory data, transmitting, from the inventory management system to a customer device associated with the ecommerce customer, at least one second GUI of the one or more second GUIs to be presented on the customer device, wherein the at least one second GUI includes information regarding at least one item of the one or more items from the merchant;receiving, at the inventory management system via the at least one second GUI presented on the customer device, a customer request for a purchase of the at least one item, the customer request including payment information;transmitting from the inventory management system to one or more processors of a payment service system (PSS) that manages the server computing device and the inventory management system, the customer request for the purchase;receiving an indication, via the at least one second GUI, that the one or more processors of the PSS have authenticated the payment information and processed the customer request;receiving a command at the inventory management system and from the one or more processors of the PSS to update, in the database, the inventory data based at least in part on processing a payment for the purchase;receiving, at the inventory management system and from the POS device via the merchant application, an indication of a second single user input to the toggle switch of the first GUI, wherein the second single user input comprises a second merchant request to deactivate the online storefront; andbased at least in part on receiving the second merchant request to deactivate the online storefront, removing access to the one or more second GUIs by the customer device associated with the ecommerce customer.
  • 2. The server computing device as claim 1 recites, wherein receiving the first merchant request includes receiving a login identification of the merchant associated with the inventory management system, and wherein retrieving the inventory data is based at least in part on the login identification.
  • 3. The server computing device as claim 1 recites, further comprising: based at least in part on a third user input associated with the first GUI after the online storefront is generated, receiving, via the merchant application, an indication of at least one of addition or removal of at least one instance of an inventory item from an inventory of the merchant;based on the at least one of the addition or the removal of the at least one instance of the inventory item, updating the inventory data; andupdating a resource for the inventory item, wherein the resource is included in the at least one second GUI.
  • 4. The server computing device as claim 1 recites, wherein causing the at least one second GUI to be presented comprises generating one or more resources for the at least one item, wherein the at least one second GUI includes the one or more resources.
  • 5. The server computing device as claim 4 recites, wherein causing the at least one second GUI to be presented further comprises determining an arrangement of at least a portion of the one or more resources for presentation on the at least one second GUI.
  • 6. The server computing device as claim 5 recites, further comprising: identifying a group of items of the one or more items as frequently purchased items,wherein determining the arrangement of the at least the portion of the one or more resources comprises presenting the group of items together on the at least one second GUI.
  • 7. The server computing device as claim 1 recites, the operations further comprising: receiving, from the POS device associated with the merchant via the merchant application at a second time, second transaction data associated with a brick and mortar (BOM) transaction between the merchant and a BOM customer; andbased at least in part on the second transaction data: processing a payment for the BOM transaction; andupdating, in the database, the inventory data.
  • 8. The server computing device as claim 1 recites, wherein removing the access to the one or more second GUIs comprises removing public access to a subdomain of the merchant including the one or more second GUIs.
  • 9. The server computing device as claim 1 recites, further comprising: causing a third GUI to be presented on the display of the POS device; andbased at least in part on a third user input associated with the third GUI, modifying an appearance of the at least one second GUI, wherein modifying the appearance comprises changing at least one of one or more of a color, a font, or a design theme.
  • 10. The server computing device as claim 1 recites, further comprising: causing a third GUI to be presented on the display of the POS device; andbased at least in part on a third user input associated with the third GUI, receiving an indication to display or hide a portion of the one or more items.
  • 11. The server computing device as claim 1 recites, further comprising: receiving, from the merchant application via the first GUI, a third user input comprising at least one of: a third merchant request associated with at least one of merchant support, viewing inventory, modifying inventory, viewing sales, viewing merchant address, or editing merchant address; orconfiguration of at least one merchant setting with the inventory management system.
  • 12. The server computing device as claim 1 recites, wherein the at least one second GUI includes one or more of: a name of the merchant;an image;contact information for the merchant;items in a shopping cart associated with the ecommerce customer;items recommended for the ecommerce customer to purchase;a description of one or more items;popular items; oritems sorted by popularity.
  • 13. The server computing device as claim 1 recites, wherein the at least one second GUI is generated according to a template, and the operations further comprising: receiving, via the merchant application, a third merchant request to customize the at least one second GUI.
  • 14. The server computing device as claim 1 recites, wherein the command to update the inventory data comprises a command to decrement a stock quantity of the at least one item in the database after the payment is successfully processed.
  • 15. The server computing device as claim 1 recites, wherein the first GUI further comprises a first interactive element selectable to send a third merchant request for support to the inventory management system and a second interactive element selectable to view historical sales of the merchant.
  • 16. A method implemented by a server computing device associated with an inventory management system, the method comprising: receiving, at the inventory management system and from a point-of-sale (POS) device of a merchant via a merchant application executing on the POS device, an indication of a first single user input to a toggle switch of a first graphical user interface (GUI) of the merchant application presented on a display of the POS device, wherein the first single user input comprises a first merchant request to generate an online storefront comprising one or more second GUIs through which online transactions with customers can be conducted;responsive to receiving the indication of the first single user input: generating and activating the online storefront comprising at least one of the one or more second GUIs; andretrieving, from a database associated with the inventory management system, inventory data associated with the merchant, the inventory data indicating one or more items available to an ecommerce customer during an ecommerce transaction with the merchant;responsive to retrieving the inventory data, transmitting, from the inventory management system to a customer device associated with the ecommerce customer, at least one of the one or more second GUIs to be presented on the customer device, wherein the at least one second GUI includes information regarding at least one item of the one or more items from the merchant;receiving, at the inventory management system via the at least one second GUI presented on the customer device, a customer request for a purchase of the at least one item, the customer request including payment information;transmitting from the inventory management system to one or more processors of a payment service system (PSS) that manages the server computing device and the inventory management system, the customer request for the purchase;receiving an indication, via the at least one second GUI, that the one or more processors of the PSS have authenticated the payment information and processed the customer request;receiving a command at the inventory management system and from the POS device via the merchant application, to update, in the database, the inventory data based at least in part on processing a payment for the purchase;receiving, at the inventory management system and from the POS device via the merchant application, an indication of a second single user input to the toggle switch of the first GUI, wherein the second single user input comprises a second merchant request to deactivate the online storefront; andbased at least in part on receiving the second merchant request to deactivate the online storefront, removing access to the one or more second GUIs by the customer device associated with the ecommerce customer.
  • 17. The method as claim 16 recites, wherein the payment comprises a first payment, the method further comprising: receiving, from the POS device associated with the merchant via the merchant application at a second time, second transaction data associated with a brick and mortar (BOM) transaction between the merchant and a BOM customer; andbased at least in part on the second transaction data: processing a second payment for the BOM transaction; andfurther updating, in the database, the inventory data.
  • 18. The method as claim 16 recites, further comprising: receiving, from the merchant application via the first GUI, a third user input comprising at least one of: a third merchant request associated with at least one of merchant support, viewing inventory, modifying inventory, viewing sales, viewing merchant address, or editing merchant address; orconfiguration of at least one merchant setting with the inventory management system.
  • 19. A server system associated with an inventory management system comprising: one or more processors managed by a payment-processing system; andone or more non-transitory computer-readable media coupled to the one or more processors having instructions stored thereon, which, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, at the inventory management system and from a point-of-sale (POS) device of a merchant via a merchant application executing on the POS device, an indication of a first single user input to a toggle switch of a first graphical user interface (GUI) of the merchant application presented on a display of the POS device, wherein the first single user input comprises a first merchant request to generate an online storefront comprising one or more second GUIs through which online transactions with customers can be conducted;responsive to receiving the indication of the first single user input: generating and activating the online storefront comprising at least one of the one or more second GUIs; andretrieving, from a database associated with the inventory management system, inventory data associated with the merchant, the inventory data indicating one or more items available to an ecommerce customer during an ecommerce transaction with the merchant;responsive to retrieving the inventory data, transmitting, from the inventory management system to a customer device associated with the ecommerce customer, at least one second GUI of the one or more second GUIs to be presented on the customer device, wherein the at least one second GUI includes information regarding at least one item of the one or more items from the merchant;receiving, at the inventory management system via the at least one second GUI presented on the customer device, a customer request for a purchase of the at least one item, the customer request including payment information;transmitting from the inventory management system to one or more processors of a payment service system (PSS) that manages the inventory management system, the customer request for the purchase;receiving an indication, via the at least one second GUI, that the one or more processors of the PSS have authenticated the payment information and processed the customer request;receiving a command at the inventory management system and from the one or more processors of the PSS to update, in the database, the inventory data based at least in part on processing a payment for the purchase;receiving, at the inventory management system and from the POS device via the merchant application, an indication of a second single user input to the toggle switch of the first GUI, wherein the second single user input comprises a second merchant request to deactivate the online storefront; andbased at least in part on receiving the second merchant request to deactivate the online storefront, removing access to the one or more second GUIs by the customer device associated with the ecommerce customer.
  • 20. The server system as claim 19 recites, the operations further comprising: based at least in part on a third user input associated with the first GUI after the online storefront is generated, receiving, via the merchant application, an indication of at least one of addition or removal of at least one instance of an inventory item from an inventory of the merchant;based on the at least one of the addition or the removal of the at least one instance of the inventory item, updating the inventory data; andupdating a resource for the inventory item, wherein the resource is included in the at least one second GUI.
RELATED APPLICATION

This patent application is a continuation application of, and claims priority to, U.S. patent application Ser. No. 15/611,219, filed Jun. 1, 2017 and issued as U.S. Pat. No. 11,250,402 on Feb. 15, 2022, which is a continuation application of and claims priority to commonly-owned U.S. patent application Ser. No. 13/829,080, filed on Mar. 14, 2013 and granted as U.S. Pat. No. 9,704,146 on Jul. 11, 2017, which is incorporated herein by reference in its entirety.

US Referenced Citations (288)
Number Name Date Kind
5652421 Veeneman et al. Jul 1997 A
5878337 Joao et al. Mar 1999 A
5960411 Hartman et al. Sep 1999 A
5991749 Morrill, Jr. Nov 1999 A
6154738 Call Nov 2000 A
6263352 Cohen Jul 2001 B1
6330544 Walker et al. Dec 2001 B1
6343275 Wong Jan 2002 B1
6612488 Suzuki Sep 2003 B2
6813608 Baranowski Nov 2004 B1
6832721 Fujii Dec 2004 B2
6868391 Hultgren Mar 2005 B1
7013149 Vetro et al. Mar 2006 B2
7167711 Dennis Jan 2007 B1
7257552 Franco Aug 2007 B1
7376431 Niedermeyer May 2008 B2
7376600 Wadawadigi et al. May 2008 B1
7475024 Phan Jan 2009 B1
7493390 Bobde et al. Feb 2009 B2
7575166 McNamara Aug 2009 B2
7685023 Abraham Mar 2010 B1
7707089 Barton et al. Apr 2010 B1
7752135 Brown et al. Jul 2010 B2
7764185 Manz et al. Jul 2010 B1
7810729 Morley, Jr. Oct 2010 B2
7853528 Schireson Dec 2010 B2
8112066 Ben Ayed Feb 2012 B2
8150740 Miller Apr 2012 B1
8160929 Park et al. Apr 2012 B1
8200537 Pike et al. Jun 2012 B2
8266014 Bhosle et al. Sep 2012 B1
8266551 Boldyrev et al. Sep 2012 B2
8326698 Tam et al. Dec 2012 B1
8498888 Raff et al. Jul 2013 B1
8615439 Ramaratnam et al. Dec 2013 B2
8630586 Dvortsov et al. Jan 2014 B2
8635113 Borders et al. Jan 2014 B2
8635117 Acuna-Rohter Jan 2014 B1
8676119 Cohen et al. Mar 2014 B2
8744919 O'Dea Jun 2014 B1
8832806 Ozzie et al. Sep 2014 B2
8838503 Pelegero Sep 2014 B2
8855312 Hodgman et al. Oct 2014 B1
8859337 Gaul et al. Oct 2014 B2
8990121 Guise et al. Mar 2015 B1
9075979 Queru Jul 2015 B1
9195985 Domenica et al. Nov 2015 B2
9400640 Baratta et al. Jul 2016 B2
9569767 Lewis et al. Feb 2017 B1
9704146 Morgan et al. Jul 2017 B1
9779392 Prasad et al. Oct 2017 B1
9792545 Sherman et al. Oct 2017 B1
9805370 Quigley et al. Oct 2017 B1
9911116 Lewis et al. Mar 2018 B1
9940616 Morgan et al. Apr 2018 B1
10055779 Varma Aug 2018 B1
10083012 Baratta et al. Sep 2018 B2
10163140 Robinson et al. Dec 2018 B2
10169308 Mizhen et al. Jan 2019 B1
10192220 Varma et al. Jan 2019 B2
10198731 Spindel et al. Feb 2019 B1
10229414 Varma et al. Mar 2019 B2
10504093 Lewis et al. Dec 2019 B1
10559019 Beauvais Feb 2020 B1
10692088 Spindel et al. Jun 2020 B1
10902406 Morgan et al. Jan 2021 B1
11010787 Tietzen et al. May 2021 B1
11250402 Morgan et al. Feb 2022 B1
11797972 Morgan et al. Oct 2023 B1
20010037245 Ranganath et al. Nov 2001 A1
20010042024 Rogers Nov 2001 A1
20010044751 Pugliese et al. Nov 2001 A1
20010049672 Moore et al. Dec 2001 A1
20020020741 Sakaguchi Feb 2002 A1
20020046092 Ostroff Apr 2002 A1
20020049622 Lettich et al. Apr 2002 A1
20020072983 Teller Jun 2002 A1
20020095343 Barton et al. Jul 2002 A1
20020095457 Sharma et al. Jul 2002 A1
20020108062 Nakajima et al. Aug 2002 A1
20020138316 Katz et al. Sep 2002 A1
20020138317 Mok et al. Sep 2002 A1
20020140542 Prokoski et al. Oct 2002 A1
20020156688 Horn et al. Oct 2002 A1
20020188535 Chao et al. Dec 2002 A1
20030014317 Siegel Jan 2003 A1
20030040976 Adler Feb 2003 A1
20030046173 Benjier et al. Mar 2003 A1
20030102373 Swartz et al. Jun 2003 A1
20030112942 Brown et al. Jun 2003 A1
20030115285 Lee et al. Jun 2003 A1
20030163399 Harper et al. Aug 2003 A1
20030204447 Dalzell et al. Oct 2003 A1
20030229590 Byrne et al. Dec 2003 A1
20040002901 Baker et al. Jan 2004 A1
20040019535 Perkowski Jan 2004 A1
20040078276 Shimogori Apr 2004 A1
20040111324 Kim Jun 2004 A1
20040128199 Cusack Jul 2004 A1
20040153359 Ho et al. Aug 2004 A1
20040181454 Manno Sep 2004 A1
20040193489 Boyd et al. Sep 2004 A1
20040215520 Butler et al. Oct 2004 A1
20050097005 Fargo May 2005 A1
20050125313 Untiedt et al. Jun 2005 A1
20050149455 Bruesewitz et al. Jul 2005 A1
20050177463 Crutchfield et al. Aug 2005 A1
20050187833 Royer et al. Aug 2005 A1
20050246245 Satchell et al. Nov 2005 A1
20050261928 Skeadas Nov 2005 A1
20050278644 Greaves et al. Dec 2005 A1
20060043175 Fu et al. Mar 2006 A1
20060047582 Jiang Mar 2006 A1
20060149637 Zellner et al. Jul 2006 A1
20060173750 Naley et al. Aug 2006 A1
20060195563 Chapin et al. Aug 2006 A1
20060224467 Walker et al. Oct 2006 A1
20060229756 Aiso Oct 2006 A1
20060271497 Cullen et al. Nov 2006 A1
20070005779 Yao et al. Jan 2007 A1
20070043602 Ettl et al. Feb 2007 A1
20070088615 Meng Apr 2007 A1
20070150387 Seubert et al. Jun 2007 A1
20070174080 Outwater Jul 2007 A1
20070174146 Tamarkin et al. Jul 2007 A1
20070175992 Brown Aug 2007 A1
20070185785 Carlson et al. Aug 2007 A1
20070203836 Dodin Aug 2007 A1
20070208930 Blank et al. Sep 2007 A1
20070255620 Tumminaro et al. Nov 2007 A1
20070265935 Woycik et al. Nov 2007 A1
20070271147 Crespo et al. Nov 2007 A1
20080035725 Jambunathan et al. Feb 2008 A1
20080037442 Bill Feb 2008 A1
20080046331 Rand Feb 2008 A1
20080162292 Roshandel Jul 2008 A1
20080177624 Dohse Jul 2008 A9
20080195507 Ratnakar Aug 2008 A1
20080197188 Jagatic et al. Aug 2008 A1
20080249939 Veenstra Oct 2008 A1
20080255968 Heinrichs Oct 2008 A1
20080296978 Finkenzeller et al. Dec 2008 A1
20090006114 Donovan et al. Jan 2009 A1
20090094126 Killian et al. Apr 2009 A1
20090106150 Pelegero et al. Apr 2009 A1
20090259527 Yang et al. Oct 2009 A1
20090276293 Zellner et al. Nov 2009 A1
20100063906 Nelsen et al. Mar 2010 A1
20100076777 Paretti et al. Mar 2010 A1
20100094729 Gray et al. Apr 2010 A1
20100257067 Chan Oct 2010 A1
20100269059 Olthmer et al. Oct 2010 A1
20100287030 Sinha et al. Nov 2010 A1
20100332400 Etchegoyen Dec 2010 A1
20110004533 Soto et al. Jan 2011 A1
20110029416 Greenspan Feb 2011 A1
20110035278 Fordyce et al. Feb 2011 A1
20110040651 Swamy et al. Feb 2011 A1
20110054992 Liberty et al. Mar 2011 A1
20110055084 Singh Mar 2011 A1
20110125566 Mclaughlin et al. May 2011 A1
20110219230 Oberheide et al. Sep 2011 A1
20110238512 Doty et al. Sep 2011 A1
20110251892 Laracey Oct 2011 A1
20110258014 Evangelist et al. Oct 2011 A1
20110258689 Cohen et al. Oct 2011 A1
20110302019 Proctor, Jr. et al. Dec 2011 A1
20120017082 Davies et al. Jan 2012 A1
20120030116 Shirey et al. Feb 2012 A1
20120046958 Pynadath et al. Feb 2012 A1
20120054050 Ziegler et al. Mar 2012 A1
20120059758 Carlson Mar 2012 A1
20120084181 Miura et al. Apr 2012 A1
20120084203 Mehew et al. Apr 2012 A1
20120089418 Kamath et al. Apr 2012 A1
20120095867 McKelvey Apr 2012 A1
20120095871 Dorsey et al. Apr 2012 A1
20120095881 Rothman Apr 2012 A1
20120109777 Lipsitz et al. May 2012 A1
20120110568 Abel et al. May 2012 A1
20120124139 Dempski May 2012 A1
20120185306 Cheng Jul 2012 A1
20120209773 Ranganathan Aug 2012 A1
20120215584 Narsude et al. Aug 2012 A1
20120229625 Calman et al. Sep 2012 A1
20120239479 Amaro et al. Sep 2012 A1
20120244885 Hefetz Sep 2012 A1
20120246074 Annamalai et al. Sep 2012 A1
20120260199 Griffin Oct 2012 A1
20120278727 Ananthakrishnan et al. Nov 2012 A1
20120284036 Evans Nov 2012 A1
20120296679 Im Nov 2012 A1
20120323685 Ullah Dec 2012 A1
20120330785 Hamick et al. Dec 2012 A1
20120330840 Stinchcombe Dec 2012 A1
20130006773 Lutnick et al. Jan 2013 A1
20130024341 Jeon et al. Jan 2013 A1
20130050080 Dahl et al. Feb 2013 A1
20130054336 Graylin Feb 2013 A1
20130065672 Gelman et al. Mar 2013 A1
20130066753 Doyle et al. Mar 2013 A1
20130066783 Wolff Mar 2013 A1
20130085835 Horowitz Apr 2013 A1
20130103946 Binenstock Apr 2013 A1
20130110656 Chau et al. May 2013 A1
20130124333 Doughty et al. May 2013 A1
20130132140 Amin et al. May 2013 A1
20130132246 Amin et al. May 2013 A1
20130132274 Henderson et al. May 2013 A1
20130132887 Amin et al. May 2013 A1
20130151381 Klein Jun 2013 A1
20130152155 Donfried et al. Jun 2013 A1
20130179227 Booth et al. Jul 2013 A1
20130189953 Mathews Jul 2013 A1
20130198032 Wallace et al. Aug 2013 A1
20130225081 Doss et al. Aug 2013 A1
20130226734 Raman Aug 2013 A1
20130238382 Schierholt et al. Sep 2013 A1
20130238455 Laracey Sep 2013 A1
20130246207 Novak et al. Sep 2013 A1
20130246301 Radhakrishnan et al. Sep 2013 A1
20130254114 Smith Sep 2013 A1
20130262206 Janes Oct 2013 A1
20130275237 Ramaratnam et al. Oct 2013 A1
20130282466 Hampton Oct 2013 A1
20130290149 Rashwan Oct 2013 A1
20130290203 Purves et al. Oct 2013 A1
20130290522 Behm, Jr. Oct 2013 A1
20130291018 Billings et al. Oct 2013 A1
20130297933 Fiducia et al. Nov 2013 A1
20130317950 Abraham et al. Nov 2013 A1
20130325612 Sommerville et al. Dec 2013 A1
20130339199 Patt et al. Dec 2013 A1
20130346221 Rangachari et al. Dec 2013 A1
20130346329 Alib-bulatao et al. Dec 2013 A1
20140019248 Stoliartchouk et al. Jan 2014 A1
20140019266 Stoliartchouk et al. Jan 2014 A1
20140019274 Hardin et al. Jan 2014 A1
20140019365 Fallows et al. Jan 2014 A1
20140032392 Ansari Jan 2014 A1
20140057667 Blankenship et al. Feb 2014 A1
20140096179 Ben-Shalom et al. Apr 2014 A1
20140099888 Flanagan et al. Apr 2014 A1
20140101036 Phillips et al. Apr 2014 A1
20140129135 Holden et al. May 2014 A1
20140129302 Amin et al. May 2014 A1
20140129951 Amin et al. May 2014 A1
20140136318 Alberth, Jr. et al. May 2014 A1
20140164280 Stepanenko Jun 2014 A1
20140172700 Teuwen et al. Jun 2014 A1
20140184505 Fullerton et al. Jul 2014 A1
20140188601 Buset et al. Jul 2014 A1
20140188639 Dinardo, Sr. Jul 2014 A1
20140201367 Trummer et al. Jul 2014 A1
20140214670 Mckenna Jul 2014 A1
20140229331 Mcintosh et al. Aug 2014 A1
20140236762 Gerber et al. Aug 2014 A1
20140244416 Venkat et al. Aug 2014 A1
20140249947 Hicks et al. Sep 2014 A1
20140254820 Gardenfors et al. Sep 2014 A1
20140278589 Rados et al. Sep 2014 A1
20140279184 Lai et al. Sep 2014 A1
20140279187 Gopinath et al. Sep 2014 A1
20140279294 Field-darragh et al. Sep 2014 A1
20140279518 Acuna-Rohter Sep 2014 A1
20140324989 Zhang Oct 2014 A1
20140337134 Bugenhagen Nov 2014 A1
20140372220 Peterson et al. Dec 2014 A1
20140379580 Varma et al. Dec 2014 A1
20150012394 Rossi et al. Jan 2015 A1
20150046271 Scholl et al. Feb 2015 A1
20150066799 Scipioni Mar 2015 A1
20150112838 Li et al. Apr 2015 A1
20150142611 Kaplan et al. May 2015 A1
20150199668 Fernando et al. Jul 2015 A1
20150206416 Marra et al. Jul 2015 A1
20160019573 Grover Jan 2016 A1
20160019628 Udumudi et al. Jan 2016 A1
20170091764 Lloyd et al. Mar 2017 A1
20170091765 Lloyd et al. Mar 2017 A1
20170270574 Hessurg Sep 2017 A1
20190005439 Nandury Jan 2019 A1
20190147446 Varma et al. May 2019 A1
20190318337 Schulz et al. Oct 2019 A1
20200082459 Varma et al. Mar 2020 A1
20200219102 Varma et al. Jul 2020 A1
20210279728 Varma et al. Sep 2021 A1
20220027980 Varma Jan 2022 A1
Foreign Referenced Citations (9)
Number Date Country
2017235924 Oct 2017 AU
2019229446 Oct 2019 AU
2841267 Jan 2013 CA
2 916 603 Dec 2014 CA
2530451 Mar 2016 GB
100426388 Apr 2004 KR
0171617 Sep 2001 WO
2009132339 Oct 2009 WO
2014210020 Dec 2014 WO
Non-Patent Literature Citations (106)
Entry
“How-To: Turn off site until development is complete ?”, Feb. 2013, https://wordpress.com/forums/topic/how-to-turn-off-site-until-development-is-complete/, (Year: 2013).
Final Office Action mailed Nov. 15, 2017, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Non-Final Office Action mailed Dec. 13, 2017, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action mailed Dec. 15, 2017, for U.S. Appl. No. 14/501,285, of Varma, A.K., filed Sep. 30, 2014.
Advisory Action mailed Feb. 2, 2018, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Examiner's Requisition for Canadian Patent Application No. 2,916,603, mailed Feb. 15, 2018.
Non-Final Office Action mailed Mar. 8, 2018, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Advisory Action mailed Mar. 8, 2018, for U.S. Appl. No. 14/501,285, of Varma, A.K., filed Sep. 30, 2014.
Notice of Allowance mailed Apr. 17, 2018, for U.S. Appl. No. 14/501,285, of Varma, A.K., filed Sep. 30, 2014.
Non-Final Office Action mailed Apr. 26, 2018, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Notice of Allowance mailed Sep. 11, 2018, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Examination Report No. 1 for Australian Patent Application No. 2017235924, mailed Sep. 13, 2018.
Notice of Allowance mailed Nov. 1, 2018, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action mailed Nov. 2, 2018, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Advisory Action mailed Jan. 25, 2019, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Examiner Requisition for Canadian Patent Application No. 2,916,603, mailed Feb. 1, 2019.
Advisory Action mailed Feb. 13, 2019, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Non-Final Office Action mailed Mar. 26, 2019, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Examination Report No. 2 for Australian Patent Application No. 2017235924, mailed Apr. 24, 2019.
Final Office Action mailed Aug. 7, 2019, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Non-Final Office action mailed Sep. 12, 2019, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Non-Final Office Action mailed Dec. 26, 2019, for U.S. Appl. No. 16/683,802 of Varma, A.K., filed Nov. 14, 2019.
Non-Final Office Action mailed Mar. 6, 2020, for U.S. Appl. No. 16/246,960, of Varma, A.K., filed Jan. 14, 2019.
Final Office Action mailed Mar. 6, 2020, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Examination Report No. 3 for Australian Patent Application No. 2017235924, mailed Aug. 15, 2019, 3 pages.
Examination Report No. 4 for Australian Patent Application No. 2017235924, mailed Sep. 10, 2019, 3 pages.
International Search Report and Written Opinion for International Application No. PCT/US2014/043891, mailed Dec. 10, 2014.
Examiner Requisition for Canadian Patent Application No. 2,916,603, mailed Jan. 23, 2020.
Final Office Action mailed Apr. 14, 2020, for U.S. Appl. No. 16/683,802 of Varma, A.K., filed Nov. 14, 2019.
Non-Final Office Action mailed Apr. 22, 2020, for U.S. Appl. No. 16/820,230, of Varma, A.K., filed Mar. 16, 2020.
Examination Report for GB Patent Application No. 1522602.0, mailed Mar. 27, 2020.
Advisory Action mailed May 27, 2020, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Non-Final Office Action mailed Aug. 14, 2020, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Advisory Action mailed Aug. 17, 2020, for U.S. Appl. No. 16/683,802 of Varma, A.K., filed Nov. 14, 2019.
Notice of Allowance mailed Aug. 25, 2020, for U.S. Appl. No. 16/246,960, of Varma, A.K., filed Jan. 14, 2019.
Non-Final Action mailed Aug. 26, 2020, for U.S. Appl. No. 16/683,802 of Varma, A.K., filed Nov. 14, 2019.
Final Office Action mailed Sep. 22, 2020, for U.S. Appl. No. 16/820,230, of Varma, A.K., filed Mar. 16, 2020.
Final Office Action mailed Nov. 24, 2020, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Notice of Allowance mailed Jan. 22, 2021, for U.S. Appl. No. 16/820,230, of Varma, A.K., filed Mar. 16, 2020.
Advisory Action mailed Feb. 2, 2021, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Final Action mailed Mar. 16, 2021, for U.S. Appl. No. 16/683,802 of Varma, A.K., filed Nov. 14, 2019.
Notice of Allowance mailed May 25, 2021, for U.S. Appl. No. 16/683,802 of Varma, A.K., filed Nov. 14, 2019.
Notice of Allowance mailed Sep. 15, 2021, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Corrected Notice of Allowability mailed Oct. 15, 2021, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Examination Report for GB Patent Application No. 1522602.0, mailed Sep. 28, 2020.
Examination Report No. 1 for Australian Patent Application No. 2019229446, mailed Nov. 21, 2020, 6 pages.
Examiner Requisition for Canadian Patent Application No. 2,916,603, mailed Jan. 22, 2021.
Examination Report No. 2 for Australian Patent Application No. 2019229446, mailed May 5, 2021, 4 pages.
Examination Report No. 3 for Australian Patent Application No. 2019229446, mailed Jul. 26, 2021, 3 pages.
Examiner Requisition for Canadian Patent Application No. 2,916,603, mailed Sep. 17, 2021.
Examination Report No. 4 for Australian Patent Application No. 2019229446, mailed Oct. 27, 2021, 3 pages.
Examiner Requisition for Canadian Patent Application No. 2,916,603, mailed Sep. 17, 2022.
Non-Final Action mailed Oct. 26, 2022, for U.S. Appl. No. 17/499,105 of Varma, A.K., filed Oct. 12, 2021.
Price, “PayPal Takes On Square, Launches ‘PayPal Here’ Credit Card Reader” dated Mar. 15, 2012, Retrieved from Internet URL: https://mashable.com/2012/03/15/paypal-takes-on-square-launches-paypal-here-credit-card-reader/, pp. 1-17.
“Another eBay Band-Aid Fails to Fix the New Pricing Structure Flaws,” posted on Oct. 18, 2008, Retrieved from the Internet URL: https://thebrewsnews.wordpress.com/2008/10/18/another-ebay-band-aid-fails-to-fix-the-new-pricing-structure-flaws/, pp. 1-4.
Authors et al.: Disclosed Anonymously, “Tying in Store Discounts to Social Media Posts,” ip.com, published on Oct. 14, 2011, pp. 1-3.
Authors et al.: “Automatic Management of On-Line Inventory for Enhancing Commerce Opportunities,” ip.com No. IPCOM000177329D, ip.com, Electronic Publication Date on Dec. 9, 2008, pp. 1-7.
C. Steinfield et al., “Integrating brick and mortar locations with e-commerce: understanding synergy opportunities,” Proceedings of the 35th Annual Hawaii International Conference on System Sciences, Big Island, HI, 2002, pp. 2920-2929.
“Card Not Present Transaction,” Wikipedia, published Mar. 4, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Card_not_present_transaction, on Jun. 6, 2014, pp. 1-2.
“CDS Assists Polk Audio in Going Direct-to-Consumer with I-Sonic Entertainment System,” Business Wire, published Sep. 6, 2006, pp. 1-3.
Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D, dated Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3.
“Merchantindustry.com—Best Merchant Services,” Retrieved from internet URL: https://web.archive.org/web/20121020212419/http://www.merchantindustry.com/, on Dec. 30, 2015, pp. 1-7.
Munson, J., and Gupta, V.K., “Location-Based Notification as a General-Purpose Service,” dated Sep. 28, 2002, Retrieved from the Internet URL—https://ai2-s2-pdfs.s3.amazonaws.com/1bb5/6ae0a70b030e2f2376ed246834bddcabd27b.pdf, pp. 40-44.
Myres, L., “The Mac Security Blog: What is Multi-Factor Authentication, and How Will It Change in the Future?,” Intego, dated Aug. 17, 2012, Retrieved from the Internet URL: http://www.intego.com/mac-security-blog/what-is-multi-factor-authentication-and-how-will-it-change-in-the-future/, on Nov. 11, 2014, pp. 1-4.
“Online Shopping,” dated Nov. 2, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Online_shopping, on Nov. 10, 2014, pp. 1-12.
“Payment Gateway,” Wikipedia, published May 30, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Pavment gateways, on Jun. 6, 2014, pp. 1-3.
“ProPay JAK Mobile Card Reader,” Propay, published Dec. 27, 2011, Retrieved from the Internet URL: https://web.archive.org/web/20111227055421/https://www.propay.com/products-services/accept-payments/jak-card-reader, pp. 1-2.
Punch, L., “E-commerce: Just what does card-present mean these days,” dated Oct. 1, 2012, Retrieved from the Internet URL: http://digitaltransactions.net/news/ story/ E-Commerce_-Just-What-Does-Card-Present-Mean-These-Days, on Feb. 17, 2015, pp. 1-4.
“Tracking Inventory,” PayPal, dated Jan. 4, 2010, Retrieved from the Internet URL: https://www.paypal-community.com/t5/How-to-use-PayPal-Archive/Tracking-inventory/td-p/19392, pp. 1-3.
“Uber—Android Apps on Google Play,” Published on Nov. 10, 2014, Retrieved from the Internet URL: https://play.google.com/store/apps/details?id=com.ubercab&hl=en, on Nov. 12, 2014, pp. 1-2.
Nadiminti K., et al., “ Distributed Systems and Recent Innovations: Challenges and Benefits,” Retrieved from URL: https://www.researchgate.net/publication/240827899_Distributed_Systems_and_Recent_Innovations_Challenges, 2006, 5 pages.
William Aspray., and Paul E. Ceruzzi., “Discovering a Role Online: Brick-and-Mortar Retailers and the Internet,” in The Internet and American Business, MITP, 2008, pp. 233-258.
Wallen, J., “Five Top Apps for Managing Inventory,” Tech Republic, dated Aug. 15, 2012, Retrieved from the Internet URL: http://www.techrepublic.com/blog/five-apps/five-top-apps-for-managing-inventory/, on Nov. 10, 2014, pp. 1-7.
https://web.archive.org/web/20130513203402/http://www.ncr.com/products/small-business/ncr-silver (Year: 2013).
“E-Commerce Intergration,” posted on Mar. 7, 2013, Retrieved from the Internet URL: http://www.amberpos.com/pint-of-sale/ecommerce-integration/, pp. 1-6.
Kourouthanassis, P., and Roussos, G., “Developing consumer-friendly pervasive retail systems”, IEEE Pervasive Computing, doi: 10.1109/MPRV.2003.1203751, vol. 2, No. 2, pp. 32-39 (Apr.-Jun. 2003).
Turow, J., “The Customized Store,” Niche Envy: Marketing Discrimination in the Digital Age, MIT Press, pp. 125-147 (Year: 2008).
Mahar, S., et al. “Using online pickup site inclusion policies to manage demand in retail/E-tail organizations”, Computers & Operations Research, vol. 39, Issue 5, pp. 991-999 (2012).
Non-Final Office Action mailed Dec. 1, 2014, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Non Final Office Action mailed Dec. 15, 2014, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action mailed Apr. 16, 2015, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Non-Final Office Action mailed May 20, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Final Office Action mailed Aug. 31, 2015, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action mailed Sep. 17, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action mailed Nov. 24, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Non-Final Office Action mailed Jan. 14, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action mailed Feb. 2, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Non-Final Office Action mailed Feb. 23, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Non-Final Office Action mailed May 5, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action mailed Aug. 10, 2016, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Final Office Action mailed Sep. 1, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Examination Report No. 1 for Australian Patent Application No. 2014302661, mailed Sep. 27, 2016.
Final Office Action mailed Oct. 11, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action mailed Nov. 28, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013.
Final Office Action mailed Nov. 28, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Examiner's Requisition for Canadian Patent Application No. 2,916,603, mailed Feb. 9, 2017.
Notice of Allowance mailed Mar. 2, 2017, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013.
Advisory Action mailed Apr. 10, 2017, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action mailed Apr. 10, 2017, for U.S. Appl. No. 14/501,332, of Varma, A.K., filed Sep. 30, 2014.
Final Office Action mailed Apr. 19, 2017, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Non-Final Office Action mailed Jun. 6, 2017, for U.S. Appl. No. 14/501,285, of Varma, A.K., filed Sep. 30, 2014.
Advisory Action mailed Jun. 30, 2017, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014.
Examination Report No. 2 for Australian Patent Application No. 2014302661, mailed Sep. 26, 2017.
Examination Report No. 5 for Australian Patent Application No. 2019229446, mailed Nov. 22, 2021, 3 pages.
Corrected Notice of Allowability mailed Nov. 9, 2021, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Corrected Notice of Allowability mailed Dec. 10, 2021, for U.S. Appl. No. 15/611,219, of Morgan, T.B., et al., filed Jun. 1, 2017.
Related Publications (1)
Number Date Country
20220198423 A1 Jun 2022 US
Continuations (2)
Number Date Country
Parent 15611219 Jun 2017 US
Child 17671521 US
Parent 13829080 Mar 2013 US
Child 15611219 US