Hi @tomasw,
This is not an end-user GQL question, but rather a question about how/why purchase order receiving at https://purchase-orders.shiphero.com makes certain calls.
Since the launch of case barcodes, we have noticed that the receiving page (https://purchase-orders.shiphero.com/purchase-orders/details/XXXX/receive) hangs on just about every scan. Digging in a bit further, it looks like each scan generates 3 calls for a product barcode:
- an OPTION call
- a POST call to check if the scanned barcode is a case pack
- a POST call to check if the scanned barcode matches a product
The total time for these tends to come in around 2 seconds, but has lingered as long as 8.
I’m curious why you aren’t matching the scanned barcode against the product payload that is loaded on the prior page? I see that the product data does not (yet?) contain the case barcode so I can understand the network call for the case pack, but is there a reason for a network call for matching a scan to a product? For us, at least, this call makes up the majority of the lag.
Thanks!
David