Rates
Rate selection
Compare eligible partners by zone, slab, COD fee, surcharge and TAT before booking.
Built for teams that outgrew public aggregator fees or mix partner couriers with their own delivery fleet.
Rates
Compare eligible partners by zone, slab, COD fee, surcharge and TAT before booking.
COD
Import partner statements, match AWB/order, and flag short, late or missing remittances.
True cost
See true cost including RTO, weight disputes, COD fees and delivery performance.
The problem
Rate selection, COD settlement and weight disputes leak money when every courier runs in its own panel.
The cheapest partner for 500g to Coimbatore isn't the cheapest for 5kg to Guwahati. Nobody checks five tabs while a customer waits, so booking happens by habit.
Rate Visibility: Low
Courier P&L
LeakHighCOD risk
?COD exposure
Five courier panels hide cost at rate selection, COD settlement and weight disputes.
When every courier runs in its own panel, these losses stay invisible.
Rate, book, track and reconcile from one board.
How it works
Order → Rate comparison → Book → AWB → Track → Deliver / NDR → RTO → COD remittance → Reconcile → Partner P&L
OthersOrders retyped into each courier panel.
CovixyManual, CSV or API from your storefront/ERP.
OthersBooked by habit, not by price.
CovixyEvery eligible partner ranked by total cost and TAT.
OthersOne panel and one order at a time.
CovixyOne click to the partner API; AWB, label and manifest.
OthersFive status vocabularies, five panels.
CovixyOne normalised timeline; failed attempts queued.
OthersReturns and remittances chased in Excel.
CovixyReturns tracked to receipt; statements auto-matched.
Others~90% matched, the rest called adjustments.
CovixyExpected vs received, and true cost per partner.
Matched
COD statements import by partner, auto-match to AWB/order, and send exceptions to review.
Modules
Rate engine, booking, tracking, NDR/RTO, COD reconciliation, weight disputes and partner P&L.
Module 01
Prices each shipment across eligible courier partners before booking.
Module 02
Creates AWB, labels and partner-wise pickup manifests.
Module 03
Normalises partner statuses into one shipment timeline.
Module 04
Imports partner statements and matches COD to shipments.
Module 05
Compares declared and charged weight when invoices arrive.
Module 06
Shows true cost by partner beyond headline rate.
Module 07
Branded tracking, WhatsApp/SMS updates and NDR customer actions.
Visibility
Role-based views that give your team exactly the data they need, when they need it. No more digging through spreadsheets or calling the floor manager.
Integrations
Implementation-based status; unknowns marked. Other partners may connect by API or bulk upload—we confirm first.
India Post: unverified. Fleet: rate N/A; all else internal. Runs in the same board.
Rate/Book/NDR: [Y/N] Track: [Push/Poll] COD: [CSV/API/PDF] · [Notes]
All capabilities unverified.
All capabilities unverified.
All capabilities unverified.
Both partners: all capabilities unverified.
Financial Impact
Return comes from rate optimisation, COD recovery, dispute wins and less RTO.
Critical Impact
Usually the largest line: every shipment priced across partners before booking.
By scope
Short, late and missing remittances found instead of written off as adjustments.
By scope
Declared weight, dimensions and photos turn re-billing into winnable disputes.
By scope
Failed attempts fixed before they become double-freight RTOs.
By scope
No per-shipment aggregator fee once you run your own system.
By scope
We model payback using shipments, partners and COD data.
Custom /mo
Target audience
Best suited to complex, high-volume delivery operations with multiple partners, COD and mixed logistics.
Best match
Better alternatives
Alternatives
When not to build: under [X] shipments a month, no direct rate contracts, or you need to start this week — use a public aggregator.
Your own aggregator on your contracts, fleet and workflow.
Shiprocket-class platform: start today, pay their margin and fee.
One login per partner; booking by habit, tracking in five places.
COD matched by hand — around 90%, the rest called adjustments.
| Feature | Covixy | Public aggregator | Panels | Excel |
|---|---|---|---|---|
| Rate contracts | Yours, direct | Theirs + margin | Yours | Yours |
| Platform fee | None after build | Per shipment | None | None |
| Rate comparison | Every order | Built in | 5 tabs, manual | Manual |
| Own fleet & B2B | Native | Rarely | Separate | Manual |
| COD reconciliation | Auto-matched | Their numbers | Per panel | ~90% matched |
| Reverse logistics | Your process | Basic | Per panel | Manual |
| Year-1 cost | Scope-based | Per shipment | ~₹0 | ~₹0 |
FAQ
The questions we hear most before teams build their own courier aggregator.
For many operations you should — the comparison above says when. Build when the platform fee exceeds the build cost, you have direct rate contracts, or your workflow (own fleet, B2B, returns) doesn't fit a parcel platform.
Most teams match around 90% and call the rest adjustments. Import last month's statement and compare expected vs received, shipment by shipment. The gap is the cost.
It happens, and it's the main ongoing maintenance cost. Integration maintenance belongs in the AMC explicitly, not in a change request. [Your AMC coverage for API changes.]
Yes. The rate engine and booking layer are partner-agnostic, so each new partner is an adapter, not a rebuild. [Cost and timeline per integration.]
Next step
We'll walk your process and tell you whether to build, configure, or buy something off the shelf. If it's the third one, we'll name the product.
Share how your operation runs today and where it hurts. We'll review it and reply with a clear recommendation.
Walk us through your process on a call. Twenty minutes, no slides, and a straight answer at the end.
No sales pitch. If an off-the-shelf product fits better, we'll name it.