Does HublerX trigger the QC clearance automatically, or does someone need to initiate it?

HublerX detects work order completion automatically from the ERP and triggers the QC clearance request without any manual step. The QC team receives the clearance request with the batch details, quantity, and the dispatch deadline it needs to meet — so they can prioritise without a phone call from the warehouse.

What happens if QC puts the completed batch on hold instead of releasing it?

If QC raises a quality hold on the completed batch, HublerX immediately flags the dispatch as at risk — notifying logistics that the truck booking may need to be revised and alerting the commercial team that the customer delivery is in jeopardy. The quality hold management workflow takes over from that point, coordinating the hold investigation and keeping logistics and commercial updated on the resolution timeline.

How does the POD capture work — does the driver need a separate app?

The delivery driver uses the HublerX mobile app to capture POD at the customer's premises — a digital signature, the delivery timestamp, and any short supply or damage notation. The POD is linked to the delivery order in the ERP immediately on capture. No paper POD to collect from the driver and key in the next morning.

Can HublerX handle partial dispatches — where only part of a production run is dispatched on the same day?

Yes. Where a customer order is fulfilled by multiple production runs or where only part of a completed batch is dispatched in a given truck, HublerX manages the partial goods issue in the ERP — updating stock levels for the dispatched quantity and leaving the remaining quantity in finished goods pending the next dispatch instruction.

Production Completion to Dispatch

HublerX connects production completion to customer dispatch — triggering quality clearance, warehouse picking, truck loading, and dispatch confirmation the moment a work order closes, without a manual handoff between any function.