Proof of Delivery for B2B Distributors: Fewer Disputes

A customer calls on Thursday: "We never got the two crates of tomatoes on Monday." Your driver is sure he left them. The signed delivery note is somewhere in the cab, or in a pile on the office desk. Nobody can prove anything, so you issue a credit and move on.

That small scene repeats itself across thousands of distributors every week. Proof of delivery (POD) is how you stop it. This guide covers what POD is, which proof to collect for which customer, and how to roll it out without annoying your drivers.

What proof of delivery actually is

Proof of delivery is a record that shows what was delivered, to whom, where and when. For a B2B distributor it usually answers four questions:

• Did the goods arrive at the right address?
• Who received them?
• Which products and quantities were handed over?
• Was anything refused, damaged or short?

Traditionally this was a paper delivery note signed by the customer. Today more and more distributors use electronic proof of delivery (ePOD): the driver records the handover on a phone, and the record is saved with the order straight away.

Paper delivery notes vs electronic POD

Paper works, until it doesn't. The typical problems:

• Notes get lost or damaged — rain, coffee, a cab floor full of paper.
• Signatures are unreadable. A scribble doesn't tell you who signed.
• Corrections are messy. "2 crates" crossed out and "1" written next to it, with no explanation.
• The office waits. Notes come back at the end of the shift, or the end of the week, and someone has to type them in before invoicing.

With electronic POD the record exists the moment the driver finishes the stop. The office can see it, attach it to the invoice and pull it up when a customer calls. Nothing needs to be scanned or retyped.

Which proof to collect for which customer

Not every stop needs the same level of proof. Asking for a signature at a café where you've delivered milk every morning for three years slows the driver down for no reason. Set the proof per customer, based on risk:

Receiver name only

Good for regular, low-risk customers who trust you and pay on time. The driver types or picks the name of the person who took the goods. Fast, and still far better than nothing.

Signature

Useful for higher-value orders, new customers, and customers who have disputed deliveries before. A signature on the phone screen, plus a printed name, is a clear acknowledgement.

Photo

Best when nobody is there to sign: early-morning drops at a restaurant back door, deliveries to a locked storage area, or building sites where the foreman is somewhere on the third floor. A photo of the pallet at the drop point, with the location visible, settles most "it wasn't there" arguments.

Delivered quantities

This is the part many distributors skip, and it matters most. Recording what was actually handed over — not just what was ordered — is what turns POD into something your invoicing can rely on.

A simple rule of thumb: the more valuable the delivery or the higher the history of disputes, the more proof you collect. Many customers will only ever need a name; a few will need signature plus photo.

How POD prevents "we never got it" disputes

Disputes usually come from uncertainty, not bad faith. A busy kitchen gets five deliveries before 9am, and the person who received yours has already gone home. With electronic POD you can answer the call in seconds:

"It was received by Marco at 7:42, here's the photo of the crates by the cold room door."

Most conversations end there. When they don't, you at least know where the problem is — maybe the delivery really was short, and you can fix it properly instead of guessing.

How POD speeds up invoicing

With paper, the invoice waits for the delivery note. With electronic POD, the invoice can go out the same day because the delivered quantities are already in the system.

A typical flow:

1. The order is planned and loaded.
2. The driver delivers and confirms quantities on the phone.
3. The order is updated with what was actually delivered.
4. The invoice is created from that order and emailed to the customer.

Customers also pay more easily when the invoice matches what they received, because there's nothing to query.

Short deliveries and returns

Real life is messy. A product is out of stock, a case is damaged, the customer refuses a crate of bruised fruit. Your POD process has to handle this cleanly:

• Record the actual quantity, not the ordered quantity.
• Add a short reason where useful: damaged, refused, not on the truck.
• Put failed or refused goods back into stock when the truck returns, so your stock figures stay correct.
• Invoice only what was delivered. This alone removes a large share of credit notes.

Scan when loading, not just when delivering

Many disputes start at the depot, not at the customer. The wrong product goes on the truck, or one order's crates end up in another order's stack.

Scanning barcodes when loading catches these mistakes before the truck leaves. The driver or warehouse staff scan each item against the order; anything missing or wrong shows up immediately. Scanning again at handover confirms the right goods went to the right customer. Two scans, and most "wrong product" complaints disappear.

What drivers need from a POD app

If the app is slow or fiddly, drivers will skip it or click through it. Look for:

• Few taps per stop. Confirm, name, done — for most customers.
• Big buttons that work with gloves, in cold rooms and in winter.
• Works on the phone they already have, ideally as an Android app and in the browser.
• Navigation built in, so they don't jump between apps.
• Clear instructions per stop: what proof this customer needs, delivery notes, access codes.

Ask two or three of your drivers to try it before you choose. They'll spot problems in five minutes.

Privacy and GDPR basics

Signatures, names and photos can be personal data, so treat them with care. General basics (not legal advice — check with your own adviser):

• Collect only what you need. If a name is enough for a customer, don't ask for a signature.
• Photograph the goods, not people. Ask drivers to avoid faces and number plates.
• Tell customers what you record and why, for example in your terms of delivery.
• Keep data secure and set a retention period that matches your accounting and dispute needs.
• Know where your data is stored. Many European businesses prefer providers that store data in the EU.

How to roll it out to drivers

A practical rollout plan:

1. Start with one route and one or two experienced drivers for a week.
2. Set proof levels per customer before go-live: most on name only, a few on signature or photo.
3. Explain the "why" to drivers: fewer angry calls, fewer arguments at the door, proof that protects them too.
4. Fix the friction they report, then extend to all routes.
5. Review disputes after a month. Look at which customers still cause problems and raise their proof level.

Proof of delivery with BeeRoutes

BeeRoutes includes proof of delivery as part of planning and delivering, not as a separate tool. You set the proof per customer — receiver name only, or signature and/or photo where needed — and it is saved with the order. Drivers scan barcodes when loading the truck and at handover, record delivered quantities, and failed deliveries go back into stock. Invoices are created from the orders and emailed as PDF.

Drivers use the Android app or the web app on any phone, with built-in voice navigation, while the office follows progress on a live map. Routes come from route optimization that respects time windows and truck capacity, and your data is stored in the EU. It suits food wholesalers as well as building-supply and drinks distributors.

See the pricing — plans start at €49/month for 3 trucks — or start your free trial: 14 days, no card required.