What proof to keep for deliveries

Delivery problems are often record problems. The item may have moved, but nobody can clearly show who received it, where it was handed over, what condition it was in, or whether the right order was involved.

Zaruni is built to keep delivery and proof events connected to the order, service, job, receipt, and support path. Good proof makes that record more useful.

What good delivery proof should show

Delivery proof should answer the basic handoff questions:

• What was delivered?
• Who handed it over?
• Who received it?
• Where did the handoff happen?
• When did it happen?
• Was the item complete and in expected condition?

Not every delivery needs every kind of proof. The goal is to keep enough context for the transaction type and risk.

Proof for sellers

Sellers should keep records that show the order was prepared and handed over correctly.

Useful seller proof includes:

• Product photo before dispatch.
• Packaging or parcel photo.
• Order reference.
• Delivery pickup time.
• Rider or delivery partner details where available.
• Buyer instructions or special notes.

If the buyer requested a specific variant, accessory, or condition, capture proof that confirms it.

Proof for riders or delivery participants

Riders should focus on handoff clarity. The proof should help confirm that the right package reached the right person or location.

Useful handoff proof includes:

• Delivery status update.
• Recipient confirmation.
• Location context when appropriate.
• Photo evidence where allowed and safe.
• Notes about failed attempts, unreachable contacts, or address issues.

Never capture sensitive information that is not needed for the delivery record.

Proof for buyers

Buyers should keep proof when the item does not match expectations or arrives damaged.

Useful buyer proof includes:

• Photo of the received item.
• Photo of damage or missing parts.
• Delivery time and recipient details.
• Screenshot or receipt of payment state.
• Clear message explaining what is wrong.

Report quickly. Delivery records are easier to review when the issue is raised close to the handoff time.

What to avoid

Avoid vague proof like “delivered” with no context when the delivery has risk. Also avoid sharing OTP codes, passwords, private account details, or unrelated personal information in delivery messages.

When proof helps support

If a delivery dispute starts, support can review the connected order, delivery status, proof, messages, and payment state. That is much stronger than separate screenshots from different apps.

Zaruni gives clearer delivery records and support paths. Users should still confirm addresses, recipients, item condition, and handoff details before closing a transaction.

Get Zaruni to keep delivery proof connected to the transaction.