Why your delivery driver's app must work without signal (and what happens if it doesn't)

Your driver's app must work without signal because part of every route runs through neighborhoods, warehouses and buildings with no coverage, and a sale that cannot be recorded on the spot ends up scribbled on paper or forgotten. An offline-first app keeps everything on the phone during the day and sends it to the office on its own once it finds signal. If it does not work that way, your team goes back to the notebook exactly where you need control the most.

What happens when the app does not work without signal

Where drivers lose signal

Anyone who delivers water knows it: signal drops more often than you would think, and almost never somewhere convenient.

• Neighborhoods on the edge of town, hillsides and rural communities.
• Warehouses, canteen kitchens, basements and underground parking lots.
• Office buildings where the garrafón (the 20-liter returnable water jug) goes up to the third floor.
• A data plan that ran out in the middle of the week.
• Networks that saturate at busy hours.

The cost of writing it down and entering it later

With an app that requires a connection, the driver stares at a spinning wheel, the customer waits, and the fix is "I'll enter it later". That "later" has consequences that show up in almost every business:

• Double entry: the sale is written on paper at the stop and typed again at night, when the driver is already tired.
• Sales and payments that never reach the office because the note got lost or wet.
• Customer balances that differ between the app and the driver's memory.
• Arguments at settlement over gaps that are not theft, just incomplete records.
• A driver who, after two weeks, stops using the app because it gets in the way more than it helps.

That last one is the most expensive. You paid for a system and your operation still runs on a notebook.

What offline-first means, in plain words

Offline-first means that, during the day, the phone is the source of truth. The app does not ask the internet for permission to sell: it sells, saves and reports later.

The normal flow looks like this:

1. In the morning, with signal or on the plant's wifi, the phone downloads the day's route, the customers, their prices, their balances and what is loaded on the truck.
2. At each stop, the sale, the payment and the jugs delivered or returned are saved on the phone first, with a provisional receipt number.
3. Everything captured goes into a pending queue that sends itself when there is a connection.
4. The office receives sales as they arrive, and the server assigns each one its final receipt number.

The difference from an "offline mode" bolted on at the last minute matters. In an offline-first app, working without signal is the normal path, not the exception. A connection only gets the information to the office sooner.

What must work without signal and what genuinely needs a connection

What cannot depend on the internet

If anything on this list needs internet, the app was not built for the street:

• A sale with each customer's special prices.
• Payment in cash, by bank transfer with its reference, or on credit within the customer's limit.
• Payments toward outstanding balances. We explain how in selling on credit to stores without losing money.
• Full jugs delivered and empty ones collected.
• The receipt: printing it on a Bluetooth thermal printer, or opening WhatsApp with the text already filled in so it goes out as soon as there is network.
• The delivery evidence photo, which uploads later.
• The GPS location of the visit, which comes from satellites, not from mobile data.
• Route expenses, such as gasoline, with a photo of the receipt.
• Marking a stop as not visited, with its reason.
• Checking what is on the truck and how much is left to sell.

What does need signal, and that is fine

Some things no app can do without a connection, and a good vendor tells you so upfront.

The main one is card payments. A card payment is approved by the bank at that moment, so a terminal such as Mercado Pago Point needs signal to charge. The right behavior is for the app to enable the card button only when there is a connection and to explain why when there is not. Once the charge is approved, the sale follows the same offline path as always.

The same applies to changes the office makes during the day. If the office adds a special order at 11 a.m., the phone receives it when it has signal. And if the office watches each truck on a map, those positions wait on the phone and are sent once the connection returns. Neither should ever block a sale.

Pending items, rejections and settlement

How to know what is pending or rejected

Without signal, the driver's question is simple: did what I sold get through? The app should answer it at all times, with an indicator that shows one of these states:

• Synced.
• A number of items pending.
• Offline.
• A number of items rejected.

A rejection is not unusual. It can happen when the office changed something while the phone was offline and the server no longer accepts that entry as it was. The real problem is not finding out. The driver must see the rejection and its reason, and the office must resolve it before closing the day.

A good habit: before heading back to the plant, open the app somewhere with signal and confirm it says "synced".

Why you should not settle with unsynced sales

If the office closes the settlement with whatever has arrived so far while sales are still sitting on the driver's phone, the numbers will not match for the wrong reasons. There is extra cash that seems to have no sale behind it, product that looks missing even though it was sold, and the next step is usually an argument with the driver that never needed to happen.

The rule is simple: sync first, settle second. Repartamos, for example, does not let you close the settlement while the driver's phone has sales waiting to be sent; it can only be forced with a reason that gets recorded. We walk through the whole process in the driver's daily settlement.

If the phone is lost or stolen

The driver's phone holds your business information: customers, phone numbers, prices and balances. If it goes missing, what matters is cutting off access quickly.

1. Revoke the phone from the office dashboard. In Repartamos, a revoked phone loses access on its next connection and wipes the business data stored on it.
2. Change the driver's password.
3. Compare the sales that did sync against the cash and product that came back.
4. Install the app on the new phone, sign in and download the route.

Keep in mind: whatever had not synced before the phone was lost is gone with it. That is one more reason the app should send data on its own every time it finds signal, even if it is one minute at a store's doorway.

Questions to ask any vendor before buying

During the demo, do not settle for the slides. Ask them to do this in front of you:

1. Can I complete a sale, receipt included, with the phone in airplane mode?
2. What happens if I close the app or the phone shuts down with unsent sales?
3. Where do I see what is pending and what was rejected, and why?
4. Are each customer's special prices, balance and loaned jugs visible without signal?
5. Does it print the receipt without internet?
6. What happens if the office changes something while the driver is offline?
7. Can I revoke a lost phone from the office?
8. Does the settlement warn me when there are unsynced sales?

If the answer is "there is almost always signal" or "we can look at that later", you already have your answer. If you are comparing broader options, also read notebook, Excel or software.

Quick checklist

• Test the app in airplane mode before you pay.
• The driver downloads the route with signal before heading out.
• Sale, payment, collections, jugs, receipt, photo, GPS and expenses all work offline.
• Only card payments require signal, and the app says so clearly.
• A visible indicator: synced, pending, offline or rejected.
• Sync first, settle second.
• Lost phone: revoke it, change the password and reconcile what was synced.