Definition
POD (Proof of Delivery, receipt) is a certificate that proves goods have been delivered and signed for, usually including delivery time, recipient, signed photo, electronic signature, GPS location, and cargo status. POD is used for logistics settlement, dispute resolution, customer confirmation, and timeliness assessment, and is core data for TMS, FMS, and supply chain visualization systems.
Digital POD replaces paper receipts, improving efficiency and reducing costs. POD data must be authentic, complete, and tamper-proof; in some scenarios, it needs to be combined with blockchain and electronic seals to enhance legal validity.
Technical Features
POD collection relies on devices such as PDAs, mobile apps, and in-vehicle terminals. Drivers take photos, obtain electronic signatures, and record GPS at the delivery site, which are uploaded in real-time to the TMS platform via IoT SIM cards. In remote areas, underground garages, and other scenarios, IoT SIM cards need to ensure network coverage and connection stability.
Use Cases
POD is widely used in express delivery, same-city distribution, cross-border logistics, fleet management, cold chain distribution, and other scenarios. Drivers collect signed photos and electronic signatures through PDAs or mobile apps, which are uploaded in real-time to the TMS platform via IoT SIM cards. SimtoLink provides stable network connectivity and dedicated APN for logistics PDAs and in-vehicle terminals, ensuring real-time POD data transmission and supply chain visibility.
What a proof of delivery must contain at the same time
On an IoT SIM, POD means a delivery collected into a voucher that can be checked, not a driver tapping "complete." The voucher must be able to answer, at the same time: which shipment, when, where, who signed, and what was seen on site. Photo, electronic signature, and position are different elements. Missing one, the record is still a draft. The terminal must be able to read the waybill number when the sign-off happens, and it must be allowed to keep the whole voucher locally when there is no network. Uploading the photo first and the position later leaves the platform, for a while, with a picture that cannot prove arrival. When positioning fails in an underground garage or inside a plant, record the positioning failure. Do not fill in a base-station coordinate far from the unloading point and mark it signed.
The voucher must hang on the same shipment's transport history. A wrong waybill number means a clear photo still belongs to another shipment. Cold-chain goods should put the temperature reading at the moment of sign-off in the same package, so the temperature record and the sign-off record do not keep separate clocks. What is backfilled after the SIM returns is the whole package, using the terminal time of the sign-off, not the time the server received it. A repeat submit must hit the same voucher ID, so a driver tapping twice does not create two proofs.
The photo arrives, and the position is filled in later
A common mistake is to send the photo and signature first so the screen can finish quickly, and to send the position later. If that later send fails, settlement already sees "signed," and a dispute has no arrival position. Another mistake is to reuse the position cached at departure as the sign-off position. The vehicle is still on the road, and the proof already sits on the warehouse coordinate. The sign-off action should take a fresh position. If it cannot, mark the failure reason explicitly. Do not reuse the previous stop's coordinate.
A signature on behalf of someone else and a signature by the recipient are also easy to write as the same success. If the terminal has no mark for the signer's identity, or for a mismatch with the consignee on the waybill, later review cannot tell a normal proxy from a misdelivery. A photo that shows only the ground or a vehicle door should not pass an automatic check either. For acceptance, take one shipment through four cases: a normal outdoor sign-off, a failed position in an underground garage, a backfill after an outage, and two taps on submit. Only the first becomes a voucher that can be settled. The second stays pending evidence. The third keeps its time. The fourth is still one proof.
A failed position must not reuse the previous stop
At sign-off, take a fresh position. If it cannot be obtained, record the failure reason and leave the voucher pending evidence. Do not fill a coarse base-station position, or the previous stop's warehouse coordinate, and then mark it signed. Photo and signature may stay on the terminal first, but settlement must not see "signed" before the position state is explicit. Two taps create only one proof, with the same voucher ID. A proxy receipt must keep a mark that the signer does not match the consignee on the waybill.
The difference between an underground sign-off and an outdoor one is the positioning result. Do not synthesize the same success just so the screen can finish. For temperature-controlled goods, the reading at the sign-off moment stays in the same package, so the times can still be matched later. An outage backfill uses the sign-off time on the terminal. Outdoor success, failed positioning, outage backfill, and a duplicate submit correspond to settleable, pending evidence, time unchanged, and still one proof. That is a complete delivery voucher.
If the photo does not show the goods or the door number, an automatic check should leave the voucher pending evidence, not pass it on the signature alone. If the recipient refuses to sign, record the refusal reason. Do not change it into a successful signature by the driver. If a multi-piece shipment signs for only some of the pieces, the piece count on the voucher must be the count actually signed, and the remainder stays incomplete, so the whole shipment is not settled. If the waybill is reassigned during backfill, archive the old voucher against the original waybill. Do not hang it on the new waybill automatically.