Vefri captures what was delivered, compares it with what comes back, and gives your team the evidence to make the right refund decision.
Order activity
#ORD-4821
Cotton shirt · Size M · $15
2:14 PM
Aug 8
Order delivered
WhatsApp link sent to customer
2:18 PM
Aug 8
Delivery recorded
11s video of the product when it reached the customer
11:02 AM
Aug 12
Return requested
Sellers can require a return recording before pickup is scheduled
11:06 AM
Aug 12
Return recorded
Same waypoints as the delivery recording
4:30 PM
Aug 14
Evidence review passed
Refund approved
The loop
Delivered → customer records → return requested → compare → your team decides.
How it works
01
Record the product when it's delivered.
02
When a return is requested, capture it again and compare both records.
03
Your team gets both records and approves, holds, or rejects the refund.
Guided recording
Same waypoints both times, so your team can compare. In-app camera only.
Trigger
A Shopify, Shiprocket, or Delhivery delivery update can start the flow. No courier-side app.
Shopify · Shiprocket · Delhivery · WhatsApp
Message
Customer gets a short link to record the product when it reaches them.
In-app camera · no gallery upload
Delivery
Front, label, and other waypoints in about 10 seconds. This is a visual record, not a sealed-parcel claim.
Same waypoints used again on return
Decision
If they return it, they record again. Vefri lines both up. Your team approves, holds, or rejects.
Courier moves the parcel · you decide
The problem
Vefri creates the record before the dispute happens.
The SKU on the ticket is not what came back.
The product was worn, opened, or swapped.
The carton returns. The product does not.
When the story is disputed, sellers are left with screenshots, chat threads, and assumptions.
Differentiation
No courier-side workflow. Courier delivers and picks up. Vefri handles the records. Your team makes the final decision.
Customer
Capture. A short guided recording at delivery, and again if they return.
Vefri
Compare. Both records sit on the order so ops is not guessing.
Your team
Decide. Approve, hold, or reject the refund with both views in front of you.
The courier moves the parcel. Your team makes the decision.
Product
Delivery capture, return comparison, and the refund decision in one layer.
Create a visual record of the product when it reaches the customer. A WhatsApp link can fire from a Shopify, Shiprocket, or Delhivery delivery event.
When a return is requested, capture it again with the same waypoints and compare both records side by side.
Optional mismatch flags help ops see what to review. Your team still makes the refund call.
Ops sees the delivery record and the return record before they approve, hold, or reject.
Keep the last word with your team, not with a courier agent or a disputed chat thread.
Connect Shopify, Shiprocket, Delhivery, and WhatsApp so the flow can start automatically. No courier-side app or agent workflow.
Integrations
Connect Shopify, Shiprocket, Delhivery, and WhatsApp Business. No courier-side app or agent workflow.
Sync orders, customers, and delivery details from your store.
AWB, pickup status, and delivery scans.
Waybill tracking and shipment events.
Capture links and return updates on WhatsApp.
FAQ
No courier-side app or agent checklist is required. Couriers deliver and pick up as usual. You can still connect Shiprocket or Delhivery so a delivery event can start the customer recording. Verification happens on the customer's phone, then your team reviews the records.
Get started
Start your first verification flow. Built for India's D2C return teams.
