# US 2025/0225568 A1 · Context for fulfillment transactions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0225568 A1
- Document ID: US20250225568A1
- Status: Published application
- Kind: A1
- Application number: 18/404,012
- Filed: 2024-01-04
- Published: 2025-07-10
- Earliest claimed: 2024-01-04
- Assignees: Motorola Mobility LLC
- Applicants: Motorola Mobility LLC
- Inventors: Krishnan Raghavan; Rahul Sahadevan; Nakul Patel
- Web page: https://patentgrep.com/patent/US20250225568A1

## CPC

- G06Q 30/0635: {replenishment orders; recurring orders}
- G06Q 30/0641: {utilising user interfaces specially adapted for shopping}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Techniques for context for fulfillment transactions are described and are implementable to enable context information for fulfillment transactions to be stored, presented, and filtered.

## Claims

### Claim 1

A client device comprising:
at least one processor; and
one or more modules executable by the at least one processor to:
implement a fulfillment transaction via a fulfillment application;
present transaction context options that are each selectable to enable user input to specify transaction context for the fulfillment transaction;
receive user input to select at least one context option and to provide one or more context values for the at least one context option;
cause a transaction record for the fulfillment transaction to be stored including the one or more context values for the at least one context option; and
present a representation of the transaction record including the one or more context values for the at least one context option.

### Claim 2 (depends on 1)

The client device of claim 1, wherein the fulfillment transaction comprises a product purchase via the fulfillment application.

### Claim 3 (depends on 1)

The client device of claim 1, wherein the context options comprise one or more of a transaction purpose option, a recipient option, or a transaction notes option.

### Claim 4 (depends on 1)

The client device of claim 1, wherein the at least one context option comprises a purpose option, and wherein the one or more modules are executable by the at least one processor to present a purpose menu that includes multiple different selectable purpose options describing different selectable purposes for the fulfillment transaction, wherein the user input to provide the one or more context values comprises a user selection of at least one of the purpose options.

### Claim 5 (depends on 1)

The client device of claim 1, wherein the at least one context option comprises a recipient option, and wherein the one or more modules are executable by the at least one processor to present a recipient menu that includes multiple different selectable recipient identifiers, wherein the user input to provide the one or more context values comprises a user selection of at least one of the recipient identifiers.

### Claim 6 (depends on 1)

The client device of claim 1, wherein the at least one context option comprises a transaction notes option, and wherein the one or more modules are executable by the at least one processor to present a notes field, and wherein the user input to provide the one or more context values comprises user input to the notes field to specify transaction notes for the fulfillment transaction.

### Claim 7 (depends on 1)

The client device of claim 1, wherein the context options comprise two or more of a transaction purpose option, a recipient option, or a transaction notes option, and wherein the one or more modules are executable by the at least one processor to present the one or more context values in the representation of the transaction record as one or more context values for the one or more of the transaction purpose option, the recipient option, or the transaction notes option.

### Claim 8 (depends on 1)

The client device of claim 1, wherein the one or more modules are executable by the at least one processor to:
receive, via the fulfillment application, user input to select a filter control;
present one or more fulfillment context filter options;
receive user selection of a fulfillment context filter option of the one or more filter options;
present filter values for the selected fulfillment context filter option;
receive user selection of one or more of the fulfillment context filter values; and
cause one or more filtered transaction records to be presented that correspond to the selected one or more fulfillment context filter values.

### Claim 9 (depends on 8)

The client device of claim 8, wherein the one or more modules are executable by the at least one processor to:
receive user input of a search term to a search field; and
cause a subset of the one or more filtered transaction records that match the search term to be presented.

### Claim 10 (depends on 1)

The client device of claim 1, wherein the one or more modules are executable by the at least one processor to:
present a contacts graphical user interface that includes contact details for a contact; and
present, as part of the contacts graphical user interface, a fulfillment history region that includes information describing one or more past fulfillment transactions associated with the contact.

### Claim 11 (depends on 10)

The client device of claim 10, wherein the one or more modules are executable by the at least one processor to:
present, as part of the contacts graphical user interface, a transaction control;
receive an indication of user selection of the transaction control; and
present a fulfillment graphical user interface to be presented that includes one or more fulfillment transaction recommendations that are filtered based at least in part on the contact.

### Claim 12

A system comprising:
at least one memory; and
at least one processor coupled to the at least one memory and configured to cause the system to:
implement, at a fulfillment service, a fulfillment transaction associated with a user account;
receive an indication of user input to select at least one context option and one or more context values for the at least one context option;
cause a transaction record for the fulfillment transaction to be stored including the one or more context values for the at least one context option;
detect a subsequent user interaction with the fulfillment service; and
transmit, to a client device associated with the user account, the transaction record including the one or more context values for the at least one context option.

### Claim 13 (depends on 12)

The system of claim 12, wherein the fulfillment transaction comprises a product purchase via the fulfillment service.

### Claim 14 (depends on 12)

The system of claim 12, wherein the at least one context option comprises a recipient option, and wherein the at least one processor is configured to cause the system to cause a recipient menu to be presented that includes multiple different selectable recipient identifiers, wherein the indication of the user input to comprises an indication of a user selection of at least one of the recipient identifiers.

### Claim 15 (depends on 12)

The system of claim 12, wherein the at least one context option comprises a transaction notes option, and wherein the at least one processor is configured to cause the system to cause a notes field to be presented, and wherein the indication of the user input comprises an indication of user input to the notes field to specify transaction notes for the fulfillment transaction.

### Claim 16 (depends on 12)

The system of claim 12, wherein the context options comprise two or more of a transaction purpose option, a recipient option, or a transaction notes option, and wherein the at least one processor is configured to cause the system to store the transaction record including the one or more context values for the one or more of the transaction purpose option, the recipient option, or the transaction notes option.

### Claim 17 (depends on 12)

The system of claim 12, wherein the at least one processor is configured to cause the system to:
receive an indication of user input to select a filter control;
cause one or more fulfillment context filter options associated with fulfillment context to be presented;
receive an indication of user selection of a fulfillment context filter option of the one or more fulfillment context filter options associated with fulfillment context;
cause filter values for the selected fulfillment context filter option associated with fulfillment context to be presented;
receive an indication of user selection of one or more of the values for the fulfillment context filter option associated with fulfillment context;
perform filtering of transaction records based at least in part on the selected one or more filter values to generate filtered transaction records; and
transmit the one or more filtered transaction records to a client device.

### Claim 18 (depends on 17)

The system of claim 17, wherein:
receive an indication of user input of a search term to a search field;
cause a search of the filtered transaction records using the search term to generate a subset of the one or more filtered transaction records that match the search term; and
transmit the subset of the one or more filtered transaction records to a client device.

### Claim 19

A method comprising:
implementing a fulfillment transaction via a fulfillment application;
presenting transaction context options that are each selectable to enable user input to specify transaction context for the fulfillment transaction;
receiving user input to select at least one context option and to provide one or more context values for the at least one context option;
causing a transaction record for the fulfillment transaction to be stored including the one or more context values for the at least one context option; and
presenting a representation of the transaction record including the one or more context values for the at least one context option.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
receiving an indication of user input to select a filter control associated with fulfillment context;
causing one or more fulfillment context filter options associated with fulfillment context to be presented;
receiving an indication of user selection of a fulfillment context filter option of the one or more fulfillment context filter options associated with fulfillment context;
causing filter values for the selected fulfillment context filter option associated with fulfillment context to be presented;
receiving an indication of user selection of one or more of the filter values;
performing filtering of transaction records based at least in part on the selected one or more filter values to generate filtered transaction records; and
transmitting the one or more filtered transaction records to a client device.
