A paper delivery slip isn't just old-fashioned. It's a bottleneck in your invoicing, a source of customer disputes, and a surprisingly common reason that a company has no real-time picture of what's going on in its own warehouse. ePOD — electronic proof of delivery via an app on the driver's phone — is one of those changes that looks cosmetic but, six months in, has quietly rewired half the business.
Before the detail, briefly what this means in practice. After unloading, instead of handing the customer a slip with a stamp, the driver hands over a phone or tablet. The customer confirms receipt with a signature on screen, maybe adds a note ("one pallet damaged"), takes a photo, and all of that — with geolocation and timestamp — flows to head office immediately. In the ERP (Comarch Optima, enova365, Subiekt, Microsoft Dynamics AX) the delivery note's status changes within a minute of unloading, not the next morning when someone in the back office retypes a stack of slips.
It's a simple tool. But in practice it resets three things that typically drag on for years in a distribution SME.
What actually changes
First: time from delivery to invoice. In the classic flow a driver finishes the route, drops off the folder of slips, someone in the office enters confirmations the next day, only then is the invoice issued. Between goods leaving the truck and the invoice going out, 2-4 working days easily pass. With 30-day payment terms, that's effectively 15% of the collection period lost before the paperwork has even moved.
Second: complaints without the "who signed what" argument. A photo of the pallet plus a signature with a timestamp on the customer's phone ends the debate over whether that missing crate was already gone at unloading or disappeared later. A couple of these a year can eat more office time than the entire ePOD rollout.
Third: real-time fleet visibility. The dispatcher sees on the map where drivers are, what they've already unloaded and what remains. This isn't spying — it's the only way to answer a 2 pm phone call with "no, your delivery wasn't skipped, the driver is 20 km away and will be at your site in half an hour". Without ePOD that answer requires a call to a driver who happens to be unloading somewhere else.
What this looks like at a real customer
An example from last year. A 32-person building-materials wholesaler near Krakow. Five drivers, 60-80 deliveries a day to construction sites and smaller contractor firms. The problem that brought them to us wasn't "we want ePOD". It was "we don't understand why our receivables keep locking up for a month".
Analysis showed the average time from unloading to invoice issuance was 3.8 working days. Not because anyone was slow, but because paper slips rode back with the drivers after the route, waited a day in the office, got entered into Comarch Optima in batches, and about every tenth slip had an unreadable signature or a missing document number and bounced back to the driver for clarification.
The rollout took six weeks: a mobile app for drivers, integration with Comarch Optima via API (automatic closing of delivery notes and triggering the invoice), geolocation from the phone's standard GPS, on-screen signature and photo. Nothing exotic — no AI, no blockchain, just an honest, workmanlike integration.
Three months in, the average time from delivery to invoice dropped to 0.4 working days — in practice: delivery in the morning, invoice in the afternoon of the same day. DSO (average collection time) improved by 4 days. Given their turnover, that freed up roughly PLN 180,000 of receivables that had previously just been waiting in the cycle. "A pallet was missing" complaints dropped by about two thirds, because every delivery suddenly came with a photo and a time-stamped signature.
It wasn't all sunshine. One driver came back after two weeks with a prepared argument for why the app was "impractical" and they had to go back to paper. The director's conversation with him took 20 minutes and consisted mostly of the director saying "we're staying with the app". The other drivers' resistance faded on its own within about a month, once it sank in that they no longer needed to drive back to the office in the evening to drop off the folder.
What not to do
The biggest traps aren't in the technology; they're in how you roll it out.
- Don't buy an off-the-shelf ePOD that doesn't integrate with your ERP. If delivery confirmations have to be retyped by hand from the ePOD panel into Comarch Optima, you'll save 20% of the effort, not 80%. All the value sits in the API.
- Don't start with all drivers at once. Three drivers on a two-week pilot will surface every problem that five would, without wrecking your invoicing.
- Don't skimp on the phones. A PLN 500 handset that dies on the third delivery will destroy trust in the system faster than a month of delays. A standard company phone with a cabin mount is plenty — but it has to actually work.
- Don't pretend you won't need to train customers. Some customers — especially older site foremen — will spend the first two weeks asking "where's my paper?". A short sticker inside the app ("this is your original slip, we're emailing a PDF") handles 90% of those conversations.
- Don't kill the paper fallback on day one. Phones die, batteries drain, there's no signal in a basement. A paper slip in the driver's folder as a Plan B costs nothing and saves one nervy delivery a month.
Side note: if the ERP you use has no documented API (it happens, especially with older versions), ePOD suddenly becomes more expensive, because integration needs a workaround rather than a clean interface. Worth knowing before you sign with an app vendor — not halfway through implementation.
When it pays off
Rough rule we use in first conversations: ePOD is worth doing from at least three drivers and at least 30 deliveries per day. Below that, the time-to-invoice gain is too small to pay back the licence and rollout in a reasonable period. Above it, each extra delivery is another 2-3 minutes saved in the office.
The second scenario where it pays off regardless of scale: if in the last year you had even one serious "you didn't deliver the full load" complaint that cost you money or a customer. A single photo with geolocation and a signature can win that argument before it properly starts.
ePOD isn't about technology. It's about the company knowing in real time what just left the warehouse and where it ended up — and about the invoice being able to go out the same day.