Can I use Gtin at check out when scanning a product instead of SKU?

[Evansq]

Hi there,

When scanning a product at check out can the program look up the barcode against the GTin database as well as the SKU. I don’t want to use the GTin as SKU as I need the SKU for re-ordering purposes. 

thank you 

[Arie]

Hey @Evansq,

Thanks for writing in and welcome to our community 👋

With Square for Retail, you can enter either SKU and GTIN for an item, or both. If you have GTIN barcodes, you can create items directly from the app by scanning the code. Here's how:

1. From the Navigation menu, tap Items.
2. Under All Items, tap Create Item.
3. Tap Product lookup and scan the GTIN associated with the item(s) you want to create using a compatible barcode scanner or the built-in camera on your device.
4. Select the item from the Product lookup screen, and tap Continue.
5. From here, select suggested variations to apply to the item or scan the GTINs associated with the variations you’d like to apply. Then tap Add variation(s).
6. Tap Save.

Let me know if you have any other questions! 

[Evansq]

Hello Arie,

I got that far, the issue I'm having is at checkout when I scan the Gtin barcode on the product although the Gtin is recorded in the system I get an error message on the register saying that code doesn't exist. it's almost as if the register is only looking for the barcode in the SKU database and not the Gtin database.

Is there a way around it? 

Many thanks 

Evans

[Arie]

I see, thank you for describing what you're seeing a bit further @Evansq!

On your Square Register , are you using the Square for Retail, or standard Point of Sale application? 

[Evansq]

square for retail

[JustinC]

Stepping in for Arie - as long as the GTIN number is added into the SKU line of the edit item page, your barcode scanner should read it. 

Since that's not the case for you, next steps are to reach out to the Retail Team so they can try to reproduce the issue you're experiencing. If they are running into the same thing, they'll notify the Product Team and correct the error for you.

@Evansq