Zettle issue with S700 barcode reader.

[bionicbillia]

I have a issue with using a S700 socket mobile barcode reader. If I try reading a manually or tablet camera read barcode that was setup it works with only the camera not the s700 it give message barcode not found create new product yes or cancel. Even if I edit a product and scan the code in it still does not work the only way is to get the s700 to read the codes is to recreate all my entered products it like there is a special code section that only work if its set up with the s700. Please fix this bug.

[thousandlakes]

I have the same problem. Have created several barcodes with the iPad camera only to find that my just received Socket doesn't recognise them. I have an event in a week and really don't have the time to recreate already done work. It seems unlikely these two instances are the only ones, as I doubt the two post writers are nearby either. Could someone take the issue seriously, please? I bought the scanner for a large sum of money and was expecting full functionality (and highest quality obviously) from the get-go, as I am used to from other products of this suite. The OP posted in early May but apparently nobody has reacted yet. Any chance of fixing this awful issue soon? Right now I am quite disappointed. Thanks in advance!

[thousandlakes]

Returning to this issue after having tested the scanner again. Extremely frustrated at the moment, angry as well.

Here are the steps I took:

1. Remove already added barcode, which was entered with camera. Save changes.

2. Testing barcode by trying to add product to cart (by scanning with camera). Popup asks if I want to add a new product, obviously not since it already exists in WooCommerce. Clearly the data was removed, which is good.

3. Edit product again, add barcode with Socket S700, save. Data shows the same WooCommerce product id as earlier, which is as hoped.

4. Attempt to add product to cart with S700, since the barcode supposedly was added successfully above. Popup asks whether I want to add new product since Zettle doesn't recognise the barcode. No, really not.

How is this even possible??? The barcode was entered with the same device the second time and now it doesn't recognise its own work?

Yeah, this sort of ruins completely the smooth checkout process I had planned for the market in exactly a week's time. Now every product has to be scanned slowly with the iPad instead.

Could someone prioritise this, since it has been a topic starting from May? It is messing with people's livelihoods.

[thousandlakes]

Results of testing round 2.

Since I didn't mention the barcode type earlier, in case it has relevance, I am using Code-128 generated by a label-printing plugin for WooCommerce.

I tried a different method of adding the barcode this time. I entered the product id into the Barcode field under Zettle tab in WooCommerce product details.

After syncing this change to Zettle, the iPad camera once again recognises this barcode, whereas Socket prompts to enter a new product due to the barcode not being recognised.

The issue clearly is with Socket S700 data management and nothing else.

Politely, why claim that a barcode reader costing several hundred euros will work "smoothly" at checkout, when nothing is done to fix issues? Now customer experience will be appallingly slow, and there is a constant risk that anyone handling the valuable iPad back and forth will drop it to the floor. This makes for a completely unprofessional shopping experience as well as a very poor working environment for my assistant and me. I hope I won't lose sales due to a line forming and checkout being too slow. It has taken me hours of research to reach this point where the process could work wonderfully, yet the current end result still makes me appear as if I went for a cheap solution, have no care about customer service, and generally don't understand tech solutions. Fantastic.

[Lecutusuk]

Hi. I have investigated this… I had the same issue. I have looked at barcode symbologies that although the S700 will scan, for some reason does not like in combination with Zettle. You need to create the barcodes in Code128-A the it all works. Very simple fix, but then I own a mobile device solution business. It should not be this hard for a normal user. You wouldnt have £10k + barcode verifiers to analyse the issue. Any way… use Code128-A for your barcodes and it will all work Lee

[Mr_Geo]

Sorry but it doesn't . Yes the Socket scanner works on Socket app but not with izettle. izettle scanner should show in the izettle app - it use to when it worked!

[Lecutusuk]

Are you definitely in app mode and not key oard mode? Are you using IoS or Android? Have you fact reset the scanner? Pretty much all symbologies are ok except CODE-128 base

[Mr_Geo]

Are you definitely in app mode and not keyboard mode?
Yes 100% app mode but the scanner doesn't work in either keyboard or app in izettle

Are you using IoS or Android?
IOS as the S700 socket only works with IOS (in izettle apparently) - It has previously worked

Have you factory reset the scanner?
Yes we have reset the scanner - taken it back to factory setting and started again more than once

Used 128A coding as suggeasted in your op
This issue appear to be the compatablilty with the izettle app.
It use to work 100% in izettle which is why we spent £250+ on the scanner
Having exactly the same probelm as everyone in the thread.
The scanner would appear in the izettle app - it no longer does - the app does not recongnise the scanner but the device does (that must be why it works with the socket apps?)
Regardless of how many time you enter the barcode on a product with the S700 or the device on board camera into the izettle app it simply won't store the bar code. It used to work fine when "Available barcode scanner" showed the S700

[bionicbillia]

This is a more detailed look at the issue.

  1.  Create a product and type numbers in barcode box.

  2. Create a second product this time scan barcode with built in camera.

  3. Turn S700 barcode read on { Note Zettle notes barcode reader is connected.}

  4. Now try reading 1-3 note that non of the products read with reader Zettle inform me with pop up box

      [Barcode Not Found - Create new product YES/No].

   Now for fun.

  5. Create a new product and where barcode goes inset barcode with S700 reader. Save Zettle will still not find it. Same message barcode not found.

  6. Scans a new product barcode with message pop up go ahead and create that product save. This is the only way s700 reader works current as of version 7.49.0

  7. Warning if you have created barcodes by scanning them in and creating them what ever you do. Do Not ! disconnect the S700 reader from you device in bluetooth devices and reconnect it! All your work to set up the codes with the reader will no longer work will have to be reScanned. I found this out 😠

    PS after this happened to me we contacted PayPal this was 4 weeks ago. Still not fixed they were going to contact us back.

    I am also concerned that if we wish to use two iPads and 2 - s700 readers that it will only work with the one set it set up. also terrified to export/import the spreadsheet as it might wipe up what ever that make the s700 work.

[Mr_Geo]

A reply from izettle customer service team today re the S700 barcode reader not working in the izettle app

With regards to your recent complaint, let me inform you that the Socket mobile scanner connectivity issue has been created by Apple's new iOS release, we are aware of it and working out a way to fix it form our side.
Yet the scanner work perfectly in all of the the current Socket app but not in izettle? How is this a problem with the apple IOS?

We do not integrate Socket Mobile's software within our app, so we are unable to apply their fix at this time.
Isn't this rather obvious?

We continue to sell the scanners because the issue is only affecting iOS 16.5 and above and not all of our merchants are using this version of the software, as we currently support as low as iOS 14 - which is not affected by this. So, not selling them would exclude many users that are able to use this hardware.
So the answer is not to update but when most devices update automatically? Yet you haven't posted an notification not to update? 1/2 the user of an upto date expensive POS  can't use the system now as intended.
Our development team is working to fix the issue, and we will release an update as soon as we can.

So there's your answer - they have no idea when the issue will be fixed - and it's easier to blame apple when it's the coding of their app that is the issue
Make what you will of the replies from Customer service but it would appear they have no idea what they are talking about