Keep Lightspeed and Foodticket updated automatically.
Today you open your shop’s admin, look at which orders came in and carry them over. With this connector, what happens in Lightspeed lands in Foodticket by itself, in the shape Foodticket expects. Request it and you get access; you hear from us within 24 hours.
What this connector takes off your hands
-
Today you open your shop’s admin, look at which orders came in and carry them over.
-
Today you enter orders by hand and correct stock afterwards, usually once something already went wrong.
What Lightspeed to Foodticket saves you
- Bring every new Lightspeed order back into Foodticket.
- Bring every refund in Lightspeed back into Foodticket.
- Bring every new Lightspeed customer back into Foodticket.
- Bring every stock change in Lightspeed back into Foodticket.
What travels across the link
Everything this connector moves between Lightspeed and Foodticket, and how often.
-
Orders
to Foodticket automaticallyEvery order becomes an order in Foodticket with line items, matched on EAN or SKU, so you handle it all from Foodticket without retyping.
-
Inventory
to Foodticket automaticallyA sale updates stock in Foodticket, so you never sell the same last unit on two channels at once.
What each side expects
Lightspeed and Foodticket do not describe the world the same way. This is what has to line up.
Foodticket
A shop platform needs to point each line at a product, usually via SKU or barcode, and track stock per product.
Setting it up
- 01
Request the connector
Request the Lightspeed to Foodticket connector and get access. You hear from us within 24 hours.
- 02
We agree what should travel
Together we settle what should travel out of Lightspeed. A shop platform needs to point each line at a product, usually via SKU or barcode, and track stock per product.
- 03
Test and switch on
You check the connector on a few test records before anything becomes final, then it runs by itself.
What you need
- A store you administer, with API access from its admin.
- A store you administer, with API access from its admin.
Where it runs
Inside your Shopify admin, as an app. You sign in through Shopify, no separate account.
Request this connector: tell us what you need and we reply within 24 hours.
Common questions
Can you connect Lightspeed to Foodticket?
Yes. Schakel connects through the official APIs of Lightspeed and Foodticket, so you install nothing on your own server and nothing travels outside those two parties.
What does the connector match products on in Foodticket?
On EAN barcode or SKU. Those have to line up on both sides; anything that does not match automatically you map once by hand, and it is remembered after that.
Does the connector touch my existing Foodticket orders?
No. Schakel only creates new orders in Foodticket and leaves your existing ones alone.
What happens on a refund or partial cancellation in Lightspeed?
It comes across, so Foodticket matches what was actually settled and you correct nothing by hand.
What does connecting Lightspeed and Foodticket cost?
You start free and only pay once the connector is really running. After that the same tiers apply as for any other connector, based on how much runs through it each month.
How often does Lightspeed sync with Foodticket?
That depends on your tier: hourly on the free tier up to real time on the unlimited tier. You can always start a sync yourself as well.
What if Lightspeed or Foodticket is briefly unavailable?
Nothing gets lost. Schakel retries later and the log shows exactly what happened, so at most you notice something coming through a little later.
How do I connect Lightspeed to Foodticket?
You give Schakel access to Lightspeed and Foodticket once and pick what should travel. We set it up together with you, so no technical knowledge is needed, and after that it runs by itself.
Connect a different pair
Lightspeed and Foodticket is one of many. Pick two systems and see what travels between them.
Missing something you need?
Tell us what Lightspeed and Foodticket should do for you. If it is not in here yet, that is usually because nobody has asked. We build on request and we reply within 24 hours.