Barcode format specification

The barcode will use the code128 specification. This format is easy to read and supported by a wide range of library and hardware barcode scanners. It also seems to be a standard in the delivery industry.

Since CoopCycle will support both internal and external barcodes, the internal ones will follow a specific format.

4 first bytes will be 6767 (the ASCII code for CC)
3 next bytes will be the instance id, this will be useful as on the long term CoopCycle will support delivery transfer between instances
The next byte will be the entity type
- 1 for task
- 2 for delivery (not sure to keep it)
The last bytes will be the entity id
If there is a package attached to it, the prefix P is used following by the task_package id then in case the quantity is $> 1$ the sign U followed by the quantity position
4 last bytes will be 8076 (the ASCII code for PL)

For example here is a barcode for a the task #420 in the demo instance (instance id 001)

https://barcode.tec-it.com/barcode.ashx?data=676700114208076&code=Code128&translate-esc=on

Internal and external barcodes can be solved via the endpoint /api/barcode

GET /api/barcode?code=6767 001 1 420 8076

{
    "ressource": "<https://demo.coopcycle.org/api/tasks/420>",
    "entity": {
	    "@id": "/api/tasks/420",
	    [...]
    }
}

Scanning process

Barcode technology is crucial in delivery, reducing errors and mental strain in parcel identification. By streamlining sorting and tracking, barcodes enhance efficiency and accuracy, ensuring timely and accurate deliveries. This saves time and minimizes human error, making the delivery system more reliable.

<aside> 💡 Each parcel/package should have a barcode. This way, it's possible to have multiple barcodes linked to the same delivery in case of multiple package drop-off or multiple drop-off deliveries.

</aside>

The process will look like this: