1111111111111111 IIIIII IIIII 11111 1111111111 1111111111 1111111111 1111111111 1111111111 11111111
`US 20080208696Al
`
`c19) United States
`c12) Patent Application Publication
`Olson
`
`c10) Pub. No.: US 2008/0208696 Al
`Aug. 28, 2008
`(43) Pub. Date:
`
`(54) POINT OF SALE SYSTEM WITH WEB-BASED
`BACK-OFFICE
`
`(52) U.S. Cl. .......................................................... 705/16
`
`(76)
`
`Inventor:
`
`Quentin Olson, Poulsbo, WA (US)
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`George O Saile and Assocs
`28 Davis Ave
`Poughkeepsie, NY 12603
`
`(21) Appl. No.:
`
`11/710,722
`
`(22) Filed:
`
`Feb.26,2007
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`G06Q 10100
`
`(2006.01)
`
`This invention provides a system and a method for managing
`a range of businesses. The business operations range from a
`single branch to a large chain of stores or branches. This
`invention relates to the managing of the points of sale (POS)
`with Web-based back-office systems. POS transaction engine
`terminals are implemented on personal computer, PC hard(cid:173)
`ware using PC software with a relational database. The trans(cid:173)
`action engine architecture provides cost-effective application
`customization. Web-based back-office software is imple(cid:173)
`mented on servers. POS and BO systems are monitored and
`supported via the web using protocol and open software com(cid:173)
`ponents.
`
`Points of Sale in Stores &
`Back Office Server on the Web
`
`POS 1
`Store 1
`
`POS 2
`Store 1
`
`POS 1
`Store 2
`
`POS 2
`Store 2
`
`21 -
`25
`
`Remote PC
`with Web
`access
`
`--
`\ 26
`I )
`
`\
`
`I
`/_
`-
`I
`Backoffice implemented on various
`Web Servers
`
`23
`
`-
`
`~ -
`22
`HTTP
`prot ocal
`eb to ~
`
`
`24
`
`Lightspeed Ex. 1006.1
`
`

`

`.... 0 =
`.... 0 = ""O = O" -....
`('D = ..... t "e -....
`
`~ .....
`
`(')
`
`~ .....
`""O
`
`~ .....
`
`(')
`
`FIG. 1
`
`-24
`
`to W:
`-prot ocal
`HTTP
`
`eb
`
`22
`
`Web Servers
`
`Backoffice inrplemented on various
`
`I
`7
`I
`
`23-
`
`\
`
`I \
`\ 26
`
`25
`
`access
`with Web
`Remote PC
`
`-
`
`21
`
`Store
`2
`POS 2
`
`Store 2
`POS 1
`
`Store 1
`POS 2
`
`Store 1
`POS 1
`
`Back Office Server on the Web
`Points of Sale in Stores &
`
`Lightspeed Ex. 1006.2
`
`

`

`Patent Application Publication Aug. 28, 2008 Sheet 2 of 3
`
`US 2008/0208696 Al
`
`Point of Sale Software (one store)
`
`Core Transaction Engine
`
`1---------------r-----~-----r---10
`
`30
`
`Configurable Modules
`
`FIG. 2
`
`13
`
`No
`
`· Warn
`User
`
`Start
`No Manager
`O'Uerride
`Dialog
`
`1
`
`Call PosEvent
`virtual method
`
`15
`
`16
`
`FIG. 3
`
`Lightspeed Ex. 1006.3
`
`

`

`(----~
`
`F JG. 4
`
`~37
`I
`I
`
`Relation DB
`
`Apache
`
`PHP
`
`Web Server
`
`36
`
`I HTTPS
`---
`
`,--------=== ~
`
`XML/RPC
`
`I
`
`HTTPS
`
`--------
`:
`(
`35
`
`-7
`
`POS/Back Office
`
`___ A_rchitecture
`
`31
`
`Relational DB
`
`Store
`POS N
`POS 2
`POS 1
`
`lja[a©js I
`
`33--------c•. ·C
`
`Web Bruwser
`
`Relational DB
`
`Store N
`POS N
`POS 2
`POS 1
`
`l;a[a©js I
`
`32
`
`••• ••••
`
`Lightspeed Ex. 1006.4
`
`

`

`US 2008/0208696 Al
`
`Aug. 28, 2008
`
`1
`
`POINT OF SALE SYSTEM WITH WEB-BASED
`BACK-OFFICE
`
`RELATED PATENT APPLICATION
`
`[0001] This application is related to docket number
`TY2006-002, filed on ___ , Ser. No. ___ , which is
`herein incorporated by reference in its entirety.
`
`BACKGROUND OF THE INVENTION
`
`[0002]
`1. Field of the Invention
`[0003] This invention relates to a system and an apparatus
`for managing a range of businesses. The business operations
`range from a single branch to a large chain of stores or
`branches.
`[0004] More particularly this invention relates to the man(cid:173)
`aging of the points of sale (POS) with Web-based back-office
`systems.
`[0005] 2. Description of Related Art
`[0006] Currently, point of sale (POS) functions are imple(cid:173)
`mented with custom hardware and/or custom software in the
`stores or business branches. In addition, custom software is
`currently used for server functions. Today, servers are
`required to be located in each store or branch for normal mode
`operation, and for a backup mode of operation, which is
`needed if the servers go down. The disadvantages of current
`practice are that store and branch changes require time and
`money for software development and testing. In addition,
`current practice has weak scalability and requires significant
`technical skill to manage the in-store components. As POS
`terminals are added within a store or branch or as stores or
`branches are added, the performance of the overall system
`degrades. Another disadvantage of current practice is the use
`of non-standard protocols. Many of these non-standard pro(cid:173)
`tocols were implemented before the availability of PC hard(cid:173)
`ware and software and before the wide spread use of universal
`web protocols. Consequently, current practice includes pro(cid:173)
`prietary protocols which were implemented earlier, but their
`continued operation is required to enable enterprises to pre(cid:173)
`serve the large investment in proprietary business operations
`and systems.
`[0007] U.S. Pat. No. 4,679,154 (Blanford) describes a
`checkout system for processing purchased merchandise
`items. The system includes a checkout counter which con(cid:173)
`tains a scanning assembly for scanning a coded label on the
`purchased item to produce data signals identifying the item
`purchased, a display member on the counter for displaying
`the price of the merchandise item purchased, an indicator
`light and a tone generator located in the display member, a
`back-office processor for obtaining the price of the merchan(cid:173)
`dise item, and a data terminal device for printing the price of
`the scanned items on a record member.
`[0008] U.S. Pat. No. 6,856,970 Bl (Cambell et al.) dis(cid:173)
`closes a financial transaction system which allows clients of a
`financial institution to use a web-based workstation to inter(cid:173)
`face with a plurality of back-office systems within one or
`more financial institutions. This system comprises a hub
`server, a plurality of financial institutions, at least one web
`server, and at least one database server.
`[0009] U.S. Pat. No. 6,504,481 B2 (Teller) describes a sys(cid:173)
`tem, method, and device for monitoring the dispensing of
`liquids, in particular, beverages dispensed at a bar or restau(cid:173)
`rant. The system includes an electronic sensor device, data
`receiver, personal computer, bottle opener/camera system,
`
`bar code scanner, point of sale, bar camera, network, Web
`server, and paging system. The method automatically detects
`and monitors dispensing events, including detecting the type
`and amount of liquid, reconciling dispensing events with
`register ring-ups, recording information, saving video spe(cid:173)
`cific to the dispensing event, and sending a page indicating
`anomalies.
`
`BRIEF SUMMARY OF THE INVENTION
`
`[0010]
`It is the objective of this invention to provide a
`system and a method for a system and an apparatus for man(cid:173)
`aging a range of businesses. The business operations range
`from a single branch to a large chain of stores or branches.
`This invention relates to the managing of the points of sale
`(POS) with Web-based back-office systems.
`[0011]
`It is further an object of this invention to the manage
`the points of sale (POS) with Web-based back-office systems.
`[0012] The objects of this invention are achieved by point
`of sale system with a web-based back-office system com(cid:173)
`prised of one or more point of sale (POS) terminals and one or
`more web servers. The POS terminals and web servers com(cid:173)
`municate via commonly used, standardized internet proto(cid:173)
`cols. The POS terminals are implemented with personal com(cid:173)
`puter hardware and software using one or more relational
`databases. The web server is implemented with web server
`hardware and software, also using one or more relational
`databases.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0013] FIG. 1 shows a high level diagram of this invention.
`[0014] FIG. 2 gives a high level diagram of a point of sale
`(POS) terminal.
`[0015] FIG. 3 gives a core transaction engine/configurable
`module flow chart.
`[0016] FIG. 4 is a more detailed diagram ofa main embodi(cid:173)
`ment of this invention.
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`[0017] FIG. 1 shows a high level diagram of this invention.
`Each point of sale (POS) terminal such as POS 21 represents
`a single cash register in a store, retail location, or business
`location. POS 21 is in STORE 1 and POS 2 (22) is in store 2.
`Each POS includes personal computer hardware and soft(cid:173)
`ware. Additional POS terminals beyond the two shown, as
`well as additional stores beyond the two shown, are within the
`scope of the invention. Each POS normally operates with a
`hardware/software connection 23 to the Internet or Web.
`However, if the web goes down, the POS terminal continues
`to operate. There is a loose coupling of the POS to the back
`office (BO). The POS to BO connection is not required for the
`basic business functions of the POS. All transaction data is
`stored in a relational database on the hard drive in the POS.
`[0018] A relational database stores all of its data inside
`tables. All operations on data are done on the tables them(cid:173)
`selves. Some operation produce other tables as the result. A
`table is a set of rows and columns. Each row is a set of
`columns with only one value for each. All rows from the same
`table have the same set of columns, although some colunms
`may have NULL values. A NULL value is an "unknown"
`value. The rows from a relational table are analogous to a
`record, and the colunms are analogous to a field. Below is an
`example of a relational table.
`
`Lightspeed Ex. 1006.5
`
`

`

`US 2008/0208696 Al
`
`Aug. 28, 2008
`
`2
`
`NAME
`
`COMPANY
`
`E MAIL
`
`Jane A. Doe
`BillX. Smith
`
`ABC
`XYZ
`
`jad@abc.com
`bxs@xyz.com
`
`There are two basic operations one can perform on a rela(cid:173)
`tional table. The first one is retrieving a subset of its columns.
`The second is retrieving a subset of its rows. The field names
`such as company describe the content of the columns of the
`relational table. The rows delineate the individual records
`stored in the relational tables.
`[0019] As transactions are created at a POS a log entry for
`the newest transaction is also created, this log entry is used to
`flag if the transaction has been uploaded to the web server.
`Part of the POS application, the BO interface is continuously
`running in the background. This component reads the log of
`transactions. If a transaction needs to be sent, it tries to send
`it. If the send fails (for example, if the connection to, or the
`Internet itself, is down), it goes to sleep and tries again later.
`Additionally, the BO interface requests update from the BO
`such as new items, price changes, employees, etc. The POS
`terminals communicate via HTTP protocol (hypertext trans(cid:173)
`fer protocol) 23 with Back-office BO software, which is
`implemented on web servers 24, which can be located any(cid:173)
`where in the world. In addition, the BO software and data can
`be viewed from any store employee at any PC who has Inter(cid:173)
`net access 26 and a password.
`[0020] The POS such as 21 send transaction data to the BO
`in the form of an HTTP post or communication. The packet 23
`sent from the POS to the BO consists of transactions,
`employee clock, customer add/update, item add/update, pro(cid:173)
`motions and more. Promotions are configured in the back
`office and associated with items or customers or departments.
`For example, a promotion may be associated with a customer
`to implement customer loyalty points or a promotion may be
`associated with a certain item for a % discount. A client who
`is the store manager or owner selects a promotion type, asso(cid:173)
`ciates it with an item, department, etc, then sets the param(cid:173)
`eters that control how that promotion works. These transac(cid:173)
`tion transmissions between the POS and the BO can be
`encrypted to insure privacy and security. A typical encryption
`method is 128 bit SSL (secure sockets layer). A further ele(cid:173)
`ment of security is that each BO client (individual POS, store
`or multi-store owner) gets their own instance of a database.
`When they log into the BO they are attached to their own
`relational database associated and validated via their user
`login and password.
`[0021] FIG. 2 is a high-level diagramofa POS terminal 10.
`There is a core transaction Engine 20 which is software which
`processes all input and output at the POS terminal and invokes
`the appropriate retail logic. The core transaction engine inter(cid:173)
`faces with configurable modules 30, which handle the mean(cid:173)
`ing & processing steps of terminal keys required. For
`example, one business or one store may require a different
`function performed by the transaction engine when the
`"Total" key on the POS terminal is pressed. A convenience
`store may have a different way of computing the summation
`of taxable items than a restaurant business. These config(cid:173)
`urable modules allow the POS terminal to be very flexible for
`use by many different types of stores and businesses.
`[0022] An example of a promotion which requires some
`level of configuration information is "Buy 1 and get one free
`
`or buy 1 and get the second 50% off'. Typically, these con(cid:173)
`figurable modules are preferably implemented in a computer
`language such as JAVA which is a combined compile and
`interpretive language. The use of a JAVA-type object-oriented
`language allows the dynamic loading of executable config(cid:173)
`urable modules at run-time to handle things such as different
`operations of the "Total" key, without changing the other
`transaction engine modules. Other examples of transaction
`engine modules are Cash Tender module and Sub-Total mod(cid:173)
`ule. This allows an efficient, low labor, low cost method of
`implementing different POS terminal functions.
`[0023] FIG. 3 is a flowchart showing how core transaction
`software could process a given key press action 11. This key
`press action 11 could be associated with one of the several
`keys on a point of sale terminal keyboard, touch screen or
`touch pad. The core transaction engine asks 12 if this key
`press action is a valid operation in the current state of the POS
`machine. If it is not 13, the user is warned via an indicator or
`message on the POS screen. If it is valid, the core transaction
`asks if the user has privilege 14. If the user does not have
`privilege, the transaction engine starts the manager override
`dialog 15, which asks the user for more information in order
`to gain access. If the user does have privilege, the transaction
`engine calls a configurable module 16 called the PosEvent
`virtual method to handle the required meaning of the key
`press action. After handling the tasks associated with the key
`press, the transaction engine returns control 17 back to the key
`press 11.
`[0024] The POS transaction is engine designed to allow
`easy extension of retail business logic through Java dynamic
`class loading. For example, ifanend user wants to modify the
`way the "Total Key" operates they only need to sub-class an
`abstract class (PosEvent) and make it available to the Java
`class loader. No other piece of code requires modification.
`The system accomplishes this design through a layered archi(cid:173)
`tecture. At the bottom is the POS context and electronic
`journal. These make up the core POS transaction engine by
`binding together the user context, system parameters and the
`transaction-processing engine. POS events interact with
`hardware and the core engine to accomplish the business
`logic. A hardware layer abstracts the POS events and the
`physical and virtual devices (key presses, peripheral I/O,
`input/output). Hardware abstraction classes manage receipt
`( or spooled) device I/O, interactive I/O ( operator prompts)
`and peripherals that invoke business logic directly (such as
`cash drawer close). The design utilizes an event model famil(cid:173)
`iar to most GUI application programmers. A listener is reg(cid:173)
`istered for events and these events are processed using classes
`derived from the base (virtual) PosEvent class. The POS event
`may be invoked or triggered in one of three ways: 1) Directly
`from a key press/GUI (graphical user interface) button press
`as shown in FIG. 3, 2) from a device event (credit card swipe,
`barcode scan, etc.), direct I/O or status change from JavaPOS
`devices or 3) programmatically from within other PosEvent
`derived classes or a dialog. An example of a dialog is shown
`in FIG. 3. A Start Manager override dialog box 15 is shown.
`This dialog box helps the system to determine if a user should
`be able to trigger the POS event 16 even though the user does
`not have "privilege" rights to do so.
`[0025] FIG. 4 is a more detailed diagram of the main
`embodiment of this invention. Stores 31, 32 illustrate several
`POS implemented with Java software using relational data(cid:173)
`bases. The boxes 31, 32 in FIG. 4 show each POS having its
`own relational database. This architecture offers an element
`
`Lightspeed Ex. 1006.6
`
`

`

`US 2008/0208696 Al
`
`Aug. 28, 2008
`
`3
`
`of security. Each BO client, which is an individual POS gets
`their own instance of a database. When they log into the BO
`they are attached to their own relational database associated
`and validated via their user login and password.
`[0026] Web Server 36 illustrates a BO implemented with
`Apache PHP using relational databases. PHP (recursive acro(cid:173)
`nym for "PHP: Hypertext Preprocessor") is a widely-used
`Open Source general-purpose scripting language that is espe(cid:173)
`cially suited for Web development and can be embedded into
`HTML (hypertext markup language). Apache is a web server
`currently used in over half of all web sites worldwide. PHP
`code is different from a script written in other languages like
`Perl or C. Instead of writing a program with lots of commands
`to output HTML, one can write an HTML script with some
`embedded code to do something (ie. to output some text). The
`PHP code is enclosed in special start and stop tags that allow
`you to jump into and out of"PHP mode". What distinguishes
`PHP from something like client-side JavaScript is that the
`code is executed on the server. If you were to have HTML
`script with PHP code imbedded in it, the client would receive
`the results of running that script, with no way of determining
`what the underlying code may be. You can even configure
`your web server to process all your HTML files withPHP. The
`advantages of using PHP are that it is extremely simple for a
`newcomer, free to use, but offers many advanced features for
`a professional programmer. A programmer can jump in and in
`a short time start writing simple scripts. Remote and local
`web browsers 33 illustrate a method used by store managers,
`corporate administrators, or system administers to access and
`view a company & its store's instantaneous performance from
`minute to minute. The POS, BO, and Web Browsers all com(cid:173)
`municate via the Web. 34. The protocols between the POS and
`Web browsers and BO servers is HTTPs, XMURPC. 35.
`XML-RPC is a remote procedure call protocol which uses
`XML to encode its calls and HTTP as a transport mechanism.
`It is a very simple protocol which defines only a handful of
`data types and commands.
`[0027] The key advantages of this point of sale system with
`a web-based back-office system are as follows. The web and
`PC architecture both offer full-scalability which results in
`improved performance and lower cost. There is a lower cost
`associated with projects developed with the technology of
`this invention due to the flexibility of easy design changes and
`well-understood software. There is less training required for
`programmers and system testers. Projects can draw on the
`huge talent pool in the open source development community.
`The invention allows configurable modules for different types
`of businesses and sales promotions. The invention allows
`remote monitoring of both the POS and back-office systems
`from anywhere via the web. There is minimal time required
`for POS installation, since POS setup is as basic as a home PC
`setup. Another advantage is that the back-office system can be
`provided as a service or deployed within a corporation. For
`example, Software as a Service (SAAS) is a software distri(cid:173)
`bution model in which applications are hosted by a vendor or
`service provider and made available to customers over a net(cid:173)
`work, typically the Internet. Another advantage of this inven(cid:173)
`tion is that the back-office system is maintained in customer
`centric databases, making it impossible for customers to see
`other's data. Each BO client (individual POS, store or multi(cid:173)
`store owner) gets their own instance of a database. When they
`log into the BO they are attached to their own relational
`database associated and validated via their user login and
`password.
`
`[0028] While this invention has been particularly shown
`and described with Reference to the preferred embodiments
`thereof, it will be understood by those Skilled in the art that
`various changes in form and details may be made without
`Departing from the spirit and scope of this invention.
`
`What is claimed is:
`1. A point of sale system with a web-based back-office
`system, comprising:
`one or more point of sale, POS, terminals and
`one or more web servers,
`wherein said POS terminals and said web servers commu(cid:173)
`nicate via internet protocols,
`wherein said POS terminals are implemented with per(cid:173)
`sonal computer hardware and software using one or
`more relational databases,
`wherein said web server is implemented with web server
`hardware and software, using one or more relational
`databases.
`2. The point of sale system with a web-based back-office
`system of claim 1 wherein said POS terminals and said web
`servers are implemented with executable, configurable soft(cid:173)
`ware modules, wherein said modules can be easily changed to
`implement different functions for different businesses.
`3. The point of sale system with a web-based back-office
`system of claim 1, wherein said POS terminals can operate
`standalone without communicating with said web server.
`4. The point of sale system with a web-based back-office
`system of claim 1, wherein said POS system and said web(cid:173)
`based back-office servers are scalable allowing the addition
`of POS terminals and business locations without degrading
`system performance.
`5. The point of sale system with a web-based back-office
`system of claim 1, wherein a real-time status of said POS
`terminals and said back-office web servers is obtained at
`remote locations via personal computers with browser based
`web access.
`6. A web-based back-office system comprising:
`one or more web servers,
`wherein said web servers are implemented with web server
`hardware and software, using one or more relational
`databases,
`wherein said web servers can communicate with point of
`sale, POS, terminals via internet protocols.
`7. The web-based back-office system of claim 6, wherein
`said web servers are implemented with executable, config(cid:173)
`urable software modules, wherein said modules can be easily
`changed to implement different functions for different busi(cid:173)
`nesses.
`8. The web-based back-office system of claim 6, wherein
`said web servers allow said POS terminals to operate standa(cid:173)
`lone without communicating with said web servers.
`9. The web-based back-office system of claim 6, wherein
`said web-based back office is scalable allowing the addition
`of POS terminals and business locations without degrading
`system performance.
`10. The web-based back-office system of claim 6, wherein
`a real-time status of said POS terminals and/or said back(cid:173)
`office system is obtained at remote locations via personal
`computers with browser based web access.
`11. A point of sale POS system comprising,
`one or more point of sale, POS, terminals,
`wherein said POS terminals can communicate with web
`servers via internet protocols,
`
`Lightspeed Ex. 1006.7
`
`

`

`US 2008/0208696 Al
`
`Aug. 28, 2008
`
`4
`
`wherein said point of sale terminals are implemented with
`personal computer hardware and software, using one or
`more relational databases.
`12. The point of sale POS system of claim 11, wherein said
`POS terminals are implemented with executable, config(cid:173)
`urable software modules, wherein said modules can be easily
`changed to implement different functions for different busi(cid:173)
`nesses.
`13. The point of sale POS system of claim 11, wherein said
`POS terminals can operate standalone without communicat(cid:173)
`ing with said web servers.
`14. The point of sale POS system of claim 11, wherein said
`POS system are scalable allowing the addition of POS termi(cid:173)
`nals and business locations without degrading system perfor(cid:173)
`mance.
`15. The point of sale POS system of claim 11, wherein a
`real-time status of said POS terminals and/or said back-office
`web servers is obtained at remote locations via personal com(cid:173)
`puters with browser based web access.
`16. A method of providing a point of sale system with a
`web-based back-office system, comprising the steps of:
`providing one or more point of sale, POS, terminals and
`providing one or more web servers,
`wherein said POS terminals and said web servers commu(cid:173)
`nicate via internet protocols,
`wherein said POS terminals are implemented with per(cid:173)
`sonal computer hardware and software using one or
`more relational databases,
`wherein said web server are implemented with web server
`hardware and software, using one or more relational
`databases.
`17. The method of providing a point of sale system with a
`web-based back-office system of claim 16 wherein said POS
`terminals and said web servers are implemented with execut(cid:173)
`able, configurable software modules, wherein said modules
`can be easily changed to implement different functions for
`different businesses.
`18. The method of providing a point of sale system with a
`web-based back-office system of claim 16, wherein said POS
`terminals can operate standalone without communicating
`with said web server.
`19. The method of providing a point of sale system with a
`web-based back-office system of claim 16, wherein said POS
`system and said web-based back-office servers are scalable
`allowing the addition of POS terminals and business locations
`without degrading system performance.
`20. The method of providing a point of sale system with a
`web-based back-office system of claim 16, wherein a real(cid:173)
`time status of said POS terminals and said back-office web
`servers is obtained at remote locations via personal comput(cid:173)
`ers with browser based web access.
`
`21. A method of providing a web-based back-office system
`comprising the steps of:
`providing one or more web servers,
`wherein said web servers are implemented with web server
`hardware and software, using one or more relational
`databases,
`wherein said web servers can communicate with point of
`sale, POS, terminals via internet protocols.
`22. The method of providing a web-based back-office sys(cid:173)
`tem of claim 21, wherein said web servers are implemented
`with executable, configurable software modules, wherein
`said modules can be easily changed to implement different
`functions for different businesses.
`23. The method of providing a web-based back-office sys(cid:173)
`tem of claim 21, wherein said web servers allow said POS
`terminals to operate standalone without communicating with
`said web servers.
`24. The method of providing a web-based back-office sys(cid:173)
`tem of claim 21, wherein said web-based back-office is scal(cid:173)
`able allowing the addition of POS terminals and business
`locations without degrading system performance.
`25. The method of providing a web-based back-office sys(cid:173)
`tem of claim 21, wherein a real-time status of said POS
`terminals and/or said back-office system is obtained at remote
`locations via personal computers with browser based web
`access.
`26. A method of providing a point of sale POS system
`comprising the steps of:
`providing one or more point of sale, POS, terminals,
`wherein said POS terminals can communicate with web
`servers via internet protocols,
`wherein said point of sale terminals are implemented with
`personal computer hardware and software, using one or
`more relational databases.
`27. The method of providing a point of sale POS system of
`claim 26, wherein said POS terminals are implemented with
`executable, configurable software modules, wherein said
`modules can be easily changed to implement different func(cid:173)
`tions for different businesses.
`28. The method of providing a point of sale POS system of
`claim 26, wherein said POS terminals can operate standalone
`without communicating with said web servers.
`29. The method of providing a point of sale POS system of
`claim 26, wherein said POS system are scalable allowing the
`addition of POS terminals and business locations without
`degrading system performance.
`30. The method of providing a point of sale POS system of
`claim 26, wherein a real-time status of said POS terminals
`and/or said back-office web servers is obtained at remote
`locations via personal computers with browser based web
`access.
`
`* * * * *
`
`Lightspeed Ex. 1006.8
`
`