JP2016212873A - Web integrated pos system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To synchronize a POS system with a web site about reservations, order-placements and electronic commerce transactions.SOLUTION: A web integrated POS reservation system includes: a POS device that hosts POS applications including database layers; and a web server for hosting web site applications composed of web site database layers. The web server is configured to host accessible web sites to the public, and the web site application is configured to process data inputs in the web site in the web site database layer. The POS application is configured to communicate with the web site application so that harmonization of the POS database layer with the web site database layer is bi-directionally synchronized in realtime, using an Internet protocol. The web integrated POS reservation system is integrated with POS reservations, order-placements and electronic commerce transactions of restaurants or other merchants to provided via the web site.SELECTED DRAWING: Figure 1

Description

Copyright
[0001] This application includes material that is subject to copyright protection. The copyright holder has no objection to facsimile reproduction by patent disclosure because it appears in the Patent and Trademark Office file or record, but does not own all copyright.
1. Technical field
[0002] The present invention relates to a POS system, and more particularly to a system for synchronizing a POS system with a website related to reservation, ordering, and electronic commerce.

2. Explanation of related technology
[0003] More restaurants allow customers to schedule online reservations via the Internet. For example, a website may allow a user to search for available times at a particular restaurant and then enter enough information to ensure the available time. However, most of these websites operate as stand-alone software applications separate from the restaurant's daily equipment and computer systems. The website collects potential customer reservation requests and sends them to the restaurant, usually via email, and enters the restaurant's own reservation system. Before confirmation is provided to potential customers, the restaurant must check the accuracy of the information and verify time validity. Potential customers are thus not given real-time confirmation, and the overall method is somewhat cumbersome, inefficient and error prone.

  [0004] Some overcome these problems by enhancing all of the restaurant reservation systems online. For example, when an online booking website is operated by a third party (website operator), the website operator can also host a booking management method service. Then, instead of a restaurant that maintains its own reservation system and enters data transmitted from the website, the reservation system is hosted online and customers and restaurants access it via the Internet. This enables real-time access of potential customers to restaurant effectiveness and near-instant booking confirmation. However, when there is an outage, this also removes the reservation system from the restaurant control and creates a loss of revenue risk. The restaurant must either log on or engage a website operator reservation system that manages this aspect of its own business. Also, these online reservation systems are often unique and website operators charge a restaurant each time a potential customer makes a reservation through the system.

  [0005] Furthermore, this type of third-party setup creates privacy issues. Website operators typically require a potential customer to register a name with that website in order to make a reservation, and as they can do so, gather similar information from potential clients. Website operators also track potential customer dining history, consumption habits, and emails exchanged between the customer and the website. Website operators can then share this data with others and use it to sell other products to their customers.

  [0006] The present invention relates to reservation data, order data, electronic commerce data, gift card data, and / or loyalty point data present in a POS device of a merchant website, and a website to the POS device. A system is provided for synchronizing and integrating with synchronization data present in a database. Using the system, customers can, for example, make restaurant reservations on a restaurant website and see real-time available time frames. Similarly, retailer employees, such as restaurants, can use a phone / PDA browser to connect a handheld device to a website in real-time with reservation data, order data, item stock data, electronic You can use their wireless smartphone or PDA to view and modify commerce data and other data types. Changes to this type of data created directly on POS devices can also be synchronized to a real-time website. These and other aspects and utilities of the overall concept of the present invention include a POS device that hosts a POS application that includes a POS database layer, and a web server for hosting a website application that comprises a website database layer. A web server hosting on a publicly accessible website, website application within the website database layer, and can be provided by providing a web integrated POS booking system The POS application uses the Internet protocol to synchronize the harmony between the POS database layer and the website database layer in real-time and bi-directionally. To communicate with. Website data entry may include at least one of customer information, a reservation request, a customer gift card number, a customer loyalty point number, a food purchase order, and an electronic commerce process. The POS database layer may include at least one data relating to available time for reservations, loyalty point information for customers, food purchase orders, e-commerce inventory and price data.

  [0007] These and / or other aspects and advantages of the overall concept of the invention will be more readily apparent from the following description of embodiments in conjunction with the accompanying drawings.

[0008] FIG. 1 is a diagram illustrating the software and hardware architecture for an application hosted on a web server and a POS device. FIG. 2 is a diagram illustrating the harmonization of information between the application of the web server and the POS device.

  [0010] For the concepts of the present invention generally, the same reference numerals are used for similar elements. Embodiments are described below to explain the concept of the invention as a whole by referring to the figures.

  FIG. 1 is a diagram illustrating hardware and software architecture for applications hosted on POS device 10 and web server 30. The present invention provides two main modules, a POS desktop application 100 and a website application 300. There are several common functions between these two modules, including reservations, gift card purchases, takeout / delivery orders. The present invention provides a means for integrating and harmonizing between the POS device 10 and the website 30. This integration ensures that the two modules can work in a consistent manner.

  As illustrated in FIG. 1, the system includes a POS device 10 that communicates with a website server 30 via an Internet protocol 20. POS or checkout is where processing takes place. This is usually the place where customers pay for goods and services. In the restaurant context, POS is where the customer checks in with the hostess, the food order begins, and the payment is processed.

  [0013] The POS device has a combination of computer hardware, software and peripherals used to process restaurant commerce. POS device 10 can be one or more computers, barcode readers (BCR), magnetic stripe readers or other types of POS indicia scanners for obtaining credit or payment from customers, operator displays, customer displays and one or more Data input devices. The POS device 10 includes a wireless device such as a tablet computer (for example, iPad), a handheld PDA, a smartphone, etc., and can be used by a waiter / waitless and executed at a table. In such embodiments, the wireless device is typical for wireless communication with conventional servers and / or other conventional POS hardware. The POS device 10 can be used to place food orders, manage reservations and process payments. Depending on the restaurant setup, the POS device can include various forms of equipment and peripherals. For example, the POS device 10 can include a touch screen terminal for data entry, a wireless handheld device for processing credit cards and other payment cards, and works with a wireless smartphone, PDA, and electronic signature capture device Can be used. The POS device 10 is used to print guest checks and execute orders or preparations for the kitchen, credit and other payment card processing, and reports.

  [0014] A merchant website is typically a collection of related pages, images, and digital content hosted on at least one web server. The website is accessible to the public on the internet using internet protocols such as the hypertext transfer protocol.

  [0015] The web server 30 resides in a computer system separate from the POS device 10 and may be geographically separated from the point of sale, may be a collection of virtual servers, in a separate location, or It may be in the cloud. Web server 30 hosts a publicly accessible website for restaurants.

  [0016] According to restaurant requirements, different software is loaded into the POS device 10 to manage the desired functions and peripherals. Two synchronization applications are loaded into the POS device 10 and the web server 30 for management of the restaurant's web integrated reservation system.

  With continued reference to FIG. 1, the POS application 100 may include a database layer 101, a data access layer 102, a controller and user interface 103, and a communication layer 104. The control and user interface 103 can include a business layer 105 and a presentation layer 106.

  [0018] The database layer 101 includes restaurant reservation data including all available times, tables, table sizes and other reservation related information. The database layer 101 can also include information regarding other related processing such as reward points associated with customers, pick-up / delivery orders and payment information. For example, the database layer 101 may be a Microsoft SQL Server, Oracle, or MySQL. Inventory (item) data, Pickup / Delivery data, Gift Card data, Loyalty points data, and other customer information. Further, it is stored in the database of the database layer 101.

[0019] The following events can modify the database of the database layer 101:
Purchase of items in electronic commerce processing via POS or customer website;
Bookings that are positioned through the website by the customer;
Pickup or delivery orders placed via customer viewers or via phone to POS; or
The purchase of a gift card by a customer at a website or POS. For example, after a customer pays for a food purchase at a restaurant via a POS system, the POS system stores the transaction in the database at the database layer 101 via the data access layer 102 and formats the transaction data Send data to the web server 30 via the communication layer 104 and to the Internet using the XML web service communication protocol 20. Once the website application 300 receives the data and stores the data to reduce the inventory volume, real-time inventory management can be performed.

  [0020] Business logic is provided to the business layer 105, inventory (item) management, item list for customer orders, shopping cart and payment processing, reservation and payment processing, pickup / delivery, gift card issuance and reloading, and Includes customer management for loyalty programs.

  [0021] The invention taught herein with respect to gift card issuance and reload functions and loyalty point program functions is disclosed in US patent application Ser. No. 13 / 106,572 filed on May 12, 2011. It can be combined with the teachings and is hereby incorporated by reference. In this application, the loyalty point conversion table taught in application number 13 / 106,572 can be used as follows. Both POS device 10 and web server 30 have loyalty point conversion tables in either database layer 101 or database layer 301 to convert customer loyalty points to either financial value or product / service value. Can be used. For example, a customer who makes a reservation through a restaurant website will be charged with monetary value for loyalty points that he can otherwise make or he will not It can be allowed to use reservations that would not. Loyalty points can be similarly charged for priority reservations, and a higher number of loyalty points can be used to obtain higher priority or otherwise better reservations.

  The communication layer 104 controls communication between the POS website application 100 and the web server website application 300. The POS device 10 and the web server 30 communicate via the internet using internet protocols (eg, XML web service and REST protocol).

  As illustrated in FIG. 1, the web server website application 300 can include a database layer 301, a data access layer 302, a controller and user interface 303 and a communication layer 304. The control and user interface 303 can include a business layer 305 and a presentation layer 306.

  [0024] The database of the database layer 301 includes the latest information on available reservation times, and is updated by customer reservation information input by the website. The database contains all requested times, party names and other related booking information. The database layer database 301 may also include information regarding other related transactions (eg, reward account number, pickup / delivery order and payment information). The database in the database layer 301 can consist of a relational database (eg, Microsoft SQL Server, Oracle, or MySQL). Inventory (item) data, reservations, pickup / delivery, gift cards, and customer information are stored in a database.

  [0025] The data access layer 302 provides data access services for the database layer 301 for downstream communications and for the business layer 305 for upstream communications. The control and user interface 303 defines a website hosted by the web server 30. The control and user interface 303 contains all the necessary web pages and interfaces to receive customer input and send the same to the database layer 301. The communication layer 304 controls communication between the POS website application 100 and the web server website application 300 using the Internet protocol. The communication layer 304 facilitates communication between the POS device 10 and the disparate web server 30 using a communication protocol such as XML web service and REST. Communication layer 304 and communication layer 104 use encryption / decryption techniques throughout the communication path to ensure data.

  [0026] Rather than using a website as a non-logged-in guest, customers who create an account and log in to the website are given additional advantages. For example, a logged-in user can provide loyalty points for making a reservation and can make a reservation or place an order using loyalty points.

  FIG. 2 is a diagram illustrating the harmonization of information between the POS device and the web server application. As shown in FIG. 1, the website application 300 uses the communication layer 304 to communicate with the communication layer 104 of the POS application 100. Communication between the website application 300 and the POS application 100 takes into account the real-time harmonization of the database layer 101 and the database layer 301. That is, as illustrated in FIG. 2, the customer's online reservation via the website application 300 is entered into the database layer 301. Communication with the POS website application 100 can integrate this information into the restaurant reservation database in the database layer 101, allowing the database layer 301 to update information regarding available time.

  [0028] The customer's online order or e-commerce purchase that begins with the website application 300 is similarly entered into the database layer 301. Communication with the website application 100 can integrate this information into the database layer 101 and the synchronized restaurant reservation database. Similarly, when customers make reservations, they can be given the option to prepay for their meals. Communication with the website application 100 can integrate this information into the restaurant sales database so that when the customer finishes the meal, a full payment is shown instead of a check for payment.

  [0029] Referring to FIG. 2, a data synchronization flow is described. There are three types of data that need to be synchronized between the POS and the website. The first is data that originates from the POS device and is pushed towards the website. For example, a menu item. The second is data that originates from the website and is pushed towards the POS. For example, online processing. The third is data that can flow in either direction. For example, such data history customer data can be created on both sides. These three types of data flows are each described individually.

  [0030] With respect to the data that occurs in a POS device and is pushed towards the website, the following types of data records need to be pushed: menu item category, menu item, reservation, event and daily special. With the exception of reservation records, this data is master and search data, so the maximum of it need not be synchronized immediately. A website management user is given the ability of a management console that he can run once or twice a day. This function operates as follows. First, retrieve a list of new data records and a list of updated records from the POS. Then, for each new record, the complete data record is retrieved and inserted into the website database. Finally, for each updated record, the updated data record is retrieved and the website database is updated.

  [0031] With respect to data originating from a website and pushed towards a POS, reservation and processing records are types of data records that fall into this category. Whenever a customer makes a reservation or places an order (takeout, delivery), the website application links with the POS to send data. The website first checks the connection to the POS, and if the connection is down, the back office connection goes down and asks the customer to call the toll-free phone number instead. Is displayed. If the connection is up, the website sends data to the POS. To ensure that no data is lost, the website keeps a local copy of the transaction record once payment is received. Once synchronization is successful, the transaction data record copy on the website can be deleted. This data is newly generated on the website side for booking and sales processing / ordering and must be synchronized immediately.

  [0032] For interactive data that can flow in either direction between a POS application and a POS website, there is only one data record type in this category, which is a customer data record. This data requires special processing because it can flow in either direction. First, whenever there is a new customer record entered in the POS system, it is pushed on the website to a website that maintains the same customer ID. Also, whenever there is a new customer record entered on the website, it is pushed to the POS, but the ID itself may change to match the customer data record on the POS side. To achieve this, customer data records from the POS side can be pushed once or twice a day by the website administrator. However, customer data records from websites must be pushed immediately to the POS. If there is a change in customer ID on the POS side, the website receives a new customer ID so that the record can be updated.

  [0033] Integration because two modules (POS application and website) are typically developed using two different platforms each (eg .NET / C # / MySQL and PHP / Zend / MySQL) Must be based on industry standards such as SOAP-based web services. In such an embodiment, there may be more than 50 web service based interfaces used for this integration. These web services are defined in .NET 4.0 using the C ++ language and deployed on Microsoft Internet Information Server (IIS). PHP / Zend web applications create proxies for these web service interfaces.

  [0034] With regard to security, each web service based integration can use basic authentication via username and password requirements. Special “system user accounts” can be created at the store level, which can be maintained with the store configuration function of the POS. Only those requests to provide certificates to this system user account are processed.

  [0035] Embodiments of the present invention can be written as a computer program and can be executed on a general use digital computer executing a program using a computer readable recording medium. Embodiments of computer readable recording media include storage media such as magnetic recording media (eg, ROM, floppy disk, hard disk, etc.), optical recording media (eg, CD-ROM or DVD), and carrier waves (eg, transmission over the Internet). .

  [0036] Although a few embodiments of the overall concept of the present invention have been described in conjunction with the drawings, changes in these embodiments and general inventive concepts, without departing from the principles, are claimed. It will be appreciated by those skilled in the art that they are defined in ranges and can be made within their equivalent ranges.

Claims (17)

A POS device that hosts a POS application, the POS application including logic for processing a checkout that includes receiving payment from a customer at the POS, logic for processing a reservation for a service at the POS, and POS A POS device comprising a database layer, wherein the POS database layer comprises order data, item stock data and electronic commerce data;
A web server for hosting a website application, wherein the website application has a website database layer; and
Have
The web server hosts a publicly accessible website, the website application processes data entry on the website within the website database layer,
A web integrated POS reservation system, wherein the POS application communicates with the website application to synchronize the harmony between the POS database layer and the website database layer in real time bi-directionally using an Internet protocol.   The website data entry comprises at least one of customer information, reservation request, food purchase order, and e-commerce transaction, gift card data, or loyalty point data. The POS reservation system described.   The POS database layer comprises at least one of data on time available for reservation, loyalty point information about a customer, food purchase order, electronic commerce inventory, and price data. The POS reservation system described.   The POS reservation system of claim 1, wherein the website is based on a user interface and controls of a website application.   2. The POS reservation system according to claim 1, wherein the POS device includes a restaurant cash register, ordering, and reservation system.   The POS reservation system according to claim 5, wherein the POS device includes a wireless handheld device that communicates with the server.   6. The POS reservation system according to claim 5, wherein the POS device further comprises an indicia reader for obtaining a credit card or debit payment from a customer.   The POS reservation system of claim 6, wherein the wireless handheld device is configured to process credit cards and other payment cards.   The POS reservation system of claim 1, wherein the system is configured to synchronize some data in real time and synchronize other part data in non-real time.   The POS reservation system according to claim 1, wherein the POS database layer is configured to store inventory data, pickup / delivery data, gift card data, loyalty point data, and customer information.   POS devices include business layers for inventory management, item lists for customer orders, shopping cart and payment processing, reservation and payment processing, pickup / delivery, gift card issuance and reloading, and loyalty program The POS reservation system according to claim 1, further comprising customer management.   The POS reservation system according to claim 1, wherein the POS device and the web server communicate via the Internet using an XML web service protocol.   The POS reservation system according to claim 1, wherein the POS device and the web server communicate via the Internet using a REST protocol.   The POS reservation system of claim 1, wherein the web application is configured to provide an additional benefit for a customer who has been generated and logged into an account and a website to place a reservation order.   15. The POS reservation system according to claim 14, wherein the additional profit includes loyalty points.   15. The POS reservation system according to claim 14, wherein the additional profit includes a priority reservation.   The POS reservation system of claim 1, wherein the web application is configured to provide the customer with an option to pre-pay for a meal when ordering.