Optical Store Software: Systems for Opticians and Costs 2026

The job bag has been sitting in the lab for nine days, and you find out because the customer walks in and asks. The lens order went out with the wrong axis, and you pay for the remake. There are four thousand euros' worth of frames locked in a drawer nobody has opened in two years. And in January, when the Sistema Tessera Sanitaria (the Italian Health Card System) deadline comes round, somebody spends three evenings fixing by hand what the software for opticians should have been recording at the counter, every day, for twelve months. None of these started life as a software problem. But they are all problems that software sees before you do — and yours told you about none of them.

This guide gives you eight questions to ask the salesperson before the demo. We wrote them while building our own system, and we know them because at the start we didn't have the right answer to most of them. They're built so they can't be recited: either the software does that thing, or you can see in three seconds that it doesn't. The argument of this guide is that on these eight things most optical store systems answer badly, and almost always in the same way — and at the end I'll tell you where we land, including the two we lose.

We know these eight questions well for a precise reason: we make optical store software ourselves. It's called RiVedi, and every one of these questions is something we actually had to solve — on several of them, at the start, we didn't have the right answer. You're on our site, so you already know who we're rooting for. But that's exactly why this list is made of things you can check in twenty minutes of demo: ours, or anyone else's.

Note. This article is for general information purposes and has a stated argument: that our system answers eight specific questions better than others do. The guidance on Sistema Tessera Sanitaria, invoicing and privacy reflects the regulatory framework as at July 2026, but it does not replace advice from your accountant or your DPO. What we describe are recurring behaviours of the market, read in July 2026 on the sites of products sold in Italy — not an accusation aimed at any one product.

The 8 questions to ask the salesperson before the demo

Take these eight questions to your next demo — ours included. They're built so that the right answer is hard to fake: either the software does that thing, or it's immediately obvious that it doesn't.

#	The question	Acceptable answer	🚩 Red flag
1	Does your Sistema TS module transmit by itself, or do you generate a file for me to upload to the portal by hand?	"It transmits from the software and hands you back the protocol number"	"We generate the XML file for you" (= you upload it)
2	Where do I decide whether an expense is AD or AA: at the counter or in January?	"At the counter, on the sales line"	"You sort it out later, at submission time"
3	Is refraction data encrypted at field level, or is the disk encrypted?	"Field by field, with a dedicated key"	"The server is secure" (that's not the same question)
4	Do you handle the lens as a matrix or as a stock item?	"As a matrix: sphere, cylinder, axis, index, coating"	"You enter it as a product"
5	Who can see the clinical record? Can I block a shop assistant from it?	"Role-based permissions, and every access is logged"	"Everyone gets in, there are only three of us anyway"
6	Do WhatsApp messages go out from a registered business number or from the shop assistant's phone?	"A registered number with approved templates"	"We use WhatsApp Web"
7	If I leave in three years, what do I take with me and in what format?	"The full history, in an open format"	"We'll export the PDFs for you"
8	What does my case cost, all in: two workstations and one store?	A number	"It depends", three times over

The next sections explain why each of these questions separates the software that works for you from the software you work for.

"Sistema TS certified" means nothing until you ask how

Practically every optical store software package claims to be integrated with Sistema TS. It's almost always true — and it almost always fails to tell you what you need to know, because the same word covers two different jobs.

Direct transmission: the software talks to Sistema TS and hands you back the protocol number that confirms receipt. If an expense is rejected, you know straight away and you fix it.

File export: the software prepares an XML for you. Then you go to the portal, you upload the file, you read the rejections. It's a legitimate function and for a small store it may well be enough — but it's a different word from "integrated", and it's worth knowing up front rather than in January.

The difference can be checked before you buy, without asking anyone: it's written on the vendors' own sites. Some document synchronous transmission and the protocol number Sistema TS hands back as a receipt; others write "compliant XML + export" — a different word, and it means you're the one going to the portal. Both are honest answers. They're two different products — and you can read the difference before you sign, not in January.

And then there's the part no brochure tells you: the AD/AA classification — the Sistema TS expense-type codes — and traceability are not a January problem, they're a counter problem. If you decide the expense type at the moment of sale, there's nothing left to decide in January. If you decide it in January, you're reconstructing twelve months of receipts from memory — and no software, however certified, can give you back data that was never recorded. Any method that "sorts it all out at year end" is working on data that's already lost.

Third question, the most uncomfortable: who pays when a rejection lands? The honest answer from anyone, us included, is "you". But software that shows you the rejection the same day and software that lets you discover it in March do not cost you the same, even if the fee is identical.

Us. RiVedi transmits from the system and hands you back the protocol number: if it doesn't come back, the expense didn't go through and you see it right away, not in January. The AD/AA classification is decided at the counter, on the sale line, while the customer is in front of you and you know what you're selling them — not in January, reconstructing twelve months from memory. That's the difference between software that records what happened and software that makes you fix it afterwards.

Refraction and clinical records: Article 9 isn't solved with a "privacy" tick-box

This is the misunderstanding that costs our trade the most. A refraction, a medical history, an attached clinical report are not "customer data": they are special categories of personal data under Article 9 of the GDPR — the same category as a hospital's data. An optical store is retail and a healthcare setting in the same square metre, and the software has to know that.

There's a single question that separates the serious answers from the marketing: is refraction data encrypted at field level, or is the disk encrypted?

This isn't pedantry. "The disk is encrypted" means that if somebody walks off with the PC from the back room they can't read a thing: that's real protection, and in a high-street store it isn't even a theoretical scenario. But it covers one case only, the computer that disappears. Encrypting at field level means the clinical data stays unreadable even to someone with access to the database: a backup that ends up in the wrong place, a supplier doing maintenance, an attack that comes in through the application. Those are two different threats, and the second one is the one that happens.

Ask these together, because they're the same question seen from three sides:

• Who reads what. A shop assistant needs to be able to see the job bag without seeing the medical history. If the software doesn't distinguish roles, your privacy policy describes a world that doesn't exist.
• Who looked. If it's ever disputed, you need to be able to say who opened that record and when. If there's no log, the answer is "I don't know".
• Where the data sits. Ask for the country, not the continent. It's your DPO's first question and the one the salesperson often can't answer — which is, in itself, information.

If you're wondering how theoretical any of this is: it's the same material every medical practice deals with, and we covered it in our guide to dental practice management software too. The difference is that the dentist knows they're a healthcare setting. The optician often thinks of themselves as a shop.

Us. In RiVedi, Article 9 data is encrypted field by field, with a dedicated key — not "the disk is encrypted", which answers a different question. Permissions are role-based, so you can close the clinical record to a shop assistant, and every access is logged: if one day you have to prove who opened what, the record is there. It's the part we spent the most time on and the part that shows least in a demo: ask for it anyway, of us and of anyone.

Lens matrices, lab orders, job bags: where generalist systems break

There's one question that closes any evaluation in thirty seconds: do you handle the lens as a matrix or as a stock item?

A generalist system — the ones that are excellent for a clothes shop — thinks in SKUs: one code, one price, one stock level. But an ophthalmic lens is not a code. It's a matrix: sphere × cylinder × axis × index × coating. The combinations run into the tens of thousands and, almost always, you don't have the item in the store: you order it when you sell it. If the software has no concept of a matrix, your lens price list becomes a separate Excel file — and from that moment the system has stopped managing the item that makes your margin.

Same story for the job bag, the work envelope that carries the prescription and the lens order through the lab. An order, for a generalist package, has two states: open and closed. A job bag has many more — quoted, deposit paid, ordered from the lab, arrived, glazed, ready, collected, paid in full — and each one is a moment where something jams and a customer rings. If the software doesn't model those states, you model them yourself: in a notebook, with sticky notes on the monitor, or by asking in the lab.

That's why the real choice is almost never "system A versus system B", but vertical versus generalist. And it's why an optician searching for "shop management software" finds excellent products — designed for people who sell shoes. It's the same fork in the road we described for other trades in how to choose the right management software for your SME: the sector changes, the trap doesn't.

Us. In RiVedi a lens is a matrix — sphere, cylinder, axis, index, coating — not a stock item with a code. That decision was made on day one and it isn't cosmetic: the lab order, the job bag with its real states and a stock list that tells you what you actually have all follow from it. Software that models a lens as an SKU can't be "fixed" with one more field: you carry it for years, on a notepad.

Cloud or installed in the store: the real question is who answers at 7pm on a Saturday

The cloud/on-premise divide is sold as a technical choice. It isn't. It's two practical questions in disguise.

First: where is your data if the PC in the back room catches fire? If the software is installed on a machine in the store, the answer depends entirely on the backup — that is, on something you configured years ago and have never tried restoring. The value of cloud isn't modernity: it's that you never have to ask that question.

The flip side, which cloud vendors never tell you — and we sell cloud, so on this one we're on the uncomfortable side. If the line goes down, a system installed in the store keeps selling and the cloud doesn't, and a Saturday afternoon offline in an optical store is real money. You pay for a perpetual licence once; a subscription, no: over eight years the installed option almost always wins on cost. And there's a third argument that plays against us on exactly the subject of the previous section: with the server in the store, your Article 9 data never leaves your four walls, and you don't have to trust anybody's data centre. If those three points weigh more than the backup, installed is the right answer — and four of the eight products below are installed.

Second: who answers at 7pm on a Saturday? Everybody underrates this one, and it's the one that ruins your year. An optical store trades when the offices are shut. Before you sign, look at the actual opening hours of the support desk — not the slogan, the hours page — and ask what happens outside them. No Italian vendor we checked, us included, offers 24/7 support. Better to know that up front.

On multi-store, a note against the grain: if you have one outlet, you don't need the multi-store feature and you're often being charged for it. It becomes decisive at the second store, when the questions become "is stock pooled or separate?" and "can a customer who bought in Vicenza collect in Padova?". Before that, it's a line on a price list.

Us, and here we lose one. RiVedi is cloud: updates and backups aren't your problem, and you can get in from home. But we don't have the technician down the road, and if what matters to you is someone turning up in the shop at 7pm on a Saturday, we're not the right choice. There's no clever answer to that objection: only telling you now instead of after you sign.

WhatsApp: the real thing, or a personal number with WhatsApp Web open?

In 2026 the channel an optician talks to customers on is WhatsApp. The point is that "the software sends WhatsApps" can mean two very different things.

There's real WhatsApp: a business number registered with Meta, with approved templates, sending "your job bag is ready" or the sight-test recall in the store's name. And there's the shop assistant's phone with WhatsApp Web open, which is what happens in most stores. It works, fair enough. But the messages go out from a personal number, when she leaves the conversation leaves with her, and there's no record of who consented to what.

Which leads to the last question, the one almost nobody asks: is consent per channel, or is it a single flag? A customer may want the appointment reminder and not want the Christmas promo. If the software has a single "consents to marketing" box, you can't honour that distinction even if you want to — and consent, under the GDPR, is specific.

Us. RiVedi sends from a registered business number with approved templates: messages arrive, they stay with the shop when the assistant changes job, and you don't end up doing marketing from someone's personal phone. Consent is per channel: a customer who wants the appointment reminder but not the promotion can have exactly that — and that's not etiquette, it's the difference between a recall that works and a spam report.

What it really costs, and why almost nobody tells you

The most useful finding of all our research isn't a price: it's that almost no vertical optical-store system publishes its price. That's not an impression — we opened the site of every product sold in Italy, one by one. Some public price lists do exist: from a few tens of euros per operator per month up to about a hundred, and there are one-off licences for a few hundred. But most of the market, including the vendors with the most stores installed, asks you to talk to a salesperson before telling you the cost. We don't publish ours either, and I won't spin that as a virtue. The only thing I can promise is how we behave when you ask: in the demo you get the number for your case, that day, all in — workstations, migration, training. Not "it depends" three times, not a quote that arrives two weeks and three meetings later. That's question 8, and if we dodge it you have every right to end the call.

Three warnings about any figure you're shown, worth more than the figure itself.

First: the subscription doesn't include what you'll actually pay. Data migration, training, extra modules, extra workstations. The subscription is the part of the cost that's easy to find out — which is exactly why it's the only one they show you.

Second: public prices don't reward the best products, they reward the ones that are simplest to sell. A vendor publishing a low figure can do so because the product is what it is; a vendor publishing nothing sells at a price that depends on your case. Reading price as a quality ranking is the easiest mistake on this page.

Third: nobody can honestly tell you who's the most widely used. In this market, installed-base numbers are declared by the vendor, not measured independently. Anyone giving you a ranking is estimating it — us included.

The practical consequence: a quote isn't read on the big number at the bottom. It's read with the eight questions above — get migration, workstations and modules in writing, then compare three-year totals, not monthly fees.

When you should NOT change your system

This section is against our interests and it's the most useful one in the guide. In most of the cases we see, the right answer is to stay put.

If you're in a franchise, you're not choosing. The brand tells you which system to use, and it makes sense that way: the price lists, the promotions and the reporting are theirs. The moment of choice will come, if at all, when you leave.

If your accountant and your lab have been working on your system for twenty years, the cost of switching isn't the subscription. It's the week you can't find anything, it's the mistakes of the first two months, it's the lab receiving orders in a new format. If it works today, switching almost always costs more than it fixes.

If your problem is a person, new software won't fix it. This is the most common case and the most misread. "The system is rubbish" often means "my support desk doesn't answer" or "whoever was supposed to enter the data didn't". Those are real problems and they need fixing — by changing supplier, or by changing how you work. But if nobody enters the data, the new software will simply have more modern empty fields.

If below a certain number of job bags the maths doesn't work, it doesn't work. Do the sum first: how many hours a month the problem costs you today, what the switch costs all in, how many months to pay it back. If the number is bigger than twenty-four, you're buying a feeling.

There's one moment when switching makes sense, and you'll recognise it: when the software stops you doing something you want to do. Opening the second store. Stopping doing recalls by hand. Sleeping at night about your clinical data. Not "the software is old": the software is blocking me.

Migration: the clause that decides whether you're a customer or a prisoner

If you do decide to switch, there's one question worth all the others put together, and it has to be asked before you sign, while you still have bargaining power: if I leave in three years, what do I take with me and in what format?

What has to come out: customer records with purchase history, refractions and clinical records, closed job bags, the payment schedule, price lists. In an open format — CSV, XML, access to the database. If the answer is "we'll export the PDFs for you", the translation is: your data becomes pictures of data. You can look at it, you can't reuse it. That applies to us too: if you leave RiVedi one day, what you take with you has to be readable by whoever comes next.

And the practical part: who pays for migrating the data from the old system, and in how many days? It's the most underrated line in the quote, it's often worth more than the first year's subscription, and it's almost never in the price they showed you.

Then there's the twin question, the one that comes before all the others and that this guide didn't ask until an optician pointed it out: what can you import from, and who has already done it? If you've been on the same system for eleven years, your problem isn't what you take away in three years' time: it's what goes in now. The customer records with their history? The refractions? The closed job bags? The acceptable answer is "we've already migrated N stores from your current system, and I'll tell you line by line what comes across and what doesn't". The red flag is "send us the data and we'll see".

That applies to us too, and our answer today is: we haven't yet migrated anyone from the long-established systems. If you're on one of them — and statistically you are — that's a risk you're taking on yourself, and you need to know it up front, not afterwards.

Where RiVedi loses, in our own words

You've just read eight times what we do. This is the part no salesperson reads out to you, and it's the one you actually need: where we're not the right choice. I'm speaking in the first person, because this is the part where I have an interest — which is exactly why I write it myself instead of letting you find it after you've signed.

RiVedi came out of these eight questions, and you've already read the answers one by one in the sections above: the protocol back from the system, classification at the counter, Article 9 field by field, the lens as a matrix, WhatsApp from a registered number. I won't repeat them: put the eight questions to us exactly as you would to anyone else.

Now the part that matters most.

We don't have twenty years of installed base. The long-established systems in this market have thousands of optical stores behind them; we don't, and that's the most honest thing I can write here. If you're choosing on the evidence that the software has held up for decades across thousands of stores like yours, they have that evidence and we don't.

We don't have an engineer in Ragusa. If what matters to you is somebody turning up at the store, we're not the right choice, and there's no clever answer to that objection.

We don't do payroll, we don't do full accounting. We do the optical store: the rest stays with your accountant.

And we're a young product. I'm saying it here, not at the bottom of the page.

What we can tell you is how we built it: we're a software house in Bolzano, the product was born with real opticians who told us where the flow breaks, and the hard things — encrypting clinical data, certified submission, lens matrices — we did before the things that photograph well.

In summary: the 8 questions, and what to do with them

Take the eight questions and put them to three suppliers. We're one of the three, and we've just written down for you where we lose: if after asking them you stay where you are, you'll still have done the best deal of the day — you'll know why you're staying. What you can't afford is signing without having asked them of anyone.

1. Does Sistema TS transmit or export?
2. Is AD/AA decided at the counter or in January?
3. Is clinical data encrypted per field, or is it the disk?
4. Is the lens a matrix or an item?
5. Do role-based permissions exist? And the access log?
6. WhatsApp: registered number or the shop assistant's phone?
7. On the way out: open format or PDF?
8. What does my case cost, all in?

Whoever answers with a number and a "yes, look, let me show you" is telling you the truth. Whoever answers "of course, it's all integrated" is selling to you. End of guide.

Frequently asked questions about optical store software

How much does optical store software cost?

It depends on how much the supplier lets you see, and that's half the problem: almost no vertical optical system publishes its price. Where a list does exist, it takes two shapes: a monthly fee per operator (from a few tens of euros to about a hundred) or a one-off licence of a few hundred. But the fee is the easy part: get migration, training, modules and extra workstations in writing, and compare three-year totals.

What is the best software for opticians in Italy?

There isn't an honest answer, and be wary of anyone who gives you one — us included. In this market adoption figures are declared by the vendor, not measured independently: any ranking is an estimate dressed up as data. The "best" one is the one that answers the eight questions well for your case: if you order Zeiss lenses daily, supply-chain interfaces matter; if your problem is Sistema TS, transmission matters.

Does the software transmit to Sistema TS by itself?

It depends, and the word "integrated" doesn't tell you. They're two different jobs: direct transmission (the software talks to Sistema TS and hands you back the protocol number) and file export (it prepares the XML, you go to the portal). You'll find both wordings on vendor sites, and some stay deliberately vague: "automatic and electronic sending" doesn't say whether the protocol comes back. Ask which of the two they're selling you, and get it in writing.

Is there free optical store software?

Free versions do exist, usually capped on the number of records: to start out, that can be enough. The point to clear up before you begin is always the same: ask how it handles Sistema TS — because that's exactly the function free versions tend not to have, and not to mention.

Is refraction data health data?

Yes. A refraction, a medical history, an attached clinical report are special categories of personal data under Article 9 of the GDPR — the same category as a hospital's data. An optical store is retail and a healthcare setting in the same square metre. Ask whether clinical data is encrypted at field level or whether only the disk is encrypted: those are two different protections.

Do you need a vertical system, or will a generalist do?

It depends on two things: the lens and the job bag. A generalist thinks in SKUs, but a lens is a matrix (sphere × cylinder × axis × index × coating) and the combinations run into the tens of thousands. And a job bag has many more states than "open" and "closed". If the software doesn't model the matrix and the states, you model them yourself — in a notebook.