The commercial side, on the same records
Operations software that stops at the shipment leaves the hardest part — getting paid correctly — to a spreadsheet. CargoXY runs quotations, billing and accounts on the same records the operations team already fills in.
What it does
Quotations and rate management
Quote from managed rates rather than memory, and keep the quote for the conversation that follows three months later.
Live tracking, no login required
Customers follow a shipment on a live tracking page without an account, while your team sees the full event history behind it. Most status calls stop arriving.
Role-based access control
Granular permissions per user, with audit logging, so who did what to which shipment is a record rather than a question.
Data isolation at the query layer
Separation is enforced where the data is read, not in the interface — the difference between a system that is private by design and one that is private by convention.
Invoicing from the job
Bill what was actually shipped, with the charges already collected against the consignment rather than assembled at month end.
Accounting built in
A double-entry ledger underneath the freight work, so revenue, cost and receivables are posted rather than estimated.
Multi-currency
Freight is rarely billed in one currency. Accounts can carry their own, with the ledger consolidating in yours.
Operations dashboard
Shipment volume, live status and revenue in one view — and profitability by shipment, customer and lane read from the same postings the daily work creates.
Common questions
Does CargoXY replace our accounting software?
It carries a full double-entry ledger, so it can. Whether it should depends on what else your finance team runs — worth covering in the demo.
Can we bill in more than one currency?
Yes. Accounts can hold their own currency while the ledger consolidates in your base currency.
Can customers raise their own bookings?
Yes, and they can follow shipment status on a live tracking page without needing a login at all.
How is our data kept separate from other companies?
Isolation is enforced at the query layer rather than in the interface, alongside role-based permissions and full audit logging.