Granted Patent B2

US 12,694,440 · App. 18/819,926 · Granted Jul 28, 2026

Inventors: Mark Charles Coker (Los Gatos, CA); William James Kendrick (Olympia, WA)

Assignee: DRAFT2DIGITAL, LLC

G06Q30/0641G06Q20/28G06Q20/401G06Q30/0276G06Q30/0623G06Q30/0633

Abstract

Claims (71)

1 . A product release system for enabling prepurchase of one or more products, the product release system comprising:

one or more servers including a processor and a non-transitory computer-readable medium coupled with the processor, storing a product release platform having a user interface, wherein the product release platform is operable to:

generate one or more prepurchase events based on a product, the prepurchase events each having a prepurchase function, a product identifier identifying the product, a starting time and pricing data for the product, wherein the prepurchase function enables one or more customers to complete a purchase transaction to purchase and obtain the product before a product release date of the product that is in the future, the prepurchase event begins and ends before the product release date and the generation of the one or more prepurchase events is initiated by a product controller account associated with a creator of the product;

generate one or more prepurchase keys for the one or more prepurchase events, wherein completion of the purchase transaction provided by the prepurchase events requires input of one or more of the prepurchase keys;

provide a dashboard module that enables the product controller account associated with the creator of the product to view at least one of active prepurchase events and inactive prepurchase events of the prepurchase events initiated by the product controller account, and modify one or more characteristics of the at least one of the active prepurchase events and the inactive prepurchase events, wherein the characteristics include the pricing data of the at least one of the active prepurchase events and the inactive prepurchase events; and

for each of the prepurchase events:

receive one or more input keys from the one or more customers;

determine if the input keys correspond to the prepurchase keys associated with the prepurchase event; and

in advance of the product release date, if the one or more input keys correspond to the prepurchase keys associated with the prepurchase event, facilitate purchase of the product by the one or more customers using the purchase function to complete the purchase transaction and provide access to the product to the one or more customers upon completion of the purchase transaction.

2 . The product release system of claim 1 , wherein each of the prepurchase keys is included within a hyperlink that links to a page associated with the prepurchase event of that prepurchase key.

3 . The product release system of claim 1 , wherein each of the prepurchase events has an end condition comprising one or more of an end time, a quantity of sales, a maximum quantity of customers accessing the prepurchase event, an inventory status of the product, and a manual cancellation of the event, and further wherein, for each of the prepurchase events, upon reaching the end condition the product release platform is operable to terminate the prepurchase event.

4 . The product release system of claim 1 , wherein the pricing data includes a pricing metric that indicates a price value for the starting time and one or more subsequent times between the starting time and an end of the prepurchase event as indicated by an end condition of the prepurchase event.

5 . The product release system of claim 1 , wherein each of the prepurchase events include one or more prepurchase conditions comprising one or more of submitting contact information, purchasing or subscribing to one or more other products or services, spending a threshold amount of money and agreeing to a terms of use of the product, and further wherein, for each of the prepurchase events, the product release platform is operable to prevent sales of the product to one or more of the customers even if the submitted key corresponds to the prepurchase keys associated with the prepurchase event if the one or more of the customers have not satisfied the prepurchase conditions.

6 . The product release system of claim 5 , wherein, for each of the prepurchase events, the product release platform is operable to add the contact information submitted to satisfy the prepurchase conditions of the prepurchase event to the product controller account.

7 . The product release system of claim 1 , wherein for each of the prepurchase events, the product release platform is operable to generate a prepurchase listing that identifies the product and the release date of the product.

8 . The product release system of claim 1 , wherein the product release platform is operable to:

generate one or more prepurchase preorder keys;

generate one or more prepurchase preorder events that are each based on one of the prepurchase events and include a prepurchase event identifier of the one of the prepurchase events, a start date and an end date that are both prior to the start time of the one of the prepurchase events and a preorder function that enables the one or more customers to preorder a purchase of the product during the one of the prepurchase events;

for each of the prepurchase preorder events, facilitate preordering of the product by one or more customers during the prepurchase preorder event using the preorder function if one or more prepurchase preorder keys submitted by the customers correspond to the prepurchase preorder keys associated with the prepurchase preorder event and prevent preordering of the product by the one or more customers during the prepurchase preorder event if the one or more prepurchase preorder keys submitted by the customers do not correspond to the prepurchase preorder keys associated with the prepurchase preorder event; and

in response to preordering of the product by the one or more customers using the preorder function, facilitate the preordered purchase of the product by the one or more customers during the identified one of the prepurchase events using the purchase function of the one of the prepurchase events.

9 . A method of enabling prepurchase of one or more products via one or more product release servers, the method comprising:

generating, with the product release servers one or more prepurchase events based on a product, wherein the prepurchase events each having a purchase function, a product identifier identifying the product, a starting time and pricing data for the product, wherein the purchase function enables one or more customers to complete a purchase transaction to purchase and obtain the product before a product release date of the product that is in the future, the prepurchase event begins and ends before the product release date and the generation of the one or more prepurchase events is initiated by a product controller account associated with a creator of the product;

generating, with the product release servers, one or more prepurchase keys for the one or more prepurchase events, wherein completion of the purchase transaction provided by the prepurchase events requires input of one or more of the prepurchase keys;

providing, with the product release servers, a dashboard module that enables the product controller account associated with the creator of the product to view at least one of active prepurchase events and inactive prepurchase events of the prepurchase events initiated by the product controller account, and modify one or more characteristics of the at least one of the active prepurchase events and the inactive prepurchase events, wherein the characteristics include the pricing data of the at least one of the active prepurchase events and the inactive prepurchase events; and

for each of the prepurchase events, with the product release servers:

receiving one or more input keys from one or more customers;

determining if the input keys correspond to the prepurchase keys associated with the prepurchase event; and

in advance of the product release date, if the one or more input keys correspond to the prepurchase keys associated with the prepurchase event, facilitating purchase of the product by the one or more customers using the purchase function to complete the purchase transaction and provide access to the product to the one or more customers upon completion of the purchase transaction.

10 . The method of claim 9 , wherein each of the prepurchase keys is included within a hyperlink that links to a page associated with the prepurchase event of that prepurchase key.

11 . The method of claim 9 , wherein each of the prepurchase events has an end condition comprising one or more of an end time, a quantity of sales, a maximum quantity of customers accessing the prepurchase event, an inventory status of the product and manual cancellation of the event, and further wherein, for each of the prepurchase events, upon reaching the end condition the product release platform is operable to terminate the prepurchase event.

12 . The method of claim 9 , wherein the pricing data includes a pricing metric that indicates a price value for the starting time and one or more subsequent times between the starting time and an end of the prepurchase event as indicated by an end condition of the prepurchase event.

13 . The method of claim 9 , wherein each of the prepurchase events include one or more prepurchase conditions comprising one or more of submitting contact information, purchasing or subscribing to one or more other products or services, spending a threshold amount of money and agreeing to a terms of use of the product, further comprising, for each of the prepurchase events, preventing sales of the product to one or more of the customers with the product release servers even if the submitted key corresponds to the prepurchase keys associated with the prepurchase event if the one or more of the customers have not satisfied the prepurchase conditions.

14 . The method of claim 13 , further comprising for each of the prepurchase events adding the contact information submitted to satisfy the prepurchase conditions of the prepurchase event to the product controller account.

15 . The method of claim 9 , further comprising, for each of the prepurchase events, generating with the product release servers a prepurchase listing that identifies the product and the release date of the product.

16 . The method of claim 9 , further comprising, with the product release servers:

generating one or more prepurchase preorder keys;

generating one or more prepurchase preorder events that are each based on one of the prepurchase events and include a prepurchase event identifier of the one of the prepurchase events, a start date and an end date that are both prior to the start time of the one of the prepurchase events and a preorder function that enables the one or more customers to preorder a purchase of the product during the one of the prepurchase events;

for each of the prepurchase preorder events, with the product release servers, facilitating preordering of the product by one or more customers during the prepurchase preorder event using the preorder function if one or more prepurchase preorder keys submitted by the customers correspond to the prepurchase preorder keys associated with the prepurchase preorder event and preventing preordering of the product by the one or more customers during the prepurchase preorder event if the one or more prepurchase preorder keys submitted by the customers do not correspond to the prepurchase preorder keys associated with the prepurchase preorder event; and

in response to preordering of the product by the one or more customers using the preorder function, facilitate the preordered purchase of the product by the one or more customers during the identified one of the prepurchase events with the product release servers using the purchase function of the one of the prepurchase events.

17 . A non-transitory computer-readable medium storing a product release platform configured to:

generate one or more prepurchase events based on a product, the prepurchase events each having a purchase function, a product identifier identifying the product, a starting time and pricing data for the product, wherein the purchase function enables one or more customers to complete a purchase transaction to purchase and obtain the product before a product release date of the product that is in the future, the prepurchase event begins and ends before the product release date and the generation of the one or more prepurchase events is initiated by a product controller account associated with a creator of the product;

generate one or more prepurchase keys for the one or more prepurchase events, wherein completion of the purchase transaction provided by the prepurchase events requires input of one or more of the prepurchase keys;

provide a dashboard module that enables the product controller account associated with the creator of the product to view at least one of active prepurchase events and inactive prepurchase events of the prepurchase events initiated by the product controller account, and modify one or more characteristics of the at least one of the active prepurchase events and the inactive prepurchase events, wherein the characteristics include the pricing data of the at least one of the active prepurchase events and the inactive prepurchase events; and

for each of the prepurchase events:

receive one or more input keys from the one or more customers;

determine if the input keys correspond to the prepurchase keys associated with the prepurchase event; and

in advance of the product release date, if the one or more input keys correspond to the prepurchase keys associated with the prepurchase event, facilitate purchase of the product by the one or more customers using the purchase function to complete the purchase transaction and provide access to the product to the one or more customers upon completion of the purchase transaction.

18 . The medium of claim 17 , wherein each of the prepurchase keys is included within a hyperlink that links to a page associated with the prepurchase event of that prepurchase key.

19 . The medium of claim 17 , wherein each of the prepurchase events has an end condition comprising one or more of an end time, a quantity of sales, a maximum quantity of customers accessing the prepurchase event, an inventory status of the product and manual cancellation of the event, and further wherein, for each of the prepurchase events, upon reaching the end condition the product release platform is operable to terminate the prepurchase event.

20 . The medium of claim 17 , wherein the pricing data includes a pricing metric that indicates a price value for the starting time and one or more subsequent times between the starting time and an end of the prepurchase event as indicated by an end condition of the prepurchase event.

21 . The medium of claim 17 , wherein each of the prepurchase events include one or more prepurchase conditions comprising one or more of submitting contact information, purchasing or subscribing to one or more other products or services, spending a threshold amount of money and agreeing to a terms of use of the product, and further wherein, for each of the prepurchase events, the product release platform is operable to prevent sales of the product to one or more of the customers even if the submitted key corresponds to the prepurchase keys associated with the prepurchase event if the one or more of the customers have not satisfied the prepurchase conditions.

22 . The medium of claim 21 , wherein, for each of the prepurchase events, the product release platform is operable to add the contact information submitted to satisfy the prepurchase conditions of the prepurchase event to the product controller account.

23 . The medium of claim 17 , wherein for each of the prepurchase events, the product release platform is operable to generate a prepurchase page that identifies the product and the release date of the product.

24 . The medium of claim 17 , wherein the product release platform is operable to:

generate one or more prepurchase preorder keys;

generate one or more prepurchase preorder events that are each based on one of the prepurchase events and include a prepurchase event identifier of the one of the prepurchase events, a start date and an end date that are both prior to the start time of the one of the prepurchase events and a preorder function that enables the one or more customers to preorder a purchase of the product during the one of the prepurchase events;

for each of the prepurchase preorder events, facilitate preordering of the product by one or more customers during the prepurchase preorder event using the preorder function if one or more prepurchase preorder keys submitted by the customers correspond to the prepurchase preorder keys associated with the prepurchase preorder event and prevent preordering of the product by the one or more customers during the prepurchase preorder event if the one or more prepurchase preorder keys submitted by the customers do not correspond to the prepurchase preorder keys associated with the prepurchase preorder event; and

in response to preordering of the product by the one or more customers using the preorder function, facilitate the preordered purchase of the product by the one or more customers during the identified one of the prepurchase events using the purchase function of the one of the prepurchase events.

25 . A product release system for enabling prepurchase of one or more products, the product release system comprising:

one or more servers including a processor and a non-transitory computer-readable medium coupled with the processor, storing a product release platform having a user interface, wherein the product release platform is operable to:

generate one or more prepurchase events based on a product, the prepurchase events each having a product identifier identifying the product, a purchase function, a starting time and pricing data for the product, wherein the purchase function enables one or more customers to complete a purchase transaction to purchase and obtain the product before a product release date of the product that is in the future, the prepurchase event begins and ends before the product release date and the generation of the one or more prepurchase events is initiated by a product controller account associated with a creator of the product;

provide a dashboard module that enables the product controller account associated with the creator of the product to view at least one of active prepurchase events and inactive prepurchase events of the prepurchase events initiated by the product controller account, and modify one or more characteristics of the at least one of the active prepurchase events and the inactive prepurchase events, wherein the characteristics include the pricing data of the at least one of the active prepurchase events and the inactive prepurchase events; and

for each of the prepurchase events, in advance of the product release date, facilitate purchase of the product by the one or more customers using the purchase function to complete the purchase transaction and provide access to the product to the one or more customers upon completion of the purchase transaction.

26 . The product release system of claim 25 , wherein each of the prepurchase events has an end condition comprising one or more of an end time, a quantity of sales, a maximum quantity of customers accessing the prepurchase event, an inventory status of the product and a manual cancellation of the event, and further wherein, for each of the prepurchase events, upon reaching the end condition the product release platform is operable to terminate the prepurchase event.

27 . The product release system of claim 25 , wherein the pricing data includes a pricing metric that indicates a price value for the starting time and one or more subsequent times between the starting time and an end of the prepurchase event as indicated by an end condition of the prepurchase event.

28 . The product release system of claim 25 , wherein each of the prepurchase events include one or more prepurchase conditions comprising one or more of submitting contact information, purchasing or subscribing to one or more other products or services, spending a threshold amount of money and agreeing to a terms of use of the product, and further wherein, for each of the prepurchase events, the product release platform is operable to prevent sales of the product to one or more of the customers if the one or more of the customers have not satisfied the prepurchase conditions.

29 . The product release system of claim 25 , wherein for each of the prepurchase events, the product release platform is operable to generate a prepurchase page that identifies the product and the release date of the product.

30 . The product release system of claim 25 , wherein the product release platform is operable to:

generate one or more prepurchase preorder events based on one of the prepurchase events and prepurchase preorder data for the product indicated by the third party device, wherein the prepurchase preorder events include a preorder function that enables the one or more customers to preorder a purchase of the product during the one of the prepurchase events, and further wherein the prepurchase preorder data includes information that identifies the one of the prepurchase events;

for each of the prepurchase preorder events, facilitate preordering of the product by one or more customers during the prepurchase preorder event using the preorder function; and

in response to preordering of the product by the one or more customers using the preorder function, facilitate the preordered purchase of the product by the one or more customers during the identified one of the prepurchase events using the purchase function of the one of the prepurchase events.

Assignments (2)

Continuity (4)

References Cited (75)