Lightspeed integrations that book every store, every day.
Lightspeed knows exactly what you sold. Your accounting, your staff planning and your managers usually don't, or only after someone exports it by hand. I connect Lightspeed to the systems that need those numbers, per location, before the day starts.
What I connect Lightspeed to.
Lightspeed to accounting
Daily revenue per location as one balanced entry, split per ledger account, VAT rate and payment method. Card fees and tips on their own lines. Into Twinfield, AFAS or SnelStart.
Lightspeed to staff planning
Revenue per store and per hour into Dyflexis or another workforce tool, so labour cost and revenue per hour sit next to each other.
Store dashboards
Sales against last year and against budget, per store, refreshed through the day. A manager sees only their own store.
Opening and closing checks
From the till's own day reports: when each store actually opened and closed, against its opening hours.
Payment reconciliation
Lightspeed Payments payouts matched against what the till recorded, so the controller stops doing it in Excel.
Product and order data
Menu items, product groups and order lines into a data warehouse or your BI tool, for anyone who wants to dig further.
These are the most common starting points. Every integration is built around how you work.
What I've built so far.
How a project runs.
A conversation first
We go through how the work runs today and what the integration has to do. Every company does this differently, so I don't start from a template.
A fixed, one-time price
You get one price for the build. No monthly licence for something that only needs looking at when a system changes.
I build it and keep it running
I build it, host it if you want me to, and keep an eye on it. The code is yours, so you're never locked in.
How your data stays safe.
Only what's neededThe integration only gets access to the data it needs for the job, and read-only access where that's enough.
Keys stay out of sightAPI keys and tokens live in an encrypted server environment, never in a spreadsheet or a shared document.
Hosted in the EUI run integrations on servers in the EU unless you prefer your own environment.
Not used to train AIWhere AI is involved, I use the business APIs of OpenAI or Anthropic. Your data is not used to train their models.
What people ask about Lightspeed.
Does Lightspeed allow custom integrations?
Yes. Lightspeed has an official API, but you need approved API access first. I take care of that application and the review with Lightspeed, so you don't have to.
Which Lightspeed product do you work with?
Mostly the K-Series (Lightspeed Restaurant). The same approach works for other Lightspeed products that offer an API.
Isn't there a ready-made connector?
Sometimes, and if it fits I'll tell you to use it. The standard connectors often can't split bookings per location, or don't support K-Series yet. That's where a custom build makes sense.
Do I pay a monthly fee?
No subscription to me. You pay once for the build. If a system changes its API later, or you want something extra, I'll quote that separately. Hosting is usually a few euros a month, at cost.
Who owns the integration?
You do. The code is yours, and so are the accounts it runs on if you want that. You can hand it to another developer at any time.
What if something breaks?
I add monitoring to every integration, so I usually see a failed run before you do. When something does stop, I fix it quickly.
Often connected together.
Want Lightspeed connected to your other systems?
Tell me what runs where today and what should happen automatically. I'll tell you what's possible, how I'd build it and what it costs.






