Freight transaction infrastructure

Freight contracts shouldn’t break when the shipment does.

Pirex Blockchain Logistics is developing transaction infrastructure that connects freight contracting, verified shipment events, exception management, facility coordination, and settlement through one connected workflow.

Pirex Blockchain Logistics is currently in development and pilot validation.
The connected freight transactionPlatform vision

A changed shipment should not mean a disconnected transaction.

When a load is delayed, a carrier breaks down, or a facility is needed, the original agreement is only part of the story. Updates, documents, new terms, and payment decisions can become scattered across systems.

See the proposed workflow
01

Keep the agreement in view.

Connect original terms and approved changes to the same transaction.

02

Carry the history forward.

Link operational events, documents, and exception decisions.

03

Coordinate what comes next.

Support reassignment, facility services, verification, and settlement conditions.

Proposed capabilities under development. Available today: explore the workflow and request a pilot discussion.
The platform / In development

One connected workflow.
From agreement to settlement.

Six planned capabilities connect the commercial and operational decisions behind a freight transaction.

01 / PLANNED CAPABILITY

Contracting

Create structured freight agreements containing shipment requirements, commercial terms, milestones, accessorials, exception rules, and settlement conditions.

02 / PLANNED CAPABILITY

Matching & Coordination

Connect transaction requirements with qualified carriers and participating logistics resources.

03 / PLANNED CAPABILITY

Shipment Events

Organize verified operational events, documentation, milestones, and relevant telematics signals into a transaction timeline.

04 / PLANNED CAPABILITY

Exception Management

Handle breakdowns, delays, rejected loads, facility requirements, reassignment, re-contracting, and other operational exceptions without losing the transaction history.

05 / PLANNED CAPABILITY

Facility Coordination

Allow participating facilities to become part of the transaction workflow when parking, temporary storage, staging, trailer handling, or other approved logistics services are required.

06 / PLANNED CAPABILITY

Settlement

Demonstrate how predefined transaction conditions could support settlement instructions after required completion events have been verified.

How it works / Proposed workflow

Built around what actually happens.

The intended workflow keeps requirements, execution, and changes tied to a shared transaction history.

  1. 01

    Create the Transaction

    The broker or shipper defines the freight requirements, commercial terms, milestones, exception rules, and settlement conditions.

  2. 02

    Coordinate Execution

    The transaction connects the appropriate carrier, shipment events, documentation, and participating logistics resources.

  3. 03

    Respond to What Happens

    When normal execution changes, the workflow can support exceptions, reassignment, facility coordination, re-contracting, and updated transaction conditions.

  4. 04

    Verify Completion

    Required shipment events and documentation are checked against the transaction conditions.

  5. 05

    Complete Settlement

    The system demonstrates how verified completion could initiate predefined settlement instructions.

Prototype / Coming soon

See the Pirex Platform in Action

Explore the workflow before it goes live.

The Pirex Blockchain Logistics prototype demonstrates how a freight transaction can move through a connected digital workflow—from contract creation and carrier coordination to shipment events, exception management, facility coordination, verification, and settlement.

The journey below outlines the planned prototype. An interactive environment is not yet available.

  1. 01

    Create the Contract

    Enter shipment requirements, commercial terms, milestones, accessorials, exception rules, and settlement conditions.

  2. 02

    Match & Confirm

    Review qualified carrier matches and move an accepted transaction into the active workflow.

  3. 03

    Monitor the Shipment

    Follow operational milestones, documents, shipment events, and relevant location or telematics signals through a unified transaction timeline.

  4. 04

    Manage an Exception

    Demonstrate what happens when a breakdown, delay, facility issue, rejected load, or other disruption changes the original transaction.

  5. 05

    Re-Contract or Reassign

    Show how affected portions of the transaction could be updated or reassigned while preserving the event history.

  6. 06

    Verify Completion

    Review delivery events and required documentation against the transaction conditions.

  7. 07

    Settlement

    Demonstrate how verified completion could initiate predetermined settlement instructions, including approved split-payment arrangements.

Built to Test the Model

The prototype is designed for workflow validation and pilot discussions with brokers, carriers, facilities, and enterprise logistics organizations.

Request a Pilot

Prototype environment only. Features shown are under development and may change. Pirex Blockchain Logistics is not currently providing live freight brokerage, transportation, custody, or payment services through this prototype.

Who it serves

For the organizations behind every freight transaction.

Planned workflows for each participant, with access and responsibilities appropriate to its role.

Brokers & Shippers

Structured contracting, transaction visibility, exception handling, carrier coordination, and settlement workflows.

Carriers & Fleets

Clear transaction requirements, documentation workflows, operational updates, exception handling, and settlement visibility.

Facility Partners

Participate in freight transactions when parking, staging, storage, trailer handling, or other approved services are required.

Enterprise Logistics Organizations

Infrastructure for organizations that need more structured coordination across freight transactions, operational events, counterparties, and settlement.

In V1, planned driver interactions focus on mobile-friendly web interfaces or secure SMS links for confirmations, documents, and exception responses.

Facility partners / Planned capability

When the shipment needs a place to go.

Participating logistics facilities could join the transaction workflow when a shipment needs an approved service.

01

Secure truck or trailer parking

A location option when a shipment is interrupted or a trailer needs to wait.

02

Temporary freight storage

A storage requirement connected to the affected transaction.

03

Staging

A planned stop or holding point coordinated with onward movement.

04

Trailer handling

Agreed handling services with documented responsibilities.

05

Recovery support

Facility support coordinated with a shipment exception.

06

Other approved logistics services

Additional services subject to provider availability and agreed transaction terms.

Facilities would be independently operated participants. Pirex Blockchain Logistics does not represent that it owns these facilities. Services would depend on partner qualification, availability, and separate agreements.

Discuss Facility Participation
Security & Compliance

Controls designed around the transaction.

These principles describe the intended architecture. They are planned controls, not claims of operational capabilities, certifications, security audits, or regulatory approval.

Role-based access

Planned access based on organizational roles and transaction responsibilities.

Multi-factor authentication

Intended additional verification for access to platform accounts.

Encrypted document storage

Designed to protect documents in transit and at rest.

Audit logs

Planned records of key access, changes, and administrative actions.

Identity & business verification

Intended integrations to support checks on participating people and organizations.

Permission controls

Designed to limit who can view documents, approve changes, or take transaction actions.

Transaction event records

Intended traceability for milestones, supporting evidence, and decisions.

Secure API architecture

Planned authentication, authorization, input validation, and controlled system integrations.

Technology approach

Logistics first.
Technology where it adds value.

A conventional web application and database are intended to handle most operational data. A limited on-chain layer could support verifiable transaction events, contract conditions, or settlement logic where it offers a specific operational advantage.

Telematics and external systems could provide operational signals. Planned integrations may support TMS data, identity and business verification, payments, and other logistics systems.

A record is not a physical-world guarantee. Authorized review, reliable evidence, and qualified service providers remain important to the intended workflow.

Pilot validation

Help Shape the Next Generation of Freight Transaction Infrastructure

Pirex Blockchain Logistics is seeking qualified logistics organizations interested in evaluating the proposed platform workflow and participating in pilot discussions.

Request a Pilot