Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

How do ShipmentRequests, OriginReleases, Distributions, and Meter Tickets Correlate?

Understanding Batches, Shipment Requests, Origin Releases, Distributions, and Meter Tickets

A batch is a planned shipment of fuel moving through the pipeline system. It begins when product enters from a refinery, terminal, or storage location and is tracked until it reaches the designated destination or customer market.

In the shipping process a Batch, which is made up of Shipment Requests, Origin Releases, Distributions, and Meter Tickets represent different points in the product movement lifecycle.

  • Batch:  serves as the overall container for the planned movement. It brings the Origin Release, Shipment Request, and Distribution together in one record.
  • Origin Release: Brings product into the pipeline system.
  • Shipment Request: Directs the product’s movement through the system.
  • Distribution: Assigns the shipment volume to the appropriate inventory owner.
  • Meter Ticket: Records the actual measured volume moved.
API Object Main Question Answered Business Purpose
Shipment Request What was requested? Captures the shipper’s intended movement
Origin Release What was approved for release? Confirms product can move from the origin
Distribution What was scheduled or allocated? Shows planned movement after scheduling
Pipeline Meter Ticket What actually moved? Confirms measured pipeline activity

Correlating Transactions

Origin Releases, Shipment Requests, and Pipeline Meter Tickets can be linked using the Origin Release ID.

Get Origin Releases Endpoint

"id": 12345,

Get Shipment Requests Endpoint

"originRelease": {
"id": 12345,

Get Pipeline Meter Tickets Endpoint

"originReleaseId": 12345,

Get Distributions

Shipment Requests and Distributions can be linked using the Shipment Request ID when product ownership remains with the same company.

When ownership changes through a consignment, sale, or transfer, the Distribution becomes a separate ownership record and no common ID is maintained.

    Correlation Rules

    • Same owner: Use shipmentRequestId to correlate Shipment Requests and Distributions.
    • Ownership change: No common ID exists between the Shipment Request and Distribution.
    • Origin Release relationship: Use the Origin Release ID to correlate the Origin Release, Shipment Request, and Pipeline Meter Ticket where those fields are present.

    Distributions are best viewed as part of the batch lifecycle rather than a direct one-to-one match with the original Shipment Request.