Why use NFC cards for Fruit Transport Documents (SPB)?

Every truck of palm fruit leaves the estate with a delivery note (SPB): the truck's plate, the note number, and how much fruit came from each block. The mill needs that data the moment the truck reaches the weighbridge, to match what arrives with what was harvested. The question is how the data gets there.

The options

• Paper. Cheap and familiar, but someone at the mill types it again, while trucks queue. Numbers get mistyped and the same note can be entered twice.
• Send it over the network. The cleanest on paper, but most estate blocks have no signal, and the note has to exist before the truck leaves, not when a phone finds coverage.
• A printed QR code. No typing, but a QR code on paper gets wet, folded and covered in dust on the way, and a long note makes a dense code that is hard to scan.
• An NFC card. The data is written once at the estate, travels with the driver, and is read at the mill with a tap.

What the card gets right

• It needs no network on either end. The estate writes it offline, and the mill reads it offline.
• It survives the trip. The chip sits inside plastic, so mud, rain and a driver's pocket don't matter, and the card can be reused.
• Reading is one motion. No aiming, no focusing, no lighting. The operator taps and the reader does the rest, which keeps the weighbridge queue moving.
• The data arrives exactly as it was written. Nobody types it, so nobody mistypes it.
• Each card has its own UID, saved with the note, so you can tell later which physical card a record came from.

What it costs

A card holds very little. A MIFARE Classic 1K has under a kilobyte of usable memory, so the note is stored as compact text: the header, then one row per block, with separators instead of field names. That is enough for a delivery note, not for photos or signatures.

A card is also just a carrier. Anything can be written to it, so the reader cannot trust it. OneTap-SPB checks the field count of every row and that harvest and loose fruit are valid numbers, and a card that fails is not saved at all. The note number is the database key, so tapping the same card twice, or on two weighbridge PCs, never creates a second record. If a note already exists, the operator sees the saved data next to the card's data and decides.

Then there's the hardware. Cards come in families that are read differently (Ultralight and NTAG, Classic with its keys, Type 4), readers get unplugged, and the network to the database drops. The app has to handle all of that without freezing, because the operator has a truck waiting.

Where it fits

NFC is not the right answer everywhere. If the estate had reliable signal, sending the note to a server would be simpler. But for a small, structured piece of data that has to move with a physical object through places without coverage, a card that costs very little and reads in a second is hard to beat. GEMA Plantation uses the same idea in the field, moving harvest data between phones; OneTap-SPB is where that card finally lands in the mill's database.