Guide · proof of delivery

Proof of delivery with third-party carriers Five ways to get it, compared

When carriers, couriers or subcontractors make your deliveries, the signed delivery note is the first thing to go missing. These are the five ways companies get proof of delivery from drivers they don’t employ - and when each one makes sense.

QR on the noteCarrier paperworkCarrier portalsDriver appText link
5 approachesside by side
Written fordistributors and 3PLs
ERP-firstwhere the record should land
// The short answer

How do you get proof of delivery from a third-party carrier?

Move the signature onto something the recipient already has: their own phone. A QR code printed on the delivery note, or a link sent by text, opens a signing page in the browser. The driver needs no app, and the signed record can go straight to the order in your ERP. Carrier paperwork and carrier portals still work for low volumes or a few large carriers, but they leave the proof outside your system – and usually days late.

// Side by side

The five approaches compared

ApproachHow it worksDriver needsWho signs, whereWhere the record landsWorks best whenWatch out for
QR on the delivery noteRecommendedA QR code printed on the document opens a signing pageNothing - just the documentOn the recipient’s phoneOn the order in your ERP, in real timeMany carriers, changing drivers, distribution-center hand-offsThe recipient needs a phone with a camera; agree on a fallback
Carrier paperworkThe carrier’s paper delivery note or bill of lading, returned or scanned laterNothing newOn paper, at the doorDays later, as a scan you attach by handLow volumes, one or two carriersLate, lost or unreadable copies; disputes you can’t settle quickly
Carrier portal or eBOLThe carrier captures the signature in its own systemThe carrier’s appOn the carrier’s device or linkStays in the carrier’s system - download or import per carrierA few large carriers with good portalsOne portal and one format per carrier; nothing for small couriers
Your driver appExternal drivers install and log in to your delivery appYour app + a loginOn the driver’s phoneDirectly in your systemStable subcontractors who drive for you every weekOnboarding, devices and user licenses for drivers who change
Text or email linkA signing link is sent to the recipient when the driver arrivesUsually an app or a dispatcher to trigger itOn the recipient’s phoneDirectly in your systemRecipients whose mobile numbers you have and trustWrong or missing numbers; the link has to arrive at the right moment

The other four approaches are listed from the simplest to the most connected. Many companies combine approaches: their own drivers use an app, and external carriers use a QR code or link. What matters is that every proof of delivery ends up on the same order record.

// What to capture

What a defensible delivery record contains

// Who and when

Signer, date and time

The name and signature of the person who received the goods, with the exact date and time. A signature without a name rarely settles a dispute.

// Where and what

Location and photos

Where the delivery was signed, and a photo of the goods or the drop point. Photos answer most “it never arrived” and “it arrived damaged” questions.

// Which document

The exact order and exceptions

The record must point to the specific delivery note or order, including shortages, damage and returns - so finance can invoice or credit without calling anyone.

// How to choose

Four questions that decide the right approach

01How many carriers deliver for you?

One or two large carriers - their portal may be enough. Many carriers, or couriers that change - keep the proof on your own document.

02Will external drivers install an app?

Weekly subcontractors may. A different driver every day will not.

03Where must the record end up?

If invoicing, credits and collections run from the ERP, the proof of delivery has to land on the order there.

04What happens in a dispute?

You need signer, time, place and photo in one record you can open in seconds.

// Where SPS fits

Proof of delivery for drivers you don’t employ

ShipSnap QR flow: the recipient scans the QR code on the delivery note, signs on their own phone, and the confirmation syncs to the ERP

ShipSnap QR is the QR-on-the-delivery-note approach, built for distributors and 3PLs. Winsert adds the QR code when your existing delivery note or label prints, so there is no change to your ERP. The recipient scans it, signs and adds a photo on their own phone, and the signed document is synced to the order and customer record in SAP Business One or the ERP you run.

Your own fleet can keep using the ShipSnap driver app - both land in the same record.

// FAQ

Proof of delivery with third-party carriers: FAQ

A record showing that a specific shipment reached a specific recipient: who signed, when, where, and in what condition the goods arrived. It is what finance relies on to invoice, credit or settle a dispute.

You can wait for the carrier’s paperwork, use the carrier’s portal, ask external drivers to use your app, send the recipient a signing link, or print a QR code on the delivery note that the recipient scans and signs on their own phone. The last two keep the record in your system without depending on the carrier.

Yes. A QR code or a link opens a signing page in the phone’s browser – nothing to install. The recipient signs, can add a photo, and the record is saved with the time and location.

Then avoid any approach that depends on the driver: an app, a login or a device. Put the proof on the document itself, so whoever delivers it, the recipient can sign.

With ShipSnap QR, the signed document and delivery details are synced to the order and customer record in SAP Business One out of the box, and in Oracle, NetSuite, Priority, IBM AS/400 and other ERPs through Winsert.

// Next step

See proof of delivery on your own delivery notes

Tell us who delivers for you and which ERP you run - we’ll show the flow on your documents.

Used in: 3PL & logistics · Wholesale & distribution · Building materials