Pakka LogisticsTalk to us

For businesses

Your dispatch desk, not a delivery app.

A separate portal with its own login, built for people who move goods every day — bulk uploads, recurring runs, a live board, and invoices your finance team can file.

The enterprise portal
  • Sign in with your company account
  • Two roles — admin and member
  • Quote, book, track and reconcile in one place

One place, five jobs.

Not the customer app with a business badge. A different sign-in, a different surface, built around a dispatch desk rather than a single parcel.

Dashboard

What is moving right now, what is unbilled, what is outstanding — in one summary rather than three reports.

Shipments

Quote, create, filter and cancel. Every shipment keeps its quote attached, so a fare question later has an answer.

Live board

Every active shipment on one screen, not one booking at a time.

Schedules

Recurring pickups that run themselves — set the cadence once.

Compliance

Documents we have asked for, what is outstanding, and the deadline on each.

Two roles: admin and member. An admin manages the account; a member books and tracks.

How an account opens.

Three gates. The third one is not a one-off — it stays open for as long as the account does.

  1. Sign up

    Company details, a billing address and a GSTIN. The billing address is required, because an invoice without one is not a tax invoice.

  2. Submit KYC

    Your documents go to a person, not a checkbox. Status moves pending → submitted → approved, and a rejection tells you which document and why.

  3. Stay compliant

    We can raise a request against a live account — a specific document, with a message and a deadline. It shows in the portal until it is satisfied.

Verification moves through four states, and you see which one you are in: pending → submitted → approved → rejected.

One file. Many drops.

Preview first, then commit. The preview is where you find the row with a bad pincode — not after two hundred bookings exist.

  1. 1

    Upload

    Your rows, one shipment each.

  2. 2

    Preview

    We price every row and show you what will happen before anything is booked.

  3. 3

    Create the batch

    Every valid row becomes a real shipment, dispatched like any other.

  • CompletedEvery row booked.
  • PartialSome rows booked and some errored. You get both lists — the batch does not silently swallow the failures.
  • FailedNothing booked. Usually a file the preview already warned you about.

The runs that happen every day anyway.

A schedule is a pickup, a drop and a time. It fires on its own and enters matching like any other booking — you do not open the portal to make it happen.

Daily
Every day, including weekends.
Weekdays
Monday to Friday.
Weekly
One chosen day each week.

Times are IST. A schedule can be paused without deleting it, so a seasonal run keeps its settings.

Everything moving, on one screen.

A dispatch desk does not want a list of bookings. It wants to know which one needs attention, and that changes minute to minute.

ReferenceDestinationStatus
PK-12B720WhitefieldOn the way
PK-12B658KoramangalaAt drop
PK-12B441PeenyaFinding a driver
PK-12B402HebbalPicked up
PK-12B377Electronic CityDelivered

Illustrative — the real board is behind your login.

A serial you can defend in an audit.

A GST tax invoice must carry a unique consecutive serial. That sounds trivial and is the thing most systems get quietly wrong.

  1. The number is taken atomically

    Not by counting existing invoices — two runs a millisecond apart would read the same count and take the same number. The database itself hands out each number once.

  2. Taken on issue, never on draft

    A serial consumed by a draft that is then discarded would leave a gap in the sequence. Numbers are only spent when an invoice is actually issued.

  3. Per financial year

    The sequence restarts where the law expects it to, and the year is part of the number.

Or skip the portal entirely.

If your systems already know what needs moving, they can book it. Five endpoints, the same dispatch behind them.

  1. POST/shipments/quote/previewPrice a shipment before committing to it.
  2. POST/shipments/create/singleBook it.
  3. GET/shipments/list/filteredYour shipments, filtered.
  4. GET/shipments/detail/:idOne shipment, in full.
  5. PATCH/shipments/cancel/:idCancel, subject to the same windows as everyone else.

There is no public reference yet — talk to us and we will send you keys and the spec.

Two ways to start.

Open an accountTell us what you move and how often. We will set up the portal and walk you through KYC.Talk to an engineerIf you want the API, ask for keys and the spec.