Xirag Register for early access

Xirag for Logistics

Xirag logistics for fleets and shipments

For carriers, fleet owners and logistics firms: bookings, dispatch, proof of delivery, fleet, cash on delivery, freight invoices and carrier payouts on the same core as every Xirag module, with named seats, maker-checker approvals and an audit trail you can prove.

Register for early access See the capabilities

Logistics modules are planned; freight money runs on Xirag Payments. Every workflow works for people on their own. Agents are not offered at launch; they are provided on request later.

Xirag for Logistics · Shipment journeyDemo
  1. Book
  2. Dispatch
  3. Transit
  4. Deliver
  5. Collect
  6. Settle
  • DispatchTrip for Ravi Transports (demo) assigned, fuel advance recorded
  • ProofDelivery signed by the consignee, location attached
  • CODCash collected matched to the carrier's weekly remittance
  • CheckerCarrier payout batch approved by the finance controller
Illustrative mock-up with fictional demo data; most steps are planned logistics modules, not a live console.
Capabilities

Logistics ERP for everything a shipment touches

From the booking to the carrier's payout, each area builds on Xirag modules that already share people, departments, approvals and the audit trail.

  • Control tower

    Bookings, trips and exceptions on one live board, with alerts routed to the person on the right seat.

    Planned · builds on the shared core

  • Shipments and tracking

    Bookings, waybills and milestones for every shipment, from first mile to last mile.

    Planned · builds on the shared core

  • Dispatch and routing

    Routes, capacity and driver assignment planned by your dispatchers, on the shared calendar.

    Planned · builds on Calendar

  • Proof of delivery

    Scan, location, photo and signature at the door, and exception evidence when a delivery fails.

    Planned · builds on eSign

  • Fleet and drivers

    Vehicles, drivers, documents, maintenance and availability, with one sign-in for every driver.

    Planned · builds on Admin, Gate

  • Rate cards and quotes

    Lane rates and surcharges, a quote in minutes, and a booking straight from the accepted quote.

    Planned · builds on Billing

  • Cash on delivery

    COD per shipment, remittance cycles per carrier, and every shortage raised as a break to work.

    Planned · builds on Xirag Payments

  • Freight invoicing

    Freight invoices with waybill references, credit limits and terms per shipper, and payment links.

    Planned · builds on Payments

  • Carrier and driver payouts

    Payouts per trip or cycle, multi-leg charge splits, and fuel and toll advances settled against the trip.

    Planned · builds on Payments

  • Partners and contracts

    Carrier onboarding with document checks, signed agreements and contract obligation alerts.

    Planned · builds on CRM, CLM, eSign

  • Returns and claims

    Return-to-origin flows, and damage, loss and shortage claims backed by delivery evidence.

    Planned · builds on Payments, eSign

  • Updates and analytics

    Consignee calls and messages, and service, COD and margin reports from the same records.

    Planned · builds on Dialer, Messenger

Beyond a logistics app

What one agentic core changes

A tracking app shows where a parcel is. Xirag also shows who is responsible for it, where its money went, and a record nobody can quietly rewrite.

  • Seats outlive shift changes

    "COD remittance" and "Carrier payouts" are seats. When a person changes shift or leaves, the open work stays with the seat.

  • COD matched to proof of delivery

    Delivered shipments are matched to the COD expected and the carrier's remittance; a delivery with no cash, or cash for a return, becomes a break.

  • Freight invoices with credit control

    Each shipper has a credit limit and terms; a shipper past its limit raises an alert, and raising a limit needs the finance controller.

  • Payouts with a second approver

    Every payout batch, and any payout to a new beneficiary, needs a person, after the bank account and name are checked.

  • One shipment, many carriers, one split

    First mile, line haul and last mile each get their share of the charge, and changing a carrier's share needs a person.

  • Trip advances that net themselves

    Fuel and toll advances are recorded against the trip and settled against its final payout, so no advance goes unrecovered.

  • A delivery record nobody edits quietly

    Status changes, proofs and write-offs go to an audit trail where each entry is linked by hash to the one before, so an edit shows.

  • Agents that draft, people who decide

    On request, agents can propose dispatch plans, flag shipments at risk of delay and prepare COD shortage cases, and a person approves each. Agents are not offered at launch; they are provided on request later.

Freight money powered by Xirag Payments

Freight, COD and payouts on a real payments stack

Freight billing, COD remittance and carrier payouts run on Xirag Payments, the stack Xirag provides to payment aggregators and gateways, with versioned APIs and signed webhooks for the carrier and transport systems you connect. Xirag Payments is in development and runs in a sandbox; money movement is partner-backed.

Explore Xirag Payments
  • COD per shipmentWith the waybill number on the record
  • Remittance cycles per carrierDelivered shipments grouped into a remittance due
  • COD reconciliationAgainst the carrier's delivery proof
  • Freight invoicesWith shipper credit limits and terms
  • Carrier and driver payoutsPer trip or cycle, partner-backed
  • Multi-leg charge splitBy leg, fixed or percentage
  • Fuel and toll advancesSettled against the trip's payout
  • Beneficiary checksBank account and name before the first payout
Trust for delivery data

Built to protect drivers, shippers and consignees

Addresses, phone numbers, locations and payouts deserve more than a password. These are the principles the product is designed around.

  • Audit trail

    Every change to a shipment, a remittance or a payout is written with who, when, before and after, linked by hash to the entry before it.

  • Maker-checker

    Payout batches, COD write-offs and credit limit increases need two people: one asks, another approves.

  • Data for its purpose

    Driver and consignee details are designed to be used for the delivery they serve, with every change on the audit trail.

  • Role scopes

    People see what their role and hub allow. An agent, when a client asks for one, acts only within the scopes of its seat.

These are design principles of the product, not certifications.

Early access

Shape Xirag for your network

Register for early access, or tell us how your bookings, dispatch, proof of delivery and carrier settlements work today.

Register for early access Talk to us