What happens if the driver has no mobile connectivity at a remote outlet?

HublerX operates in offline mode where connectivity is unavailable. The driver captures the POD — signature, photo, quantities — on the device without a network connection. The data syncs to HublerX and the ERP the moment connectivity is restored, typically when the driver reaches the next urban area or returns to the depot. The POD timestamp reflects the actual delivery time, not the sync time.

Can the outlet receiver sign on their own device rather than the driver's phone?

Yes. HublerX supports a QR code flow where the outlet receiver scans a QR code on the driver's screen with their own phone, signs on their device, and the signature is transmitted directly to the delivery record. This can be useful where the outlet prefers not to handle the driver's device.

Does digital POD eliminate the need for a paper delivery challan?

In most operations, HublerX digital POD can replace the paper challan for ERP and AR purposes. Some modern trade customers still require a paper challan as part of their receiving process — in those cases, the driver can print or carry a pre-printed challan alongside the digital capture. The ERP posting is driven by the digital record regardless.

How does HublerX handle partial deliveries or returns?

Short deliveries, returns, and rejections are captured in the app at the outlet — with the reason (damage, expiry, wrong SKU, customer refusal) and a photo. The ERP goods issue is posted for the actually delivered quantity only. Returns are logged against the delivery record and trigger a return goods receipt when the driver returns to the depot.

Proof of Delivery to ERP

HublerX captures digital proof of delivery at each outlet — signature, photo, timestamp, and GPS — and posts the goods issue and delivery confirmation to the ERP the moment the driver taps confirm. No paper. No end-of-day batching. No disputes.