Blog

Zoho ERP Proof of Delivery: How to Close Every Drop the Right Way

Bipanjeet Singh
November 4, 2026

Short answer Zoho ERP proof of delivery makes a delivery agent take a photo, enter a code sent to the customer, or both, before marking a shipment as delivered in a delivery run. You switch it on in the Beats preferences. Zoho ERP’s help documents it in the Beat – Zoho ERP Android app, and the September 2026 update adds it to the iOS app. Delivery runs are in early access.

Last updated: November 12, 2026 · 10 min read

The van comes back in the evening, and the driver says all eighteen shops took their stock. Two days later, one shop owner calls to say the cartons never came.

Without proof, that call turns into an argument. With proof of delivery, it turns into a lookup, because the driver could not have marked that shop Delivered without a photo or the customer’s own code. The September 2026 update brings delivery runs and proof of delivery to the Beat app on iOS, so more of your delivery team can use it.

Who this guide is for

This guide is for owners, dispatch heads and sales coordinators who ship to many customers a day from Zoho ERP, or plan to. It also suits distributors who run their own vans. You will learn what proof of delivery checks, how delivery runs carry it, what the update adds on iOS and Android, how to set it up, what happens to a failed drop, and what Zoho has not documented yet.

Key takeaways
  • A delivery run groups shipments and assigns them to one delivery agent for one date. Unlike a beat, it needs no route or journey plan.
  • Proof of delivery means photo capture, a verification code, or both. At least one method must be on, and you set it under Settings, Module Settings, Beats.
  • Photos come from the camera only: up to 5 per delivery, and the app does not accept gallery uploads.
  • The code goes by SMS to the contact’s Mobile field. A number in Work Phone gets nothing, and an empty Mobile field blocks the delivery.
  • Platforms: the update lists delivery runs and proof of delivery for iOS. Zoho ERP’s help pages document both on Android. Delivery runs are still in early access.
  • October 2026: the Beat app adds customer location updates on iOS, plus catalog items in off-beat quotes and sales orders and PDF downloads on Android.

What is Zoho ERP proof of delivery?

Proof of delivery is a preference in Zoho ERP’s Beat Management. Its Beat Management preferences page puts it plainly: “Delivery agents must submit proof before they can mark a shipment as delivered. At least one proof method must be enabled.”

In practice, there are two methods, and you can turn on one or both:

Method What the agent does Rules Zoho documents
Photo capture “The agent takes a photo at the point of delivery.” Up to 5 photos, taken with the device’s camera. Gallery and file manager uploads are not allowed.
Verification code “A unique code is sent to the customer. The agent enters this code to complete the delivery.” The code goes by SMS to the contact person’s Mobile field. Work Phone numbers do not receive it.

So the two methods prove different things. For instance, a photo shows the goods at the shop. A code shows that someone at the customer’s end received the SMS and handed the code to your agent. For high-value drops, we usually switch on both.

What the September 2026 update adds to Zoho ERP proof of delivery

The Zoho ERP product updates for September 2026 list separate changes for the two Beat apps. Here they are, word for word:

Beat – Zoho ERP iOS app Beat – Zoho ERP Android app
“The home page now opens to a beats overview showing the total, sales, and delivery beats counts, and a list of beats.” “You can now create quotes in sales beats.”
“Delivery runs are now supported, letting delivery agents view their delivery beats, their shipments, and mark shipments as delivered.” “Beats that were previously ended can now be restarted.”
“Delivery agents can now submit proof of delivery for delivery beats.”
“Beats that were previously ended can now be restarted.”

However, the help pages tell the other half of the story. Zoho ERP’s Delivery Runs help page already walks through delivery runs and proof of delivery on the Android app, step by step. In other words, the update brings iOS up to what Android agents can already do. As of November 4, 2026, no Zoho ERP help page documents the iOS app itself.

October 2026: more Beat app changes

A month later, the Zoho ERP product updates for October 2026 added three smaller Beat changes. None of them changes proof of delivery itself, but they help the same field team:

  • iOS, customer location: “Salespersons can now update the location of their customers from the Beat – Zoho ERP app. This applies to customers who don’t have the latitude and longitude details on record.”
  • Android, off-beat orders: “If off-beat transactions is enabled for your organization, salespersons can now select items from your item catalog and add them to quotes or sales orders they create for customers.”
  • Android, PDFs: “Salespersons can now download the quote, sales order, or payment they create for their customers as a PDF.”

The location update matters for delivery runs too. Because you drag customers into drop order on a map, a shop with no coordinates is hard to place. So ask your sales team to fill in missing locations on their next visit. For every other change that month, see our Zoho ERP October 2026 update summary.

How do delivery runs carry Zoho ERP proof of delivery?

Proof of delivery lives inside a delivery run. In Zoho’s words, “A delivery run groups a set of shipments and assigns them to a delivery agent for a specific date.” Also, “Unlike beats, delivery runs are not tied to any route or journey plan,” so you can create one for any day’s dispatch.

Then each run moves through four statuses:

Status What it means What you can still do
Draft Created, not confirmed. The agent cannot see it yet. Edit details, add or remove shipments, delete
Scheduled Confirmed. The run now shows up in the agent’s Beat app. No edits. Reassign the agent or delete only
In Progress Started on the delivery date. The agent is making drops. Mark shipments delivered (with proof) or failed
Completed Stopped. Every shipment is delivered or failed. Search and review

In addition, two date rules matter here. First, “A delivery run can only be started on its delivery date.” Second, “Shipments can only be marked as delivered on the delivery run’s delivery date.” As a result, nobody can back-date a drop a week later.

How to set up Zoho ERP proof of delivery, step by step

The steps below follow Zoho ERP’s Distribution overview, Delivery Runs and Beat Management preferences help pages.

  1. Turn on Beat Management

    First, go to Settings, then Setup & Configurations, then Configure Modules. Check Beat Management under Distribution, agree to the terms and click Save. Beat Management then shows on the left sidebar.

  2. Ask Zoho to enable delivery runs

    Next, write to support@zohoerp.com. Zoho’s note says delivery runs are “currently in early access”, so they have to switch them on for your organisation.

  3. Add your delivery agents

    Then add each driver or delivery person as a salesperson and mark them as a Delivery Agent in the Salesperson module. Only those people appear in a run’s Delivery Agent field.

  4. Switch on Zoho ERP proof of delivery

    After that, go to Settings, Module Settings, and click Beats under Distribution. On the Preferences tab, check Require proof of delivery, pick Photo capture, Verification code or both, and click Save.

  5. Fix the customer Mobile numbers

    Before the first run, check every delivery contact. The code only reaches the Mobile field, and “Deliveries cannot be completed if the selected contact person’s Mobile field is empty.”

  6. Create and schedule the delivery run

    Now go to Beat Management, Delivery Runs, + New. Fill in the name, date and agent, select the shipments, and drag the customers into delivery order on the map. Save it as a Draft, then click Mark as Scheduled.

  7. Deliver with Zoho ERP proof of delivery in the app

    Finally, on the delivery date the agent taps Start Beat in the Beat app. At each shop they select the shipments and tap Submit Proof, take the photos, send the code to the contact, and tap Verify & Mark as Delivered.

A worked example: 18 shops, one van

For example, take a distributor of electrical fittings and hardware that serves retail shops across one side of the city (sample data). Its dispatch head sets up one delivery run for Tuesday:

Field Value
Delivery run DR-0047, “East market, Tuesday”
Delivery agent The van driver, added as a Delivery Agent
Shipments 31 shipments for 18 shops, dragged into drop order on the map
Proof of delivery Photo capture and verification code, both on

How the Tuesday run goes with Zoho ERP proof of delivery

First, the driver starts the run in the Beat app on Tuesday morning. At each shop, they take a photo of the cartons on the counter. Then they send the code to the shop’s contact and type in the number the owner reads out. Sixteen shops go through like this.

However, two drops go differently. Shop 11 has its shutter down, so the driver marks the delivery as failed with the reason “Shop closed”. At shop 14, one of three cartons arrives damaged. So the driver delivers two shipments with proof and marks the third as failed with a reason. As a result, Zoho ERP shows that shop as Partially Delivered.

16 of 18

Shops marked Delivered, each with a photo and a verified code

Sample data

2

Failed shipments that become available for the next delivery run

Zoho ERP behaviour · sample data

Two days later, shop 6 calls to say its cartons never came. Now the dispatch head opens DR-0047. Shop 6 shows Delivered, and with both methods on, the driver could only get there with a photo and the code from the shop’s own mobile. So the conversation starts from that fact, not from the driver’s word.

Still settling delivery disputes on the phone? We set up beat management, delivery runs and proof of delivery in Zoho ERP, clean your customer mobile numbers, and train your drivers on the Beat app.

Book a 30-minute call

What happens when a delivery fails?

A failed drop does not vanish. The agent records it with a reason, and Zoho ERP keeps the shipment in play: “A shipment marked as failed will be available for the next delivery run.” Also, “A shipment marked as failed can be re-marked as delivered if the delivery is completed later.”

Meanwhile, each customer in the run gets a status that updates by itself:

Customer status When Zoho ERP shows it
Yet To Be Delivered No shipment delivered or marked as failed yet
Delivered All shipments delivered
Delivery Failed All shipments marked as failed
Partially Delivered Some delivered, others pending or failed

Finally, the run cannot close with loose ends. “You cannot stop a delivery run while shipments are still pending.” So every shipment ends the day as delivered or failed, and none sits in limbo.

The same discipline helps upstream. If your receiving team already checks goods at the door with Zoho ERP three-way matching, proof of delivery closes the loop at the other end of the chain. And if the goods left on a challan rather than an invoice, use the proved drop as your cue to invoice the delivery challan.

BS

From the implementation floor

The setting takes two minutes. The customer master takes longer. When we move a distributor onto Zoho ERP, the old system’s phone numbers often land in whichever phone column was free. With verification codes on, every contact without a Mobile number becomes a delivery the driver cannot close. So we clean the Mobile field first, run one pilot route, and only then switch on codes for every run.

What Zoho has not documented about Zoho ERP proof of delivery yet

Based on Zoho ERP’s pages as of November 4, 2026, these points are still open:

  • The iOS app. The update lists delivery runs and proof of delivery for iOS, but the help pages only show the Android screens. Zoho does not say whether iOS uses the same photo limit and code flow.
  • Where the proof shows. Zoho does not document where an admin views the photos and code afterwards, or whether they appear on the shipment, invoice or customer record.
  • Proof from the web app. The web section carries a note that you must capture proof “such as a photo or OTP verification” before marking a shipment Delivered, but it does not show how an admin does that from a desk.
  • Offline use, location and time stamps. Nothing is documented about delivering without a signal, or about a location tag on the photo.
  • Restarting ended beats. The update says ended beats can be restarted on both apps. The help pages do not show the steps yet.
  • Plans and SMS. The pricing page lists Beat management and the Beat app, but we could not read which plan carries delivery runs. Zoho also does not state SMS limits for verification codes.

None of these stop a pilot. Rather, they are points to test with your own routes and customers, which is the kind of work a Zoho ERP implementation partner should do before your whole fleet depends on it.

Related reading: every change in the September 2026 update, inventory management in ERP, and Zoho ERP batch tracking.

Frequently asked questions about Zoho ERP proof of delivery

What is proof of delivery in Zoho ERP?

It is a Beat Management preference. When you turn it on, delivery agents must submit proof before they can mark a shipment as delivered in a delivery run. You choose photo capture, a verification code sent to the customer, or both. At least one method must be on.

Does the Zoho ERP Beat app support proof of delivery on iPhone?

Yes, according to the September 2026 update: “Delivery agents can now submit proof of delivery for delivery beats” on the iOS app, which now supports delivery runs. Zoho ERP’s help pages document the full flow on the Android app. As of November 4, 2026, no help page shows the iOS screens.

Can a delivery agent upload a photo from the phone gallery?

No. Zoho ERP’s help says the agent can add up to 5 photos, taken only with the device’s camera. The app does not let the agent upload photos from the gallery or file manager. So the photo has to be taken at the drop itself.

Why is the customer not getting the verification code?

Check the contact’s Mobile field. Zoho ERP sends the code by SMS only to the Mobile field of the customer record. Numbers in Work Phone do not receive it, and if the selected contact’s Mobile field is empty, the agent cannot complete the delivery.

What happens to a shipment marked as failed?

The agent records a reason, and the shipment becomes available for the next delivery run. If the delivery happens later, you can re-mark it as delivered. A run cannot be stopped while any shipment is still pending, so each one ends as delivered or failed.

Do I need a route or journey plan for a delivery run?

No. Unlike beats, delivery runs are not tied to any route or journey plan. You pick the shipments, a delivery agent and a date, then set the drop order on a map. Delivery runs are in early access, so ask Zoho at support@zohoerp.com to enable them.

Conclusion

In short, Zoho ERP proof of delivery turns “the driver says it was delivered” into a photo and a code on the record. The setting is small. The real work is clean customer mobile numbers, delivery agents who know the app, and a dispatch team that plans every day as a delivery run.

So, one question for your next dispatch review: how many of yesterday’s drops could you prove today?

Prove every drop your vans make

Digiwah, a Zoho Authorized Partner, sets up Beat Management, delivery runs and proof of delivery in Zoho ERP, and trains your dispatch team and drivers to run them.

Book a 30-minute call

Prefer to write? Tell us how your deliveries run today.

Bipanjeet Singh

Team Digiwah

Business automation expert at Digiwah — helping companies implement Zoho, AI tools, and digital operations that actually work.