Logistics intelligence
PilotSee the logistics lifecycle, then act on the exceptions.
Boni and Bino connect container, port, CFS, yard, road, vehicle, manifest, and shipment signals into lifecycle views, charge checks, and accountable exception operations.
For: Importers, exporters, manufacturers, freight teams, forwarders, transport operators, and finance or commercial desks.
What the product connects
One operating record across the workflow
Connect
Join the available container, manifest, port, CFS, yard, vehicle, road, and shipment records around one authorised reference.
Understand
Build a time-ordered lifecycle, compare facilities and dwell, and surface the next likely operational or commercial exception.
Act
Assign the responsible desk, deadline, evidence request, dispute, release, recovery, planning action, and final outcome.
How it works
The product is the decision loop, not a pile of source responses.
A useful logistics workflow turns fragmented observations into a lifecycle and combines them with the customer's commercial records, permissions, decisions, and verified outcomes.
- 01
Enter an authorised reference
Use a Bino logistics tool or secure charge-check link with an identifier the user is permitted to check.
- 02
Build the lifecycle
Review the available manifest, port, CFS, yard, road, vehicle, and state-change evidence in time order, with source-coverage gaps visible.
- 03
Add commercial evidence
Attach or review the invoice, contracted rate, free-time terms, extension, delivery order, proof of delivery, and responsible party.
- 04
Classify the exception
Decide whether the issue is timing, detention, demurrage, storage, duplicate billing, wrong rate, delayed return, or incomplete evidence.
- 05
Assign the next action
Record the owner, counterparty, case number, evidence still needed, deadline, and escalation path.
- 06
Measure the outcome
Close the case as released, prevented, recovered, credited, formally cancelled, unsupported, or unresolved with evidence.
Product scope
What the product covers.
Container lifecycle views across available manifest, port, CFS, yard, release, road-movement, and empty-return observations.
Import and export manifest context, port-side events, container status, vehicle details, recent toll-movement signals, and e-waybill checks for authorised references.
Dwell, turnaround, facility-pressure, arrival-planning, and likely-release signals derived from time-ordered observations rather than a single status field.
Movement-date and contractual-clock comparison for a container charge before payment or dispute.
Secure customer-specific charge-check links instead of an open data lookup.
Case records for the billed period, movement evidence, contractual clock, responsible party, and next charge date.
Exception queues with owner, deadline, evidence gaps, case number, and next action.
Daily observation history and predicted-versus-actual outcomes so planning and exception models can improve over time.
Outcome tracking for prevented charges, realised recoveries, usable credits, and formal cancellations.
Clear degraded states when a source has no record, stale coverage, or an unavailable check.
Connection to Bow Chat for accountable communication and follow-up.
Connection to Trade OS when delivery, stock, claims, or distributor operations share the same business workflow.
Start with a defined operating scope.
Each rollout names the workflow, participants, source records, owner, success measures, and the parts that remain in existing systems.
Movement evidence is not the contract
A tracking date can support a case, but it cannot establish the agreed rate, free time, waiver, liability, or legal outcome without the customer's commercial documents.
No automatic savings claim
An estimated exposure or flagged mismatch is not recovered value. Success is counted only when the customer receives cash, a usable credit, or a formal cancellation of a payable charge.
Authorised checks only
The tools require a user session and are intended for references the user is entitled to inspect. They are not a public asset-enumeration surface.
Coverage depends on the reference
No single source covers every mode, facility, asset, or event. Boni shows available evidence, source timing, and gaps instead of presenting partial data as a complete national view.
Operational scope stays honest
Boni coordinates evidence and exception work. It does not replace licensed legal advice, contractual authority, the carrier, the forwarder, or the customer's transport system.
Connected products
Use it alone, or connect the next part of the operation.
Bino logistics tools
Run authorised checks for shipment, vehicle, container, port, and movement references from a focused user flow.
Open the toolsContainer charge check
Use a secure personal link to compare one billed-through date with recorded movement dates before paying or disputing it.
Learn about the checkBoni Trade OS
Connect logistics exceptions to the order, stock, delivery, claim, distributor, and accounting-evidence workflow when relevant.
Explore Trade OSQuestions
Common questions
Can Boni prove that every flagged container charge is wrong?
No. Movement records can show an exception or timing mismatch, but the commercial answer also depends on the customer's invoice, rate agreement, free-time terms, extensions, and responsibility for the delay.
What can I check on Bino?
Authorised users can start from shipment, vehicle, container, port, or movement references using dedicated Bino logistics tools. The available result depends on the identifier and source coverage.
How is the container charge check priced?
The current recovery pilot has no setup or subscription fee. Boni charges 20% only on a realised recovery, such as cash received, a usable credit, or formal cancellation of a payable charge, within the agreed pilot terms.
Does this replace a freight forwarder, legal adviser, or transport management system?
No. It is an evidence and exception workflow. The responsible logistics, finance, commercial, carrier, forwarder, or legal team still owns the underlying operational and contractual decisions.
Start with one bounded workflow