METHOD, SYSTEM, AND MEDIUM FOR TRANSFORMING TRANSACTION DATA TO SUBSCRIPTION DATA USING DISPARATE COMPUTING PLATFORMS

Abstract

Techniques for transforming transaction data to subscription data using disparate computing platforms is described, including receiving an input configured to request data associated with a product, generating javascript used to render a web page including the data retrieved using a product identifier, invoking a controller script to request a widget file generated compositely to include an offer identifier, a session identifier, a merchant identifier, and the product identifier, calling a platform associated with the second server to determine whether a subscription is associated with the product identifier, and injecting the data, other data, and further data in a composite interface that is configured to simultaneously present a shopping cart with product content and subscription content.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is continuation application of copending U.S. patent application Ser. No. 16/590,210, filed Oct. 1, 2019 and entitled, “METHOD, SYSTEM, AND MEDIUM FOR TRANSFORMING TRANSACTION DATA TO SUBSCRIPTION DATA USING DISPARATE COMPUTING PLATFORMS,” U.S. patent application Ser. No. 16/590,210 is a continuation application of U.S. patent application Ser. No. 13/962,213, filed Aug. 8, 2013, now U.S. Pat. No. 10,453,112 and entitled “METHODS, APPARATUS, AND COMPUTER READABLE MEDIUM FOR CONVERTING ONE-TIME BUYERS OF A PRODUCT/SERVICE INTO SUBSCRIBERS,” U.S. patent application Ser. No. 13/962,213 claims the benefit of U.S. Provisional Patent Application No. 61/791,873, filed Mar. 15, 2013 and entitled “AUTOMATED METHOD AND SYSTEM FOR CONVERTING ONE-TIME BUYERS OF A PRODUCT/SERVICE INTO RECURRING SUBSCRIBERS,” all of which are herein incorporated by reference in their entirety for all purposes.

FIELD

The present disclosure relates to computer and data science and data analytics. More specifically, the present disclosure relates to a data processing and analytics topology configured to transform transaction data to subscription data using disparate computing platforms.

BACKGROUND

Prior to the advent of Internet-based shopping, retailers and service providers grew accustomed to maintaining a loyal following of regular customers. Due to limited access to information about prices, quality of goods and services, and customer service provided by the retailers and/or service providers, a customer was likely to seek out a source for a particular good or service once and, if pleased with the good or service, return to the retailer or service provider for subsequent purchases.

As the Internet has progressed in the past several years, retailers and service providers have established online stores. As more and more retailers and service providers establish these online stores, customers' ability to access information pertinent to the retailers and service providers is increased dramatically. Instead of regularly returning to a particular retailer or service provider that the customers had become accustomed to frequently purchasing from, the customers are now able to seek out the most attractive offer for each of their individual purchases.

While this increase in access to information might be beneficial to the customers, retailers and service providers may, as a result, experience unpredictable fluctuations in purchases as well as difficulty retaining customers due to this increase in Internet-based information and the resulting purchases.

SUMMARY

Embodiments provide subscription platforms that can be incorporated into merchant webpages to implement a subscription service on pre-existing online stores. In accordance with the embodiments, subscription platforms are provided that respond at least in part to the foregoing issues and/or other issues. Platforms of the current embodiment enable Internet-based retailers or service providers (hereinafter umerchants”) to add subscription services to their existing online stores.

In one embodiment, the presently disclosed subject matter (hereinafter usystem”) receives from the merchant's website an indication that a potential customer has accessed a web page pertaining to a product or service. The system, in response to the indication, builds a subscription offer pertaining to the product or service. The system sends the subscription offer to the merchant's website. If the customer accepts the subscription offer, the system receives an indication from the merchant's website and the system builds a subscription order pertaining to the accepted subscription offer. At a time determined by the accepted subscription offer, the system sends the subscription order to the retailer or service provider's website.

The system can determine whether a subscription is available prior to building the subscription offer. In various embodiments, the system builds content pertaining to a product related to the subscription offer and sends that content to the merchant's website for presentation to the customer. In further embodiments, the subscription offer may be contained in a widget, a module, etc. The widget of the current embodiments deploys to the merchant's website an application program interface that receives the subscription order pertaining to the accepted subscription offer. The system can deploy a module to the retailer's or service provider's website that conveys terms of the subscription offer.

BRIEF DESCRIPTION OF THE DRAWINGS

Various novel and non-obvious features of the disclosed subject matter are set forth in the claims. The disclosed subject matter itself, however, as well as modes of use, will best be understood by reference to the detailed description when read in conjunction with the accompanying drawings, wherein:

FIG. 1 depicts one embodiment of the method in which the system tracks and collects information, builds subscription offers, and delivers those subscription offers to the merchant's website.

FIG. 2 depicts one embodiment of the subscription ordering system as an overview.

FIG. 3 depicts one embodiment of the process of building a subscription offer.

FIG. 4 depicts one embodiment of the process of building a subscription order.

FIG. 5 depicts a screenshot of one embodiment of a merchant's product page with a subscription offer being displayed.

FIG. 6 displays a screenshot of one embodiment of a merchant's online shopping cart with an accepted subscription offer applied.

FIG. 7 displays a screenshot of one embodiment of a merchant's customer interface.

FIG. 8 displays a screenshot of one embodiment of a merchant's product page with an option to add the product to the customer's subscription order injected into the page.

FIG. 9 displays a screenshot of one embodiment of a subscription offer for a customer that has already accepted another subscription offer.

DETAILED DESCRIPTION

Reference is now made to the drawings, in which the same reference numbers are used throughout the different figures to designate the same components.

The subscription platform and related external components and methods (hereinafter, the “system”) of the current embodiments provide subscription-related content and offers to Internet-based merchants. The system of the current embodiments also responds to a subscription offer accepted by a merchant's customer by creating a related subscription order.

FIG. 1 depicts one embodiment of the method in which the system 100 interacts with a merchant's product or service webpage. When the system receives from the merchant an indication of a product-page load status on the merchant website the offer builder 108 determines if a subscription is available via the subscription database 104. If a subscription is available the subscription offer is injected into the merchant's webpage via the widget builder 106. The injected subscription offer is displayed on the merchant's product or service page 112 in the current embodiment.

The subscription tracker 114 tracks the information contained in the merchant's online shopping cart 116. Subscription tracker 114 and the cart 116 also receives an indication when a subscription offer was accepted by a customer. The subscription builder 110 receives a notification from the subscription tracker 114 when the customer accepts the subscription offer. The subscription builder 110 handles the subscription order.

The customer interface 102 is accessible to a customer that has accepted a subscription offer. The customer interface 102 allows a customer to edit the terms of a subscription. The subscription builder 110 is notified when there is a change to the subscription via the customer interface 102 and can re-build the subscription if necessary.

When an online merchant's customer is ready to purchase the merchant's good or service they navigate to the merchant back end 120. The system's subscription information is incorporated into the merchant back end 120.

FIG. 2 depicts one embodiment of the process flow of the system. When an action occurs on a merchant's product or service webpage the system receives a load status indication 200 from an online merchant's webpage.

In some embodiments, the system builds a subscription offer at reference 202 in response to a load status indication from the merchant's webpage. In other embodiments, the system can first determine if a subscription is available for the particular product or service related to the received load status indication.

Once a subscription offer is prepared, the system injects the subscription offer into the merchant's product or service webpage. See reference 204. In some embodiments, the system can enter a wait state after injecting the subscription offer into the merchant's webpage. In other embodiments, the system can monitor the customer's activity on the merchant's webpage to determine if the subscription offer was accepted or not.

The system receives an indication that the subscription offer was accepted. See reference 206. The system subsequently builds a subscription order based on the accepted subscription offer at a time indicated in the accepted subscription offer. See reference 208. At that time, the system sends the subscription order pertaining to the accepted subscription offer to the merchant website via the network interface. See reference 210.

FIG. 3 depicts one embodiment of the process in which the system determines if a subscription is available fora particular product or service and subsequently builds and delivers a subscription offer for said product or service.

The system receives information related to a product or service webpage on a merchant's website at reference 300. In one embodiment, the information related to the product or service is a product or service identifier. In other embodiments, the information can be an alpha-numeric merchant identifier and an alpha-numeric product or service identifier such that the system can determine subscription availability.

The system determines if a subscription offer is available. See reference 302. In some embodiments, the system can determine whether a subscription offer is available via a database containing available subscriptions. In other embodiments, the system can determine if a subscription is available by communicating with the merchant and/or the merchant's website.

If the system determines that no subscription is available, the system will not pursue further the subscription building process at reference 304.

On the other hand, if the system determines that a subscription is available at reference 302, the system will process the product or service information and build a subscription offer at reference 306. In some embodiments, the subscription offer comprises an offer to the customer that will allow them to have the particular product or service pertaining to the subscription ordered on terms in accordance with the subscription. In other embodiments, the subscription offer can include incentives to encourage the customer to accept the subscription offer. In some embodiments, the incentive can include a discounted price for the good or service. In other embodiments, the incentive can include reduced shipping and/or handling charges, coupons for other goods or services offered by the merchant, etc.

Once the subscription offer is built, the subscription offer is injected into the merchant's website at reference 308. In some embodiments, the subscription offer is an add-on module to the merchant's website, such that the customer can see both the entire merchant's webpage as well as the content injected into that webpage by the system. In other embodiments, the system injects webpage code into the merchant's webpage so that the system's additions perform such operations on the merchant's webpage.

FIG. 4 depicts one embodiment of the system's response to an indication that a subscription offer was accepted and other related information. The system receives an indication when the customer accepts the subscription offer at reference 400. In some embodiments, the merchant's customer can accept the subscription offer via a button injected into the merchant's webpage by the system. In other embodiments, the subscription offer can be accepted when the customer selects a subscription offer acceptance indicator and adds the product or service to their online shopping cart.

After receiving the subscription acceptance notification at reference 400, the system computes the terms of the subscription at reference 402. The subscription terms can include the date of the subscription order, the price of the good or service, etc.

Once the terms of the subscription offer are computed at reference 402, the system creates a subscription order at reference 404 from a variety of information collected during the subscription process. The system delivers the subscription order to the merchant website at a time indicated in the accepted subscription offer at reference 406. The information sent from the system to the merchant's website allows the merchant website to extract the order related information from each subscription related order and places the orders accordingly. It is the merchant website of the current embodiment, therefore, that processes each of these orders. Note also that each of these orders is for the product on the particular product page from which the subscription offer arose.

FIG. 5 depicts a screenshot of a merchant's product webpage 500. The system has injected a subscription offer 502 into the merchant's product webpage. The injected subscription offer includes the option to deliver the product only once 504. This can be equated to the customer not accepting the subscription offer. The merchant shopping cart 116 can process such orders. The injected subscription offer also includes the option to deliver the product 506 in accordance with the terms of the offered subscription. This includes the incentive of an offer for a discounted price for the product. In addition, the injected offer includes various options 508 and a hyperlink 510 which allows the customer to view the terms of the subscription offer.

FIG. 6 depicts a screenshot of a customer's shopping cart 600 on a merchant's website with the subscription related information injected by the system. The subscription terms 602 are displayed to the customer for review. In addition, the option to modify the subscription and/or its terms 604 is available. The discounted price 606 is injected into the merchant's webpage as well.

FIG. 7 depicts a screenshot of one embodiment of the customer interface 102. The customer interface 102 contains information related to the customer's subscription, options for modification of the subscription, and other subscription related content. The customer interface 102 displays the date of the next subscription order 702, per the terms of the subscription, as well as hyperlinks that allow the customer to edit their subscription details. Multiple individual subscriptions can be managed by the customer via the subscription interface simultaneously.

In some embodiments, the system can also inject an offer 704 to the customer to add another product which is available from that merchant. In this case, the system receives an indication that the customer has selected the product offer when the customer selects the add product button 706.

FIG. 8 depicts a screenshot of a merchant's product page 800. The system has injected an offer 802 to add the product related to the product page 800 to an already existing subscription order.

FIG. 9 depicts a screenshot of the webpage response 900 in relation to a customer selecting the subscription offer 802 from FIG. 8. The pop-up window provides the customer with several options related to the subscription offer. In the current embodiment, the first option is to add the product to an existing subscription order 902 for one-time delivery in accordance with the terms of the subscription. In addition, the option to add the product to an existing subscription order and/or modify the subscription order 904 for the product is available. The system collects information related to which selection is made. If the system receives a notification that option 904 was chosen, the frequency for the subscription order related to the product is also received and the subscription order is modified accordingly.

An option to add the product to the customer's online subscription order and return to the merchant's website 906 as well as an option to add the product to the customer's subscription order and to be transferred to a subscription order review webpage 908 are injected by the system. In some embodiments, the system can collect additional information related to the subscription offer 904 such as the quantity of the product desired. In other embodiments, the subscription offer 904 can include incentives to encourage the customer to accept the subscription offer.

Embodiments of the system 100 can provide subscription-related content and subscription-related offers to merchant webservers. The system responds to accepted subscription offers by creating subscription orders and sending them to the merchant websites 112 in accordance with the subscriptions.

Various embodiments of the system 100 operate in an e-commerce environment that includes the Internet 122 or some other wide area network (WAN) to facilitate communications among various parties. These parties include merchants, their customers, and the system. The independent merchant websites typically include numerous product pages 112. Each of these product pages provides information pertaining to a particular and corresponding product to the customers. The independent merchant websites also include shopping carts 116 or similar e-commerce mechanisms to receive, process, accept payment for, and fulfill orders placed by the customers with the merchants. These e-commerce mechanisms would often exist on the merchant website with or without the remainder of the system.

Embodiments of the system allow customers to subscribe to various products while the independent merchants deliver the products in accordance with orders received via shopping carts 116 operated by those merchants. The system 100 does, however, manage the subscription process.

When a customer navigates to a particular merchant website, the merchant website presents to the customer the various product pages 112. The customer browses through these product pages 112 and/or navigates to particular product page 112 according to their interests and desires. The system 100 does not consider in its processing how the customer navigates to a particular product page.

In some embodiments, the system 100 can track the progress of activities in the customer's shopping cart 116 by implementing a controller script that waits until a product page 112 is fully loaded. The system receives an indication 124 from the merchant s website that includes the user's session ID, the merchant's ID, a product ID, etc. The system can use the foregoing information to determine if a product subscription is available. If a subscription is available, the system produces and delivers a subscription offer to the merchant's website.

In various embodiments, the injected offer includes a hypertext markup language (HTML) control that allows the customer to accept the subscription offer. This control does not provide the customer with the capability of actually ordering the product. Rather, this control operates only in the context of accepting the subscription offer. In those situations in which the customer accepts the subscription offer, the system receives an indication of that acceptance. The controller script computes the discounted, subscription-based price for the product and sends that information to the merchant's shopping cart 116 for that customer.

Once the customer completes their shopping, the system 100 creates subscriptions for each product that corresponds to an accepted subscription offer and stores pertinent subscription-related information in a subscription database 104. Thus, as it relates to subscription offers, the system of the current embodiment operates independently of the merchant website. Moreover, the system of the current embodiment manages only the subscriptions and not the customer's orders.

It might be worth noting that a subscription is a contractual agreement between the merchant and the customer whereby the customer often receives a discounted rate on a given product in return for agreeing to purchase that product from the merchant on a regular basis.

In the present embodiment, the system 100 builds subscription orders for a particular product on a day determined in accordance with the terms of the accepted subscription offer. The system 100 can create a file corresponding to that subscription order and transmit that file to the merchant's website via an application program interface (API) 118 provided by the system.

The merchant backend 120 fulfills the order in accordance with their pre-existing practices. The system 100 builds subsequent subscription related orders 110 in accordance with the terms of the subscription.

In some embodiments, the system 100 allows the merchant's customers to access and manage the customer's subscriptions via a subscription interface 102. The system 100 can inject the customer interface 102 into the merchant's website. The content of the subscription interface can be rendered based on the merchant's ID, a randomly generated hash which acts as a password, and/or among other information. After logging into that particular merchant's website, a customer can view their subscriptions related to that merchant and modify the terms of their subscription via the customer interface 102. In addition, the system can accept additional subscriptions from a customer via the customer interface 102.

Claims

1. A method, comprising

receiving an input configured to request data associated with a product; generating javascript used to render a web page including the data retrieved using a product identifier from a first server; receiving data representing a web page load status indication that indicates an action occurring on the web page as displayed in a user interface, a received web page load status indication being formed when an action is detected on the web page, the action changing the web page as displayed on the user interface; invoking a controller script responsive to the web page load status indication to track activities associated with an online shopping cart presented on the web page, the web page load status indication including data representing the activities being further associated with one or more of an offer associated with the product, a session identifier, a merchant identifier, and the product identifier, the offer being retrieved by a second server and presented on the web page; performing a program call to a platform associated with the second server to determine whether a subscription is associated with the product identifier related to the received web page load status indication; deploying a widget to the web page, the widget being configured to retrieve the offer from the second server over an application program interface (“API”), the offer being used to build a subscription offer and configured to inject the subscription offer into the widget on the web page; generating a user control input using a markup language, the user control input being configured to receive data indicating acceptance of the subscription offer on the web page, the markup language being associated with the product identifier if the subscription is associated with the product identifier; injecting other data into the web page associated with the product identifier, the other data being used to display the data into the web page and the online shopping cart, whereby the other data is rendered with the web page to form a composite interface that is configured to simultaneously present the online shopping cart displaying product content and subscription related content, the online shopping cart being presented with the web page in the user interface; and using the merchant identifier and a hashing algorithm to generate a password, the password being configured to be transmitted from the platform to the second server in the program call when requesting the other data.