Resources · Zapier integration

Lightspeed Retail POS (X-Series) Zapier integrationAutomate Lightspeed Retail POS (X-Series) with Zapier.

The Lightspeed Retail POS (X-Series) Zapier integration gives you 13 triggers, 4 actions and 3 searches. Every one of the 13 triggers is instant, so sales, customers, stock and registers reach your other apps the moment they change, even on the free plan.

See the 20 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Lightspeed Retail POS (X-Series) Zapier integration actually does

Lightspeed Retail POS (X-Series) is a point-of-sale and retail management system that runs in the cloud, for the shop counter, online sales and mobile. Connecting it to Zapier lets each sale, customer or stock movement start work in your other apps, and lets those apps create customers, products or sales back in Lightspeed.

Three results show up again and again. A sales log you never type: New Sale hands each sale, with its line items, to the next step, which writes it into a spreadsheet or an accounting tool. Customers that exist everywhere: New Customer and Updated Customer push each customer record out, while Create Customer brings new ones in from a form or a CRM. Stock that warns you: Updated Inventory fires whenever a product's stock moves, so a filter can catch the levels you care about.

Here is what Zapier does not do for this app. There is no action to update or delete an existing customer, product or sale: the four actions only create. The triggers report creations and updates, never the deletion of a customer or a product. And Updated Inventory stays silent on any product that does not track inventory.

No Make or n8n page exists yet for this app; to weigh the tools in general, our n8n vs Zapier comparison sets out the criteria.

Vocabulary

Zapier words, in plain English

Eight terms come back on this page. Here is what each one means before you open the editor.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap, a new sale for instance. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists, a customer or a product, so later steps can use what it found.
Connection
Your Lightspeed account linked to Zapier once, then reused by every step of every Zap that touches the app.
Cost

What a Lightspeed Zap really costs

Lightspeed Retail POS (X-Series) is not a premium app, so it works on the free plan. The bill is counted in tasks, and only completed actions count.

  • Free plan100 tasks per month
  • Free plan Zap size2 steps: 1 trigger, 1 action
  • Premium appNo
  • Instant triggers13 out of 13

Triggers cost nothing, however many sales go through the till. Each action that succeeds counts once, so a Zap with two actions uses twice as much. An action that fails is not counted. The free plan allows 100 tasks a month and two-step Zaps only, one trigger plus one action. A filter, a search step or a second action makes the Zap multi-step, and that needs a paid plan. The polling grid below does not apply here: all 13 triggers are instant.

Connect

Connect your Lightspeed account in three steps

  1. 01

    Open the Apps page

    From your Zapier account, go to Apps, then click + Add connection. A dialog opens with a search box: type Lightspeed Retail POS (X-Series) and pick the X-Series app from the list.

  2. 02

    Add the connection

    Click Add connection. A new tab opens on Lightspeed: sign in with the account of the store whose sales, customers and products the Zap should read or write. You need a Lightspeed account first.

  3. 03

    Grant access

    Allow Zapier to use the account. If the Zap must touch outlets or records you do not own yourself, check that your account has read or write access to them, or the actions will fail later.

First Zap

Your first Zap: log each Lightspeed sale in a spreadsheet

GoalEach time a sale goes through Lightspeed, keep only the ones that match one field, then add them as a row in your spreadsheet.

  1. 01

    Pick the trigger

    Start a new Zap, choose Lightspeed Retail POS (X-Series) as the trigger app and New Sale as the event, then select your connection.

  2. 02

    Test on a real sale

    Run the test: Zapier brings back the three most recent sales of your account. Pick a real one with its line items, so every later step is mapped on actual data.

  3. 03

    Add a filter

    Click the plus icon, add Filter, then fill the three boxes: the field to read, the rule, the value. Use a number rule for amounts and a text rule for text.

  4. 04

    Add the row

    Add your spreadsheet's action that creates a row and map the sale fields into its columns. With a filter, this Zap has three steps, so it needs a paid plan.

  5. 05

    Test, then publish

    Test each step once and read what came back. When the row looks right in your spreadsheet, click Publish to switch the Zap on.

Triggers

Lightspeed Retail POS (X-Series) triggers

13 events start a Zap when something happens in Lightspeed Retail POS (X-Series), and 13 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Awaiting Dispatch Sale

Instant trigger

In Zapier“Triggers when a sale is awaiting shipping (with line item support). Typically a sale received from e-commerce.”

Catches a sale that is waiting to be shipped, usually an order that came in through your online store, and passes it on with its line items so the parcel can be prepared elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the people packing orders work from another tool and need each order to show up there without anyone copying it.
Watch out
it only covers sales waiting to be shipped; to follow every sale, New Sale is the trigger you want.
2

New Awaiting Pickup Sale

Instant trigger

In Zapier“Triggers when a sale is awaiting pickup (with line item support). Typically a sale received from e-commerce.”

Reacts to a sale the customer will collect in person, most often one placed online, and sends it on with every line item.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the store team has to be told that an order is waiting for collection, in the chat or task tool they actually watch during the day.
Watch out
dispatch and pickup are two different triggers; a Zap built on this one ignores shipped orders entirely, so build a second Zap if you need both.
3

New Customer

Instant trigger

In Zapier“Triggers when a customer is added.”

Fires as soon as a customer is added to Lightspeed, whether at the till or elsewhere, and hands over the new customer record.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a new customer should also appear in your mailing tool, your CRM or a shared spreadsheet, without a second round of typing.
Watch out
a Zap that starts here and ends with Create Customer in Lightspeed would add the customer again and set itself off in a loop.
4

New Register Closure

Instant trigger

In Zapier“Triggers when a register is created.”

Starts your Zap when Lightspeed records a new register closure, and passes its details along.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when whoever checks the cash needs each closure copied into a spreadsheet or announced to a manager, instead of opening Lightspeed to look.
Watch out
updates to an existing closure come through Updated Register Closure instead, so plan both Zaps if those updates matter.
5

New Sale

Instant trigger

In Zapier“Triggers when a new sale is created (with line item support).”

Hands every new sale to your Zap, with its line items, which makes it the broadest trigger of the app and the usual starting point.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when each sale should feed a log, an accounting tool or a report, whatever channel it came from.
Watch out
it fires on every sale, so a busy store burns tasks fast on any action behind it; a filter keeps only the sales worth acting on, and makes the Zap multi-step.
6

New Voided Sale

Instant trigger

In Zapier“Triggers when a sale is cancelled (with line item support).”

Reports a sale that has been cancelled, with its line items, so the cancellation can be mirrored wherever the original sale was copied.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
as the counterpart of a Zap built on New Sale, so that a spreadsheet or report does not keep counting a sale that no longer exists.
Watch out
Zapier cannot delete the original row for you through this app; the next step has to mark or remove it in the other tool.
7

Received Consignment

Instant trigger

In Zapier“Triggers when a consignment is received.”

Goes off when Lightspeed records a consignment as received, and passes the consignment along to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the person who orders stock wants confirmation that goods came in, or a purchase tracker should close the line on its own.
Watch out
it says nothing about goods leaving; to hear about the shipment itself, set a second Zap on Sent Consignment.
8

Sent Consignment

Instant trigger

In Zapier“Triggers when a consignment is sent.”

Fires on the other end of the journey: when a consignment is sent out from Lightspeed, the Zap gets its details right away.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the outlet or partner on the receiving side should be warned that goods are on their way, through a message or a shared sheet.
Watch out
received and sent are separate triggers, so tracking a consignment from start to end takes two Zaps, one on each.
9

Updated Customer

Instant trigger

In Zapier“Triggers when a customer is updated.”

Notices every change to an existing customer record and sends the updated version to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a phone number or an email corrected at the till must also change in your CRM or mailing list, so the two never drift apart.
Watch out
a brand new customer goes through New Customer instead; to cover both creation and edits, plan one Zap on each trigger, which means two Zaps to maintain.
10

Updated Inventory

Instant trigger

In Zapier“Triggers when a product’s inventory is updated. If a product does not use inventory tracking, this trigger won’t fire.”

Fires whenever the inventory of a product is updated in Lightspeed, and hands the new figures to your Zap so the next steps can use them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a filter behind it should catch the stock levels you care about and warn the buyer, or when an online catalog must show the same stock as the store.
Watch out
a product that does not use inventory tracking never fires it, whatever happens to its stock.
11

New or Updated Outlet

Instant trigger

In Zapier“Triggers when an outlet is created or updated.”

Watches your outlets, the stores or sales points set up in Lightspeed, and fires when one is created or its settings change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a shared directory of locations, or the tool your team uses to plan shifts, must stay in step with what Lightspeed holds.
Watch out
new and changed outlets come through the same trigger, so add a filter if only one of the two should go on.
12

New or Updated Product

Instant trigger

In Zapier“Triggers when a product is created or updated.”

Reacts to your catalog: a product created in Lightspeed, or an existing one edited, reaches the Zap with its details.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when another catalog, a price list or a spreadsheet of references should mirror every product change made in the back office.
Watch out
a Zap that starts here and ends with Create Product writes where its trigger watches, and can fire itself again and again.
13

Updated Register Closure

Instant trigger

In Zapier“Triggers when a register is updated.”

Fires when a register closure already in Lightspeed is updated, and sends the new version to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
next to a Zap on New Register Closure, so the spreadsheet that keeps your closures also follows their updates.
Watch out
the next step has to find and overwrite the earlier row; adding a new one leaves you with two versions of the same closure.
Actions

Lightspeed Retail POS (X-Series) actions

Lightspeed Retail POS (X-Series) gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Customer

Action

In Zapier“Creates a new customer.”

Adds a customer to Lightspeed from data collected elsewhere, a signup form or a CRM entry, so staff find them at the till.

When to use it
when customers first meet you online and should already exist when they walk into the store.
Watch out
First Name and Last Name are required, and the Do Not Email box records an opt-out, so map it rather than leave it to chance.
2

Create Customer Group

Action

In Zapier“Creates a new customer group.”

Creates a new customer group in Lightspeed with nothing more than a name, ready for customers to be placed in it.

When to use it
when a group created in another tool, for a campaign or a club, should have its twin in the till.
Watch out
Name is its only required field, and none of the three searches covers groups, so the Zap cannot check in Lightspeed whether the group already exists.
3

Create Product

Action

In Zapier“Creates a new product.”

Adds a product to your Lightspeed catalog from another source, a supplier sheet or a product database.

When to use it
when new references are prepared outside Lightspeed and should reach the till without manual entry.
Watch out
Name is required, and variants of one product share the same name, so the name alone will not tell them apart.
4

Create Sale

Action

In Zapier“Creates a new sale.”

Records a sale in Lightspeed from an order that happened in another system, line item included.

When to use it
when sales made through a channel Lightspeed does not see should still land in the same register.
Watch out
it is the most demanding action: Status, User ID, Product ID, Quantity, Price, Tax and Tax ID are all required, so a Find Product step before it often saves the day.
Searches

Lightspeed Retail POS (X-Series) searches

3 search steps look for data that already exists in Lightspeed Retail POS (X-Series), so a later step can use it.

The three searches sit at the bottom of the action list, under the SEARCH heading. Each one looks up an existing customer, product or sale and hands it to the next steps. Each also has a find-or-create variant: the same search with one box ticked, not an extra operation.

1

Find Customer

SearchFind or create

In Zapier“Finds customer in the system.”

Looks for a customer who is already in Lightspeed, so a later step can reuse their record instead of creating a duplicate.

When to use it
before Create Sale or any step that needs a customer that might already exist.
Watch out
the editor also lists Find or Create Customer: it is this same search with the create box ticked, and it then asks for the fields of a new customer.
2

Find Product

SearchFind or create

In Zapier“Finds product in the system.”

Retrieves a product from your Lightspeed catalog and passes on its details, the product ID among them.

When to use it
right before Create Sale, which needs a Product ID that the triggering app rarely carries.
Watch out
Find or Create Product is not a separate operation but this search with creation switched on, which adds a product whenever none matches.
3

Find Sale

SearchFind or create

In Zapier“Finds sale in the system (with line item support).”

Finds a sale that is already recorded, with its line items, so the following steps can read or reuse it.

When to use it
when a later step needs the details of a sale an earlier step only referred to.
Watch out
the Find or Create Sale line in the editor is this same search with the create box ticked; it then asks for what a new sale requires.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Lightspeed Zap breaks

Zapier attaches no help article to this app, so the known failure points are the general ones of any Zap, applied to how Lightspeed works.

Four cases cover most of what goes wrong. If yours is not among them, our Zapier troubleshooting page goes further.

  • Past sales never show up

    A Zap only reacts to sales, customers or stock changes that happen after you publish it. Earlier history stays in Lightspeed; moving it is a separate job.

  • The Zap keeps firing itself

    A Zap on New or Updated Product that ends with Create Product, or on New Customer with Create Customer, writes where its trigger watches and loops.

  • A big batch is held back

    After a bulk import of products or customers, a sudden wave of trigger events can be held back by Zapier's flood protection.

  • Stock changes but nothing fires

    Updated Inventory only fires for products that use inventory tracking. For a product without it, the Zap never starts, whatever happens on the shelf.
Need help

Need help automating Lightspeed Retail POS (X-Series) with Zapier?

A person reads every message.

FAQ

Lightspeed Retail POS (X-Series) and Zapier: common questions

01Is the Lightspeed Retail POS (X-Series) Zapier integration free?
Yes, it works on the free Zapier plan, because Lightspeed Retail POS (X-Series) is not a premium app. The free plan gives you 100 tasks a month and Zaps of two steps, one trigger and one action. A Zap that copies each new sale into a spreadsheet fits. As soon as you add a filter, a search step such as Find Product, or a second action, the Zap becomes multi-step and you need a paid plan.
02How many tasks does a Lightspeed Zap use?
One task per action that completes, and nothing for the trigger. A Zap on New Sale with one action uses one task per sale, which adds up quickly in a busy store: the free allowance of 100 tasks a month can go fast. Adding a filter or a search also makes the Zap multi-step, so it needs a paid plan. A failed action is not counted against your plan. If your volume is high, put the filter first so only the sales that matter reach the action.
03Do Lightspeed triggers work in real time?
Yes. All 13 triggers are instant: Lightspeed tells Zapier the moment a sale, a customer, a stock level, an outlet or a register closure changes, and the Zap starts right away, whatever your plan. The polling grid that sets how often Zapier checks other apps, every 15 minutes on the free plan, does not apply here. In the editor, a Zap built on one of these triggers shows a lightning bolt.
04What does it take to connect Lightspeed Retail POS (X-Series)?
A Lightspeed Retail POS (X-Series) account, and access to the outlets and records the Zap will touch. In Zapier, open Apps, click + Add connection, search the app, click Add connection, sign in on the tab that opens and grant access. Before building a Zap with Create Sale, check that the cashier user, the product and the tax you will map already exist in Lightspeed, since all three are required. One connection then serves every Zap you build on the app.
05Why does Updated Inventory never fire for some products?
Because those products do not use inventory tracking. The trigger only reacts to stock changes on products that track inventory; for the others, nothing is reported to Zapier, whatever is sold or delivered. Check in Lightspeed which products use inventory tracking before you rely on this trigger. Until a product tracks inventory, no Zap built on this trigger can see its stock movements, so a stock alert for it has to come from somewhere else.
06What if the Lightspeed operation you want is missing?
Then the Zapier side cannot do it today. Reading is well covered: 13 triggers and three searches, Find Customer, Find Product and Find Sale. Writing is not: the four actions only create a customer, a customer group, a product or a sale, and nothing edits or removes a record already in Lightspeed. If your job is a write of that kind, one fallback is to record the change in a spreadsheet and update Lightspeed by hand. No Make or n8n page exists yet for this app.
07Zapier, Make or n8n for Lightspeed Retail POS (X-Series)?
It depends on your criteria, not on a winner. Zapier gives you 13 instant triggers, and the free plan covers two-step Zaps. If your store produces many sales a day, the task count becomes the deciding factor, so compare how Make and n8n bill a run, what each exposes for Lightspeed, and who on your team will maintain the automation over time. Test each option on a real sale before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations