Price encoded as the product identifier
Changing a price would create a different scan value and can break the POS mapping.
Map the identifiers, names, SKUs and prices already maintained in your product sheet to one reusable label. BatchLabel checks the selected barcode structure per row and keeps the human-readable price separate, so a price update does not silently alter the encoded product number.
Choose a CSV or XLSX to continue in the full mapping workspace. Nothing is uploaded.
A practical workflow
Keep the assigned EAN/UPC as text and include the display price and SKU in separate columns.
Map the code format explicitly, then filter missing values or checksum errors before layout.
Print and scan representative products, checking price text against the point-of-sale record.
Avoid rework
Changing a price would create a different scan value and can break the POS mapping.
Retail variants may require distinct identifiers even when the product name is shared.
BatchLabel does not automatically connect to a POS or synchronize prices.
Retail assignment, legal pricing display and print-grade requirements remain the merchant's responsibility.
Questions, answered
It can render and structurally validate numbers you provide, but it does not assign GTINs or confirm that a number belongs to a product.
Yes, as separate projects or templates that map the same columns differently. Test each stock and size because their layout and scan conditions differ.