Product handle used as a permanent SKU
URL handles can change with merchandising and may contain characters the receiving workflow does not expect.
Ecommerce catalogues often contain both marketplace identifiers and internal variant SKUs. BatchLabel lets you choose which value is actually scanned, while product title, option, location and price remain editable label fields for picking or stock organization.
Choose a CSV or XLSX to continue in the full mapping workspace. Nothing is uploaded.
A practical workflow
Include one row per sellable variant with a stable SKU and any assigned GTIN in separate columns.
Select the exact field and symbology expected by picking, packing or inventory software.
Test short and long product names, duplicate-looking variants and the intended scanner workflow.
Avoid rework
URL handles can change with merchandising and may contain characters the receiving workflow does not expect.
Rows with a shared product title can look identical if option columns are not mapped.
The MVP does not write changes back to a store or keep catalogue data synchronized.
Marketplace label and fulfilment requirements must be checked in their current official documentation.
Questions, answered
No. The local workflow starts from a CSV/XLSX export. Integration pages describe import preparation and do not imply an active OAuth connection.
Use the value expected by the scanner's destination. Internal picking may use an alphanumeric SKU, while retail channels may require an assigned GTIN.