Integration · in queue

Neucelle + Lightspeed Restaurant

Strong in Canada and Europe — including FR / CH / BE / QC. Neucelle's Lightspeed sync is in active development; CSV import works today.

Setup time ~10 min · Sync direction: data flows into Neucelle

What syncs

  • Sales by item (CSV today, live API queued)

Setup walkthrough

  1. 01

    Export sales from Lightspeed

    Use the daily sales report and download the CSV.

  2. 02

    Import into Neucelle

    We detect the Lightspeed Restaurant schema automatically.

Who this integration is for

We see Lightspeed Restaurant most often in three operator types — the integration is built first for the ones below.

About Lightspeed Restaurant

Lightspeed Restaurant is one of the most-used platforms in indie restaurants in 2026 in its category. The Neucelle integration is designed to stay out of the way: read-only or one-way write, with no schema migrations on the Lightspeed Restaurant side and no behaviour changes for the operator.

Visit Lightspeed Restaurant

Lightspeed Restaurant integration — FAQ

Is the Neucelle + Lightspeed Restaurant integration live?

In active development. We have an early-access cohort — email hello@neucelle.ch to join. Current status: in queue.

How long does Lightspeed Restaurant setup take?

About 10 minutes. The walkthrough above covers the full flow — OAuth grant, field mapping, and posting cadence.

What data flows between Neucelle and Lightspeed Restaurant?

Data flows into Neucelle. Synced fields: Sales by item (CSV today, live API queued).

Can I disconnect Lightspeed Restaurant later without losing my data?

Yes. Disconnecting revokes Neucelle's OAuth token; data captured up to that point stays in Neucelle. Nothing is deleted on Lightspeed Restaurant's side.

Do I need Lightspeed Restaurant to use Neucelle?

No. You can run the full Neucelle invoice-capture and food-cost loop without Lightspeed Restaurant connected. The integration adds sales-side reconciliation for theoretical-vs-actual variance — useful, but not required for the core workflow.