Keep the agreement in view.
Connect original terms and approved changes to the same transaction.
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.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 workflowConnect original terms and approved changes to the same transaction.
Link operational events, documents, and exception decisions.
Support reassignment, facility services, verification, and settlement conditions.
Six planned capabilities connect the commercial and operational decisions behind a freight transaction.
Create structured freight agreements containing shipment requirements, commercial terms, milestones, accessorials, exception rules, and settlement conditions.
Connect transaction requirements with qualified carriers and participating logistics resources.
Organize verified operational events, documentation, milestones, and relevant telematics signals into a transaction timeline.
Handle breakdowns, delays, rejected loads, facility requirements, reassignment, re-contracting, and other operational exceptions without losing the transaction history.
Allow participating facilities to become part of the transaction workflow when parking, temporary storage, staging, trailer handling, or other approved logistics services are required.
Demonstrate how predefined transaction conditions could support settlement instructions after required completion events have been verified.
The intended workflow keeps requirements, execution, and changes tied to a shared transaction history.
The broker or shipper defines the freight requirements, commercial terms, milestones, exception rules, and settlement conditions.
The transaction connects the appropriate carrier, shipment events, documentation, and participating logistics resources.
When normal execution changes, the workflow can support exceptions, reassignment, facility coordination, re-contracting, and updated transaction conditions.
Required shipment events and documentation are checked against the transaction conditions.
The system demonstrates how verified completion could initiate predefined settlement instructions.
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.
Enter shipment requirements, commercial terms, milestones, accessorials, exception rules, and settlement conditions.
Review qualified carrier matches and move an accepted transaction into the active workflow.
Follow operational milestones, documents, shipment events, and relevant location or telematics signals through a unified transaction timeline.
Demonstrate what happens when a breakdown, delay, facility issue, rejected load, or other disruption changes the original transaction.
Show how affected portions of the transaction could be updated or reassigned while preserving the event history.
Review delivery events and required documentation against the transaction conditions.
Demonstrate how verified completion could initiate predetermined settlement instructions, including approved split-payment arrangements.
The prototype is designed for workflow validation and pilot discussions with brokers, carriers, facilities, and enterprise logistics organizations.
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.
Planned workflows for each participant, with access and responsibilities appropriate to its role.
Structured contracting, transaction visibility, exception handling, carrier coordination, and settlement workflows.
Clear transaction requirements, documentation workflows, operational updates, exception handling, and settlement visibility.
Participate in freight transactions when parking, staging, storage, trailer handling, or other approved services are required.
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.
Participating logistics facilities could join the transaction workflow when a shipment needs an approved service.
A location option when a shipment is interrupted or a trailer needs to wait.
A storage requirement connected to the affected transaction.
A planned stop or holding point coordinated with onward movement.
Agreed handling services with documented responsibilities.
Facility support coordinated with a shipment exception.
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 ParticipationThese principles describe the intended architecture. They are planned controls, not claims of operational capabilities, certifications, security audits, or regulatory approval.
Planned access based on organizational roles and transaction responsibilities.
Intended additional verification for access to platform accounts.
Designed to protect documents in transit and at rest.
Planned records of key access, changes, and administrative actions.
Intended integrations to support checks on participating people and organizations.
Designed to limit who can view documents, approve changes, or take transaction actions.
Intended traceability for milestones, supporting evidence, and decisions.
Planned authentication, authorization, input validation, and controlled system integrations.
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.
Pirex Blockchain Logistics is seeking qualified logistics organizations interested in evaluating the proposed platform workflow and participating in pilot discussions.