SYSTEM AND METHOD OF SAFELY DISTRIBUTING HIGH DEMAND PRODUCTS
A system for use with computing devices each associated with one of a plurality of customers. The system includes a customer application executing on each of the computing devices and a computing system that receives requests, from a requesting portion of the computing devices, to purchase a product not yet available for purchase. The computing system assigns potential reservations to selected winning ones of the customers associated with the requesting portion, receives confirmations from a confirmed portion of the selected winning customers, converts the potential reservations to actual reservations for the confirmed portion, and transmits a code to each of the confirmed portion of the selected winning customers only after the selected winning customer submits validation information that the computing system determines satisfies validation criteria. A merchant transfers the product to one of the customers at a physical store location only if the customer provides the code to the merchant.
Latest Synchrony Bank Patents:
- NETWORK DATA MANAGEMENT AND DATA SECURITY
- SYSTEMS AND METHODS FOR GENERATING MODELS FOR CLASSIFYING IMBALANCED DATA
- Distributed ledger system for automated claim adjudication
- Systems and methods for secure transaction reversal
- SYSTEM AND METHOD FOR PROCESSING OF PROMOTIONS IN CONNECTION WITH DIGITAL PURCHASING
This application is a continuation of U.S. patent application Ser. No. 15/882,639, filed on Jan. 29, 2018, which is incorporated by reference herein its entirety.
BACKGROUND OF THE INVENTION Field of the InventionThe present invention is directed generally to methods of improving customer safety and particularly to methods of safely distributing high demand products.
Description of the Related ArtIf a customer wishes to receive an instance of a product immediately, that customer is typically required to travel to a physical store location to pick up the instance of the product. This can create problems when the product is in high demand. High demand products, such as limited edition sneakers, concert tickets, iPhones, movie tickets, and limited edition items, can cause lines, public disturbance, theft, violence, or even death. Therefore, a need exists for new and improved methods of distributing and/or obtaining such products. The present application provides these and other advantages as will be apparent from the following detailed description and accompanying figures.
Like reference numerals have been used in the figures to identify like components.
DETAILED DESCRIPTION OF THE INVENTIONThe system 100 may include any number of customer computing devices each like the customer computing devices 110A-110C and each operated by a different customer. However, for ease of illustration, only the three customer computing devices 110A-110C have been illustrated and will be described below. Nevertheless, each of the customer computing devices may include substantially identical components and be configured to perform the same functions attributed to the customer computing devices 110A-110C. Similarly, the system 100 may include any number of merchant computing systems each like the merchant computing systems 120A and 120B each operated by a different merchant. However, for ease of illustration, only the merchant computing systems 120A and 120B have been illustrated and will be described below. Nevertheless, each of the merchant computing systems may include substantially identical components and be configured to perform the same functions attributed to the merchant computing systems 120A and 120B.
By way of a non-limiting example, each of the customer computing devices 110A-110C may be implemented as a mobile communication device 400 (illustrated in
Referring to
Each of the merchants 122A and 122B operates one or more physical store locations. For example, in
Referring to
The reader application 154 is configured to detect the proximity signal 182 (see
The product reservation computing system 130 is configured to facilitate the sale of high-demand products by collecting requests for reservations for a particular product (e.g., the product “SKU1”) and selecting (e.g., via a lottery process) those of the customers 112A-112C who will be allowed to purchase the particular product. The product reservation computing system 130 implements a product reservation module 140 that includes a collection of wish lists 142 and an Assignment Script Algorithm (“ASA”) 144. The product reservation computing system 130 may also implement a database 146.
The product reservation module 140 may be characterized as a comprehensive Internet-based application for managing and loading an inventory of products and marketing the products. In particular, the product reservation module 140 may be used to launch a new high demand product safely. For example, the merchant 122A may enter launch information into the product reservation module 140. Then, the product reservation module 140 may receive requests for the product from the customers 112A-112C (e.g., via the customer application 152 executing on the customer computing devices 110A-110C, respectively). Next, the product reservation module 140 determines which of the customers 112A-112C has won (e.g., via a lottery process) the opportunity to purchase the product and assigns potential reservations to such winning customers. At this point, the winning customers must confirm that they are planning on picking up the product at one of the merchant's store locations. The product reservation module 140 converts the potential reservation to an actual reservation for each winning customer who confirms that the winning customer will pick up the product. Next, those of the winning customers with actual reservations either pick up the product at one of the merchant's physical store locations or fail to pick up the product.
In first block 210 (see
In next block 212 (see
The merchant 122A may also identify those of the store locations 160A and 160B where the product “SKU1” is or will be available as well as inventory data related to the product “SKU1.” For example, the merchant 122A may enter an amount of the product “SKU1” available for each product option (e.g., size, color, etc.) at each of the store locations 160A and 160B where the product “SKU1” is or will be available. In addition, the merchant 122A may enter a name associated with the product “SKU1” as well as a manufacturer of and/or a brand associated with the product “SKU1.” Thus, the merchant 122A instantiates the availability of the product “SKU1” using the product reservation module 140. The merchant 122A may also provide additional launch information, such as when (e.g., date and time) the product “SKU1” will be available for purchase (e.g., at one or both of the store locations 160A and 160B).
The product reservation module 140 may use the date and time when the product “SKU1” will be available for purchase to generate a default countdown clock 214 (see
In block 218 (see
In block 224 (see
Optionally, after the product reservation module 140 receives the customer submission, the product reservation module 140 may send product information related to the product “SKU1” to the customer application 152. The customer application 152 may display the product information on a product page 228 (see
Referring to
Alternatively, referring to
Optionally, referring to
After the customer 112A has provided the information necessary to request the reservation, the product reservation module 140 may send a confirmation to the customer application 152 indicating that the request has been received and the product “SKU1” has been added to the wish list 226 associated with the customer 112A. Referring to
Referring to
Optionally, in block 224 (see
Referring to
By way of a non-limiting example, the status may include “won,” “waitlisted,” and “lost.” The status “won” indicates that the customer 112A has the opportunity to reserve the product “SKU1.” The status “waitlisted” indicates that the customer 112A might have the opportunity to reserve the product “SKU1” if enough other customers who were assigned the status “won” decide not to reserve or purchase the product “SKU1.” The status “lost” indicates that the customer 112A will not be given the opportunity to reserve the product “SKU1.” Thus, the product reservation module 140 determines which of the customers 112A-112C will ultimately have chance of purchasing the product “SKU1.” For example, if the customers 112A-112C include 5000 customers who have each added the product “SKU1” for the store location 160A to their wish lists but the store location 160A has only 500 units of the product “SKU1” available, the ASA 144 decides which of the 5000 customers are provided the opportunity to purchase the product “SKU1.”
The product reservation module 140 performs block 250 (see
As mentioned above, the ASA 144 may select winning customers randomly from those customers whose personal countdown clocks have reached zero. Alternatively, the ASA 144 may decide which of the customers 112A-112C whose personal countdown clocks have reached zero is to be assigned the status “won” based on several factors. By way of non-limiting examples, these factors may include loyalty status of each of the customers 112A-112C, number of in-store visits (as measured by the customer application 152) made by each of the customers 112A-112C, purchase history of each of the customers 112A-112C, number of times each of the customers 112A-112C failed to pick up a product after confirming that the customer would pick up the product, and the like. The ASA 144 may be designed to be extensible and take inputs from recursive analysis (e.g., what status has the customer 112A been assigned in the past) as well as machine learning outputs.
In block 255 (see
Referring to
If the status assigned to the customer 112A is “lost,” the customer 112A has not been awarded the opportunity to reserve the product “SKU1” for purchase. When this occurs, the method 200 (see
If the status assigned to the customer 112A is “won,” the customer 112A has been awarded the opportunity to reserve the product “SKU1” for purchase. In block 260 (see
In decision block 265 (see
When the decision in decision block 265 (see
Referring to
An economic transaction may or may not be required to secure the actual reservation. For example, the customer 112A may purchase the product “SKU1” using the customer application 152. Alternatively, the customer 112A may purchase the product “SKU1” at the selected store location when the customer 112A picks up the instance of the product “SKU1” assigned to the customer 112A.
To pick up the product “SKU1” (e.g., at the store location 160A), the customer 112A and/or the customer computing device 110A may be required to supply validation information to the product reservation module 140 (e.g., within a predetermined amount of time following confirmation). After the product reservation module 140 receives the validation information (e.g., the store location code), the product reservation module 140 determines whether the validation information satisfies validation criteria. The validation criteria may be used to validate the user and/or the customer computing device 110A. Non-limiting examples of the validation information may include one or more of the following:
-
- 1. An indication of proximity to the proximity beacon 172, which may be implemented as a Bluetooth enabled Beacon, an AKA Beacon, an iBeacon, or a Bluetooth Low Energy (“BLE”) device;
- 2. A physical location of the customer computing device 110A (e.g., at the store location 160A), which may be identified (e.g., a latitude and a longitude) by a location module 488 (see
FIG. 11 ), such as a conventional geolocation or Global Positioning System (“GPS”) module, of the customer computing device 110A; - 3. An in-store unlock code or pin (e.g., provided manually by an employee, such as a store associate, of the merchant 122A);
- 4. One or more commonly used identifiers, such as a Unique Device Identifier (“UDID”), a Universally Unique Identifier (“UUID”), an Android DeviceID, one or more cookies, and any other identifier defined by the product reservation computing system 130;
- 5. A digital user authentication, which may include authenticating a user name and password, authenticating a biometric signature, and/or other commonly used authentication models or methods;
- 6. Physical user authentication, which may include an indication that an employee of the merchant 122A has authenticated a government issued identification presented by the customer 112A.
For example, the validation criteria may include evidence that the customer 112A is physically at the store location 160A. The product reservation module 140 may determine this validation criteria is satisfied when the product reservation module 140 receives an indication (e.g., the store location code) from the customer computing device 110A that the customer computing device 110A has detected (e.g., using the optional reader application 154) the proximity signal 182 (see
In decision block 276 (see
When the decision in decision block 276 (see
When the decision in decision block 276 (see
Referring to
Alternatively and/or additionally, the code 286 (see
Optionally, the customer 112A may inform the customer application 152 (e.g., click a link or a button 288 (see
Optionally, the merchant 122A and/or the merchant application 150 inform the product reservation module 140 that the customer 112A has picked up the product “SKU1.”
Referring to
Referring to
When the decision in decision block 290 is “YES,” the product reservation module 140 (see
When the decision in decision block 290 is “NO,” in block 295, the launch of the product “SKU1” has ended. For example, in block 295, the instances of the product “SKU1” may have sold out. Optionally, the status of the customer 112A (see
The mobile communication device 400 also contains a memory 420. The memory 420 may store instructions and data to control operation of the CPU 410. The memory 420 may include random access memory, ready-only memory, programmable memory, flash memory, and the like. The mobile communication device 400 is not limited by any specific form of hardware used to implement the memory 420. The memory 420 may also be integrally formed in whole or in part with the CPU 410.
The mobile communication device 400 also includes conventional components, such as the display device 430 and one or more user input devices 440 (e.g., buttons, a keypad, a keyboard, and the like). These are conventional components that operate in a known manner and need not be described in greater detail. The display device 430 may be implemented as a touch display or touchscreen configured to receive user input (e.g., selections from the list 222, a selection of the store option 230A, selection of the product options 230B and 230C, selections from the list 231, selection of the button 238, selection of the item(s) 248, selection of the confirm button 263 or the decline button 264, selection of the button 288, and the like). By way of non-limiting examples, the display device 430 is operable to display the screens and pages (e.g., the product launch page 220, the product page 228, the store selection page 232, the head start page 246, the countdown page 240, a confirmation page 262, and the product pick up page 275) depicted in
The memory 420 stores computer executable instructions that when executed by the CPU 410 cause the CPU 410 to generate the screens and interfaces described above and displayed by the display device 430. Referring to
The mobile communication device 400 also includes a network transmitter 450 such as may be used by the mobile communication device 400 for normal network wireless communication with the network(s) 134 (see
While not illustrated in
Referring to
The various components illustrated in
The memory 420 may store instructions executable by the CPU 410. The instructions may implement portions of the method 200 illustrated in
Moreover, those of ordinary skill in the art will appreciate that implementations may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Implementations may also be practiced in distributed computing environments (e.g., cloud computing platforms) where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
The exemplary hardware and operating environment of
The computing device 12 includes a system memory 22, the processing unit 21, and a system bus 23 that operatively couples various system components, including the system memory 22, to the processing unit 21. There may be only one or there may be more than one processing unit 21, such that the processor of computing device 12 includes a single central-processing unit (“CPU”), or a plurality of processing units, commonly referred to as a parallel processing environment. When multiple processing units are used, the processing units may be heterogeneous. By way of a non-limiting example, such a heterogeneous processing environment may include a conventional CPU, a conventional graphics processing unit (“GPU”), a floating-point unit (“FPU”), combinations thereof, and the like.
The computing device 12 may be a conventional computer, a distributed computer, or any other type of computer.
The system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory 22 may also be referred to as simply the memory, and includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements within the computing device 12, such as during start-up, is stored in ROM 24. The computing device 12 further includes a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM, DVD, or other optical media.
The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical disk drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules, and other data for the computing device 12. It should be appreciated by those of ordinary skill in the art that any type of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices (“SSD”), USB drives, digital video disks, Bernoulli cartridges, random access memories (“RAMs”), read only memories (“ROMs”), and the like, may be used in the exemplary operating environment. As is apparent to those of ordinary skill in the art, the hard disk drive 27 and other forms of computer-readable media (e.g., the removable magnetic disk 29, the removable optical disk 31, flash memory cards, SSD, USB drives, and the like) accessible by the processing unit 21 may be considered components of the system memory 22.
A number of program modules may be stored on the hard disk drive 27, magnetic disk 29, optical disk 31, ROM 24, or RAM 25, including the operating system 35, one or more application programs 36, other program modules 37, and program data 38. A user may enter commands and information into the computing device 12 through input devices such as a keyboard 40 and pointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, touch sensitive devices (e.g., a stylus or touch pad), video camera, depth camera, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus 23, but may be connected by other interfaces, such as a parallel port, game port, a universal serial bus (USB), or a wireless interface (e.g., a Bluetooth interface). A monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor, computers typically include other peripheral output devices (not shown), such as speakers, printers, and haptic devices that provide tactile and/or other types of physical feedback (e.g., a force feedback game controller).
The input devices described above are operable to receive user input and selections. Together the input and display devices may be described as providing a user interface.
The computing device 12 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 49. These logical connections are achieved by a communication device coupled to or a part of the computing device 12 (as the local computer). Implementations are not limited to a particular type of communications device. The remote computer 49 may be another computer, a server, a router, a network PC, a client, a memory storage device, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computing device 12. The remote computer 49 may be connected to a memory storage device 50. The logical connections depicted in
Those of ordinary skill in the art will appreciate that a LAN may be connected to a WAN via a modem using a carrier signal over a telephone network, cable network, cellular network, or power lines. Such a modem may be connected to the computing device 12 by a network interface (e.g., a serial or other type of port). Further, many laptop computers may connect to a network via a cellular data modem.
When used in a LAN-networking environment, the computing device 12 is connected to the local area network 51 through a network interface or adapter 53, which is one type of communications device. When used in a WAN-networking environment, the computing device 12 typically includes a modem 54, a type of communications device, or any other type of communications device for establishing communications over the wide area network 52, such as the Internet. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a networked environment, program modules depicted relative to the personal computing device 12, or portions thereof, may be stored in the remote computer 49 and/or the remote memory storage device 50. It is appreciated that the network connections shown are exemplary and other means of and communications devices for establishing a communications link between the computers may be used.
The computing device 12 and related components have been presented herein by way of particular example and also by abstraction in order to facilitate a high-level view of the concepts disclosed. The actual technical design and implementation may vary based on particular implementation while maintaining the overall nature of the concepts disclosed.
In some embodiments, the system memory 22 stores computer executable instructions that when executed by one or more processors cause the one or more processors to perform all or portions of one or more of the methods (including the method 200 illustrated in
The foregoing described embodiments depict different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.
While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this invention and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this invention. Furthermore, it is to be understood that the invention is solely defined by the appended claims. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations).
Accordingly, the invention is not limited except as by the appended claims.
Claims
1. (canceled)
2. A method comprising:
- receiving, by a product reservation computing system, requests to purchase a product from a merchant when the product is not yet available for purchase;
- determining that the product is available for reservation;
- processing the requests to purchase the product using an assignment script algorithm to assign reservations to select customers that meet a set of criteria to purchase the product from the merchant;
- transmitting a notification of an assigned reservation associated with a customer;
- receiving a confirmation associated with the customer of the select customers, the confirmation including validation information for the customer;
- processing the validation information to confirm that the customer is authorized to purchase the product from the merchant based on the set of criteria;
- generating a unique code associated with the product and the customer; and
- transmitting the unique code, wherein when the unique code is received by a product reservation module of a device associated with the customer, the unique code facilitates purchase of the product.
3. The method of claim 2, wherein transmission of the unique code is triggered by a personal countdown dock associated with the customer.
4. The method of claim 2, wherein when the unique code is displayed by the device associated with the customer, a point of sale device associated with the merchant uses the unique code to verify that the customer is authorized to purchase the product.
5. The method of claim 2, wherein the unique code is a two dimensional barcode.
6. The method of claim 2, wherein when the unique code is received by a merchant system, the merchant system matches the unique code to a communication associated with the customer to confirm that the customer is authorized to purchase the product.
7. The method of claim 2, wherein assignment of the reservations is associated with a default countdown clock indicating a default time when the product will be available for purchase.
8. The method of claim 2, wherein the notification of the reservation for the customer is associated with a default countdown clock and a personal countdown clock that indicates a time when the product will be available for purchase by the customer.
9. A product reservation computing system comprising:
- one or more processors; and
- one or more non-transitory machine-readable storage media containing instructions that, when executed on the one or more processors, cause the one or more processors to perform operations including:
- receiving, by the product reservation computing system, requests to purchase a product from a merchant when the product is not yet available for purchase;
- determining that the product is available for reservation;
- processing the requests to purchase the product using an assignment script algorithm to assign reservations to select customers that meet a set of criteria to purchase the product from the merchant;
- transmitting a notification of an assigned reservation associated with a customer;
- receiving a confirmation associated with the customer of the select customers, the confirmation including validation information for the customer;
- processing the validation information to confirm that the customer is authorized to purchase the product from the merchant based on the set of criteria;
- generating a unique code associated with the product and the customer; and
- transmitting the unique code, wherein when the unique code is received by a product reservation module of a device associated with the customer, the unique code facilitates purchase of the product.
10. The system of claim 9, wherein transmission of the unique code is triggered by a personal countdown clock associated with the customer.
11. The system of claim 9, wherein when the unique code is displayed by the device associated with the customer, a point of sale device associated with the merchant uses the unique code to verify that the customer is authorized to purchase the product.
12. The system of claim 9, wherein the unique code is a two dimensional barcode.
13. The system of claim 9, wherein when the unique code is received by a merchant system, the merchant system matches the unique code to communication associated with the customer to confirm that the customer is authorized to purchase the product.
14. The system of claim 9, wherein assignment of the reservations is associated with a default countdown clock indicating a default time when the product will be available for purchase.
15. The system of claim 9, wherein the notification of the reservation for the customer is associated with a default countdown clock and a personal countdown clock that indicates a time when the product will be available for purchase by the customer.
16. A non-transitory computer readable medium comprising instructions that, when executed by one or more processors of a device, cause the device to perform operations comprising:
- receiving requests to purchase a product from a merchant when the product is not yet available for purchase;
- determining that the product is available for reservation;
- processing the requests to purchase the product using an assignment script algorithm to assign reservations to select customers that meet a set of criteria to purchase the product from the merchant;
- transmitting a notification of an assigned reservation associated with a customer;
- receiving a confirmation associated with the customer of the select customers, the confirmation including validation information for the customer;
- processing the validation information to confirm that the customer is authorized to purchase the product from the merchant based on the set of criteria;
- generating a unique code associated with the product and the customer; and
- transmitting the unique code, wherein when the unique code is received by a product reservation module of a device associated with the customer, the unique code facilitates purchase of the product.
17. The non-transitory computer readable medium of claim 16, wherein transmission of the unique code is triggered by a personal countdown clock associated with the customer.
18. The non-transitory computer readable medium of claim 16, wherein when the unique code is displayed by the device associated with the customer, a point of sale device associated with the merchant uses the unique code to verify that the customer is authorized to purchase the product.
19. The non-transitory computer readable medium of claim 16, wherein the unique code is a two dimensional barcode.
20. The non-transitory computer readable medium of claim 16, wherein when the unique code is received by a merchant system, the merchant system matches the unique code to communication associated with the customer to confirm that the customer is authorized to purchase the product.
21. The non-transitory computer readable medium of claim 16, wherein assignment of the reservations is associated with a default countdown clock indicating a default time when the product will be available for purchase.
Type: Application
Filed: Sep 8, 2020
Publication Date: Feb 25, 2021
Applicant: Synchrony Bank (Stamford, CT)
Inventors: Alex Muller (Stamford, CT), Yan Makher (Stamford, CT), Thomas Kulesza (Stamford, CT), Kimberly Dorn (Stamford, CT), Travis Watson (Stamford, CT), Brad DeWitt (Stamford, CT)
Application Number: 17/014,635