Skip to content
QuickE
Start free

Analytics and heat maps

See where the volume clusters and where it fails

Carrier performance, failed delivery reasons, ageing COD and delivery density sit in one place, read from the same shipments your team dispatched. The question you get asked in a meeting is answered from a screen, not assembled from exports the night before.

Start freeBook a demo

Carrier performance, side by side

Every carrier you hand shipments to is measured on the shipments you actually gave it: delivered on time, delivered late, failed, returned, and how long its COD takes to come back to you. Your own fleet appears in the same table on the same definitions, so moving a route in house or out to a carrier is a comparison rather than a hunch.

Failed delivery reasons, ranked

Every failed attempt carries the reason the driver or the carrier recorded, and the reasons are ranked by how often they happen and where. Customer not answering in one area is a different problem from wrong address in another, and the ranking tells you which one to work on this week instead of leaving failure as a single percentage.

COD exposure, bucketed by age

Cash that has been collected but has not reached you yet is grouped by how long it has been outstanding and by who is holding it, a driver, a hub or a carrier. The oldest bucket is the one to chase first, and the trend shows whether a carrier is getting slower before the amount grows large enough to hurt.

Delivery density on a map

Completed and failed deliveries are drawn over your areas, so the map shows where the volume clusters and where the failures do. A zone heavy on volume tells you where the next hub or a dedicated driver would earn its keep, and a zone heavy on failures tells you where to look before a merchant asks you to.

The month end deck, and what fed it

  • A monthly slide deck assembled by hand from carrier exports.
  • A pivot table that answers last month’s question after the moment has passed.
  • A guess about which areas are worth a hub.
  • Asking each carrier for its own scorecard and taking its word for it.

Where this matters most

See last mile deliverySee 3PL and courier companies

Questions operators ask

Where do the analytics numbers come from?
From the shipments themselves. Every figure is computed from the orders, delivery attempts, cash entries and carrier records already in QuickE, so the report and the operation cannot disagree. There is no separate data entry step and no import to run before looking.
What is a delivery heat map?
A delivery heat map is a map of a delivery operation’s service area shaded by how many deliveries happen in each part of it, so busy zones read darker than quiet ones. Operators use it to decide where to place a hub, where a dedicated driver is justified, and where failed deliveries cluster enough to need attention.
What does COD exposure mean?
COD exposure is the cash a delivery operation has collected on behalf of merchants but not yet remitted, plus the cash still out with drivers and carriers. Ageing it by how long each amount has been outstanding shows which driver, hub or carrier is sitting on money and for how long, before the gap becomes a dispute.
Can I compare my own drivers with outside carriers?
Yes. Your fleet and every connected carrier are measured on the same definitions of on time, failed and returned, over the shipments each one actually carried. Shifting volume between your drivers and a carrier becomes a like for like decision instead of a feeling about who complains less.
Can I export a view for a merchant or a monthly review?
Yes. Any view exports as a file, and the exported figures match what is on screen at the moment of export. The version you send a merchant or bring to a review is the version you looked at, not a second copy that drifted.

Stop assembling the deck

Start free, run a week of deliveries through it, and open the report on Friday instead of building it. Or book a demo and put last month’s questions to a live screen.

Start freeBook a demo