IP Library Granted Patent US 12,555,064
Granted Patent B2
US 12,555,064 · App. 18/377,607 · Granted Feb 17, 2026

Technologies for retrieving and analyzing shipping data and rendering interfaces associated therewith

Inventors: Quintin C. Carlson (Chicago, ID); Michael B. Wey (Austin, TX); Andrew Dash (Berkeley, CA); Nanxin Zhao (Redwood City, CA)
Assignee: PROJECT44, LLC
G06Q10/0833
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,555,064
App. No.
18/377,607
Granted
Feb 17, 2026
Kind
B2
Abstract

Systems and methods for retrieving and analyzing shipping data and rendering interfaces associated therewith are disclosed herein. An example method includes receiving an indication of a reference key from a user computing device, and aggregating, by utilizing one or more application programming interfaces (APIs), a set of data entity information from one or more shipping service provider devices. The set of data entity information may correspond to the reference key and include real-time data from each shipping service provider participating in logistics or transportation of an object from the set of data entity information along a transportation route. The example method may further include partitioning the data entity information into multiple workspace cards, and causing the user computing device to render a workspace graphical user interface (GUI) that includes at least one workspace card of the multiple workspace cards for access by a user of the user computing device.

Claims (80)

1 . A method for retrieving and analyzing shipping data and rendering interfaces associated therewith, the method comprising:

receiving, at one or more processors, an indication of a reference key from a user computing device;

aggregating, by the one or more processors utilizing one or more application programming interfaces (APIs) from a set of APIs, a set of data entity information from two or more shipping service provider devices associated with two or more different shipping service providers, the set of data entity information corresponding to the reference key and including real-time data from each shipping service provider participating in logistics or transportation of an object included in the set of data entity information along a transportation route;

partitioning, by the one or more processors executing a workspace application, the set of data entity information into multiple workspace cards, each workspace card providing a different portion of the set of data entity information;

combining, by the one or more processors, at least two of the multiple workspace cards into a combined workspace (GUI), the at least two workspace cards being associated with a first shipping service provider and a second shipping service provider of the two or more shipping service providers;

determining, by the one or more processors based on a size of the multiple workspace cards, to transmit the multiple workspace cards to the user computing device in a single signal or a plurality of signals;

transmitting, by the one or more processors, the multiple workspace cards to the user computing device in the single signal or the plurality of signals; and

causing, by the one or more processors, the user computing device to render the combined workspace GUI for access by a user of the user computing device in the workspace application, wherein the combined workspace GUI includes: (i) an overview card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider, (ii) a map card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider, and (iii) a route card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider.

2 . The method of claim 1 , further comprising:

generating, by the one or more processors, a predicted value for one or more entries included in the at least two workspace cards; and

causing, by the one or more processors, the user computing device to render a predicted value graphical indication within the at least two workspace cards of the workspace GUI.

3 . The method of claim 1 , further comprising:

determining, by the one or more processors, that a first entry in the set of data entity information indicates a delay has taken place along the transportation route;

generating, by the one or more processors, a graphical indication of the delay for display in a map card of the multiple workspace cards; and

causing, by the one or more processors, the user computing device to render at least the map card of the multiple workspace cards as part of the workspace GUI.

4 . The method of claim 3 , further comprising:

analyzing, by the one or more processors, the first entry to determine a source of the delay;

responsive to determining the source of the delay, determining, by the one or more processors, a first shipping service provider participating in the logistics or the transportation of the object that is responsible for the source of the delay;

retrieving, by the one or more processors, contact information corresponding to the first shipping service provider; and

causing, by the one or more processors, the user computing device to render the contact information as part of the workspace GUI, wherein a user interacting with the contact information causes the user computing device to initiate contact between the user computing device and a first shipping service provider device of the first shipping service provider.

5 . The method of claim 1 , wherein

the set of data entity information includes at least one of: (i) an order data entity, (ii) a container data entity, (iii) an inventory data entity, (iv) an asset data entity, (v) a location data entity, or (vi) a people data entity; and

the workspace cards of the workspace GUI include at least one of (i) an overview card, (ii) a route card, (iii) a map card, (iv) an activity feed card, (v) an order health information card, (vi) a nested shipments card, (vii) an inventory onboard card, or (viii) a route plan card.

6 . A system for retrieving and analyzing shipping data and rendering interfaces associated therewith, the system comprising:

one or more processors; and

one or more memories communicatively coupled with a user interface and the one or more processors, the one or more memories storing computer executable instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

receive an indication of a reference key from a user computing device,

aggregate, by utilizing one or more application programming interfaces (APIs), a set of data entity information from two or more shipping service provider devices associated with two or more different shipping service providers, the set of data entity information corresponding to the reference key and including real-time data from each shipping service provider participating in logistics or transportation of an object included in the set of data entity information along a transportation route,

partition the set of data entity information into multiple workspace cards, each workspace card providing a different portion of the set of data entity information,

combine at least two of the multiple workspace cards into a combined workspace (GUI), the at least two workspace cards being associated with a first shipping service provider and a second shipping service provider of the two or more shipping service providers,

determine, based on a size of the multiple workspace cards, to transmit the multiple workspace cards to the user computing device in a single signal or a plurality of signals,

transmit the multiple workspace cards to the user computing device in the single signal or the plurality of signals, and

cause the user computing device to render the combined workspace GUI for access by a user of the user computing device in the workspace application, wherein the combined workspace GUI includes: (i) an overview card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider, (ii) a map card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider, and (iii) a route card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider.

7 . The system of claim 6 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

generate a predicted value for one or more entries included in the at least two workspace cards; and

cause the user computing device to render a predicted value graphical indication within the at least two workspace cards of the workspace GUI.

8 . The system of claim 6 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

determine that a first entry in the set of data entity information indicates a delay has taken place along the transportation route;

generate a graphical indication of the delay for display in a map card of the multiple workspace cards; and

cause the user computing device to render at least the map card of the multiple workspace cards as part of the workspace GUI.

9 . The system of claim 8 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

analyze the first entry to determine a source of the delay;

responsive to determining the source of the delay, determine a first shipping service provider participating in the logistics or the transportation of the object that is responsible for the source of the delay;

retrieve contact information corresponding to the first shipping service provider; and

cause the user computing device to render the contact information as part of the workspace GUI, wherein a user interacting with the contact information causes the user computing device to initiate contact between the user computing device and a first shipping service provider device of the first shipping service provider.

10 . The system of claim 6 , wherein

the set of data entity information includes at least one of: (i) an order data entity, (ii) a container data entity, (iii) an inventory data entity, (iv) an asset data entity, (v) a location data entity, or (vi) a people data entity; and

the workspace cards of the workspace GUI include at least one of (i) an overview card, (ii) a route card, (iii) a map card, (iv) an activity feed card, (v) an order health information card, (vi) a nested shipments card, (vii) an inventory onboard card, or (viii) a route plan card.

11 . A tangible machine-readable medium comprising instructions that, when executed, cause a machine to at least:

receive an indication of a reference key from a user computing device;

aggregate, by utilizing one or more application programming interfaces (APIs), a set of data entity information from two or more shipping service provider devices associated with two or more different shipping service providers, the set of data entity information corresponding to the reference key and including real-time data from each shipping service provider participating in logistics or transportation of an object included in the set of data entity information along a transportation route;

partition the set of data entity information into multiple workspace cards, each workspace card providing a different portion of the set of data entity information;

combine at least two of the multiple workspace cards into a combined workspace (GUI), the at least two workspace cards being associated with a first shipping service provider and a second shipping service provider of the two or more shipping service providers;

determine, based on a size of the multiple workspace cards, to transmit the multiple workspace cards to the user computing device in a single signal or a plurality of signals;

transmit the multiple workspace cards to the user computing device in the single signal or the plurality of signals; and

cause the user computing device to render the combined workspace GUI for access by a user of the user computing device in the workspace application, wherein the combined workspace GUI includes: (i) an overview card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider, (ii) a map card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider, and (iii) a route card corresponding to the set of data entity information associated with the first shipping service provider and the second shipping service provider.

12 . The tangible machine-readable medium of claim 11 , wherein the instructions, when executed, further cause the machine to:

generate a predicted value for one or more entries included in the at least two workspace cards; and

cause the user computing device to render a predicted value graphical indication within the at least two workspace cards of the workspace GUI.

13 . The tangible machine-readable medium of claim 11 , wherein the instructions, when executed, further cause the machine to:

determine that a first entry in the set of data entity information indicates a delay has taken place along the transportation route;

generate a graphical indication of the delay for display in a map card of the multiple workspace cards; and

cause the user computing device to render at least the map card of the multiple workspace cards as part of the workspace GUI.

14 . The tangible machine-readable medium of claim 13 , wherein the instructions, when executed, further cause the machine to:

analyze the first entry to determine a source of the delay;

responsive to determining the source of the delay, determine a first shipping service provider participating in the logistics or the transportation of the object that is responsible for the source of the delay;

retrieve contact information corresponding to the first shipping service provider; and

cause the user computing device to render the contact information as part of the workspace GUI, wherein a user interacting with the contact information causes the user computing device to initiate contact between the user computing device and a first shipping service provider device of the first shipping service provider.

15 . The tangible machine-readable medium of claim 11 , wherein

the set of data entity information includes at least one of: (i) an order data entity, (ii) a container data entity, (iii) an inventory data entity, (iv) an asset data entity, (v) a location data entity, or (vi) a people data entity; and

the workspace cards of the workspace GUI include at least one of (i) an overview card, (ii) a route card, (iii) a map card, (iv) an activity feed card, (v) an order health information card, (vi) a nested shipments card, (vii) an inventory onboard card, or (viii) a route plan card.

16 . The method of claim 1 , further comprising:

determining, by the one or more processors based on the indication, that (i) the set of data entity information is contained at least on a first shipping service provider device of the two or more shipping service provider devices and a second shipping service provider device of the two or more shipping service provider devices, (ii) communicating with the first shipping service provider device is implemented through a first API of the set of APIs, and (ii communicating with the second shipping service provider device is implemented through a second API of the set of APIs; and

aggregating, by the one or more processors, the set of data entity information at least partially from (i) the first shipping service provider device via the first API and (ii) the second shipping service provider device via the second API.

17 . The system of claim 6 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

determine, based on the indication, that (i) the set of data entity information is contained at least on a first shipping service provider device of the two or more shipping service provider devices and a second shipping service provider device of the two or more shipping service provider devices, (ii) communicating with the first shipping service provider device is implemented through a first API of the set of APIs, and (iii) communicating with the second shipping service provider device is implemented through a second API of the set of APIs; and

aggregate the set of data entity information at least partially from (i) the first shipping service provider device via the first API and (ii) the second shipping service provider device via the second API.

18 . The tangible machine-readable medium of claim 11 , wherein the instructions, when executed, further cause the machine to:

determine, based on the indication, that (i) the set of data entity information is contained at least on a first shipping service provider device of the two or more shipping service provider devices and a second shipping service provider device of the two or more shipping service provider devices, (ii) communicating with the first shipping service provider device is implemented through a first API of the set of APIs, and (iii) communicating with the second shipping service provider device is implemented through a second API of the set of APIs; and

aggregate the set of data entity information at least partially from (i) the first shipping service provider device via the first API and (ii) the second shipping service provider device via the second API.

Assignments (2)
SECURITY INTEREST Recorded Jul 16, 2026
From: PROJECT44, LLC
To: SIXTH STREET SPECIALTY LENDING, INC., AS AGENT
Reel/Frame 075293/0078 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 23, 2023
From: CARLSON, QUINTIN C.; WEY, MICHAEL B.; DASH, ANDREW; ZHAO, NANXIN
To: PROJECT44, LLC
Reel/Frame 065305/0164 →
Continuity (2)
Provisional Application 63378676 · Oct 6, 2022
Related Publication 20240119403A1 · Apr 11, 2024
References Cited (11)
US 8214747B1 · Yankovich · 2012 [cited by examiner]
US 20050197892A1 · Bilibin · 2005 [cited by examiner]
US 20150015407A1 · Markwitz · 2015 [cited by examiner]
US 20150324741A1 · Parry · 2015 [cited by examiner]
US 20170053234A1 · Lozito · 2017 [cited by examiner]
US 20200265379A1 · Walker · 2020 [cited by examiner]
US 20210056504A1 · Scott · 2021 [cited by examiner]
US 20210081882A1 · Franklin · 2021 [cited by examiner]
US 20220207449A1 · Cooks · 2022 [cited by examiner]
US 20220292584A1 · Kumar · 2022 [cited by examiner]
Google Workspace for Developers “Cards” last updated Feb. 12, 2021 (available at: https://web.archive.org/web/20210327041748/https://developers.google.com/workspace/add-ons/concepts/cards) (Year: 2021). [cited by examiner]