Short answer: Parcel delivery with proof creates a sequence of verifiable events instead of relying on one final status. KiloDrive can record declared contents and value, pickup OTP or signed QR, package photos, recipient confirmation, signature or photo where policy requires it, failed attempts and return-to-sender evidence. Each proof is scoped to the delivery and current step. It reduces ambiguity without guaranteeing contents, condition or coverage.
What this means Describe the parcel honestly, package it appropriately and select every required proof before dispatch. Give one-time codes only to the person completing the relevant handover. Evidence helps reconstruct events; it does not erase legal limits, prohibited-goods rules or the need to report a problem promptly.
The chain starts before a driver accepts
A sender builds the request with pickup and destination, parcel description, declared contents, declared value and currency, size or handling details, delivery window and any available protection choice. The route and configuration produce a quote. A declared value is a sender statement, not automatic insurance coverage or proof of the contents.
The request should settle important obligations before dispatch: whether pickup proof is required, whether the recipient must provide an OTP or QR, whether a signature or delivery photo is required, the maximum failed attempts, and the return policy. Adding these after a driver already has the parcel would change the job unfairly. The KiloDrive parcels guide describes the service, while the accepted delivery record holds the exact choices.
Dangerous and prohibited goods require special attention. UPU and IATA publish frameworks for their networks, while local road delivery remains subject to country law, carrier policy and service terms. Never conceal batteries, flammable liquids, weapons, controlled substances or another restricted item behind a vague description. If eligibility is uncertain, do not dispatch until the applicable policy is confirmed.
Pickup proof establishes the first custody change
At pickup, the sender or authorized handover person uses the challenge issued for that delivery. KiloDrive's courier lifecycle supports short-lived, single-use OTP or signed QR challenges with bounded attempts. Only a protected digest needs to be stored; the clear code should not appear in logs, support metadata or notification history. A code from one parcel must not work for another.
The driver can add structured pickup evidence, including reviewed package photos where required. Uploads remain private and pass ownership, file-type and security-scan checks. A quarantined file is not clean evidence, and the app should explain that review state instead of exposing a raw conflict error. Photograph the package rather than unrelated people, documents or the inside of a private home.
A successful pickup creates a timestamped custody event. Subsequent events should be append-only or versioned so a retry, double tap or lost response does not produce a second pickup. The sender and driver should see the same server state after reconnecting.
Recipient proof closes the correct delivery
At destination, the recipient uses the delivery-specific OTP or signed QR. Depending on the policy selected before dispatch, the driver may also record the recipient name, signature or proof photo. The interface should show which evidence is required and why; it should not collect extra personal data merely because a camera is available. Review KiloDrive's Privacy Policy for access, retention and deletion treatment.
Proof confirms that a configured handover step occurred. It does not prove hidden contents, condition inside the packaging or legal ownership. If the parcel appears damaged, the recipient should record the concern through the delivery or support case before discarding the packaging. A structured support workflow can link the delivery, evidence and case number without placing sensitive material in ordinary chat.
Failed delivery is a state, not a dead end
When delivery cannot be completed, the driver selects a structured reason and adds required evidence. Examples can include recipient unavailable, inaccessible location or recipient refusal, subject to the current policy. Free-text alone is weak because it is difficult to compare and easy to misunderstand. The system counts confirmed attempts and, when the agreed threshold is reached, can move the parcel into a return-to-sender workflow.
Return is another custody transition. It needs its own OTP or QR where required, return evidence and timeline entry. The parcel should not simply disappear from the active list after a failure. Both parties need a clear status, next action and any policy-based fee or refund treatment.
Payment, escrow and protection
For an eligible wallet delivery, acceptance can hold the agreed fare so it is no longer spendable. Completion releases the hold and credits the driver under the configured settlement rules; a qualifying cancellation refunds the hold. Cash and legacy deliveries can follow different accounting paths. Every movement should use an idempotent reference and immutable ledger record.
Optional parcel protection is country- and provider-gated. A protection charge, coverage cap, exclusions, claim window and required evidence must be shown before selection. Declared value alone does not create coverage. Never describe the service as insured unless the applicable legal product and provider contract are active. Read the current Terms and Legal Centre.
What is still uncertain
Parcel availability, permitted contents, proof requirements, delivery windows, protection, refund rules and business integrations vary by country and feature readiness. Signature and photo requirements can also be limited by privacy law and device capability. The live quote and accepted policy—not this article—control a delivery. Legal and product reviewers must verify every country-specific claim before publication.
Sources
- Dangerous Goods — Universal Postal Union.
- Dangerous Goods Regulations — IATA.
- KiloDrive Privacy Policy and Terms.
Frequently asked questions
Is a pickup OTP valid for the whole delivery?
No. It is a short-lived, single-use challenge scoped to one purpose and delivery. Recipient or return confirmation uses its own challenge when required.
Does a package photo prove what is inside?
No. It documents visible condition and packaging at a point in time. It does not prove concealed contents, value, ownership or legal compliance.
What happens after a failed delivery attempt?
The driver records a structured reason and required evidence. The delivery shows a next action and can enter return-to-sender after the policy's confirmed-attempt threshold.
Is declared value the same as insurance coverage?
No. Declared value is a sender-provided amount. Protection applies only when a reviewed country/provider product is offered, selected and confirmed with explicit terms.
Can delivery proof be shared publicly?
No. OTPs, signatures, addresses, photos and custody evidence are restricted delivery data. They should be accessed only through authorized, audited product and support workflows.