Supporting SKU with multiple barcodes during the picking
How-to Guide
Author:
Fluent Commerce
Changed on:
4 Feb 2025
Key Points
A typical scenario where the EAN 13 barcode (e.g., `0123456789123`) and sometimes the barcode on the physical product might not include the leading 0. So when the product gets scanned, it will return `123456789123` rather than `0123456789123`, and the Pick screen will not be able to find the product from the pick list.
We can utilize product attributes to include possible barcodes and to include fields.
Steps
Adding the setting
Setup the setting: fc.mystique.fields.picklist
display barcode in product page
Putting it all together: animation
Video to demonstrate scan barcode and search in attributes.
barcode value must be unique across the system
The business is responsible for ensuring all barcode values are unique across all products, as duplicate values might prevent scanned items from not being found.
Fluent Commerce
1{2"query":"query ($waveId: ID!) { pickwave:waveById(id: $waveId) { items(first: 100) { edges { node { quantity product { name ... on VariantProduct { __typename ref gtin stdProduct:product{ ... on StandardProduct{ __typename ref attributes{ name value } } } catalogue { ref } attributes { name value } categories(first: 1) { edges { node { name } } } } } } } } }}",3"startQuantityAtMax":false,4"dataSource":"pickwave.items",5"attributes":[6{7"label":"i18n:fc.sf.ui.wave.pickAndPack.list.pick.column.productName.heading",8"value":"{{img product.attributes.byName.imageUrl product.attributes.byName.imageUrlRef alt='alt' width=50 margin='0.5em'}} {{product.name}}",9"sortBy":"product.name"10},11{12"label":"Barcode",13"value":"{{product.gtin}}",14"sortBy":"product.gtin"15},16{17"label":"StdProductName",18"value":"{{product.stdProduct.ref}}",19"sortBy":"product.stdProduct.ref"20},21{22"label":"brandname",23"value":"{{product.stdProduct.attributes.byName.imageUrl}}",24"sortBy":"product.stdProduct.attributes.byName.imageUrl"25},26{27"label":"i18n:fc.sf.ui.wave.pickAndPack.list.pick.column.sku.heading",28"value":"{{product.ref}}",29"sortBy":"product.ref"30}31],32"scanner":{33"scannerFields":[34"product.gtin",35"product.attributes.byName.BARCODE1",36"product.attributes.byName.BARCODE2"37],38"filterFields":[39"product.gtin",40"product.attributes.byName.BARCODE1",41"product.attributes.byName.BARCODE2"42],43"rowId":"product.ref",44"scanTimeout":200,45"incrementBy":1,46"toastTimeout":2000,47"highlightDuration":30048},49"rowExpansion":[50{51"component":"fc.card.attributes.grid",52"dataSource":"product.attributes",53"props":{54"exclude":[55"imageUrl",56"imageUrlRef"57]58}59}60]61}
The first scan was against the barcode from the custom attributes field upcs, which was not part of the `scannerFields`. The Fluent STORE returns a "scanned item not found" message.Next, scan the custom attributes field BARCODE1, which returns a successful message.Then, scan the GTIN barcode, which also returns a successful message.
Adding the setting
