Patent Grant
12141853
Various embodiments relate generally to data science and data analysis, computer software and systems, and control systems to provide a platform to facilitate implementation of an interface, and, more specifically, to a computing and data storage platform that implements specialized logic to facilitate predictive consumption of a sample of an item in accordance with an automatically adaptive schedule.
Advances in computing hardware and software, as well as computing networks and network services, have bolstered growth of Internet-based product and service procurement and delivery. For example, online shopping, in turn, has fostered the use of “subscription”-based delivery computing services with an aim to provide convenience to consumers. In particular, a user becomes a subscriber when associated with a subscriber account, which is typically implemented on a remote server for a particular seller. In exchange for electronic payment, which is typically performed automatically, a seller ships a specific product (or provides access to a certain service) at periodic times, such as every three (3) months, every two (2) weeks, etc., or any other repeated periodic time intervals. With conventional online subscription-based ordering, consumers need not plan to reorder to replenish supplies of a product.
But conventional approaches to provide subscription-based order fulfillment, while functional, suffer a number of other drawbacks. For example, traditional subscription-based ordering relies on computing architectures that predominantly generate digital “shopping cart” interfaces with which to order and reorder products and services. Traditional subscription-based ordering via shopping cart interfaces generally rely on a user to manually determine a quantity and a time period between replenishing shipments, after which the quantity is shipped after each time period elapses. Essentially, subscribers receive products and services on “auto-pilot.”
So while the conventional approaches to implementing shopping cart interfaces may be functional for stable rates of consumption, such approaches are not well-suited to facilitate timely reordering of products and services with which consumers may use at rates that vary from the fixed periods of time between repeated deliveries. Thus, conventional approaches to reordering or procuring subsequent product and services deliveries are plagued by various degrees of rigidity that interject sufficient friction into reordering that cause some users to either delay or skip making such purchases. Unfortunately, such friction causes some users to supplement the periodic deliveries manually if an item is discovered to be running low more quickly than otherwise might be the case (e.g., depleting coffee, toothpaste, detergent, wine, or any other product more quickly than normal).
Examples of such friction include “mental friction” that may induce stress and frustration in such processes. Typically, a user may be required to rely on one's own memory to supplement depletion of a product and services prior to a next delivery (e.g., remembering to buy coffee before running out) or time of next service. Examples of such friction include “physical friction,” such as weighing expending time and effort to either physically confront a gauntlet of lengthy check-out and shopping cart processes, or to make an unscheduled stop at a physical store.
Typical online approaches, including conventional shopping cart interfaces, suffer from less than optimal means with which to reconcile the different rates of product and service usage of different users. One prevalent consequence of mismatches between time periods for delivering subscribed products or services and consumption rates by consumers is that, over time, the supply of a subscribed item is either over-delivered or under-delivered. An oversupply of subscribed product or service typically degrades consumer experience due to a number of reasons. For example, subscribers may believe that a seller is “over-billing” the customer for unneeded products or services. Similarly, an under-supply of subscribed product may give to frustration and friction that an expected subscribed product or service is scarce or unavailable.
Online retailers and merchants may experience similar consequences due to mismatching of delivery times and consumption rates, such as at an aggregate level of subscribers. In the aggregate, the mismatches may cause either overstocking or understocking of inventory of the online retailers and merchants. Fluctuations in inventory may cause non-beneficial consumption of resources and time. Note, too, that the computing systems of online retailers and merchants are not well-adapted to address the above-described mismatching phenomena when ordering, shipping, and performing inventory management. These types of subscription models, therefore, are not generally well-suited for application to usual consumption rates of depletable products and services (e.g., product usage that depletes some or all of the product or service).
In some approaches, online retailers and merchants attempt to increase exposure and awareness of certain products by, for instance, providing samples of products to potential consumers. In one approach, a printed paper, such as a “flyer,” is typically added a box containing a purchased product being readied for shipment (e.g., from a warehouse). The flyer usually conveys information about a product in which a consumer may purchase in the future. For example, a flyer may include a website or other contact information that accompanies a variety of snacks and directs a recipient how to order a favored snack from the variety of snacks. But prior to sampling a product, the “friction” encountered by a consumer to acquire the sample described in a flyer is relatively high (e.g., a low likelihood of future acquisition of the item). Consumers have little time to follow directions to receive a sample for a product they are not aware that they would like to receive. In a modified approach, a sample of the product (e.g., either free or at a nominal price) may be included in a boxed shipment and the flyer, which explains how to purchase a product should the consumer desire.
Conventional computing platforms that implement traditional online merchant techniques, while functional, suffer drawbacks that limit opportunities to receive information regarding one or more consumers' experiences regarding a product. Known software and applications, therefore, are suboptimal in determining information of consumer experiences. As manufacturers and retailers expend millions to billions of dollars in investing in manufacturing samples for distribution, the information received back via conventional software and applications have yet to reach their potential.
Thus, what is needed is a solution to facilitate techniques of automatically predicting an amount of consumption of a sample for an item according to an adaptive schedule, without the limitations of conventional techniques.
Various embodiments or examples (“examples”) of the invention are disclosed in the following detailed description and the accompanying drawings:
Various embodiments or examples may be implemented in numerous ways, including as a system, a process, an apparatus, a user interface, or a series of program instructions on a computer readable medium such as a computer readable storage medium or a computer network where the program instructions are sent over optical, electronic, or wireless communication links. In general, operations of disclosed processes may be performed in an arbitrary order, unless otherwise provided in the claims.
A detailed description of one or more examples is provided below along with accompanying figures. The detailed description is provided in connection with such examples, but is not limited to any particular example. The scope is limited only by the claims, and numerous alternatives, modifications, and equivalents thereof. Numerous specific details are set forth in the following description in order to provide a thorough understanding. These details are provided for the purpose of example and the described techniques may be practiced according to the claims without some or all of these specific details. For clarity, technical material that is known in the technical fields related to the examples has not been described in detail to avoid unnecessarily obscuring the description.
Commerce platform controller 112 may be configured to perform functions to support the initiation of the distribution (e.g., shipment) of an item, among other things. For example, commerce platform controller 112 may be configured to facilitate financial-related transactions with one or more merchant computing systems 130a, 130b, and 130n, including, but not limited to, credit card transactions or the like. In some cases, commerce platform controller 112 may also control participation by users and their electronic interactions with adaptive distribution platform 110. For example, commerce platform controller 112 may manage enrollment of a user to form an electronic account that enables access via a computing device, such as one of mobile computing devices 152a and 152b, to adaptive distribution platform 110.
Distribution predictor 114 may be configured to predict a point in time (or a range of time) at which an item may be exhausted, and based on the prediction, adaptive distribution platform 110 may be further configured to determine a zone of time (not shown) in which depletion and near exhaustion of an item is predicted. Further, distribution predictor 114 may be configured to determine the zone of time relative to a distribution event. In some cases, a zone of time is determined as a range of time preceding the distribution event. Distribution predictor 114 may be configured to associated a point in time with the zone of time, the point in time defining a moment at which an electronic message may be transmitted to a computing device 142, 152a, or 152b to inform a user of a pending exhaustion of an item and to provide an opportunity to replenish the item in a configurable manner.
Conversation platform controller 115 may be configured to facilitate an exchange of electronic messages and data, as a “conversation,” between adaptive distribution platform 110 and any of user computing devices 142, which may include mobile computing devices 152a and 152b. According to some examples, conversation platform controller 115 may be configured to monitor whether to replenish an item, for example, by determining whether a particular date coincides with a zone of time. If the particular date coincides with a date range of the zone of time, conversation platform controller 115 may transmit data representing an electronic message 124a via one or more networks 120a and 120b to mobile computing device 152b to cause presentation of a reminder message in an interface 156b. In response, mobile computing device 152b may transmit data representing an electronic message 124b to initiate distribution (e.g., shipment) of an item.
In some examples, conversation platform controller 115 may be configured to receive an electronic message 122b originating at user computing device 152a as conversation platform controller 115 monitors whether to replenish an item. Electronic message 122b may include data representing an item characteristic (e.g., a product classification, such as “paper towels,” or a product type, such as a brand name (e.g., “Brand ‘X’”)). In this example, a user 144 may enter a product classification (“paper towels”) 158a as displayed in a user interface 156a. Also, conversation platform controller 115 may be configured to initiate transmission of a control message (e.g., via commerce platform controller 112) to one of merchant computing systems 130a, 130b, and 130n to initiate distribution of an item for replenishment, whereby a merchant computing system may initiate distribution, shipment, delivery, etc. of the item, by any known means, to a geographic location (e.g., an address) associated with an account (e.g., a user account associated with user 144). Thus, conversation platform controller 115 may be configured to control replenishment of an item regardless of whether an electronic message that initiates a conversation originates at adaptive distribution platform 110 or at user computing device 142, 152a, or 152b.
Adaptive distribution platform 110 may be configured to facilitate “adaptive” scheduling services via a computing system platform for multiple online or Internet-based retailers and service providers, both of which may be referred to as merchants. In this example, a merchant may be associated with a corresponding one of merchant computing systems 130a, 130b, or 130n that includes one or more computing devices (e.g., processors, servers, etc.), one or more memory storage devices (e.g., databases, data stores, etc.), and one or more applications (e.g., executable instructions for performing adaptive subscription services, etc.). Examples of merchant computing systems 130a, 130b, or 130n may be implemented by any other online merchant. Accordingly, adaptive distribution platform 110 can be configured to distribute items in accordance with predicted distribution events (e.g., a predicted time of distribution), any of which may be adaptively derived to optimize delivery of items.
In view of the foregoing, the structures and/or functionalities depicted in
According to various examples, a distribution event may be predicted automatically or manually to form an adaptive schedule (e.g., an adaptive shipment schedule). A “distribution event” may refer, at least in some examples, to an event at which a shipment is to occur (or is likely to occur), or at which an item (e.g., a depletable item) is predicted to be exhausted. For example, a distribution event (e.g., either depletion or shipment) may be timed to occur at the 30th day after a user has purchased a bottle of vitamin supplements having 30 tablets that are taken once a day (e.g., at a depletion rate of 1 tablet per day). In some examples, a distribution event (e.g., a time of distribution) may be predicted as a “predicted distribution event” (e.g., a “predicted time of distribution”) based on any number of sources of information and/or item characteristics, including, but not limited to, as a usage rate of item by a particular user 144 or a population of users 144 associated with one or more merchant computing systems 130a, 130b, and 130n. In some examples, a usage rate may be a function of a depletion rate. Further, a “predicted distribution event” may be optimized based on, for example, feedback or results of various data analyses. For example, a value representing a predicted distribution event or date may be optimized by including a user's monitored preference in predicting a modified distribution event. A particular user may prefer to deviate from a predicted distribution event by delaying or expediting a shipment (e.g., repeatedly pushing back or pulling forward shipment dates). Thus, a reminder message may be generated in accordance with the user's preference.
According to some examples, a term “order” may be used interchangeably with “reorder.” In some cases, an “order” may refer to a first transaction for a good or service, and a “reorder” may refer to subsequent transactions. During a first transaction, such as a text requesting an order to a merchant via adaptive distribution platform 110, a prior relationship may not exist with a merchant. If a prior relationship has yet to exist between user 144 and a merchant computing system 130a, payment information and shipping address information may not be available to a merchant with which user 144 is engaging. In some examples, adaptive distribution platform 110 may determine user 144 has a prior relationship with any other networked merchant computing systems (e.g., systems 130b and 130n). Thus, payment information and shipping address information may be used from prior orders with merchant computing systems 130b and 130n. In one case, however, if no relationship exists with either adaptive distribution platform 110 or any merchant computing systems 130a, 130b, and 130n, adaptive distribution platform 110 may generate an electronic message requesting payment information and shipping address information. The payment information and shipping address information may be transmitted via any medium (e.g., website, via phone, email, text messaging, etc.).
In some embodiments, data representing a predicted distribution event or any other data described herein may be implemented by an inventory management controller 131 to manage an amount of inventory to enhance optimally the efficacy of fulfilling and replenishing items for an aggregate number of users 144. A merchant computing system, such as merchant computing system 130a, may include an inventory management controller 131, which may be implemented as a known inventory management software application. The inventory management software application may be adapted to receive an aggregate number of predicted distribution events for group of users 144 (or an aggregated representation thereof) to refine, for example, amounts of inventory at a storage facility prior to dispatch or replenishment. Adaptive distribution platform 110 may be configured to provide a subset of predicted distribution events (e.g., predicted shipment dates) for an item for respective users. Alternatively, platform 110 may provide an optimal value for a predicted distribution event for an item to inventory management controller 131. Accordingly, inventory management controller 131 may be configured to determine an inventory amount (e.g., dynamically) based on the values representing one or more predicted distribution events. Therefore, a merchant associated with merchant computing system 130a may be configured to optimally determine an amount or quantity of items for fulfillment in an inventory based on, for example, a predicted shipment date and/or a predicted date of exhaustion.
As described, commerce platform controller 112 may facilitate financial-related transactions and enrollment of user accounts. According to some examples, commerce platform controller 112 may be configured to enroll user 144 and form a corresponding electronic account as a data arrangement, which may include data representing an indication that user 144 has interacted at least one time with at least one of merchant computing systems 130a, 130b, and 130n (i.e., a consumer has purchased previously a product from a merchant, and a data relationship between the merchant and the consumer may exist). Based on a previous purchase, commerce platform controller 112 may access data to facilitate reordering, such as data representing a geographic location (e.g., a shipping address), a payment instrument (e.g., a credit card number, a debit card number, a PayPal™ number, or any other type or form of payment, etc.) and a list of products previously ordered. A user computing device identifier, such as a user's mobile phone number, email address, etc., may also be included as data in the electronic account, which may be formed during an enrollment process or upon initiation of the distribution of an item (e.g., during reordering). An enrollment process may be implemented as an algorithm that may be executed during a check-out process so user 144 may opt to include the above-described data, including authorization to receive electronic messages (e.g., text messages), at a mobile computing device. Further, the enrollment process may be performed at a merchant or a point of sale. For example, a customer of a health food establishment may be presented with an opportunity to enroll (e.g., provide payment and shipping information). In some cases, the opportunity to avail oneself of the various features described herein may be integrated or supplemented with the merchant's loyalty or member program.
In at least one example, data relating to a user profile acquired in a previous transaction may be disposed in a merchant repository 174, which may include data generated by one or more of merchant computing systems 130a, 130b, and 130n. User profile and account data may be stored in user repository 170, which may include data relating to one or more users 144, or stored in a platform repository 172, which may include data relating to any aspect of data transactions among users 144 and merchant computing systems 130a, 130b, and 130n used to facilitate operability of adaptive distribution platform 110.
Commerce platform controller 112 may be configured to facilitate financial-related transactions and need not perform a financial transaction. For example, commerce platform controller 112 may receive a control message to initiate distribution of an item. In response, commerce platform controller 112 may transmit transaction-related data (e.g., credit card information, destination address, etc.) to one of merchant computing systems 130a, 130b, and 130n, which, in turn applies payment (e.g., receives credit card authorization) and distributes an item. Hence, commerce platform controller 112 may provide data transfer of information so that each of merchant computing systems 130a, 130b, and 130n may be a merchant of record.
Distribution predictor 114 may include a distribution calculator 116, a distribution optimizer 118, and a zone generator 119. Distribution calculator 116 may be configured to calculate one or more predicted distribution events or replenishment-related data to form an adaptive schedule (e.g., an adaptive shipping schedule). Distribution optimizer 118 may be configured to optimize values of predicted distribution events to, for example, adapt scheduling of distributed items (i.e., product shipments) to conform (or substantially conform) to delivery or usage preferences of user 144 or a group of users 144. For example, distribution optimizer 118 may be configured to analyze data representing purchasing patterns related to a particular item for a specific user 144. Based on the results of such an analysis, distribution optimizer 118 may be configured to emphasize certain item characteristics (or values thereof) that may align more closely to a user's ordering or reordering patterns. For example, replenishment of an exact brand name at a later date may be preferred by user 144 over substitution of a comparable other brand at an earlier date. Zone generator 119 may be configured to define a zone of time, which may be configurable or adjusted based on, for example, one or more of user preferences, an amount of time since a prior distribution (e.g., a prior purchase), one or more usage rates, units of depletion or depletion rate, etc. An example of a depletion rate is the rate at which 2 units of a product are depleted per unit time. To illustrate another example, consider that a bottle of vitamins has 180 tablets and is reordered or depleted every 72 days. Thus, a predicted rate of depletion may be 2.5 per day (e.g., 180 units/72 days). For example, a user may consume 2 to 3 tablets per every other day).
Distribution calculator 116 may be configured to receive data representing item characteristics data 102, according to some embodiments, and may be configured further to determine (e.g., identify, calculate, derive, etc.) one or more distribution events based on one or more item characteristics 102, or combinations thereof (e.g., based on derived item characteristics). For example, distribution calculator 116 may compute a projected date of depletion for a particular product, such as a vitamin product, based on usage patterns and/or ordering patterns of a specific user 144. Note, however, a projected date of depletion may also be based on usage patterns and/or ordering patterns of other users 144 over any number of merchant computing systems 130a, 130b, and 130n. In some examples, a projected data of depletion may be correlated to, or used interchangeably with, the terms a “predicted distribution event,” a “predicted shipment date,” a “predicted time of distribution,” or the like.
In at least one example, distribution calculator 116 may be configured to operate on data representing an item characteristic 102, which may be derived or calculated based on one or more other item characteristics 102. Examples of item characteristics data 102 may include, but are not limited to, data representing one or more characteristics describing a product, such as a product classification (e.g., generic product name, such as paper towels), a product type (e.g., a brand name, whether derived from text or a code, such as a SKU, UPC, etc.), a product cost per unit, item data representing a Universal Product Code (“UPC”), item data representing a stock keeping unit (“SKU”), etc., for the same or similar items, or complementary and different items. Item characteristics 102 may also include product descriptions associated with either a SKU or UPC. Based on a UPC for paper towels, for example, item characteristics 102 may include a UPC code number, a manufacture name, a product super-category (e.g., paper towels listed under super-category “Home & Outdoor”), product description (e.g., “paper towels,” “two-ply,” “large size,” etc.), a unit amount (e.g., 12 rolls), etc. Item characteristics 102 also may include any other product characteristic, and may also apply to a service, as well as a service type or any other service characteristic. In some examples, data representing item characteristics 102 may be accessed from and/or stored in any of repositories 170, 172, and 174.
A predicted distribution event for an item may be based on a usage rate of the item (e.g., a calculated usage rate), whereby a usage rate may be a rate at which a product or service is distributed (e.g., ordered or reordered), consumed, or depleted. In one example, predicted distribution of an item for a user 144 may be based on a predicted time of exhaustion, such as exemplified in the above example in which a distribution event for a bottle of 30 vitamin tablets is predicted to occur at the 30th day (e.g., relative to a previous delivery). In another example, predicted distribution of an item for user 144 may be based on the user's pattern of purchasing, using, ordering, or reordering the item (or generically similar or complementary items). For example, a predicted time of distribution to replenish an item, such as a bottle of ketchup, may be based on a user's past rates of replenishment (e.g., shipment rates), such as a median or average time between successive requests to distribute reordered items. A distribution event may be predicted or supplemented by predicting a time of distribution for ketchup based on rates of past replenishment of mustard, a complementary product having a usage rates that may correlate to that of ketchup as both items may be used together (and thus consumed at similar depletion rates). Other users' patterns of purchasing, using, ordering, or reordering of the same item (e.g., same brand of vitamin A at the same merchant) or equivalent item (e.g., different brands of vitamin A at the same or different merchants) may also be used to predict a time of distribution. For example, consider that user 144 is replenishing an item, such a vitamin A tablets, at a merchant X. However, there may be negligible information to predict a usage rate (or a time of distribution) for that item at merchant X. Therefore, other users' patterns of reordering vitamin A at another merchant, merchant Y, may be used to form a predicted time of distribution for use in purchasing vitamin A tablets at merchant X.
In some examples, a usage rate to determine a predicted time of distribution may be based on identifying distribution rates of an item relative to one or more other accounts associated with one or more other users or other user computing systems to form an aggregate usage rate. An aggregated usage rate for an item may express, for example, a nominal usage rate that may be used (at least initially) to ascertain predicted time of reorder with a relatively high degree of confidence. Thus, the aggregated usage rate may be used to generate a predicted time of distribution. According to one implementation, usage rates associated with other users may originate from item characteristic data accessed from one or more merchant computing systems 130a, 130b, and 130n. The usage rates received from merchants may be to determine a predicted time of distribution for an item. As an example, usage rates may be derived by analyzing shipment rates of an item to identify time periods between deliveries (i.e., time intervals between order and reorder) relative to one or more merchant computing systems 130a, 130b, and 130n. Thereafter, a usage rate may be used to calculate a predicted time of distribution.
Distribution optimizer 118 may be configured to optimize values of predicted times of distribution, for example, by adapting scheduled distribution of items to conform (or substantially conform) to, for example, usage preferences of user 144 or a group of users 144. Distribution optimizer 118 may configured to receive data representing distribution-related data from distribution calculator 116, including predicted times of distribution, usage rates, etc., as well as item characteristics data 102, to determine one or more optimized times of distribution, according to some embodiments. In at least one example, distribution optimizer 118 may be configured to determine an optimal default predicted times of distribution with which to establish a time frame to deliver an item. In some examples, distribution optimizer 118 may be configured to modify a value of predicted time of distribution relative to, for example, a prior shipment, or a receipt of a reminder message, etc. A value of predicted time distribution may be modified, for example, by an adjustment factor that may be derived through computation or determined empirically. To illustrate, consider that user 144 receives electronic messages 124a at computing system 152b over multiple periods of time, whereby user 144 responds via electronic messages 124b to request a shipment delay of seven (“7”) days rather than ordering at time of that message 158b is initially received. In this example, the adjustment factor may have a value of “7” that may modify a value of predicted time of distribution to form a modified value of predicted time of distribution (e.g., modified to 37 days after a last order of 30 vitamin tablets rather than 30 days). According to some embodiments, distribution calculator 116 and/or distribution optimizer 118 may be configured to monitor and update the one or more values of the item characteristics. As such, distribution optimizer 118 may be configured to dynamically determine a modified time of distribution with which to associate with a specific item (e.g., for specific user 144), among other parameters. Further, distribution optimizer 118 may be configured to derive an adjustment factor value in accordance with any number of processes or techniques described herein or that are otherwise known.
Zone generator 119 may be configured to determine a zone of time as a function of an item and/or a user, among other parameters, according to various examples. Zone generator 119 may form a zone of time (not shown) in which depletion or near exhaustion of an item is predicted. A zone of time may be relative to a distribution event (e.g., a time of distribution). In some cases, zone generator 119 may generate a zone of time as a range of time either preceding a distribution event, or subsequent thereto, or both. To illustrate, consider an example in which an item of paper towels may be exhausted in eight (8) days from generation of a reminder electronic message 124a. A zone of time may include a range of seven (7) days during which user 144 may select to delay delivery of the item by any day from seven days to one (1) day prior to the day of exhaustion. Optionally, a zone of time may also include another range of seven (7) days extending after the day of exhaustion. Thus, a user may delay or postpone replenishment of an item with any time during a range of 14 days. Note that the above-described values defining the example of a zone of time are not intended to be limiting, but may be of any value or number of days in accordance with various examples.
Conversation platform controller 115 may include a data interface 117, and may be configured to facilitate an exchange of electronic messages and data via data interface 117 between adaptive distribution platform 110 and mobile computing devices 152a and 152b to replenish a consumable item (e.g., a depletable product). Adaptive distribution platform 110 may be configured to replenish an item responsive to one of electronic messages 122b and 124b, according to some examples. In at least one implementation, adaptive distribution platform 110 may facilitate a complete transaction, from online ordering to shipment, of a product responsive to a unitary electronic message, such as electronic messages 122b or 124b. In at least one example, electronic messages 122b or 124b are text messages configured to include 160 characters or fewer.
Conversation platform controller 115 further may include logic, whether implemented in hardware or software, or a combination thereof, configured to control one or more exchanges of data to identify or determine one or more of a user account (and associated user or consumer), one or more item characteristics, and a destination account identifier. According to various examples, adaptive distribution platform 110 may initiate item replenishment. To illustrate, consider the following example. Conversation platform controller 115, or any other element of adaptive distribution platform 110, may include logic configured to monitor values of data representing predicted distribution events for user computing systems 142 and corresponding users 144. The logic may also monitor values of data representing a zone of time associated with a predicted distribution event. For example, conversation platform controller 115 may compare a point of time (e.g., a date and/or time, such as December 7, 20XX at 5:00 pm) against a zone of time (e.g., a date range from December 7, 20XX to December 14, 20XX) associated with a predicted time of distribution for an item, such as “paper towels.” If conversation platform controller 115 detects that a point of time, such as 5:00 pm on December 7, 20XX, coincides with a zone of time for an item “paper towels,” conversation platform controller 115 may initiate transmission of an electronic message 124a via data interface 117 to, for example, user computing device 152b. Further to the example, December 14, 20XX may coincide with a predicted date of exhaustion, whereby message 124a is transmitted at a point of time that is 7 days prior. Thus, a user has an opportunity to conveniently replenish an item prior to exhaustion.
Data interface 117 may be configured to adapt data transmission to a particular communication medium and application, as well as data protocol, to form electronic message 124a. For example, data interface 117 may adapt electronic messages to implement short message service (“SMS”), as a text messaging service for reception by a mobile computing device, including mobile phones, or any other networked computing device. An example of SMS is described in one or more standards, including RFC 5724 maintained by the Internet Engineering Task Force (“IETF”), among others. According to some embodiments, electronic messages 124a need not be initiated as a function of predicted times of distribution. In some cases, electronic messages 124a (and 122a) may be manually-generated (e.g., other than algorithmically triggered).
Electronic message 124a transmitted to computing device 152b may include data configured to present via user interface 156b the following reminder message 158b to user 144, who is associated with a pending exhaustion of paper towels: “You're likely running low on {PAPER TOWELS}. Reply ‘NOW’, if you'd like to order 1 unit of 12 rolls of {BRAND X} paper towels for $17.95 incl. tax and shipping. If you'd like to place a future order, reply with the number of days when you'd like to place your order (e.g., text ‘7’ if you'd like your order to be shipped in 7 days from today).” Data representing a destination account identifier 154b may also be transmitted in electronic message 124a, and, as such, user interface 156b need only receive at least one user input by user 144 to effect replenishment. In this example, destination account identifier (“324178”) 154b may be implemented as a “shortcode” (e.g., five- or six-digit SMS-based shortcode) associated with either adaptive distribution platform 110 or one or more of merchant computing systems 130a, 130b, and 130n. Destination account identifier 154b may also be implemented as a phone number or as any other type of identifier.
If user 144 desires to ensure a supply of paper towels is not exhausted at or around the projected date of exhaustion, interface 156b may be configured to receive an input “NOW,” which, in turn, may be transmitted as electronic message 124b to adaptive distribution platform 110. Conversation platform controller 115 generates a control message 121 to, for example, merchant computing system 130a to initiate completion of the transaction. Optionally, conversation platform controller 115 may generate a confirmation electronic message for transmission to user computing device 152b to confirm acceptance of order. Control message 121 may include financial data associated with user 144 (e.g., credit card information) to initiate authorization at merchant computing system 130a, which, in turn, ships the item and optionally sends shipping confirmation to user computing device 152b to notify user 144 of an item in transit.
If user 144 desires to modify a distribution event (e.g., a shipment), interface 156b may be configured to receive an input “#,” which may represent a value with which to delay the distribution event relative to a predicted distribution event. For example, a user input “7” may be received into user interface 156b. Computing device 152b then may transmit data indicated an amount of delay as via electronic message 124b. According to some examples, a value 159 may be presented that is adapted to particular user 144 or item. For example, if user 144 historically postpones delivery by 7 days for this or other items, a value of “7” may be presented. Alternatively, a value 159 may be based on other users' patterns of postponement. Conversation platform controller 115 generates control message 121 for transmission to, for example, merchant computing system 130a, which, in turn, initiates authorization of the transaction, but with a hold on shipment (until an amount of delay expires). For example, control message 121 may include financial data to enable authorization at merchant computing system 130a. Optionally, conversation platform controller 115 may generate a confirmation electronic message for transmission to user computing device 152b to confirm a “future” order. Subsequently, conversation platform controller 115 may detect that an amount of delay has elapsed (e.g., 7 days), and, in response, may generate control message 121 to cause merchant computing system 130a to generate an order, charge the credit card, ship the item, and optionally send shipping confirmation.
In other examples, a user computing device 152a may initiate item replenishment. For example, user interface 156a may receive a user input 158a of “paper towels,” and, optionally, a destination account identifier (“774169”) 154a, such as a shortcode (or a phone number, an email address, a URL, etc.). User computing device 152a may be configured to transmit data representing user input 158a as electronic message 122b, which may also include data representing an account identifier (e.g., a mobile phone number) associated with user 144. Conversation platform controller 115 includes logic configured to extract data representing a portion of text, “paper towels,” and analyzes the extracted data to determine that the text entered correlates to a specific item requested for replenishment. Conversation platform controller 115, for example, can compare text “paper towels” (or alternatively texted as “papr towls,” or other like short-hand or erroneous entries) to data stored in one or more repositories 170, 172, and 174 to confirm that user 144 is requesting paper towels.
Once the item is identified, conversation platform controller 115 may be configured to match “paper towels” against data representing UPC information, SKU information, and other information, as well as any other associations to user 144 based on data linked to the user's account identifier. A mobile phone number can be used to link or identify item characteristics associated with past purchases of paper towels by user 144. In situations in which user 144 has historically purchased paper towels with different item characteristics (e.g., different SKUs, UPCs, etc.), conversation platform controller 115 may select an item based on the latest purchase. According to at least one example, the above-described actions may be sufficient to complete a transaction with at least one of merchant computing systems 130a, 130b, and 130n.
Item replenishment may proceed as follows, according to some further examples. Conversation platform controller 115 may transmit a summary electronic message 122a (not shown) of the item to be replenished, such as “If you would like to order 1 unit of 12 rolls of {BRAND X} paper towels for $17.95 including tax and shipping, please reply ‘YES.’” In response, user interface 156a may receive a user input “YES,” thereby causing user computing device 152a to transmit order affirmation as electronic message 122b. Responsive to receiving “YES,” conversation platform controller 115 may generate a control message 121 for transmission to, for example, merchant computing system 130a to initiate completion of the transaction. Optionally, conversation platform controller 115 may generate a confirmation electronic message 122a for transmission to user computing device 152a. An example of such a confirmatory message is as follows: “Your order has successfully been placed. Thank you. You'll receive another text once your order has been shipped. In case of questions or problems, please call 1-800-555-1234.” Control message 121 may include financial data (e.g., credit card information) associated with user 144 to initiate authorization at merchant computing system 130a, which, in turn, ships the item and optionally sends shipping confirmation to user computing device 152a to notify user 144 of an item in transit. Merchant computing system 130a may be configured to generate an order, charge the credit card, ship the item, and optionally send shipping confirmation.
User-initiate replenishment may be implemented as follows, at least in some examples. Destination account identifier (“774169”) 154a may be displayed in advertising media (e.g., including printed ads, such as in newspapers and magazines, billboards, and the like), product packing, etc. so a user can review a package of, for example, Brand V protein powder to identify shortcode “774169” (or phone number) and the text to be entered (entry “V powder”) to initiate a replenishment of Brand V protein powder (based on linking data related to the mobile phone number of user 144, such as shipping address, billing information, etc.). Alternatively, destination account identifier 154a may encode the product to replenish. For example, a package or other media (e.g., printed or online advertisements) may include the following: “Reorder Brand V protein powder by texting ‘NOW’ to 7741,” whereby shortcode 7741 may be reserved to order Brand V protein powder at a merchant computing system 130. Other examples include According to various other examples, short codes, phone numbers (to text replenishment requests), etc. may encode any type of information to, for example, uniquely identify one or more of the following: a specific product, a specific merchant, and a specifically-configured shipment date and time, among other things.
Specific interfaces 217a to 217n may be implemented in hardware or software, or a combination thereof. In some cases, one of specific interfaces 217a to 217n may be implemented as an applications programming interface (“API”). For example, interface 217a may be configured to exchange data via HTML, HTTPS, or any other communication service/protocol between conversation platform controller 215 and web page 210. As another example, interface 217b may be configured to exchange data via POP, SMTP, IMAP, or any other communication service/protocol between conversation platform controller 215 and electronic mail message 220. Interface 217n may be configured to exchange data via SMS, EMS, MMS (“Multimedia Messaging Service”) services, or any other communication service/protocol between conversation platform controller 215 and text message application in computing device 242b or a proprietary fulfillment application 241 disposed, for example, in computing device 242a. Thus, conversation platform controller 215 may be agnostic regarding the various forms of communication channels or media for which data interface 217 provides specialized interfacing.
Various structures and/or methods described herein may be applied to web pages 210, emails 220, multi-media text messages 248a and 248b, among other forms of communicating request to replenish an item. Web page 210 includes an order or reorder page as a user interface 212 to order or reorder an item (e.g., paper towels) by selecting in interface portion 214 either immediate delivery via input 211 or delayed delivery via input 213 and input 219 (a pull-down menu to select an amount of delay). Data received into interface 212 via inputs 211, 213, and 219 may be stored until input (“send”) 218 is activated, after which the data may be transmitted contemporaneously (or substantially contemporaneously) to conversation platform controller 215 to initiate an order.
An electronic message to remind a user of imminent exhaustion of an item may be communicated as an email 220, which is shown to include an item characteristic 222 in a subject line so a user readily may discern the action required for such a communication. In email body 224, various delivery options may be embedded as hypertext links to enable a user to order or reorder an “Product P” “now,” by selecting link 275a, or postponing shipment by 7 days with the selection of link 275b. According to some embodiments, the presentation of a link for a “7 day” delay, as a first link, may be due to its relatively high degree of compatibility with user 144 (based on probabilistic determinations at a distribution predictor, which is not shown). The presentation of a link 275c for a “3 day” delay, as a yet another link, may be due to its second-highest degree of compatibility. Thus, an adaptive distribution platform including conversation platform controller 215 may adapt presentation of user inputs to accommodate user purchasing and scheduling patterns and preferences to enhance, among other things, users' experiences.
User computing device 242a may include any messaging application 243 configured to transmit electronic messages based on, for example, SMS, MMS, or any other type of messaging service application. For example, FACEBOOK™ Messenger, TWITTER™, TWILIO™, WHATSAPP™, or any other like application may be suitable for implementation as messaging application 243, or in support of fulfillment application 241. In some examples, user computing device 242a may include executable instructions constituting a fulfillment application 241, which may be integrated with, or disposed on (e.g., built on), a messaging application layer (including messaging application 243) to provide enhanced functionality.
Further to user computing device 242a, consider that a user may initiate distribution of an item by capturing an image 248a of product label or code (e.g., UPC), such as by using a camera of user computing device 242a, to import into interface 246a. User computer device 242a may transmit image 248a as an electronic message to an adaptive distribution platform using shortcode (“774169”) 244a, whereby the adaptive distribution platform may implement image processing, such as optical character recognition or other similar processes to identify an item to replenish based on an image. In some cases, transmitting image 248a from a known mobile phone number may be sufficient to complete the transaction to ensure that a supply of an item is replenished.
An adaptive distribution platform may initiate distribution of an item by transmitting message 248b for presentation in user interface 246b of user computing device 242b. As shown, multiple user inputs 249a and 249b are presented to receive different user inputs to activate a transaction. Selection of link 249a generates an electronic message requesting an immediate order for transmission to a destination account identifier 244b, whereas selection of link 249b generates an electronic message that requests an order at a delayed time, as defined by the link (e.g., 7 days). According to various embodiments, certain amounts of delay may be presented in descending order from highest probability or likelihood (e.g., 7 days) to a lowest probability (e.g., 5 days), whereby the probabilities may be determined based on a user's preferences and purchasing patterns. Thus, a user likely can find its top three most probable preferences for the amounts of postponement (e.g., 7, 4, and 5 days) with less expended time than otherwise might be the case.
Transaction controller 280 may include logic configured to control the exchange of data to identify items for replenishment and other actions associated with an order. In text-based requests, transaction controller 280 may operate to parse text submitted as an order to determine a requested product. According to some examples, transaction controller 280 may operate in accordance with a predictive model (e.g., decision tree) that operates on XML formatted messages to generate control messages to replenish an item. Transaction controller 280 may implement deep learning, machine learning, neural networks, fuzzy logic, regression techniques, or other computer-based artificial intelligence techniques to identify a user's request from various types of electronic messages. Note that the above-described implementation for
In the example shown, distribution calculator 316 is shown configured to generate predicted times of distribution subsequent to, for example, an initial order and distribution (i.e., shipment) at time (“D1”) 363a. Examples of predicted times of distribution, as shown shipment rate implementation 360, may include a predicted time (“D2”) 363b of distribution, a predicted time (“D3”) 363c of distribution, predicted time (“D4”) 363d of distribution. Predicted times 363b, 363c, and 363d of distribution are predicted distribution events that may be a function of a user 331 (e.g., a user's usage rates and consumption patterns) or an item 333 and its characteristics (e.g., based on usage rates and consumption patterns of a group of users over one or more merchant computer systems). Note that predicted times 363b, 363c, and 363d of distribution need not be predicted as if under a subscription. That is, the depiction of predicted times 363b, 363c, and 363d of distribution is for purposes of discussion, and a predicted time of distribution need not be predicted beyond a next shipment that replenishes an item nearing exhaustion.
Predicted times 363b, 363c, and 363d of distribution may be correlated to a period of time, such as periods of time p1 and p2, based a rate of depletion of an item. For example, a period of time, p, may define an amount of time (e.g., a time interval) between an initial supply level (e.g., a full supply on date of initial purchase, such as time (“D1”) 363a) and a predicted date of exhaustion, such as time (“D2”) 363b, which may coincide with a predicted time of distribution (e.g., time of delivery). To illustrate, a distribution event at time (“D2”) 363b may be timed to occur at the 30th day after a user has purchased at time (“D1”) 363a a bottle of vitamin supplements having 30 tablets that are taken once a day. Thus, distribution predictor 314 may generate data 322 representing periods 323 of time, such as periods of time (“p1”) 362a and 362b, both of which are depicted as 1.5 units of time, and period of time (“p2”) 362c is depicted as 1 unit of time. In some examples, distribution optimizer 318 may receive feedback relating to ordering patterns of user 331 (e.g., user 331 typically requests shipments prior to a date of exhaustion). Based on the feedback, distribution optimizer 318 may be configured to adjust a predicted distribution event at time 363d and a period 362c of time, which is shorter than periods 362a and 362b of time.
Zone generator 319 may be configured to determine a zone of time in which depletion of an item is predicted. A zone of time, and its duration, may be adapted relative to a distribution event or a period of time since, for example, a known supply level of an item (e.g., a full supply at a previous purchase). As shown, zone generator 319 may be configured to determine a zone 368a of time associated with time 363b, a zone 368b of time associated with time 363c, and a zone 368c of time associated with time 363d, each of which may be a range of time preceding a distribution event. In some cases, zone generator 319 may be configured to determine a zone 368d of time that succeeds a distribution event at time 363d. Zone 368c of time may be different (e.g., shorter) than zones 368a and 368b of time based on respective periods of time, according to some examples.
Distribution predictor 314 also may be configured to associate a point in time with a zone of time, the point in time defining a moment at which an electronic message may be transmitted to a computing device (e.g., a mobile phone) to inform a user of the pending exhaustion of an item and to provide an opportunity to replenish the item in a configurable manner. As shown, distribution predictor 314 may associate a point 370a to zone 368a of time, a point 370b of time to a zone 368b of time, and a point 370c to zone 368c of time, whereby an adaptive distribution platform (not shown) may generate electronic reminder messages at points 370a, 370b, and 370c of time. Thus, an electronic reminder message transmitted at, for example, point 370a of time is associated with a zone 368a of time. Consider an example in which an electronic message is sent at point 370a of time, which may be eight (8) days prior to time 363b. Thus, zone 368a of time may be subdivided into, or otherwise include, various times at which to delay initiation of an order. For example, an electronic reminder message may be sent to a user eight (8) days prior to time 363b, whereby the electronic reminder message may provide user inputs to delay distribution by “7,” “6,” “4,” “2,” days, or any other amount of delay, within zone 368a of time.
According to some embodiments, distribution predictor 314 may be configured to receive and/or determine data for one or more item characteristics that may include, but are not limited to, data representing one or more characteristics of an item, shipment rate-related data 302, indicator-related data 304, and usage-related data 308, and the like. Note that data 302, 304, and 308 may be referred to as examples of item characteristics, according to various examples. Examples of some item characteristics may include a product or product type, a service or service type, SKU data, UPC data, etc. for the same or similar items, or complementary and different items (e.g., complementary or correlatable products may be predicted to have similar predicted times of distribution or rates of consumption and/or depletion). Examples of shipment rate-related data 302 may include a number of purchases or orders per user, per group of users, or per item, a number of shipments, etc. Examples of indicator-related data 304 may include data representing items characteristics that may be correlatable to, for example, order and shipment rate-related data (e.g., a “take rate,” a “cancellation rate,” etc., or any other data type, such as an “adoption rate” of platform-initiated or user-initiated reordering, a “conversion rate” of responding to reminder messages as a function of user and item, etc.), which, in turn, may be used to derive a predicted time of distribution. The term “take rate” may include data representing a rate at which users “take” or implement a presented value of delay (e.g., delay by “7” days) as a default amount of delay, according to some examples. The term “cancellation rate” may include data representing a rate at which users “cancel” an order (e.g., based on, for example, frustrations of over-supplied or under-supplied amounts), according to some examples.
Examples of usage-related data 308 may include data representing attributes specifying contextual-related information associated with an item, such as, but not limited to, user-related characteristics, such as demographic information, purchasing-related data (e.g., purchase patterns), and the like. In some cases, usage-related data may include attributes 340 describing items historically purchased by a user 341 (e.g., patterns of a parent), as well as attributes 344 describing items historically purchased by associated users 345 (e.g., patterns of a grandparent) or a subpopulation or a population of which a user belongs. Also, usage-related data may include sale-related and shipment-related attributes 348 provided by merchant computer systems 349. Data representing attributes 340, 344, and 348 may be stored in repositories 342, 346, and 350, according to some examples.
At 508, a determination is made whether replenishment may be adjusted. If no adjustment is detected, flow 500 continues to 512, otherwise flow 500 continues to 510. For example, if no delay in replenishment is detected at 508, then flow 500 continues to 512, at which a control signal may be transmitted (e.g., to a merchant computing system) to initiate scheduled delivery of an item, which may be any good or service. For example, a confirmation electronic message may be optionally generated at 512 for transmission to a user computing device to confirm acceptance of order. The control message may include financial data (e.g., credit card information) to initiate authorization of payment at a merchant computing system. If delay in replenishment is detected at 508, then flow 500 continues to 510, at which transmission of the control signal may be recalibrated. For example, a control signal may be generated for transmission to a merchant computing system to initiate authorization of the transaction with a hold on shipment. Thus, the recalibrated control signal may provide financial data for authorization of payment, but may postpone or withhold authorization to complete the transaction, including shipment. After an amount of delay has elapsed (e.g., 7 days), as determined at 510, another control message may be released for transmission to cause the merchant computing system to generate an order, charge the credit card, ship the item, and optionally send shipping confirmation.
At 514, a predicted distribution event may be adjusted, which, in turn, may modify a zone of time. For example, a predicted distribution event may be optimized based on feedback or analysis of data trends associated with users and merchants. A value representing a predicted distribution event or date may be optimized by including a user's monitored shipment delay preference, whereby the optimized predicted time of distribution may be a modified distribution event. For example, a particular user may prefer to deviate from a predicted distribution event by delaying or expediting shipping (e.g., repeatedly). Thus, a reminder message may be generated in accordance with the user's preference, which may be embodied in presented amounts of delay or in a modified date of predicted exhaustion.
According to various examples described herein, the structures and/or processes set forth to replenish items may apply to one or more items (e.g., a single item, or multiple items). In some examples, a point of time at 502 may be determined that substantially coincides with a zone of time for multiple items, such as a vitamin regimen in which a user consumes different vitamin supplement tablets (e.g., vitamins A, B, D, E, etc.) at a daily rate. In some examples, a user may set up via a user computing device a list of vitamins to be shipped at a recurring date, or predicted dates based on predicted dates of depletion or exhaustion (e.g., a time of distribution). The list may be entered via mobile phone, email, phone, webpage, etc., whereby and adaptive distribution platform may manage the tracking and delivering of multiple bottles of vitamins either in accordance with a list, or by calculating predicted times of distribution or delivery (e.g., based on computed or projected usage rates for each of the vitamins). For example, bottles of 30 vitamin tablets may be included in a list every month, whereas bottles of 60 vitamin tablets may be included in the list every other month.
At 504, an electronic message, such as a text message, and may be transmitted from adaptive distribution platform to a user computing device, whereby the electronic message may include a list of items associated with a predicted optimal point in time at which one or more items in the list are depleted or substantially depleted. For example, the electronic message may indicate: “The following is a list of items that you may wish to replenish. Reply ‘Yes’ if you wish to replenish each item in the list, or reply with a corresponding number for those items you wish to replenish. For vitamin A enter ‘1,’ for vitamin B enter ‘2,’ for vitamin C enter ‘3,’ for vitamin E enter ‘4,’ and cod liver oil tablets enter ‘5’ (separated by space or comma).” A user desiring to replenish vitamins C and E then would enter and text “3 4” in reply at 506. At 508, one or more items (e.g., bottles of vitamins) may be delayed by any amount of time. For example, a user may enter “1p7d,” “2p1m,” and “5p1y,” where “p” indicates an instruction to “postpone” delivery by an amount of time expressed by “d” (day), “m” (month), or “y” (year). In this example, the user is requesting to postpone delivery of vitamin A by 7 days (“1p7d, where 1=vitamin A, p=postpone, 7=number of time units to delay, and d=time units), postpone delivery of vitamin B for one month, and postpone delivery of cod liver oil tablets by one year. The delivery of vitamins A and B, as well as cod liver oil, may be recalibrated at 510 to comply with the user's requested delivery postponements. At 512, a control signal to ship vitamins C and E may be transmitted to, for example, a merchant computing system.
To illustrate, consider that item characteristic correlator 717 is configured to identify usage rates 752a to 752c (e.g., a rate at which a product or service is reordered, or consumed or depleted) for corresponding user accounts 742a to 742c (e.g., associated with user phone numbers). In this example, consider that users 742a to 742c purchase a “laundry detergent” having usage rates 752a to 752c. Usage rates between “0” and “1” (e.g., usage amounts during a spring season), usage rates between “1” and “2” (e.g., usage amounts during a summer season), and usage rates between “2” and “3” (e.g., usage amounts during a fall season). It may be that users 742a to 742c play football during the fall, and consequently use more laundry detergent due to football practices and games in inclement weather (e.g., due to muddy fields, etc.) Thus, distribution predictor 714 may be able to discern patterns 750 of usage. Further, distribution predictor 714 may aggregate the usage rates to form an aggregated usage rate pattern 730 for a group of users 740. Based on aggregated usage rate pattern 730, distribution predictor 714 may be able to generate or predict an aggregated distribution event or an aggregated time of distribution 790.
Distribution predictor 714 may also use other types of data with which to evaluate when calculating a predicted time of distribution. Examples of such data are shown in diagram 700 and may include activity characteristics data 781 (e.g., characteristics indicative of participation in a sport or task), geographic characteristic data 782, demographic characteristic data 783 (e.g., aggregated user data), user-specific characteristic data 784 (e.g., history of purchases by a user, etc.), product characteristics data 785, complementary product characteristics data 786, and other item characteristics data 787.
Based on the above, distribution predictor 714 may be configured to identify a usage rate 720 of a new user 799, and further configured to match the new usage rate 720 against aggregated usage rate 729 of aggregated usage rate pattern 730 to predict, for example, that user 799 “plays football,” as well as other characteristics of the user with which to derive an optimized predicted time of distribution. According to some examples, distribution predictor 714 may predict future participation in an activity or an increase in usage rate during interval 728. Thus, distribution predictor 714 may adapt a predicted time of distribution so as to prepare a user for increased usage rates by adjusting the periods of time prior to a modified time of distribution to reflect an increased laundry detergent amount or a decreased amount of time between shipments. Note that the example described in diagram 700 is not intended to be limiting to laundry detergent, but may be applicable to any characteristic of an item or other items.
In some cases, computing platform 800 or any portion (e.g., any structural or functional portion) can be disposed in any device, such as a computing device 890a, mobile computing device 890b, and/or a processing circuit in association with implementing any of the various examples described herein.
Computing platform 800 includes a bus 802 or other communication mechanism for communicating information, which interconnects subsystems and devices, such as processor 804, system memory 806 (e.g., RAM, etc.), storage device 808 (e.g., ROM, etc.), an in-memory cache (which may be implemented in RAM 806 or other portions of computing platform 800), a communication interface 813 (e.g., an Ethernet or wireless controller, a Bluetooth controller, NFC logic, etc.) to facilitate communications via a port on communication link 821 to communicate, for example, with a computing device, including mobile computing and/or communication devices with processors, including database devices (e.g., storage devices configured to store any types of data, etc.). Processor 804 can be implemented as one or more graphics processing units (“GPUs”), as one or more central processing units (“CPUs”), such as those manufactured by Intel® Corporation, or as one or more virtual processors, as well as any combination of CPUs and virtual processors. Computing platform 800 exchanges data representing inputs and outputs via input-and-output devices 801, including, but not limited to, keyboards, mice, audio inputs (e.g., speech-to-text driven devices), user interfaces, displays, monitors, cursors, touch-sensitive displays, LCD or LED displays, and other I/O-related devices.
Note that in some examples, input-and-output devices 801 may be implemented as, or otherwise substituted with, a user interface in a computing device associated with a subscriber or user account identifier in accordance with the various examples described herein.
According to some examples, computing platform 800 performs specific operations by processor 804 executing one or more sequences of one or more instructions stored in system memory 806, and computing platform 800 can be implemented in a client-server arrangement, peer-to-peer arrangement, or as any mobile computing device, including smart phones and the like. Such instructions or data may be read into system memory 806 from another computer readable medium, such as storage device 808. In some examples, hard-wired circuitry may be used in place of or in combination with software instructions for implementation. Instructions may be embedded in software or firmware. The term “computer readable medium” refers to any tangible medium that participates in providing instructions to processor 804 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks and the like. Volatile media includes dynamic memory, such as system memory 806.
Known forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can access data. Instructions may further be transmitted or received using a transmission medium. The term “transmission medium” may include any tangible or intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 802 for transmitting a computer data signal.
In some examples, execution of the sequences of instructions may be performed by computing platform 800. According to some examples, computing platform 800 can be coupled by communication link 821 (e.g., a wired network, such as LAN, PSTN, or any wireless network, including WiFi of various standards and protocols, Bluetooth®, NFC, Zig-Bee, etc.) to any other processor to perform the sequence of instructions in coordination with (or asynchronous to) one another. Computing platform 800 may transmit and receive messages, data, and instructions, including program code (e.g., application code) through communication link 821 and communication interface 813. Received program code may be executed by processor 804 as it is received, and/or stored in memory 806 or other non-volatile storage for later execution.
In the example shown, system memory 806 can include various modules that include executable instructions to implement functionalities described herein. System memory 806 may include an operating system (“O/S”) 832, as well as an application 836 and/or logic module(s) 859. One or more logic modules 859 may each be configured to perform at least one function as described herein.
The structures and/or functions of any of the above-described features can be implemented in software, hardware, firmware, circuitry, or a combination thereof. Note that the structures and constituent elements above, as well as their functionality, may be aggregated with one or more other structures or elements. Alternatively, the elements and their functionality may be subdivided into constituent sub-elements, if any. As software, the above-described techniques may be implemented using various types of programming or formatting languages, frameworks, syntax, applications, protocols, objects, or techniques. As hardware and/or firmware, the above-described techniques may be implemented using various types of programming or integrated circuit design languages, including hardware description languages, such as any register transfer language (“RTL”) configured to design field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”), or any other type of integrated circuit. According to some embodiments, the term “module” can refer, for example, to an algorithm or a portion thereof, and/or logic implemented in either hardware circuitry or software, or a combination thereof. These can be varied and are not limited to the examples or descriptions provided.
In some embodiments, modules 859 of
In some cases, a mobile device, or any networked computing device (not shown) in communication with one or more modules 859 or one or more of its/their components (or any process or device described herein), can provide at least some of the structures and/or functions of any of the features described herein. As depicted in the above-described figures, the structures and/or functions of any of the above-described features can be implemented in software, hardware, firmware, circuitry, or any combination thereof. Note that the structures and constituent elements above, as well as their functionality, may be aggregated or combined with one or more other structures or elements. Alternatively, the elements and their functionality may be subdivided into constituent sub-elements, if any. As software, at least some of the above-described techniques may be implemented using various types of programming or formatting languages, frameworks, syntax, applications, protocols, objects, or techniques. For example, at least one of the elements depicted in any of the figures can represent one or more algorithms. Or, at least one of the elements can represent a portion of logic including a portion of hardware configured to provide constituent structures and/or functionalities.
For example, modules 859 of
As hardware and/or firmware, the above-described structures and techniques can be implemented using various types of programming or integrated circuit design languages, including hardware description languages, such as any register transfer language (“RTL”) configured to design field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”), multi-chip modules, or any other type of integrated circuit.
For example, modules 859 of
According to some embodiments, the term “circuit” can refer, for example, to any system including a number of components through which current flows to perform one or more functions, the components including discrete and complex components. Examples of discrete components include transistors, resistors, capacitors, inductors, diodes, and the like, and examples of complex components include memory, processors, analog circuits, digital circuits, and the like, including field-programmable gate arrays (“FPGAs”), application-specific integrated circuits (“ASICs”). Therefore, a circuit can include a system of electronic components and logic components (e.g., logic configured to execute instructions, such that a group of executable instructions of an algorithm, for example, and, thus, is a component of a circuit). According to some embodiments, the term “module” can refer, for example, to an algorithm or a portion thereof, and/or logic implemented in either hardware circuitry or software, or a combination thereof (i.e., a module can be implemented as a circuit). In some embodiments, algorithms and/or the memory in which the algorithms are stored are “components” of a circuit. Thus, the term “circuit” can also refer, for example, to a system of components, including algorithms. These can be varied and are not limited to the examples or descriptions provided.
Adaptive distribution platform 910, as described herein, may be configured to facilitate “adaptive” scheduling services, as described herein, via a computing system platform for multiple online or Internet-based retailers and service providers, both of which may be referred to as merchants. In this example, a merchant may be associated with a corresponding one of merchant computing systems 930a, 930b, or 930n that includes one or more computing devices (e.g., processors, servers, etc.), one or more memory storage devices (e.g., databases, data stores, etc.), and one or more applications (e.g., executable instructions for performing adaptive subscription services, etc.). Examples of merchant computing systems 930a, 930b, or 930n may be implemented by any other online merchant.
Distribution predictor 914 is further shown to include an information feedback predictor 914a, which may be configured to predict a date of consumption with which to solicit feedback regarding a replica of an item, the replica being a portion or “sample” of an item. A replica, therefore, may be one or more units of an item configured to provide a recipient an opportunity to experience the item, whereby a recipient may learn information regarding the item (e.g., learning information regarding the benefits of using the item, such as the health-related benefits of “Omega-3” fatty acid-based health supplements). Units of an item may describe a serving size, such as a number of Omega-3 tablets, a volumetric amount (e.g., a number of milliliters or ounces of shampoo), and the like.
According to various examples, information feedback predictor 914a may be configured identify one or more samples of items to transmit to a location associated with an electronic account for consumer 944. Further, information feedback predictor 914a may be configured to automatically generate a communication channel 926 to facilitate communication via one or more electronic messages 924a and 924b to identify whether a sample, for example, is consumed and the results therefrom. In at least one example, electronic message may be formatted and transmitted as a short message service (“SMS”) message or equivalents thereof. In at least some embodiments, information feedback predictor 914a may be configured to generate data automatically at a determined point in time (or time interval) that may be optimized to solicit feedback by transmitting an electronic message requesting feedback of a consumed sample. For example, data representing a request for feedback may be transmitted as electronic message 924a at a point in time at which a particular consumer 944 may likely have predictively consumed at least one unit of consumption to render a position for generating feedback information and data.
Diagram 900 depicts information feedback predictor 914a as including a consumption calculator 916a, a feedback optimizer 918a, and a feedback zone generator 919a, each of which may include logic, whether implemented in hardware or software, or a combination thereof, similar or equivalent to that in distribution calculator 916, distribution optimizer 918, and zone generator 919, respectively. Logic in one or more of distribution calculator 916, distribution optimizer 918, and zone generator 919 may be modified or supplemented to facilitate the functionality of consumption calculator 916a, feedback optimizer 918a, and feedback zone generator 919a, according to at least some examples. In one example, consumption calculator 916a may be configured to calculate a time (e.g., a time interval) at which one or more units of consumption of a sample may be consumed. Responsive to the calculated time, information feedback predictor 914a may generate an electronic message requesting feedback at this point.
In another example, feedback optimizer 918a may be configured to optimize a determination of a time at which one or more units of consumption of a sample may be consumed. Hence, feedback optimizer 918a may optimize a calculated time of consumption as determined by consumption calculator 916a. In particular, feedback optimizer 918a may be configured to adapt a computed time interval in which consumption is likely to predict a date of consumption by user 944 based on, for example, user characteristics, such as, but not limited to, a consumer's usage rate (or “consumption rate”) of an item, demographic characteristics of consumer 944, data representing patterns of historic purchasing and/or consumption behaviors, and the like. For example, consumer 944 may historically consume vitamins or supplements at a rate less than recommended (e.g., a user may consume 1 tablet a day rather than the recommended 2 tablets a day), and, thus, consumer 944 may consume an item at a different rate. Hence, feedback optimizer 918a may be configured to adapt optimally data representing consumption rates (and dates) to conform to consumption (e.g., usage) patterns of a particular user 944. Responsive to data representing characteristics of a user and/or item, information feedback predictor 914a may generate an electronic message requesting feedback at this point.
In yet another example, feedback zone generator 919a may be configured to adjust an adapted consumption date or range of dates, responsive to data generated at a user computing device, such as computing device 952b. For example, a user computing system 942 and/or associated electronic account for consumer 944 may include data indicating whether a unit of consumption may have been consumed or may be pending (e.g., a user 944 may yet to sample a portion of an item during an interval of time). Thus, an input may be received as data signals representing user input into interface 956b to initiate, for example, an adjusted interval of time in which to solicit feedback. Consider that user 944 may have returned from a two (2) week vacation and received a package containing a sample. The two week delay may be accommodated or addressed by enabling mobile computing device 952b (and/or adaptive distribution platform 910) and associated software applications to adjust the period in which to provide feedback.
To illustrate operation of information feedback predictor 914a, consider an example in which at least one sample 927a is included in a shipment of a purchased item transmitted via, for example, U.S. Postal Service or any other carrier. Information feedback predictor 914a may be configured to predict a date of consumption of at least a part of a replica or sample 927a. Note that sample 927a can be shipped or obtained independently from a purchased item. According to various examples, a predicted date of consumption may be based on one or more user characteristics and/or one or more item characteristics, for example. Examples of user characteristics include data representing attributes specifying contextual-related information associated with user 944, such as, but not limited to, user-related characteristics, such as demographic information, purchasing-related data (e.g., purchase patterns), and the like. In some cases, usage-related data may include attributes describing items historically purchased by a user, as well as an electronic account identifier, a payment instrument identifier (e.g., a credit card number), a location (e.g., an address), and other user-related information. User characteristics may also be mapped or otherwise associated with one or more item characteristics. For example, a usage rate of an item may be associated with a particular user (e.g., consumer 944 consumes or uses a product, such as shampoo, at a particular rate of consumption or depletion). Also, user characteristics may also include aggregated user characteristics that represent user-related information of a subpopulation from which predictions regarding, for example, selection of sample 927a or a consumption date may be determined. Examples of item characteristics include, but are not limited to, one or more other item characteristics 102 of
Referring back to
Information feedback predictor 914a may be configured to generate a subset of data 924a representing an electronic message (or a portion thereof) that may be transmitted to mobile computing device 952b to cause or otherwise initiate, for example, execution of instructions to generate feedback regarding sample 927a. As shown, subset of data 924a may cause user interface 956b to generate a message 958b with user inputs 959 and 961, among others, to determine a status of sample 927a (e.g., whether a sample has been received and consumed, which may be a basis from which to render feedback). In the example shown, user interface 956b displays the following: “How do you like SAMPLES x, y, z, . . . ? Reply X to order product for $X.XX, or Reply Y to order product Y for $Y.YY, or Reply ALL to order all.” Also, user interface 956b may also display the following: “If additional time is needed to provide feedback, please respond with “#” (i.e., a number) of days at which to check back.” Subset of data 924a may also include data representing a destination account identifier (“324178”) 954b, to which a feedback response may be transmitted as electronic message 924b. According to some examples, user 944 may initiate generation of electronic message 924b, which includes feedback, via destination account identifier (“324178”) 954b (or by any mode of communication) to indicate a sample has been consumed and feedback (e.g., including a purchase) may be available.
According to some examples, consumer 944 may cause generation of an input signal via user input 959 to order item “X” (e.g., based on sample 927a), order item “Y” (e.g., based on sample 927b), order other items (not shown), or order “All.” Adaptive distributive platform 910 and/or merchant computing systems 930a, 930b, and 930n may assign product identifiers (e.g., SKUs) to a sample for treatment by platform 910 as any item, according to a specific implementation. Data representing user input 959 may be transmitted via electronic message 924b. Thus, a response may be interpreted positively, according to at least some embodiments, when a response confirms an interest in acquiring or purchasing an item (e.g., in accordance with a subscription or other distribution and online sales arrangements as described herein). According to some examples, a lack of response to electronic message 924a may be viewed as negative or a lack of interest related to samples 927a and 927b.
In at least one example, user 944 may have yet to consume either sample 927a or 927b, and may further request additional time (e.g., additional number of days) via user input 961 to provide feedback. Data representing a delayed request may be transmitted as electronic message 924b. Accordingly, information feedback predictor 914a may include logic configured to predict an adapted time or timing to provide feedback to enable consumer 944 to sufficiently enjoy or experience a sample 927a or 927b to provide meaningful feedback. Thus, an input 961 (“#”) may be received as data signals representing user input into interface 956b to initiate, for example, an adjusted interval of time in which to solicit feedback in situations, for example, when user 944 has yet to open a package containing a sample. The delay may be addressed by enabling mobile computing device 952b (and/or adaptive distribution platform 910) and associated software applications to adjust the period in which to provide feedback. User 944 may select a particular units of time (e.g., days) with which to postpone providing feedback so as to consume a sample, such as sample 927a.
According to some examples, information feedback predictor 914a may be configured to analyze user characteristics associated with, for example, user 944 to match or align types and attributes of samples that user 944 may be likely to consume and provide feedback. For example, consider that information feedback predictor 914a may identify user characteristics that indicate user 944 likely is (1) a young parent (e.g., based on historic purchases of baby formula, diapers, baby powder, etc.), is (2) likely a pet owner (e.g., based on past purchases of dog food, puppy treats, rawhide bones, etc.), and (3) may be a vegetarian (e.g., based on previously-stored grocery purchases that exclude meat, meat-related items, or the like). Based on such exemplary user characteristics, information feedback predictor 914a may be configured to select a replica of an item as a sample. For example, information feedback predictor 914a may select a sample 927a as a sample of “diaper cream,” a sample of a “bacon-flavored dog treat,” or a sample of spices, herbs, or vegetables, any of which may be selected to enhance accuracies in predicting an invoked response (e.g., feedback) via electronic message 924b. By contrast, and further to the above example, information feedback predictor 914a may be configured to deemphasize “cat-related” items, “geriatric-related” items, or “meat-related” items as sample 927a for user 944.
In at least some examples, information feedback predictor 914a may be configured to determine one or more other samples 927b based on, for example, sample 927a. For instance, consider sample 927a may be any of the followings items: “catsup,” “shampoo,” or a “first product” of Brand “X.” Information feedback predictor 914a may be configured to determine sample 927b as a complementary item that, for example, may have a relatively high correlation of synchronous usage and consumption, and, thereby, a likelihood of sampling by user 944. Thus, sample 927b may be one of “mustard” and “conditioner,” which are respective compliments of “catsup” and shampoo.” A “second product” of Brand “X” may be selected as sample 927b based on, for example, determining a likelihood or degree of similarity between items or predicting brand loyalty based on past purchases of Brand X products, whereby user 944 may be likely to sample the first product of Brand X and provide feedback.
In at least one example, information feedback predictor 914a may be configured to analyze data representing user-related characteristics associated with the electronic account (e.g., for user 944) against other user-related characteristics associated with other electronic accounts (e.g., for users other than user 944). In this example, information feedback predictor 914a may be configured to identify attributes of users and items common with user 944 to identify a universe of items having a relatively high likelihood of being consumed or purchased by a group of users including user 944. For example, a group of users residing in a northwest portion of the United States (e.g., the state of Maine, which experiences cold, wintery seasons) may have previously purchased “snow boots” having sizes associated with “elementary-aged” children. Thus, a common other item, such as “mittens,” may be identified as being previously purchased by the other users for weather activities except user 944 (at least in this example). Therefore, information feedback predictor 914a may be configured to determine “mittens” as sample 927b (e.g., either at a discounted cost or without charge). “Mittens” may be viewed as a target item for sampling by user 944 based on data associated with the other electronic accounts.
Information feedback predictor 914a may be configured to implement any analytical determination to correlate and classify users and/or items for predicting samples, according to various examples. According to some embodiments, information feedback predictor 914a may be configured to classify and/or quantify various user and item attributes by, for example, applying machine learning or deep learning techniques, or the like. In one example, information feedback predictor 914a may be configured to segregate, separate, or distinguish a number of data points representing similar (or statistically similar) attributes, thereby forming one or more clusters or groups of data (not shown). The clustered data may be grouped or clustered about a particular attribute of the data, such as a source of data (e.g., a channel of data), a type of language, a degree of similarity with synonyms or other words, etc., or any other attribute, characteristic, parameter or the like. While any number of techniques may be implemented, information feedback predictor 914a may apply “k-means clustering,” or any other known clustering data identification techniques. In some examples, information feedback predictor 914a may be configured to detect patterns or classifications among datasets and other data through the use of Bayesian networks, clustering analysis, as well as other known machine learning techniques or deep-learning techniques (e.g., including any known artificial intelligence techniques, or any of k-NN algorithms, regression, Bayesian inferences and the like, including classification algorithms, such as Naïve Bayes classifiers, or any other statistical or empirical technique).
In view of the foregoing, the structures and/or functionalities depicted in
By enhancing accuracy of relevant information pertaining to a sample, information feedback predictor 914a may generate additional analytic information and insights into whether a particular sample is, for example, enhancing a “sample-to-purchase” conversion metric that describes, for example, a ratio of a number of items purchased against a number of samples sent. With improvements in said metric, fewer resources may be consumed or expended unnecessarily without a return on investment. According to various examples, adaptive distributive platform 910 and/or information feedback predictor 914a, or any other element, may be configured to store data memorializing electronic transactions and messages associated with predicting consumption of samples and feedback about the samples. Therefore, stored electronic transaction and electronic message data may be used to further refine a predicted date of consumption, as well as refinements in selecting a sample and modifying a feedback response interval of time, according to various examples. Logic, including hardware or software, or a combination thereof, may facilitate one or more structures or functions of adaptive distributive platform 910 and/or information feedback predictor 914a, or any other element to effectuate enhanced prediction of consumption of a sample for generating adaptively-scheduled electronic messages.
Diagram 1000 also depicts distribution predictor 1014 and information feedback predictor 1014a being configured receive item characteristic data 1004 and user characteristic data 1008 from, for example, repositories 1042, 1046, and 1050. In some cases, user-related and/or usage-related data 1008 may include data representing attributes 1040 that, for example, describe demographic characteristics (e.g., location, age, gender, familial status, etc.) for items historically purchased by a user 341 (e.g., data representing patterns of a parent, patterns of a pet owner, patterns of a particular sports fan, etc.). Data representing attributes 1044 may describe items historically purchased by other users 1045 (e.g., patterns of a group of grandparents, patterns of a group of pet owners, patterns of a group of sports fan for a particular team, etc.). Attributes 1044 may represent an aggregation of a subpopulation or a population of which a user belongs. Also, usage-related data may include sale-related and shipment-related attributes 1048 provided by merchant computer systems 1049. Data representing attributes 1040, 1044, and 1048 may be stored in repositories 1042, 1046, and 1050, according to some examples. Examples of some item characteristics in data 1004 may include a product or product type, a service or service type, SKU data, UPC data, etc. for the same or similar items, or complementary or different items (e.g., different items that may have correlatable samples of products that can be predicted to have similar predicted rates of consumption and/or depletion, and may be have a likelihood of a feedback response by a recipient).
Information feedback predictor 1014a may be configured to generated data 1022 to predict, among other things, a date of consumption with which to solicit feedback regarding a replica of an item. A date of consumption may be predicted to occur (e.g., statistically) in a feedback commencement interval or time 1090 during which user 1031 may be predicted to have received a sample 1033 of item 1034. Thus, predicted points in time 1063c, 1063d, and 1063e of consumption (e.g., a predicted time of consumption of a sample) may be a function of a user 1031 (e.g., a user's usage rates and consumption patterns) and/or an item 1034 and its characteristics (e.g., based on usage rates and consumption patterns of a group of users over one or more merchant computer systems). Sample 1033 may be representative of item 1034 and, hence, may include its characteristics. Note that feedback commencement interval 1090 may represent a single point in time, or any number of points in time, according to some examples.
Information feedback predictor 1014a may be configured to receive data from a merchant computing system 1049 that a sample 1033 has shipped to a location at a time (“S”) 1063a. Further, information feedback predictor 1014a may be configured to receive data representing that sample 1033 has been delivered to a location at time (“R”) 1063b. As such, information feedback predictor 1014a may identify time 1063b as a beginning of feedback commencement time 1090. Consumption calculator 1016a may be configured to calculate a time (“C1”) 1063c, time (“C2”) 1063d, or time (“C3”) 1063e (or a time interval) at which one or more units of consumption of a sample may be consumed. According to some examples, times 1063c, 1063d, and 1063e, as well as interval 1090, may be based on usage rates or rates of depletion.
Feedback optimizer 1018a may be configured to adapt a computed time interval 1090 in which consumption is likely to predict a date of consumption by user 1031 based on, for example, user characteristics. Hence, feedback optimizer 1018a may be configured to extend or reduce a size of interval 1090 by adjusting one or more points by modifying beginning or an ending time (e.g., shifting the interval in directions 1081 or 1083). Feedback zone generator 1019a may be configured to adjust an adapted consumption date or range of dates, responsive to data 1024 generated at a user computing device. For example, a user may request to extend a feedback response time to point of time (“F”) 1063f. Thus, feedback zone generator 1019a may be configured to receive adjustment data responsive to data 1022 to generate feedback, the adjustment data configured to modify a predicted date of consumption to time 1063f (or another time). As such, feedback zone generator 1019a can be configured to cause generation of another subset of data to ask or solicit feedback at later date by generating ancillary data representative of another request for a feedback response from user 1031. User 1031 may generate feedback data 1024 including, for example, a request to purchase or subscribe to item 1034 at time (“D1”) 1063f. Feedback other than a purchase, whether positive or negative, may also be included in data 1024 (e.g., a request for an additional sample). At time 1063f, data representing a feedback response to accept a unit of the item in an online purchase may be received, whereby scheduling of transmission of a unit of the item to the location (associated with electronic account) may be generated to initiate successive shipments of the item to user 1031.
Information feedback predictor 1014a may be configured to transmit a request of feedback via electronic message data 1022 at any time in feedback commencement time 1090. For example, information feedback predictor 1014a may transmit electronic message data 1022 to user 1031 at time (“C1”) 1063c, time (“C2”) 1063d, or time (“C3”) 1063e, any of which may be selected based on user characteristics and/or item characteristics. For example, user 1031 may be likely to render feedback after a first unit of consumption at time 1063c for “shampoo,” whereas user 1031 may likely require additional time to render feedback for a sample of a “health supplement,” which may take several days to experience (e.g., two tablets per day for a two weeks). Thus, an item characteristic of “product classification” (e.g., classification of “shampoo” in contrast to “health supplements”) may be used to determine or predict a point in time to transmit a request for feedback during time interval 1090. In some cases, user characteristics of user 1031 may also be used to select one or time (“C1”) 1063c, time (“C2”) 1063d, or time (“C3”) 1063e. If user 1031 is determined or predicted to belong to a household of two to four persons (e.g., a family), then additional time may be provided to ensure multiple persons may experience sample 1033. Thus, a subsequent time 1063e may be selected rather than a first time 1063c. Other user characteristics and item characteristics may be used to select an optimal time at which to solicit feedback, according to various examples.
At 1104, a characteristic of a user or an item, or both, may be identified. For example, an item characteristic may be identified, such as a product classification (e.g., generic product name, such as shampoo), a product type (e.g., a brand name), etc., any of which may be used to describe a sample. Further, user characteristics (e.g., past usage or consumption patterns, including past purchasing patterns), and the like, may be used to predict a date of consumption for providing a timely acquisition of a response from a recipient of a sample.
At 1106, a date of consumption of a replica may be predicted to form a predicted date of consumption as a function of, for example, one or more characteristics (e.g., one or more user characteristics and/or one or more item characteristics). According to some examples, a usage rate of an item may be calculated at 1104, whereby a sample may be a replica of the item (e.g., a consumable item). In some cases, a usage rate may be determined as a function of a depletion rate of the consumable item. A time for a unit of consumption may be computed (e.g., predicted) based on a calculated usage rate. Also, a unit of consumption may be selected as a feedback commencement time during which to solicit feedback. In one example, an interval of time for a predicted unit of consumption may be determined similarly to a zone of time as described herein.
In some examples, a subset of the data (e.g., included in an electronic message) may be transmitted to generate feedback from a user computing device. Data representing a command to delay a feedback commencement time may be received via, for instance, a merchant computing system. Further, transmission of another subset of the data (e.g., another electronic message including feedback) may be postponed by an amount of time. For example, a recipient may request a certain number of additional days to provide feedback. Or, a second electronic message to delay feedback may be transmitted based on predicted or empirical data. Further, a predicted date of consumption may be adapted to form an adapted predicted date of consumption. For example, data representing a feedback commencement time (e.g., a point in time or an interval in which feedback may be solicited) may be modified based on an adapted predicted distribution date to form a modified feedback commencement time.
At 1108, data to cause shipment of a replica may be generated to initiate shipment of the replica or sample to a location associated with the electronic account. For example, an application or software module may include executable instructions to modify or control a shipping application (e.g., an enterprise-level application configured to coordinate shipping of online purchases) to ship a purchased item in a container. In some cases, the selection of the sample may be based on the above-described characteristic. At 1110, a subset of data disposed in an electronic message may be generated to cause initiation of executable instructions to perform a process in which feedback may be generated relative to a date of consumption.
Various structures and/or methods described herein may be applied to web pages 1209, emails 1220, among other forms of communicating requests for acquiring feedback for a sample. Web page 1209 includes a feedback page as a user interface 1212 to provide feedback of a sample (e.g., a shampoo sample) by selecting in interface portion 1215 either immediate feedback via input 1211 (e.g., including an order) or delayed feedback via input 1213. Input 1219 (a pull-down menu to select an amount of delay) may be used to delay a feedback response by “t” units (e.g., any time units, such as units of days). Data received into interface 1212 via inputs 1211, 1213, and 1219 may be stored until input (“send”) 1218 is activated, after which the data may be transmitted contemporaneously (or substantially contemporaneously) to information feedback predictor 1214a and adaptive distribution platform 1210.
An electronic message to request feedback of the sample may be communicated as an email 1220, which is shown to include an item characteristic 1222 in a subject line may be display so a user readily may discern the action required for such a communication. In email body 1224, various delivery options may be embedded as hypertext links to enable a user to provide feedback for a sample of a “Product P” “now,” by selecting link 1275a, or postponing feedback by 7 days with the selection of link 1275b. According to some embodiments, the presentation of a link for a “7 day” delay, as a first link, may be due to its relatively high degree of certainty that a user may experience the sample within another 7 days (based on probabilistic determinations). Thus, adaptive distribution platform 1210 including information feedback predictor 1214a may adapt presentation of user inputs to accommodate user purchasing and scheduling patterns and preferences to enhance, among other things, users' experiences when sampling a good or service.
In view of the foregoing, webpages 1209 and emails 1220 may be formed as integrated electronic messages that are a hybrid of different formatted data originating from different sources, whereby a user may perceive webpages 1210 and emails 1220 as originating from a single source (e.g., a merchant).
Although the foregoing examples have been described in some detail for purposes of clarity of understanding, the above-described inventive techniques are not limited to the details provided. There are many alternative ways of implementing the above-described invention techniques. The disclosed examples are illustrative and not restrictive.
This application is a continuation application of copending U.S. patent application Ser. No. 15/716,486, filed Sep. 26, 2017 and titled, “ADAPTIVE SCHEDULING OF ELECTRONIC MESSAGING BASED ON PREDICTIVE CONSUMPTION OF THE SAMPLING OF ITEMS VIA A NETWORKED COMPUTING PLATFORM,” U.S. patent application Ser. No. 15/716,486 is continuation-in-part application of U.S. patent application Ser. No. 15/479,230, filed Apr. 4, 2017 and titled “ELECTRONIC MESSAGING TO DISTRIBUTE ITEMS BASED ON ADAPTIVE SCHEDULING,” and U.S. patent application Ser. No. 15/716,486 claims the benefit of U.S. Provisional Patent Application No. 62/425,191, filed Nov. 22, 2016 and titled, “ADAPTIVE SCHEDULING TO FACILITATE OPTIMIZED DISTRIBUTION OF SUBSCRIBED ITEMS,” all of which are herein incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4814996 | Wang | Mar 1989 | A |
| 4869266 | Taylor et al. | Sep 1989 | A |
| 5090734 | Dyer et al. | Feb 1992 | A |
| 6204763 | Sone | Mar 2001 | B1 |
| 6415262 | Walker et al. | Jul 2002 | B1 |
| 6963848 | Brinkerhoff | Nov 2005 | B1 |
| 7251617 | Walker et al. | Jul 2007 | B1 |
| 7295990 | Braumoeller et al. | Nov 2007 | B1 |
| 7340414 | Roh et al. | Mar 2008 | B2 |
| 7353194 | Kerker et al. | Apr 2008 | B1 |
| 7540767 | Czarnecki | Jun 2009 | B1 |
| 7552068 | Brinkerhoff | Jun 2009 | B1 |
| 7747543 | Braumoeller et al. | Jun 2010 | B1 |
| 7953645 | Kerker et al. | May 2011 | B2 |
| 8121876 | Braumoeller et al. | Feb 2012 | B1 |
| 8126784 | Agarwal | Feb 2012 | B1 |
| 8353448 | Miller et al. | Jan 2013 | B1 |
| 8370271 | Robinson et al. | Feb 2013 | B1 |
| 8417639 | Baram | Apr 2013 | B1 |
| 8428988 | Braumoeller et al. | Apr 2013 | B1 |
| 8458051 | Saltzman et al. | Jun 2013 | B1 |
| 8498888 | Raff et al. | Jul 2013 | B1 |
| 8620707 | Belyi et al. | Dec 2013 | B1 |
| 8818836 | Braumoeller et al. | Aug 2014 | B1 |
| 8867401 | Tomay et al. | Oct 2014 | B1 |
| 8924262 | Shuster | Dec 2014 | B2 |
| 9047607 | Curial et al. | Jun 2015 | B1 |
| 9134675 | Yang et al. | Sep 2015 | B2 |
| 9659310 | Allen et al. | May 2017 | B1 |
| 9792643 | Masterman | Oct 2017 | B1 |
| 9886810 | Murphy | Feb 2018 | B1 |
| 9959565 | Shuster | May 2018 | B2 |
| 10078860 | Masterman | Sep 2018 | B1 |
| 10262294 | Hahn et al. | Apr 2019 | B1 |
| 10275740 | Alvo et al. | Apr 2019 | B2 |
| 10332067 | Sirisilla et al. | Jun 2019 | B2 |
| 10360617 | High et al. | Jul 2019 | B2 |
| 10430858 | Glasgow et al. | Oct 2019 | B1 |
| 10445751 | Nakano et al. | Oct 2019 | B2 |
| 10453112 | Alvo et al. | Oct 2019 | B2 |
| 10586266 | Fredrich et al. | Mar 2020 | B2 |
| 10614501 | Fredrich et al. | Apr 2020 | B2 |
| 10719860 | Bifolco et al. | Jul 2020 | B2 |
| 10769708 | Alvo et al. | Sep 2020 | B2 |
| 10796274 | Putcha et al. | Oct 2020 | B2 |
| 10817885 | Concannon et al. | Oct 2020 | B2 |
| 11126955 | Watson et al. | Sep 2021 | B1 |
| 11144980 | Fredrich et al. | Oct 2021 | B2 |
| 11354718 | Fredrich et al. | Jun 2022 | B2 |
| 11416810 | Fredrich et al. | Aug 2022 | B2 |
| 11556973 | Alvo et al. | Jan 2023 | B2 |
| 11599931 | Alvo et al. | Mar 2023 | B2 |
| 11763370 | Fredrich et al. | Sep 2023 | B2 |
| 20020161652 | Paullin et al. | Oct 2002 | A1 |
| 20020161670 | Walker et al. | Oct 2002 | A1 |
| 20030004784 | Li et al. | Jan 2003 | A1 |
| 20030110103 | Sesek et al. | Jun 2003 | A1 |
| 20030195788 | Loeb et al. | Oct 2003 | A1 |
| 20030212614 | Chu et al. | Nov 2003 | A1 |
| 20040111326 | Rock et al. | Jun 2004 | A1 |
| 20040162880 | Arnone et al. | Aug 2004 | A1 |
| 20050150951 | Sacco et al. | Jul 2005 | A1 |
| 20050165656 | Frederick et al. | Jul 2005 | A1 |
| 20060025938 | Cottrell | Feb 2006 | A1 |
| 20080015951 | Kerker et al. | Jan 2008 | A1 |
| 20080059309 | Welch | Mar 2008 | A1 |
| 20080071626 | Hill | Mar 2008 | A1 |
| 20090024801 | Choi et al. | Jan 2009 | A1 |
| 20090094121 | Newhouse et al. | Apr 2009 | A1 |
| 20100102082 | Ebrom et al. | Apr 2010 | A1 |
| 20100217450 | Beal et al. | Aug 2010 | A1 |
| 20100241484 | Nichols | Sep 2010 | A1 |
| 20100280960 | Ziotopoulos et al. | Nov 2010 | A1 |
| 20110032070 | Bleile | Feb 2011 | A1 |
| 20110054935 | Hardaway | Mar 2011 | A1 |
| 20110153466 | Harish et al. | Jun 2011 | A1 |
| 20110246215 | Postma et al. | Oct 2011 | A1 |
| 20110251807 | Rada et al. | Oct 2011 | A1 |
| 20110258072 | Kerker et al. | Oct 2011 | A1 |
| 20120004977 | Daniels, Jr. et al. | Jan 2012 | A1 |
| 20120036045 | Lowe et al. | Feb 2012 | A1 |
| 20120124859 | May et al. | May 2012 | A1 |
| 20120150461 | Ohiwa et al. | Jun 2012 | A1 |
| 20120150677 | Shuster | Jun 2012 | A1 |
| 20120330472 | Boot | Dec 2012 | A1 |
| 20130041605 | Ting et al. | Feb 2013 | A1 |
| 20130080968 | Hanson et al. | Mar 2013 | A1 |
| 20130117053 | Campbell | May 2013 | A2 |
| 20130128396 | Danesh et al. | May 2013 | A1 |
| 20130159454 | Hunter et al. | Jun 2013 | A1 |
| 20130268315 | Cotton et al. | Oct 2013 | A1 |
| 20140012706 | Foerster | Jan 2014 | A1 |
| 20140191573 | Chen et al. | Jul 2014 | A1 |
| 20140258165 | Heil | Sep 2014 | A1 |
| 20140279208 | Nickitas et al. | Sep 2014 | A1 |
| 20140279215 | Alvo et al. | Sep 2014 | A1 |
| 20140279276 | Tolcher | Sep 2014 | A1 |
| 20140279291 | Brosnan et al. | Sep 2014 | A1 |
| 20140297487 | Bashkin | Oct 2014 | A1 |
| 20140304026 | Delaney et al. | Oct 2014 | A1 |
| 20140324598 | Freeman | Oct 2014 | A1 |
| 20140351078 | Kaplan et al. | Nov 2014 | A1 |
| 20140368565 | Webb et al. | Dec 2014 | A1 |
| 20150019342 | Gupta | Jan 2015 | A1 |
| 20150105880 | Slupik et al. | Apr 2015 | A1 |
| 20150106228 | Shuster | Apr 2015 | A1 |
| 20150106238 | Shuster | Apr 2015 | A1 |
| 20150112826 | Crutchfield, Jr. | Apr 2015 | A1 |
| 20150127421 | Nakano et al. | May 2015 | A1 |
| 20150149298 | Tapley | May 2015 | A1 |
| 20150178654 | Glasgow et al. | Jun 2015 | A1 |
| 20150261644 | Zhang et al. | Sep 2015 | A1 |
| 20150278912 | Melcher et al. | Oct 2015 | A1 |
| 20150302510 | Godsey et al. | Oct 2015 | A1 |
| 20150363866 | Depew et al. | Dec 2015 | A1 |
| 20150363867 | Tipton et al. | Dec 2015 | A1 |
| 20160034024 | Mergen et al. | Feb 2016 | A1 |
| 20160148149 | Suddamalla et al. | May 2016 | A1 |
| 20160218884 | Ebrom et al. | Jul 2016 | A1 |
| 20160231792 | Richter et al. | Aug 2016 | A1 |
| 20160275424 | Concannon | Sep 2016 | A1 |
| 20160275530 | Concannon et al. | Sep 2016 | A1 |
| 20160282231 | Keene et al. | Sep 2016 | A1 |
| 20160286059 | Hitaka et al. | Sep 2016 | A1 |
| 20160314514 | High | Oct 2016 | A1 |
| 20160356641 | Larson | Dec 2016 | A1 |
| 20160371762 | Fergis et al. | Dec 2016 | A1 |
| 20170011304 | Shimizu | Jan 2017 | A1 |
| 20170019266 | Lim et al. | Jan 2017 | A1 |
| 20170032101 | Skoda | Feb 2017 | A1 |
| 20170109687 | Kamadolli et al. | Apr 2017 | A1 |
| 20170134182 | Davis et al. | May 2017 | A1 |
| 20170193433 | Qin et al. | Jul 2017 | A1 |
| 20170206489 | Sirisilla et al. | Jul 2017 | A1 |
| 20170300984 | Hurwich | Oct 2017 | A1 |
| 20180005173 | Elazary et al. | Jan 2018 | A1 |
| 20180031616 | Hansen et al. | Feb 2018 | A1 |
| 20180053153 | Mai | Feb 2018 | A1 |
| 20180082038 | Blair et al. | Mar 2018 | A1 |
| 20180084078 | Yan | Mar 2018 | A1 |
| 20180089614 | Laskowitz et al. | Mar 2018 | A1 |
| 20180131658 | Bhagwan et al. | May 2018 | A1 |
| 20180144290 | Alvo et al. | May 2018 | A1 |
| 20180144389 | Fredrich et al. | May 2018 | A1 |
| 20180204256 | Bifolco et al. | Jul 2018 | A1 |
| 20180249735 | Espinosa | Sep 2018 | A1 |
| 20180253952 | Huang | Sep 2018 | A1 |
| 20180285809 | Fredrich et al. | Oct 2018 | A1 |
| 20180315111 | Alvo et al. | Nov 2018 | A1 |
| 20180322447 | Cantrell | Nov 2018 | A1 |
| 20180336512 | Clarke et al. | Nov 2018 | A1 |
| 20180349980 | Alvo et al. | Dec 2018 | A1 |
| 20180357688 | Webb et al. | Dec 2018 | A1 |
| 20180365753 | Fredrich et al. | Dec 2018 | A1 |
| 20190066183 | Fredrich et al. | Feb 2019 | A1 |
| 20190073627 | Nakdimon et al. | Mar 2019 | A1 |
| 20190087769 | Glasgow et al. | Mar 2019 | A9 |
| 20190295148 | Lefkow et al. | Sep 2019 | A1 |
| 20190295150 | High et al. | Sep 2019 | A1 |
| 20190370888 | Walker et al. | Dec 2019 | A1 |
| 20190392378 | Alvo et al. | Dec 2019 | A1 |
| 20200104903 | Alvo et al. | Apr 2020 | A1 |
| 20200250727 | Fredrich et al. | Aug 2020 | A1 |
| 20200250728 | Fredrich et al. | Aug 2020 | A1 |
| 20210004881 | Bifolco et al. | Jan 2021 | A1 |
| 20210049670 | Alvo et al. | Feb 2021 | A1 |
| 20220198545 | Fredrich et al. | Jun 2022 | A1 |
| 20220343387 | Fredrich et al. | Oct 2022 | A1 |
| 20230316220 | Bifolco et al. | Oct 2023 | A1 |
| 20230342714 | Alvo et al. | Oct 2023 | A1 |
| 20230360108 | Alvo et al. | Nov 2023 | A1 |
| 20230410184 | Alvo et al. | Dec 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 8694301 | Mar 2002 | AU |
| 106157185 | Nov 2016 | CN |
| 2000148432 | May 2000 | JP |
| 2017074757 | May 2017 | WO |
| 2019089480 | May 2019 | WO |
| Entry |
|---|
| Y.-J. Wu, et al. “An enhanced recommendation scheme for online grocery shopping.” IEEE 15th International Symposium on Consumer Electronics (ISCE), 2011, pp. 410-415 <https://ieeexplore.ieee.org/document/5973860?source=IQplus> (Year: 2011). |
| “Belkin WeMo Insight Switch”, Belkin Instruction Manual, Part# 8830uk17750/SKU: F7C029uk, Oct. 23, 2014, http://www.free-instruction-manuals.com/pdf/pa_1184191.pdf. |
| “WeMo Insight Smart Plug, F7C029 Frequently Asked Questions”, Belkin Knowledge Article, retrieved Nov. 9, 2017, http://www.belkin.com/US/support-article?articleNum=80139. |
| Alvo et al., “Consumable Usage Sensors and Applications to Facilitate Automated Replenishment of Consumables via an Adaptive Distribution Platform,” U.S. Appl. No. 62/579,871, filed Dec. 31, 2017. |
| Alvo et al., “Consumable Usage Sensors and Applications to Facilitate Automated Replenishment of Consumables via an Adaptive Distribution Platform,” U.S. Appl. No. 15/801,002, filed Nov. 1, 2017. |
| Alvo et al., “Consumable Usage Sensors and Applications to Facilitate Automated Replenishment of Consumables via an Adaptive Distribution Platform,” U.S. Appl. No. 62/579,872. |
| Alvo et al., “Consumable Usage Sensors and Applications to Facilitate Automated Replenishment of Consumables via an Adaptive Distribution Platform,” U.S. Appl. No. 15/801,172, filed Nov. 1, 2017. |
| Alvo et al., “Sensors and Executable Instructions to Compute Consumable Usage to Automate Replenishment or Service of Consumables via an Adaptive Distribution Platform,” U.S. Appl. No. 15/905,764, filed Feb. 26, 2018. |
| Alvo et al., Consumable Usage Sensors and Applications to Facilitate Automated Replenishment of Consumables via an Adaptive Distribution Platform, U.S. Appl. No. 16/398,241, filed Apr. 29, 2019. |
| Alvo, Greg, “Automated Method and System for Converting One-Time Buyers of a Product/Service Into Recurring Subscribers”, U.S. Appl. No. 61/791,873, filed Mar. 15, 2013. |
| Amazon Dash Replenishment Adds New Device Makers and Launches New Products. Retrieved from . Originally published Nov. 22, 2016. (Year: 2016). |
| Amazon, “Order a Subscribe & Save Subscription,” archived back at least as far as Oct. 2014, accessed Jul. 10, 2019 at https://web.archive.org/web/20141009140840/http://www.amazon.com/gp/help/customer/display.html? nodeId=201125870. |
| Anonymous, Amazon.com Launches Magazines Store; Customers Can Now Purchase Magazine Subscriptions for Themselves or as Gifts on Amazon.com, Oct. 30, 2001, Business Water, pp. 1-2. (Year: 2001). |
| Bargeon, Brittany E., Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/962,213 mailed Jul. 25, 2019. |
| Bargeon, Brittany E., U.S. Patent and Trademark Office Final Office Action mailed Oct. 23, 2015 for U.S. Appl. No. 13/962,213 (24 pages). |
| Bargeon, Brittany E., U.S. Patent and Trademark Office Non-Final Office Action mailed Aug. 14, 2014 for U.S. Appl. No. 13/962,213 (21 pages). |
| Bargeon, Brittany E., U.S. Patent and Trademark Office Non-Final Office Action mailed Jun. 9, 2016 for U.S. Appl. No. 13/962,213 (26 pages). |
| Bargeon, Brittany E., U.S. Patent and Trademark Office Non-Final Office Action mailed Nov. 18, 2016 for U.S. Appl. No. 13/962,213 (22 pages). |
| Bifolco et al., “Adaptive Scheduling to Facilitate Optimized Distribution of Subscribed Items”, U.S. Appl. No. 62/425,191, filed Nov. 22, 2016. |
| Bifolco et al., “Adaptive Scheduling to Facilitate Optimized Distribution of Subscribed Items,” U.S. Appl. No. 15/821,362, filed Nov. 22, 2017. |
| CTIA's Annual Survey Says US Wireless Providers Handled 3.2 Trillion Megabytes of Data Traffic in 2013 for a 120 Percent Increase Over 2012, Jun. 17, 2014, https://web.archive.org/web/20140723023447/http://www.ctia.org/resource-library/press-releases/archive/ctia-annual-survey-2013. |
| Eskridge, Cory W., Final Office Action mailed Apr. 6, 2021 for U.S. Appl. No. 15/479,230. |
| Eskridge, Cory W., Final Office Action mailed Feb. 21, 2020 for U.S. Appl. No. 15/479,230. |
| Eskridge, Cory W., Non-Final Office Action mailed Aug. 18, 2020 for U.S. Appl. No. 15/479,230. |
| Fredrich et al., “Adaptive Scheduling of Electronic Messaging Based on Predictive Consumption of the Sampling of Items via a Networked Computing Platform”, U.S. Appl. No. 15/716,486, filed Sep. 26, 2017. |
| Fredrich et al., “Dynamic Processing of Electronic Messaging Data and Protocols to Automatically Generate Location Predictive Retrieval Using a Networked, Multi-Stack Computing Environment,” U.S. Appl. No. 16/046,690, filed Jul. 26, 2018. |
| Fredrich et al., “Dynamic Processing of Electronic Messaging Data and Protocols to Automatically Generate Location Predictive Retrieval Using a Networked, Multi-Stack Computing Environment,” U.S. Appl. No. 16/115,474, filed Aug. 28, 2018. |
| Garg, Yogesh C., Non-Final Office Action mailed Nov. 12, 2019 for U.S. Appl. No. 15/821,362. |
| Kim, Harry C., Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2018/058053 mailed May 7, 2019. |
| Koester, Michael R., Non-Final Office Action mailed Jan. 8, 2021 for U.S. Appl. No. 15/716,486. |
| Koester, Michael R., Notice of Allowance and Fee(s) Due, Examiner Interview Summary and Examiner's Amendment mailed Jun. 10, 2021 for U.S. Appl. No. 15/716,486. |
| Koester, Michael Richard, Final Office Action mailed Jun. 5, 2020 for U.S. Appl. No. 15/716,586. |
| Koester, Michael Richard, Non-Final Office Action mailed Nov. 25, 2019 for U.S. Appl. No. 15/716,486. |
| Mahone, Kristie A., Final Office Action for U.S. Appl. No. 15/801,002 mailed Sep. 28, 2018. |
| Mahone, Kristie A., Non-Final Office Action for U.S. Appl. No. 15/801,002 mailed Mar. 8, 2018. |
| Mitchell, Nathan A., Final Office Action mailed Jul. 28, 2021 for U.S. Appl. No. 15/905,764. |
| Mitchell, Nathan A., Final Office Action mailed Jul. 28, 2021 for U.S. Appl. No. 16/398,241. |
| Mitchell, Nathan A., Non-Final Office Action for U.S. Appl. No. 15/905,764 mailed Mar. 18, 2020. |
| Mitchell, Nathan A., Non-Final Office Action mailed Mar. 23, 2021 for U.S. Appl. No. 16/398,241. |
| Mitchell, Nathan A., Notice of Allowance and Fee(s) Due mailed Mar. 1, 2019 for U.S. Appl. No. 15/801,002. |
| Rao, Leena, “Amazon to Add Trash Cans, Dishwashers, Dryers to Smart Reordering Service.” Published Aug. 2016. Retrieved from on Feb. 22, 2019. |
| Ricker, Thomas; “Wanted: An Amazon Fridge That Automatically Reorders Food,” Published Jan. 18, 2017; Retrieved From on Mar. 18, 2020. |
| Ricker, Thomas; “Wanted: An Amazon Fridge That Automatically Reorders Food.” Published Jan. 2017. Retrieved from on Feb. 22, 2019. |
| Stinson, Tanner, “AmazonKitchen DRS”, Hackster Project, Published Feb. 5, 2017, https://www.hackster.io/tanner-stinson/amazonkitchen-drs-75fc24?ref=challenge&ref_id=78&offset=9. |
| Vodnick, Craig, “How Do You Handle Subscription Renewals?”, Published Mar. 28, 2011, Cleverbridge Blog, URL: <> (Year: 2011). |
| Wilder, Andrew H., Non-Final Office Action mailed Nov. 25, 2019 for U.S. Appl. No. 15/801,172. |
| Zimmerman, Jeffrey P., Final Office Action mailed Apr. 15, 2019 for U.S. Appl. No. 16/046,690. |
| Zimmerman, Jeffrey P., Non-Final Office Action mailed Jun. 20, 2019 for U.S. Appl. No. 15/479,230. |
| Zimmerman, Jeffrey P., Non-Final Office Action mailed Jun. 20, 2019 for U.S. Appl. No. 16/046,690. |
| Zimmerman, Jeffrey P., Final Office Action mailed Apr. 15, 2019 for U.S. Appl. No. 16/115,474. |
| Zimmerman, Jeffrey P., Non-Final Office Action for U.S. Appl. No. 16/046,690 mailed Dec. 10, 2018. |
| Zimmerman, Jeffrey P., Non-Final Office Action for U.S. Appl. No. 16/115,474 mailed Dec. 6, 2018. |
| Zimmerman, Jeffrey P., Non-Final Office Action mailed Jul. 15, 2019 for U.S. Appl. No. 16/115,474. |
| Bargeon, Brittany E., Non-Final Office Action mailed Dec. 13, 2021 for U.S. Appl. No. 16/590,210. |
| Eskridge, Cory W., Final Office Action mailed Dec. 15, 2021 for U.S. Appl. No. 15/479,230. |
| Garg, Yogesh C., Non-Final Office Action mailed Oct. 18, 2021 for U.S. Appl. No. 16/930,825. |
| Garg, Yogesh C., Notice of Allowance and Fee(s) Due mailed Jan. 10, 2022 for U.S. Appl. No. 16/930,825. |
| Mitchell, Nathan A., Non-Final Office Action mailed Dec. 13, 2021 for U.S. Appl. No. 15/905,764. |
| Bargeon, Brittany E., Final Office Action mailed Aug. 25, 2022 for U.S. Appl. No. 16/590,210. |
| Bargeon, Brittany E., Non-Final Office Action mailed Nov. 7, 2023 for U.S. Appl. No. 18/098,039. |
| Bargeon, Brittany E., Notice of Allowance and Fee(s) Due mailed Sep. 15, 2022 for U.S. Appl. No. 16/590,210. |
| Eskridge, Cory W., Notice of Allowance and Fee(s) Due mailed Apr. 14, 2022 for U.S. Appl. No. 15/479,230. |
| Eskridge, Cory W., Notice of Allowance and Fee(s) Due mailed Jun. 29, 2023 for U.S. Appl. No. 17/887,756. |
| Fredrich et al., “Electronic Messaging to Distribute Items Based on Adaptive Scheduling”, U.S. Appl. No. 15/479,230, filed Apr. 4, 2017. |
| Garg, Yogesh C., Non-Final Office Action mailed Oct. 18, 2023 for U.S. Appl. No. 17/711,560. |
| Hsu et al., “Smart Pantries for Homes,” 2006 IEEE International Conference on Systems, Man and Cybernetics, 2006, pp. 4276-4289, dot: 10.1109/ICSMC.2006.384806, Retrieved May 28, 2022; https://ieeexplore.ieee.org/document/4274571?source=IQplus (Year: 2006). |
| Koester, Michael R., Final Office Action mailed Aug. 9, 2022 for U.S. Appl. No. 17/693,341. |
| Koester, Michael R., Non-Final Office Action mailed Jun. 23, 2022 for U.S. Appl. No. 16/779,600. |
| Koester, Michael R., Non-Final Office Action mailed Jun. 7, 2022 for U.S. Appl. No. 17/693,341. |
| Koester, Michael Richard, Final Office Action mailed Jan. 24, 2024 for U.S. Appl. No. 16/779,600. |
| Koester, Michael Richard, Final Office Action mailed Jul. 21, 2023 for U.S. Appl. No. 17/693,341. |
| Koester, Michael Richard, Final Office Action mailed Sep. 23, 2022 for U.S. Appl. No. 16/779,600. |
| Koester, Michael Richard, Non-Final Office Action mailed Apr. 10, 2023 for U.S. Appl. No. 16/779,600. |
| Koester, Michael Richard, Non-Final Office Action mailed Mar. 28, 2023 for U.S. Appl. No. 17/693,341. |
| Lowry et al., Online Payment Gateways Used to Facilitate E-Commerce Transactions and Improve Risk Management, Jan. 2006, Communications of the Association for Information Systems (CAIS), vol. 17, Article 6, pp. 1-49. (Year: 2006). |
| Mitchell, Nathan A., Final Office Action mailed Apr. 6, 2022 for U.S. Appl. No. 15/905,764. |
| Mitchell, Nathan A., Final Office Action mailed Apr. 6, 2022 for U.S. Appl. No. 16/398,241. |
| Mitchell, Nathan A., Non-Final Office Action mailed Aug. 11, 2022 for U.S. Appl. No. 15/905,764. |
| Mitchell, Nathan A., Non-Final Office Action mailed Oct. 17, 2023 for U.S. Appl. No. 18/072,639. |
| Mitchell, Nathan A., Notice of Allowance and Fee(s) Due mailed Aug. 23, 2022 for U.S. Appl. No. 16/398,241. |
| Mitchell, Nathan A., Notice of Allowance and Fee(s) Due mailed Dec. 23, 2022 for U.S. Appl. No. 15/905,764. |
| Wilder, Andrew H., Non-Final Office Action mailed Feb. 9, 2022 for U.S. Appl. No. 16/943,226. |
| Wilder, Andrew H., Notice of Allowance and Fee(s) Due mailed Oct. 19, 2022 for U.S. Appl. No. 16/943,226. |
| Wilder, Andrew H., Notice of Allowance and Fee(s) Due mailed Oct. 2, 2023 for U.S. Appl. No. 18/117,980. |
| Wilder, Hunter, Final Office Action mailed Jun. 23, 2022 for U.S. Appl. No. 16/943,226. |
| Yesildag, Mehmet, Notice of Allowance and Fee(s) Due mailed May 11, 2023 for U.S. Appl. No. 17/712,063. |
| Number | Date | Country | |
|---|---|---|---|
| 20210406984 A1 | Dec 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62425191 | Nov 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15716486 | Sep 2017 | US |
| Child | 17365954 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15479230 | Apr 2017 | US |
| Child | 15716486 | US |
