Every hyperlocal carrier asks for the same thing: exact pickup and drop coordinates. Most sellers don't have lat/lng for customer addresses — Google Maps lookups per order aren't a workflow. Borzo solves it differently: send the address string, it geocodes itself.
Why no-coordinates matters
Porter's API prefers coordinates for accuracy — meaning a seller without geocoded addresses either builds a geocoding step or accepts misquotes. Borzo takes the address text and resolves it internally — the quote works off what you actually have. It sounds minor; it's the difference between 'works now' and 'needs a Maps integration'.
Where it prices best
Documents, parcels under ~10 kg, point-to-point in metros — Borzo's crowdsourced fleet prices per-trip like Porter but often lands cheaper on short hops. The Bengaluru-Mumbai-Delhi metros are its strength.
The trade-offs
Vehicle classes are limited — two-wheelers mostly, no mini-truck for your bulky stuff. Fare calculation returns decimal pricing (₹111.28, not rounded slabs) — the invoice math is precise but watch for the API's string-decimal format if you integrate directly.
On Pakka Parcel
Borzo's adapter handles the address-to-geocode dance server-side — you send the order, it quotes; no coordinates required from your store.
Pakka Parcel runs the whole stack described here — one place for every carrier.
See how →The playbook
Use it for document/light parcels
The fleet's strength — short hops, low fares.
Skip the geocoding headache
Borzo resolves addresses itself — the API advantage.
Stay in metros
Coverage is city-focused — national orders go elsewhere.
Compare it per order
Sometimes Borzo wins, sometimes Porter — quote both.
