SYSTEM AND METHOD FOR REMOTE MANAGEMENT OF SALE TRANSACTION DATA

• US 20150278789A1
• Filed: 04/01/2015
• Published: 10/01/2015
• Est. Priority Date: 03/02/2010
• Status: Abandoned Application

• Current Assignee: ShopKeep, Inc. (Lightspeed Commerce, Inc.)
• Original Assignee: Shopkeep.com Incorporated
• Inventors: Richelson, Jason, Ordway, Jason
• Application Number:
  US14/676,146
• Publication Number:
  US 20150278789A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

This invention discloses a novel system and method for providing retail point of sale terminals that are connected securely over the Internet to a back-office service that manages the retailer'"'"'s data as a service using a system that supports more than one retailer, each of which will have one or more point of sale terminals. The system is adapted to provide transaction reconciliation with an accounting system whenever a user ends a shift and logs out of the register instance they are operating.

Claims

1. A system for managing sale transaction data comprising:

a register instance operated by a user running on a register terminal associated with a vendor, said register terminal connected by a data network to a server, said server being connected to a database comprised of a portion associated with the vendor;

a module adapted to detect the condition that the register instance has entered the completed session state for the user in dependence on such detection, update to a closed state at least one data tag associated with at least one corresponding transaction records associated with the user and the completed session;

a module adapted to store the at least one updated data tags in a data storage device; and

a module adapted to transmit to an accounting system the at least one closed transaction data records associated with the user.

2. The system of claim 1 further comprising a module adapted to run a shift reconciliation process on the at least one closed transaction records.

3. The system of claim 2 further comprising a module adapted to update at least one data tag associated with the corresponding at least one transaction tickets associated with the user that are stored on the register terminal to the closed state and transmit the updated transaction tickets associated with the user to the server.

4. The system of claim 2 further comprising a module adapted to transmit a closed state status update command to the server and transmit a user identifier to the server, said user identifier associated with the closed state status update.

5. The system of claim 2 further comprising a module adapted to transmit to the server at least one data message comprised of a reference number associated with a corresponding transaction ticket associated with the user stored on the server and an open/close state data value, and where the module adapted to detect the condition is further configured to detect the open/close state data value and in dependence on the open/close state data value, change the data tag associated with the transaction ticket corresponding to the reference number to the closed state.

6. The system of claim 2 where shift reconciliation module is further configured to receive at the server a session completion status message, receive at the server an identifier associated with the user, and update at least one transaction records stored on the server that are associated with the user that are in the open state to the closed state.

7. The system of claim 1 where the module adapted to transmit is adapted to periodically sweep transaction ticket data that is in the closed state and transmit the swept data to the accounting system.

8. The system of claim 7 where the module adapted to transmit is further adapted to sweep transaction ticket data that is in the closed state at a predetermined time.

9. The system of claim 1 the module adapted to transmit is adapted to receive a command to sweep closed transaction ticket data and in dependence on receiving such command, transmit the swept transaction data to an accounting system.

10. The system of claim 1 where the shift reconciliation module is further configured to check that all of the closed transaction tickets associated with the user that are residing on the register instance are synchronized between the register instance and the transaction data records stored in the database on the server.

11. The system of claim 10 where the shift reconciliation module is further configured to:

detect whether the data in the closed transaction tickets associated with the user stored on the server are correct or incorrect.

12. The system of claim 11 the shift reconciliation module is further configured to:

receive a first value representing an amount of cash associated with the register terminal;

determine if the at least one closed transaction tickets indicating a cash transaction associated with the completed session are not consistent with the received first value amount of cash and in dependence on such determination, transmit to the register terminal an error message.

13. The system of claim 12 the shift reconciliation module is further configured to:

receive a second value representing a revised amount of cash associated with the register terminal on the register terminal; and

determine if the at least one closed transaction tickets indicating a cash transaction associated with the completed session are not consistent with the received second value amount of cash, and in dependence on such determination, transmit to the register terminal an error message.

14. The system of claim 11 where the shift reconciliation module is further configured to:

receive from the register instance a message representing an error adjustment; and

store a transaction ticket associated with user and the completed session that is comprised of at least one value in the error adjustment message.

15. The system of claim 11 where the shift reconciliation module is further configured to:

transmit an error message to an authorized person associated with the vendor, said message comprised of an identity of the user and a time value, and a type of error.

16. The system of claim 11 where the shift reconciliation module is further configured to:

detect a reconciliation error; and

transmit an error message to an authorized person associated with the vendor.

17. The system of claim 16 where the shift reconciliation module is further configured to:

store a reason slug associated with the detected reconciliation error, said slug comprised of data values representing the type of error.

18. The system of claim 17 where the system is adapted so that the type of error is one of jammed_register, missing_uuids, incorrect_checksum.

19. The system of claim 1 where the system is further comprised of a module adapted to:

receive transaction data from the register instance;

detect a problem that prevents the received transaction data from being stored as a transaction record in the database;

in dependence on such detection, store the received transaction data as a rescue blob;

receive commands to convert the data stored as a rescue blob into a transaction data record;

store the transaction record comprised of data stored in the rescue blob; and

run a shift reconciliation process.

20. The system of claim 19 where the detected problem is a credit card transaction error.

21. The system of claim 19 where the detected problem is a data error.

22. The system of claim 19 where the detected problem is a protocol error.