Closed hangy closed 8 months ago
In addition, we could just accept AI strings in the API, e.g. /api/v3/product/(01)3274080005003(15)230501(3103)000123 would return the product 3274080005003
I think it could be advantageous for the API to accept other types, too. Otherwise. each app/client would have to be able to parse all the GS1 barcode variations, as well.
I think this will be satisfied by #9791
New barcodes like GS1 DataMatrix, GS1 QR Code, and GS1 Digital Link can contain more information than the GTIN (AI (Application Identifier) = 01). For example, they can contain the product weight for variable weight items, and the "best before" date.
Example
(The string is split into multiple lines for readability. The AI string returned from
libgs1encoders
doesn't contain newlines.)Proposal
GS1::SyntaxEngine::FFI
after a successful run ofscan_barcode
,TBD: API integration
This would only solve product search from images uploaded from the web. (Mobile) apps that use the API need some way to search by the new GS1 barcodes and/or the AI data string.
Part of
8333
Depends on
9013