IP Library Granted Patent US 9,672,572
Granted Patent B2
US 9,672,572 · App. 14/218,268 · Granted Jun 6, 2017

Real-time availability of omni-channel sales data

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,672,572
App. No.
14/218,268
Granted
Jun 6, 2017
Kind
B2
Abstract

Techniques of implementing providing real-time availability of omni-channel sales data are disclosed. In some example embodiments, purchase information comprising information of purchases made by a consumer via a plurality of retail channels is received by a back-end system. The purchase information can be stored on the back-end system. A request to access the stored purchase information can be received from the consumer on a computing device. The request can comprise an identification of a virtual host and an identification of a service to invoke on the back-end system to retrieve the purchase information stored on the back-end system. An identification of an internal host can be determined based on the identification of the virtual host. The identification of the internal host can identify the back-end system. The purchase information can be retrieved from the back-end system using the identification of the internal host and the identification of the service.

Claims (36)

1. A computer-implemented method comprising:

receiving, by a back-end system, purchase information comprising information of purchases made by a consumer via a plurality of retail channels;

storing the received purchase information of the consumer in a database on the back-end system;

receiving, from the consumer on a computing device, a request to access the stored purchase information, the request comprising an identification of a virtual host and an identification of a service to invoke on the back-end system to retrieve the purchase information stored on the back-end system, the identification of the service comprising an OData Uniform Resource Locator (URL) that identifies an Open Data Protocol (OData) service on the back-end system;

determining, by a machine having a memory and at least one processor, an identification of an internal host based on the identification of the virtual host, the identification of the internal host identifying the back-end system;

retrieving, from the database, the purchase information using the identification of the internal host and the identification of the service, the purchase information being retrieved using a concatenation of the OData URL with the identification of the internal host; and

providing the retrieved purchase information to the consumer on the computing device.

2. The method of claim 1 , wherein the plurality of retail channels comprises a brick-and-mortar retail channel and an online retail channel.

3. The method of claim 1 , wherein the back-end system is dedicated to a single retail entity having a central management, the single retail entity having transacted the purchases made by the consumer.

4. The method of claim 3 , wherein the single retail entity comprises a plurality of chain stores.

5. The method of claim 3 , wherein the back-end system is part of a private network of the single retail entity, and the back-end system is used by the single retail entity to manage purchase transactions and product inventory.

6. The method of claim 5 , wherein the purchase information is made available for retrieval and presentation to the consumer on the computing device in real-time or near real-time with respect to the purchase information being stored on the back-end system.

7. The method of claim 1 , wherein the purchase information is received by the back-end system in real-time or near real-time with respect to completion of the corresponding purchases.

8. A system comprising:

a machine having a memory and at least one processor; and

aback-end system configured to:

receive purchase information comprising information of purchases made by a consumer via a plurality of retail channels; and

store the received purchase information of the consumer in a database on the back-end system; and

a cloud connector on the machine configured to:

receive, from the consumer on a computing device, a request to access the stored purchase information, the request comprising an identification of a virtual host and an identification of a service to invoke on the back-end system to retrieve the purchase information stored on the back-end system, the identification of the service comprising an OData Uniform Resource Locator (URL) that identifies an Open Data Protocol (OData) service on the back-end system;

determine an identification of an internal host based on the identification of the virtual host, the identification of the internal host identifying the back-end system; and

retrieve, from the database, the purchase information from the back-end system using the identification of the internal host and the identification of the service, the purchase information being retrieved using a concatenation of the OData URL with the identification of the internal host.

9. The system of claim 8 , wherein the plurality of retail channels comprises a brick-and-mortar retail channel and an online retail channel.

10. The system of claim 8 , wherein the back-end system is dedicated to a single retail entity having a central management, the single retail entity having transacted the purchases made by the consumer.

11. The system of claim 10 , wherein the single retail entity comprises a plurality of chain stores.

12. The system of claim 10 , wherein the back-end system is part of a private network of the single retail entity, and the back-end system is used by the single retail entity to manage purchase transactions and product inventory.

13. The system of claim 12 , wherein the purchase information is made available by the back-end system for retrieval and presentation to the consumer on the computing device in real-time or near real-time with respect to the purchase information being stored on the back-end system.

14. The system of claim 8 , wherein the back-end system is further configured to receive the purchase information in real-time or near real-time with respect to completion of the corresponding purchases.

15. A non-transitory machine-readable storage medium, tangibly embodying a set of instructions that, when executed by at least one processor, causes the at least one processor to perform a set of operations comprising:

receiving, by a back-end system, purchase information comprising information of purchases made by a consumer via a plurality of retail channels;

storing the received purchase information of the consumer in a database on the back-end system;

receiving, from the consumer on a computing device, a request to access the stored purchase information, the request comprising an identification of a virtual host and an identification of a service to invoke on the back-end system to retrieve the purchase information stored on the back-end system, the identification of the service comprising an OData Uniform Resource Locator (URL) that identifies an Open Data Protocol (OData) service on the back-end system;

determining an identification of an internal host based on the identification of the virtual host, the identification of the internal host identifying the back-end system; and

retrieving, from the database, the purchase information using the identification of the internal host and the identification of the service, the purchase information being retrieved using a concatenation of the OData URL with the identification of the internal host; and

providing the retrieved purchase information to the consumer on the computing device.

16. The non-transitory machine-readable storage medium of claim 15 , wherein the plurality of retail channels comprises a brick-and-mortar retail channel and an online retail channel.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2014
From: LEHNERT, BERND; MICHAUD, MARK; GRENIER, YAN
To: SAP AG
Reel/Frame 033718/0927 →
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →