Built for modern optical teams
Run appointments, prescriptions, workshop flow and billing from one optical platform.
OpticFlow gives optical stores a clear operating system for client intake, prescription capture, order production, invoicing, and customer follow-up.
An optical back office designed to align store, workshop, and client follow-up.
Appointments today
Prescription
My invoices, documents, and payments
One operating flow
From the first appointment to the final pickup
OpticFlow is structured around the real sequence optical teams execute every day.
Appointments that match real store availability
Manage intake, fitting, after-sales visits, and branch schedules from one calendar view.
Prescription capture without spreadsheet chaos
Record sphere, cylinder, axis, PD, heights, and notes directly on the order workflow.
Workshop production and pickup tracking
Move optical orders through quote, confirmation, lab, ready, and delivered stages with a clean operational timeline.
Invoices and collections tied to the real dossier
Issue quotes and invoices from the same order, track balances, and keep payment history readable.
Reporting for owners and managers
See branch activity, collections, and operational pressure without leaving the back office.
A client portal that is actually useful
Clients can review orders, invoices, workshop documents, and payment actions from a lightweight portal.
Why teams switch
Operational clarity instead of module sprawl
The goal is not more screens. The goal is one workspace that matches how optical teams actually work.
Less manual back-and-forth
Appointments, dossiers, invoices, and payments stay tied together from the start.
Cleaner branch execution
Each team member works with the right branch, the right rights, and the right queue.
Better client communication
The portal gives clients the useful status, documents, and payment actions they actually need.
We stopped chasing information between appointments, prescriptions, and billing. The store runs with much less friction.
The operational timeline is what changed the most for us. Workshop, front desk, and collection are finally aligned.
Clients now have a real portal instead of scattered PDFs and WhatsApp messages.
Clear pricing
Choose the plan that fits your optical workflow
Start with a trial, then move to the monthly or yearly plan that matches your branches, users, and client volume.
Starter
Essential for a single store with customers, orders, products, and billing.
Monthly billing
- Up to 1 branch
- Up to 3 users
- Up to 750 customers
- 5 GB storage
- Appointments
- Client portal
Growth
Built for multi-branch operations with reporting and advanced permissions.
Monthly billing
- Up to 5 branches
- Up to 15 users
- Up to 5000 customers
- Up to 3 custom domains
- 25 GB storage
- Appointments
- Reporting
- Client portal
- Branch permissions
Scale
Expanded capacity for large multi-site operations.
Monthly billing
- Unlimited branches
- Unlimited users
- Unlimited customers
- Up to 10 custom domains
- 100 GB storage
- Appointments
- Reporting
- Client portal
- Branch permissions
One operating flow
From the first appointment to the final pickup
OpticFlow is structured around the real sequence optical teams execute every day.
Book or register the visit
Create the appointment, welcome the client, and open the working dossier with the right branch context.
Capture the prescription and product choices
Store prescription details, selected frames, lenses, and notes without jumping between disconnected tools.
Issue quote or invoice
Generate commercial documents directly from the dossier, with tax, currency, and payment logic already aligned.
Track workshop and client follow-up
Move the order through production, publish workshop documents, and let the client check progress from the portal.
Guides and updates
Practical content for optical operations
Read short articles about workflow setup, appointments, billing discipline, and client communication.
How to keep an invoice readable for both team and client
A good invoice is not only correct. It also needs to stay readable at checkout, in the portal, and on paper.
Read moreWhen to show payment actions to the client
Showing every payment button all the time creates noise. They should appear only when useful and truly configured.
Read moreWhy branches need a clear working context
Multi-branch execution breaks quickly when users do not see the right queue, cash desk, and dossiers.
Read more