Resources · Zapier integration

Loyverse Zapier integrationAutomate Loyverse with Zapier.

Loyverse Zapier integration: 5 triggers, 20 actions, 30 searches. Instant triggers on receipts, stock, items, customers and shifts, plus actions and lookups across the whole back office. What each one does, what it costs, and where it breaks.

See the 55 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Loyverse Zapier integration actually does

Loyverse is a free point of sale and stock management tool that runs on a phone or a tablet, with a back office for sales, inventory and staff. On Zapier it is one of the broader apps: it tells Zapier when receipts, stock, items, customers or shifts change, and lets a Zap create, update, delete or look up most of what the back office holds.

A sales log that keeps itself. Receipts Update fires as each receipt is created or changed, and a Zap writes it to the spreadsheet where you follow sales. Nobody exports a report at closing.

A stock alert before the shelf is empty. Inventory Update fires when a stock level moves. Put a filter behind it and your team chat only hears about the levels that matter to you. The restock itself can come back through Update Inventory Levels for Items once the delivery is in.

A catalog that follows your other tools. Create or Update Single Item, Create or Update Category and Create or Update Tax let another system push its changes into Loyverse, so the till sells what the rest of the business has decided.

Now the limits. There is no trigger for a deleted item, a new discount or a new employee: only the five events listed below start a Zap. Refunds through Create Refund Receipt only work on receipts paid with a single payment, and not on receipts paid by a payment provider integrated in the Loyverse POS app. Searches return what exists; none of them creates anything when nothing is found. If you also look at Make for this app, see our Loyverse Make integration page.

Vocabulary

Zapier vocabulary in one minute

Eight words come back across this page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Loyverse has five, from a receipt to a new shift synced to the Back Office.
Action
What the Zap does once it has started: the step that writes, sends, changes or deletes something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is counted in those.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so later steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, on a paid plan.
Cost

What a Loyverse Zap really costs

Loyverse is not a premium app on Zapier, so it works from the free plan. The trigger never costs a task.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Triggers5, all instant
  • Searches30, each one makes the Zap multi-step

Each action that succeeds is one task; one that fails is not counted. The free plan gives 100 tasks a month and two-step Zaps: one trigger, one action. That fits a receipt-to-spreadsheet Zap. With 30 searches on offer, the temptation is to add a lookup, and a search, a filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks polling triggers; it does not apply to Loyverse, whose five triggers are all instant.

Connect

Connect your Loyverse account to Zapier

  1. 01

    Open Apps in Zapier

    In your Zapier account, open the Apps page and click + Add connection. A connection is your Loyverse account linked once, then reused by every Loyverse step in every Zap.

  2. 02

    Find Loyverse and add it

    Type Loyverse in the dialog, select it and click Add connection. You need a Loyverse account with access to the stores, items and customers the Zap should read or change.

  3. 03

    Sign in and grant access

    Sign in to Loyverse in the tab that opens and let Zapier use the account. If the back office belongs to someone else, check that your login reaches every store the Zap must touch.

First Zap

Your first Zap: a stock alert in your team chat

GoalWhen a stock level changes in Loyverse and meets the rule you choose, post a message to your team chat so someone reorders in time.

  1. 01

    Pick the trigger

    In a new Zap, choose Loyverse as the app and Inventory Update as the event, then your Loyverse connection. This is the build step on the starting side.

  2. 02

    Test on a real stock change

    Change a stock level in Loyverse, then test the trigger. Zapier brings back the three most recent items, so you map fields from a real update.

  3. 03

    Add the filter

    Add a Filter from the plus icon and fill its three boxes: the field to look at, the rule, the value to compare with. Pick a number rule for a number field, or it never passes.

  4. 04

    Add the message

    Add your team chat as the action and build the message from the stock fields of the test. The filter makes this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test and publish

    Test each step and read what came back, then publish the Zap to switch it on. Stock changes made before that moment are not sent. For a guided walk through Zaps like this one, see our Zapier training.

Triggers

The 5 Loyverse triggers on Zapier

5 events start a Zap when something happens in Loyverse, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Customer Update

Instant trigger

In Zapier“Triggers when a customer is updated.”

Starts the Zap when a customer record changes in Loyverse, so your other tools hear about a new phone number or a corrected name without anyone retyping it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to keep the contact in your email tool in line with what the cashier just edited at the till.
Watch out
a Zap that answers this trigger with Create or Update Single Customer on the same record changes it again and can set itself off in a loop.
2

Inventory Update

Instant trigger

In Zapier“Triggers when a stock updates.”

Fires each time a stock level updates in Loyverse, whatever caused the change. It is the event to build on when stock levels are what you need to watch.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
behind a filter, to warn the team only about the levels that fall under the threshold you set.
Watch out
without a filter every single stock change becomes a run, and every action in that run a task.
3

Items Update

Instant trigger

In Zapier“Triggers when an item is updated.”

Reacts when an item is updated in the Loyverse catalog, so your other systems learn about the change straight from the source instead of a copy someone forgot to refresh.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to mirror catalog edits made in Loyverse into the spreadsheet or tool that publishes your product list elsewhere.
Watch out
if another Zap pushes items into Loyverse with Create or Update Single Item, the two can feed each other in a loop.
4

Receipts Update

Instant trigger

In Zapier“Triggers when a receipt gets created or updated.”

Hands each receipt to your Zap, both when it is created and when it is changed later. It is the closest thing to a live feed of what happens at the till.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to log every sale in a spreadsheet, or to tell a delivery team that an order was rung up.
Watch out
one receipt can start the Zap more than once, since an update fires it too, so plan for duplicate rows downstream.
5

Shifts Create

Instant trigger

In Zapier“Triggers when a shift is created and synced to the Back Office.”

Fires when a shift is created and synced to the Loyverse Back Office, giving your Zap the shift that has just landed there.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to keep a shift log in a spreadsheet for whoever handles staff schedules, without opening the back office.
Watch out
the event is the sync to the Back Office, not the moment the shift opens, and the trigger only covers creation.
Actions

The 20 Loyverse actions on Zapier

Loyverse gives you 20 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create or Update Single Item

Action

In Zapier“Create or update a single item”

Adds a product to the Loyverse catalog, or updates one that already exists, from data another tool provides.

When to use it
when your product list lives in a spreadsheet and the till should follow it.
Watch out
Item Name is required, and Track Stock decides whether Loyverse counts stock for that item.
2

Create or Update Receipts

Action

In Zapier“Creates a receipt”

Writes a receipt into Loyverse from a sale that happened somewhere else, so your sales figures sit in one place.

When to use it
when online orders should appear next to till sales in the back office.
Watch out
Store ID is required, and a Zap that also listens to Receipts Update will see its own receipts come back.
3

Create Refund Receipt

Action

In Zapier“Creates a refund receipt. When using the refund API you should take into account these notes: - At the moment refund API allows creating a refund only for sales receipts which are paid by a single payment. For any attempt to make a refund for a sales receipt that has more than one payment Loyverse API will respond with an error. - Refund API doesn't support a refund of receipts paid by integrated payments using Loyverse POS app (e.g. iZettle, Sumup, etc.). For this purpose please use Loyverse POS app. - If a refund is created successfully, it will cause a restock of items specified in a refund receipt.”

Creates a refund against an existing sales receipt and, when it succeeds, puts the refunded items back into stock.

When to use it
when returns are approved in a support tool and the refund should follow without a cashier.
Watch out
it only works on receipts paid with a single payment, not on those paid through a payment provider integrated in the Loyverse POS app.
4

Create or Update Category

Action

In Zapier“Creates or Updates a single category.”

Creates a category for your items, or renames and updates an existing one, so the catalog stays organized from outside.

When to use it
before pushing items, so each one lands in a category that exists.
Watch out
the Name field is required, even when the step only updates a category.
5

Create or Update Single Customer

Action

In Zapier“Creates or Updates a Single Customer.”

Puts a customer into Loyverse, or refreshes an existing record, so the till recognizes them at checkout.

When to use it
when people sign up on your website and should exist in the POS before their first visit.
Watch out
Name is the only required field, so check the source sends enough details to recognize the person later.
6

Create or Update Discount

Action

In Zapier“Creates or Updates a single discount.”

Creates a discount the cashier can apply, or edits one already in the back office.

When to use it
to roll out a promotion decided in your planning tool without keying it in by hand.
Watch out
Type and Name are required, and Restricted Access set to true means the POS asks for a password before the discount applies.
7

Create or Update Modifier

Action

In Zapier“Creates or Updates a modifier.”

Builds or edits a modifier, the options a customer can add to an item, with their prices and order.

When to use it
when the same set of extras must exist across several items and you maintain it elsewhere.
Watch out
four fields are required: the modifier name, the option name, the price and the option position.
8

Create or Update POS Device

Action

In Zapier“Creates or Updates a single POS device.”

Registers a point of sale device under a store, or updates one that is already registered.

When to use it
when opening a new till point is planned in another tool and you want the device ready in Loyverse.
Watch out
Name and Store ID are both required, so look up the store first with Get List of Stores.
9

Create or Update Supplier

Action

In Zapier“Creates or Updates a single supplier.”

Adds a supplier to the back office or updates the one you already have.

When to use it
when your supplier list is maintained in a purchasing spreadsheet and Loyverse should mirror it.
Watch out
Name is required; everything else is optional, so check that the record you get is complete enough to be useful.
10

Create or Update Tax

Action

In Zapier“Creates or Updates a tax.”

Sets up a tax in Loyverse, or changes an existing one, with its name and its rate.

When to use it
when a rate changes and you keep the reference rates in another system.
Watch out
both Name and Rate are required, so the source has to carry the rate as well as the label.
11

Delete Single Discount

Action

In Zapier“Deletes a single discount.”

Takes a discount out of the back office so cashiers can no longer apply it.

When to use it
to close a promotion when your planning tool marks it as over.
Watch out
Discount ID is required; the name is not enough, so look the discount up first with Get List of Discounts.
12

Delete Single Modifier

Action

In Zapier“Deletes a single Modifier.”

Deletes a modifier and the options it carried from the catalog.

When to use it
when a set of extras is withdrawn from every item at once.
Watch out
Modifier ID is required; Get List of Modifiers returns it if your source only knows the name.
13

Delete Single POS Device

Action

In Zapier“Deletes a single POS Device.”

Removes a point of sale device from the back office.

When to use it
when a till point is closed and its device should stop appearing in the store.
Watch out
POS Device ID is required; Get List of POS Devices lists the most recent devices first, which helps you spot the right one.
14

Delete Single Category

Action

In Zapier“Deletes a single category.”

Removes a category from the catalog by its ID.

When to use it
when a product family is dropped from your range and the category has become empty.
Watch out
Category ID is required, so pair it with Get List of Categories or Get Single Category to pass the right one.
15

Delete Single Customer

Action

In Zapier“Deletes a single customer.”

Removes one customer record from Loyverse, identified by its ID.

When to use it
when someone asks to be removed from your customer files and that request is logged in another tool.
Watch out
Customer ID is required, and Get Single Customer or Get List of Customers is how you obtain it.
16

Delete Singe Item

Action

In Zapier“Deletes a single item.”

Removes one item from the Loyverse catalog, picked by its ID. The name is spelled this way in the editor.

When to use it
when a product is discontinued in your master list and should disappear from the till too.
Watch out
Item ID is required; Get List of Items with Show Deleted can still list removed items afterwards.
17

Delete Single Supplier

Action

In Zapier“Deletes a single supplier.”

Deletes a supplier you no longer buy from out of the back office.

When to use it
to keep the Loyverse supplier list in step with your purchasing records.
Watch out
Supplier ID is required; Get List of Suppliers gives you the ID behind each name.
18

Delete Single Tax

Action

In Zapier“Deletes a single tax.”

Removes a tax from Loyverse by its ID.

When to use it
when a rate is abolished and should no longer be offered at the till.
Watch out
Tax ID is required; Get List of Taxes, with Show Deleted if needed, returns the IDs.
19

Delete Single Variant

Action

In Zapier“Deletes a single variant.”

Deletes one variant of an item, such as a size or a color you no longer sell, and leaves the item itself in place.

When to use it
to retire a single option without touching the rest of the product.
Watch out
Variant ID is required; Get List of Variants is where to find it.
20

Update Inventory Levels for Items

Action

In Zapier“Batch updates Inventory Levels for Item Variants.”

Sets new stock levels for item variants in a store, in one batch, by giving the stock figure after the change.

When to use it
when a delivery is counted in another tool and Loyverse should show the new quantities.
Watch out
Variant ID, Store ID and Stock After are required; the name Stock After points to the stock after the change, so check on a test variant how Loyverse applies your figure before you publish.
Searches

The 30 Loyverse searches on Zapier

30 search steps look for data that already exists in Loyverse, so a later step can use it.

A search step looks up something that already exists in Loyverse and hands it to the steps after it. In the editor, the searches sit at the bottom of the Action event list, under SEARCH. Loyverse offers no find-or-create variant: no search here creates a missing record.

1

Get List of POS Devices

Search

In Zapier“The list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first”

Returns the point of sale devices registered in your account, sorted so the most recent ones come first.

When to use it
to find the ID of a device before a later step updates it with Create or Update POS Device or removes it.
Watch out
Show Deleted brings back removed devices too, so leave it off unless you are cleaning up after a deletion.
2

Get Single POS Device

Search

In Zapier“Get a single pos device.”

Fetches the full record of one point of sale device, starting from its ID.

When to use it
when a previous step gave you a device ID and the next one needs the rest of the record, such as its name or the store it belongs to.
Watch out
POS Device ID is required, so map it from an earlier step.
3

Get List of Categories

Search

In Zapier“Get list of all categories.”

Lists every category your catalog contains, so a Zap can see how products are grouped before it touches them.

When to use it
before Create or Update Single Item, to check which category names already exist and avoid creating a near-duplicate.
Watch out
with several matches, the multiple-results setting decides whether you keep the first one or pass them all on.
4

Get List of Discounts

Search

In Zapier“Get list of discounts”

Pulls the discounts currently set up in the back office into the Zap, ready for the steps that follow.

When to use it
to find the ID of a promotion your planning tool only knows by name, before Create or Update Discount edits it or Delete Single Discount closes it.
Watch out
if two discounts share a similar name, check which one the setting keeps.
5

Get List of Employees

Search

In Zapier“Gets a list of employees.”

Gives the Zap the people registered as employees in your Loyverse account.

When to use it
to attach a readable name to an employee ID an earlier step handed over, before writing it to a staff report.
Watch out
the list covers every employee, so narrow it with what a later step needs rather than copying it all into a message.
6

Get List of Inventory Levels for Items

Search

In Zapier“Gets a list of Inventory Levels of Item Variants.”

Reads the current stock levels of your item variants, as Loyverse holds them right now.

When to use it
to compare what Loyverse shows with a count made in another tool, before deciding whether Update Inventory Levels for Items should run.
Watch out
this only reads stock; nothing changes until an action writes the new level.
7

Get List of Modifiers

Search

In Zapier“Gets list of modifiers.”

Collects the modifiers of your catalog, each with the options a customer can add to an item.

When to use it
to get the ID of a set of extras before Create or Update Modifier edits it or Delete Single Modifier removes it.
Watch out
a source that knows only the modifier name needs this step first, since the actions work by ID.
8

Get List of Customers

Search

In Zapier“Get list of Customers”

Hands the Zap the customers stored in Loyverse, so later steps can work with records that already exist.

When to use it
to see whether a person is already on file before Create or Update Single Customer adds them a second time.
Watch out
when several people match, the multiple-results setting decides which record the next step receives.
9

Get List of Items

Search

In Zapier“Get list of items”

Fetches the products in your catalog in one go, so a Zap can work from the real list instead of a copy.

When to use it
to get the ID of a product your spreadsheet knows only by name, before an update or a deletion.
Watch out
Show Deleted includes removed items, which helps after a deletion but clutters a normal lookup.
10

Get List of Payment Types

Search

In Zapier“Get list of Payment Types”

Returns the payment types configured in your back office, the ones a cashier picks when a customer pays.

When to use it
to turn a payment type ID from an earlier step into a label a person reading the report understands.
Watch out
the list reflects your setup at the moment the Zap runs, so a type you add or remove changes what it returns.
11

Get List of Receipts

Search

In Zapier“Get list of receipts”

Lists receipts from your Loyverse account, for a Zap that needs sales data without waiting for a new one.

When to use it
in a Zap started by another app, for instance a form asking for a report, since Receipts Update only covers events after publishing.
Watch out
the list can be long; decide with the multiple-results setting whether every receipt goes on or only the first.
12

Get List of Shifts

Search

In Zapier“Get list of shifts”

Pulls the shifts recorded in the back office into the Zap, so a later step can report on them.

When to use it
to feed a staff report built by a Zap that starts somewhere else, since Shifts Create only fires for new shifts.
Watch out
pick the multiple-results option carefully, or the report only ever shows the first shift.
13

Get List of Stores

Search

In Zapier“Get list of stores”

Lists the stores attached to your Loyverse account, with the IDs that several actions ask for.

When to use it
to find the Store ID required by Create or Update Receipts, Create or Update POS Device and Update Inventory Levels for Items.
Watch out
Show Deleted adds closed stores to the results, so leave it off when you want live stores only.
14

Get List of Taxes

Search

In Zapier“Get list of taxes”

Returns the taxes defined in Loyverse, so a Zap knows which rates the till currently applies.

When to use it
to get the ID of a rate before Create or Update Tax changes it or Delete Single Tax removes it.
Watch out
Show Deleted brings back removed taxes as well, which you rarely want in a pricing check.
15

Get List of Suppliers

Search

In Zapier“Gets a list of suppliers.”

Gathers the suppliers recorded in the back office, so the Zap can match a name to an existing record.

When to use it
to check that a supplier exists before Create or Update Supplier adds it again, or to get the ID for Delete Single Supplier.
Watch out
two suppliers with close names will both match; check which one the setting keeps.
16

Get List of Variants

Search

In Zapier“Get lists of item variants.”

Returns the variants of your items, such as a size or a color, each with its own ID.

When to use it
to obtain the Variant ID that Update Inventory Levels for Items and Delete Single Variant both require.
Watch out
stock lives on variants, not on the item, so this is usually the step a stock Zap is missing.
17

Get Merchant Information

Search

In Zapier“Get merchant information.”

Reads the details of the merchant account behind your connection, the business itself rather than one store.

When to use it
to stamp the business details on a document or a message that a later step produces, without typing them into the Zap.
Watch out
the result describes the account you connected, so a Zap on a colleague's login returns their business.
18

Get Single Category

Search

In Zapier“Get Single Category.”

Fetches one category from its ID and returns its details, including the readable name.

When to use it
when an earlier step gives you only a category ID and your report should show the name people recognize.
Watch out
Category ID is required, so map it from an earlier step or from Get List of Categories.
19

Get Single Customer

Search

In Zapier“Get Single Customer”

Looks up one customer from their ID and returns the complete record held in Loyverse.

When to use it
when an earlier step gives you a customer ID and the next step needs the name or the contact details.
Watch out
Customer ID is required; a name alone will not do, so map the ID itself.
20

Get Single Discount

Search

In Zapier“Gets a single discount.”

Pulls one discount from the back office with its current settings.

When to use it
to check a discount before Create or Update Discount edits it, so the Zap changes the one you meant.
Watch out
Discount ID is required, which usually means running Get List of Discounts earlier in the Zap.
21

Get Single Employee

Search

In Zapier“Gets a single employee.”

Fetches one employee record, starting from its ID.

When to use it
to put a name on an employee ID before it reaches a team message.
Watch out
Employee ID is required, so the step has to come after something that supplies it.
22

Get Single Item

Search

In Zapier“Get single item”

Returns one product of the catalog with its details, from its ID.

When to use it
when an earlier step only passed a product ID and your message should name the product.
Watch out
Item Id is required; look for it in the data an earlier step brought back during its test.
23

Get Single Modifier

Search

In Zapier“Gets a single modifier.”

Reads one modifier and the options it offers, with their prices.

When to use it
to check the prices of extras before Create or Update Modifier rewrites them from another source.
Watch out
Modifier ID is required, so pair it with Get List of Modifiers when your source only has the name.
24

Get Single Payment Type

Search

In Zapier“Gets a single payment type.”

Translates one payment type ID into its readable name.

When to use it
to show a payment type in plain words in a sales log, instead of a bare ID nobody can read.
Watch out
Payment Type ID is required, so an earlier step, or Get List of Payment Types, has to supply it.
25

Get Single Receipt

Search

In Zapier“Get a single Receipt.”

Fetches one receipt from its number, so the rest of the Zap works on the sale itself.

When to use it
before Create Refund Receipt, to check that a sale exists under that number.
Watch out
Receipt Number is required; it is the receipt number, not an internal ID.
26

Get Single Shift

Search

In Zapier“Gets a single shift.”

Reads one shift from the back office and returns its details.

When to use it
to complete a shift record in a report when only its ID came through from an earlier step.
Watch out
Shift ID is required, and its dropdown shows each shift by the time it opened.
27

Get Single Store

Search

In Zapier“Get Single Store”

Retrieves the details of one store, from the Store ID.

When to use it
to add the store name to a message when an earlier step only gave you its ID.
Watch out
Store ID is required; Get List of Stores finds it if no earlier step provides it.
28

Get Single Supplier

Search

In Zapier“Gets a single supplier.”

Fetches one supplier record with the details kept in the back office.

When to use it
to bring a supplier's details into a reorder message after a stock alert from Inventory Update.
Watch out
Supplier ID is required, so the Zap must know which supplier before this step runs.
29

Get Single Tax

Search

In Zapier“Gets a single tax.”

Reads one tax from Loyverse together with its rate.

When to use it
to confirm the current rate before a Zap writes prices into another system.
Watch out
Tax ID is required; map it from a record that carries it or from Get List of Taxes.
30

Get Single Variant

Search

In Zapier“Gets single item variant.”

Pulls one item variant from its ID, such as the exact size or color behind a stock figure.

When to use it
when an earlier step gives you a Variant ID, to tell the team which size or color is concerned rather than quoting an ID.
Watch out
Variant ID is required, and it is the variant, not the parent item, that this step needs.

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 there 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?
    This box turns a search into a find-or-create elsewhere on Zapier. Loyverse exposes no such variant, so here a search only ever looks.
  3. If multiple search results are found?
    Three ways out when several records 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 Loyverse Zap breaks

Zapier lists no help article and no rate limit specific to Loyverse. What goes wrong comes from the refund rules, the required IDs, and how every Zap behaves.

These six cases are the ones to rule out first. If yours is not here, our Zapier troubleshooting page is the next stop.

  • A refund that is refused

    Create Refund Receipt only handles receipts paid with a single payment. A sale split across two payments, or paid through an integrated provider in the POS app, is rejected.

  • A Zap that feeds itself

    Customer Update plus Create or Update Single Customer, or Items Update plus Create or Update Single Item, can set each other off again and again and burn tasks fast.

  • The same receipt twice

    Receipts Update fires on creation and on every update. A spreadsheet row per run can therefore end up with one receipt on two lines.

  • An action missing its ID

    Every delete and many updates require an ID. If no earlier step or search supplies it, the action fails.

  • Past receipts never arrive

    A Zap only reacts to events after you publish it. Earlier receipts and stock moves stay out, and moving that history is a separate job.

  • A bulk change held back

    After a large import into the catalog or the stock, a sudden huge batch of events can be held back by Zapier's flood protection instead of running each one.
Need help

Need help automating Loyverse with Zapier?

A person reads every message.

FAQ

Loyverse Zapier integration: frequent questions

01Is the Loyverse Zapier integration free?
Yes, for simple Zaps. Loyverse is not a premium app, so the free plan can use it, with 100 tasks a month. That plan builds two-step Zaps only, one trigger and one action, which covers a receipt-to-spreadsheet log. Anything with a filter, one of the 30 searches or a second action becomes a multi-step Zap and needs a paid plan. A stock alert that only fires below a threshold is a typical example.
02How many tasks does a Loyverse Zap use?
One per action that succeeds, each time the Zap runs. The trigger costs nothing, and a run stopped by a filter costs nothing after that point. A receipt logged in a spreadsheet is one task; a receipt that also feeds a team message is two. Failed actions are not counted. Watch the busy triggers: Receipts Update and Inventory Update fire on every receipt and every stock change, and each run multiplies the actions it contains.
03Is Loyverse instant on Zapier?
Yes. All five Loyverse triggers are instant: Loyverse itself tells Zapier when a receipt, a stock level, an item, a customer or a shift changes, and the Zap starts at once. That holds on every plan, free included, so the polling interval grid does not concern this app. In the editor, a lightning bolt marks Zaps built on an instant trigger. The only exception to watch is Shifts Create, which waits for the shift to sync to the Back Office.
04What do you need to connect Loyverse to Zapier?
A Loyverse account and a Zapier account, plus access to the stores and records the Zap will touch. You add the connection from the Apps page of Zapier with + Add connection, sign in to Loyverse and grant access. Before building, note your Store ID: several actions require it, including Create or Update Receipts and Update Inventory Levels for Items. Get List of Stores returns it if you do not have it at hand.
05Why does Create Refund Receipt fail on some receipts?
Because Loyverse only accepts refunds on receipts paid with a single payment. A sale split across more than one payment, or paid through a payment provider integrated in the Loyverse POS app, is refused; for the latter, the refund has to be made in the Loyverse POS app. When a refund does go through, the refunded items return to stock. Placing Get Single Receipt before it at least confirms that the receipt number exists.
06What if the Loyverse operation you want is not on Zapier?
Then Zapier cannot do it today, and no setting will reveal it. Loyverse covers a lot, 55 operations in all, but there is no trigger for deletions, new discounts or new employees, and no search creates a missing record. Before building around a gap, check the full list on this page, then compare what other automation platforms offer for Loyverse. The searches in particular cover most of the back office, so a missing piece is often a trigger rather than a lookup.
07Zapier, Make or n8n for Loyverse?
Decide on criteria rather than on a ranking. Start with speed: all five Loyverse triggers are instant on Zapier, free plan included, so a receipt or a stock change reaches your Zap at once. Then count the steps: deletes and many updates need an ID that a search has to fetch first, and that search makes the Zap multi-step, so a paid plan. Finally, check that the other platform covers the Loyverse operations you rely on, refunds and stock updates in particular, before you compare anything else.
Same platform

Other docs you might need on this stack.

Browse all integrations