Hello, We’ve just launched a POS extension for verifying U.S. drivers licenses. We’re making use of the Barcode Scanner API to capture details from the ID. However, we’ve noticed an issue with how the Scanner API works, and we’re not sure how to work around it. The issue The scanner API only prov…

Hi @Dylan , thanks for the feedback. Unfortunately, this is due to the nature of subscribables, and the way they are held onto in memory on the POS side so long as the extension is running. I see this is a bad API design for your use case, so I think what we can look into is providing a reset() funct…

@JS_Goupil thanks for the note here! Any idea of a workaround for the time being? @Dylan if you figure out a workaround please share, and good luck in the meantime!!

@RobDukarski I don’t think there’s a work around for completely resetting the state of the data, if getting it to be undefined is what you’re trying to accomplish. Can you provide a specific example of what you’re trying to achieve on a higher level, and I’ll see if I can think of an approach?

@JS_Goupil For us, the biggest pain point is that merchants have to close the tile and re-open it to scan multiple barcodes. Since that’s the only way to clear the state of the data variable. We’ve tried using a ref in combination with the data variable from the hook, but still not able to find a w…

@Dylan , interesting, I would have thought that you can still scan multiple items serially without closing the modal. ie The scanner should replace the current value with the new value. You’re saying that’s not the case?

@JS_Goupil You can, but the problem is writing a useEffect that can differentiate between scans, since you can only depend on the data attribute. In our case we need to make an external API call to process the information on the barcode. So we need a loading state, then a results state. There’s q…

This may not be helpful but would it be possible to add some sort of unique event identifier to the data being sent each call so that if it receives the same identifier again it will know to ignore it and you can proceed like you want? Just trying to help think of a workaround for the time being…

@RobDukarski yes potentially. I think there’s still some complications around rescanning the same data again in case of a network outage/API outage. The merchant wouldn’t be able to rescan because the data would effectively been the same twice. The identifier couldn’t rely on the barcode data alon…

Hello @Dylan @JS_Goupil Have you found a solution for this problem? I’m facing the same issue, the merchant needs to scan the same item multiple times do the useEffect is not triggered

Sorry @Tiago_Ramalho I don’t have a workaround yet. This is a real productivity killer for merchants. Paired with the issues with the Scanner API + no Camera API, it really hurts timely checkouts. Merchants have to literally close the tile in order to refresh the state of the Scanner API. I don’…

Scanner API state does not reset

Extensions

Gunes February 4, 2026, 10:30am 14

Let’s do a little trip down the memory lane, shall we?

Topic		Replies	Views
Scanner API is returning stale data, again. v2026-01 Extensions pos-extensions	13	151	February 27, 2026
Camera scanner adds leading 0 to barcode Extensions pos-extensions	2	115	October 15, 2025
POS UI Extension - useScannerSourcesSubscription is [] on initial tile load Extensions pos-extensions	4	111	January 29, 2025
Physical scanner no longer works on non-initial pages Extensions pos-extensions	3	42	March 26, 2026
[Bug] Urgent POS Extension Camera detection Extensions pos-extensions	4	65	May 28, 2026

Scanner API state does not reset

Related topics