Lightspeed K-Series variable-weight barcodes
Lightspeed K-Series cannot read variable-weight barcodes from your scale. No POS migration needed. A small piece on top closes the gap in about four days.
Lightspeed K-Series cannot read variable-weight barcodes. It does barcode lookup: it sees your EAN-13 and matches it 1 to 1 to a product, ignoring the weight or price the scale embedded in that barcode. That is a hard limit of the product, not a switch hiding somewhere. If you run fresh-cut products on a scale (cheese, meat, deli), you do not need to replace your whole POS for this. A small piece on top closes that one gap, in about four days, with no second licence. This happened for real at a speciality food shop in Ghent. Below I explain plainly how I fixed it.
What is a variable-weight barcode?
If you have worked with a scale in a deli, you know them. It is an EAN-13 with prefix 2, then five digits of product code, then five digits with the weight or price embedded. The printer at the scale prints one label per piece of cheese or piece of meat. The cashier scans it, and the till needs to read those last five digits to know the price. A plain fixed barcode on a wine bottle does not work this way, there the price lives in the product. With weighed products the price sits inside the barcode itself, and that is where it pinches.
Why does my scale’s barcode not work on K-Series?
Because K-Series only does barcode lookup. It sees your EAN-13 and finds the matching product, one to one. The embedded price or weight in those last digits is not read. Scan a 250-gram cheese label and K-Series finds the product “cheese”, but not the 2.50 euro the scale put in there. That is not a config switch turned off somewhere, it is a hard limit of the product. Lightspeed Retail X-Series supports it, K-Series does not.
Do I need to migrate my whole POS to X-Series?
That is the reflex, but usually not needed. Lightspeed Retail X-Series does support variable weight, so you could switch. But then you run two Lightspeed products side by side, two subscriptions, two setup tracks, and two places where your customer data lives. For one gap in one of your two locations, you feel like you are bringing a tank to a mosquito fight. The question is not which POS can do this, it is whether you should rip out your whole till for it. Almost never.
How do you connect a scale to Lightspeed K-Series without migrating?
With a small piece on top of K-Series, instead of replacing K-Series. It is a bridge that closes the variable-weight gap and touches nothing else. Concretely, the piece does this:
- Reads the scale over the serial port.
- Pulls the product info via the K-Series API.
- Calculates the price (weight times price per kilo).
- Prints a label the till can handle, or pushes it through as an open-quantity item in K-Series.
The till itself, K-Series, stays K-Series. The bridge only fills the gap. Classic a la carte on top of your existing SaaS. I do not replace your till and I am not a POS vendor, I add the missing piece on top.
How much work is a bridge like this?
For a speciality food shop in Ghent I estimated the bridge alone at about four days. No second POS, no second licence, no migrating customer data. Compare that to a parallel Lightspeed install plus a duplicate licence that comes back every month, even when you no longer need it. About four days of one-off work versus a fixed cost that never goes away. The work runs from 100 euro per hour (excl. VAT), and it stays a short, bounded job.
Why a separate desktop app and not a till plugin?
The short version. It runs as a normal desktop app on the shop’s Windows machine. It updates itself, so no one has to fiddle with it. That is exactly what you want for a machine nobody likes to touch. There is a solid reason underneath: for a steady, lasting connection to the scale over the serial port, this kind of app is simply more stable than a plugin inside the till. Not a fashion choice, just what holds up on a shop floor.
Frequently asked questions
Does Lightspeed K-Series support variable-weight barcodes?
No. K-Series only does barcode lookup: it matches your EAN-13 1 to 1 to a product and ignores the price or weight the scale put in the last digits. It is a hard limit of the product, not a setting turned off somewhere. Lightspeed Retail X-Series does support it, K-Series does not.
Can I connect my scale to Lightspeed K-Series?
Not directly for variable weight, but yes with a small piece on top. It reads the scale over the serial port, pulls product info via the K-Series API, calculates the price, and pushes it through as an open-quantity item or as a label the till can handle. Your K-Series stays your K-Series.
What is an EAN-13 with weight or price embedded?
It is a variable-weight barcode: prefix 2, then five digits of product code, then five digits with the weight or price embedded. The scale prints one per piece of cheese or meat. A normal till needs to read those last digits to know the price, and that is exactly what K-Series does not do.
Do I need to switch to X-Series to fix this?
Usually not. X-Series does support variable weight, but then you run two Lightspeed products side by side, with two subscriptions and two places where your customer data lives. For one gap in one location, a small piece on top of K-Series is cheaper and faster than migrating your whole till.
How much does this kind of integration cost?
For a comparable shop I estimated the bridge at about four days of work, from 100 euro per hour (excl. VAT). One-off, with no second licence or monthly cost added. The first look is free, no strings, so you quickly know whether your case is also just a few days of work.
Do you replace my till or my SaaS?
No. I am not a POS vendor and I do not replace your Lightspeed. Your SaaS stays your foundation, I add the missing piece on top, a la carte. In this case that is only the bridge that handles variable weight, the rest of K-Series stays untouched.
Does this also work for a deli, butcher or cheese shop?
Yes. Anywhere you weigh fresh-cut products and the scale prints a variable-weight label, the same gap shows up. The bridge does not care whether it is cheese, meat or deli, it reads the scale and calculates the price the same way. You just keep the product codes and price per kilo in K-Series.
Recognise the gap? Fresh-cut products on the scale your till almost reads, and no appetite for migrating your whole POS over it. Let me come and look. The first look is free, no strings. Book a first look.