A practical delivery exception
A delivery reaches the customer but only part of the shipment is accepted. The intended process records the actual outcome, reason and evidence, then routes the remaining goods or issue for follow-up. Marking the entire shipment delivered would hide the exception.
Prepare dispatch and delivery responsibilities
Identify who releases an order, prepares the pick list, packs goods, creates the invoice and assigns delivery. Bring examples of partial deliveries, failed attempts, returns and proof-of-delivery requirements. Confirm how transporters and delivery personnel access the relevant information.
Review the proof you need
Photos, signatures and OTP are distinct forms of evidence described in the roadmap. Their availability, device support and operational requirements need confirmation. Decide what evidence is appropriate for each delivery process before choosing a rollout.
What makes delivery reporting useful?
Separate pending dispatch, in-transit shipments, completed deliveries and unresolved exceptions. Agree how rescheduled attempts and partial acceptance are counted so performance figures describe the real workflow.
A connected workflow
Order & stock check → Pick & pack → Invoice → Dispatch → Delivery outcome → Proof of delivery
Discuss your rollout
These capabilities describe the product model and development roadmap. Ask us to confirm available modules, implementation requirements and pricing for your business.
Is there a delivery-person app?
A delivery-person app is included in the development roadmap. Ask the team to confirm its current release status and supported devices before relying on it for your rollout.
Are maps, shipping and payment integrations included?
The document lists these as future integrations. Provider support, configuration, availability and any additional charges need to be confirmed separately.
Explore connected solutions
Distribution & Partner Network Management
Quality Management & Batch Traceability