--- title: "Loyverse Integration" description: "Connect AI agents to Loyverse POS. Agents manage catalog items and categories, register loyalty customers, record and export sales and refund receipts, monitor inventory stock levels, and read stores, payment types, and employees." url: https://flowrunner.ai/integrations/loyverse date_modified: 2026-08-01T02:40:32-07:00 --- # Loyverse [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Connect AI agents to Loyverse POS. Agents manage catalog items and categories, register loyalty customers, record and export sales and refund receipts, monitor inventory stock levels, and read stores, payment types, and employees. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · API key · available [Loyverse website](https://loyverse.com/) · [Platform Documentation](https://developer.loyverse.com/docs/) · Capability data verified 2026-08-12 1. A new online order arrives from the storefront 2. List Customers matches the shopper by email or phone against the loyalty database 3. Create Customer registers first-time shoppers so this sale earns them points from day one 4. List Items resolves each ordered SKU to a POS variant, and List Payment Types resolves how the sale was paid 5. Orders carrying a SKU that does not match any catalog variant stop for the store manager, who maps it or confirms it is genuinely new 6. Create Item fills the confirmed catalog gap with the right variant, price, and category 7. Create Receipt records the sale in the correct store with the customer attached 8. The day's synced sales post to the channel as one reconciled summary ## What This Integration Enables Retail truth splits the moment a store sells in more than one place. Loyverse is where the store actually operates, the registers, the staff, the loyalty balances, and every sale that happens outside it creates a second version of the business that someone reconciles later, or never. FlowRunner agents keep one ledger: online orders become receipts in the right store, shoppers become loyalty customers before the sale is recorded, and the stock counts reflect everything that sold, not just what crossed the counter. - Record externally generated sales back into Loyverse as receipts, with customers attached so points accrue - Register customers in the loyalty database ahead of the sale that rewards them - Export sales and refund receipts by store and date range for reporting and accounting - Sync catalog items, categories, and stock levels into spreadsheets, databases, and other stores - Enrich automations with store, payment type, and employee details One API constraint worth designing around: Loyverse accepts a single payment type per receipt, so split-payment sales cannot be recorded through the API and route to a person instead. ### Without FlowRunner **Two versions of the business**: Online sales live in the storefront, register sales live in the POS, and neither tells the whole story **Loyalty stops at the door**: A customer's online purchases earn nothing, so the loyalty program only sees half their spend **Stock counted by walking the floor**: Nobody knows a variant ran out until a customer asks and an employee goes to look ### With FlowRunner **One ledger of sales**: Online orders become POS receipts in the right store, so reporting and accounting read one source **Points follow the customer everywhere**: Shoppers are registered and attached to receipts automatically, whichever channel they bought through **Stock levels watched continuously**: Inventory sweeps flag low variants to the team before the shelf goes empty ## Use Case Scenarios ### Online orders join the ledger A [Shopify](https://flowrunner.ai/integrations/shopify) order lands. The agent matches the shopper with List Customers, registers newcomers with Create Customer, resolves variants and payment types, and calls Create Receipt against the right store. The customer's points balance grows with their online spend, end-of-day reporting includes every channel, and nobody exports a CSV to make the numbers agree. ### The stock check that never sleeps On a rolling schedule, List Inventory pulls in-stock quantities for tracked variants across stores. When a variant crosses its reorder threshold, the agent pulls its details with Get Item and posts an alert to [Slack](https://flowrunner.ai/integrations/slack) naming the variant, the store, and the remaining count. The reorder decision stays with the manager who knows the supplier lead times; the counting stops consuming anyone's afternoon. ### Loyalty data becomes lifecycle marketing After Create Customer or Get Customer returns a profile, the agent syncs it to [Klaviyo](https://flowrunner.ai/integrations/klaviyo) with the loyalty balance, total spend, and visit count as properties. The email program can now segment on how customers actually behave at the register: lapsed regulars, high-spend visitors, first-timers who never came back. Receipts pulled through List Receipts feed a daily revenue log in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), so marketing and finance read the same numbers. ## Human-in-Loop Highlight Create Receipt does not only record sales; it records refunds, and a refund receipt is a financial event. It changes reported revenue, adjusts the customer's loyalty balance, and lands in the same books the accountant closes at month end. A refund recorded against the wrong store, the wrong amount, or the wrong customer is not a row to quietly fix; it is a discrepancy someone has to explain. So FlowRunner flows post routine sales receipts autonomously and stop on refunds above the threshold the operator sets. The manager sees the original receipt pulled through Get Receipt, the refund amount, and the customer's history from Get Customer, then approves or rejects. The same gate catches the API's own edge: split-payment sales that cannot be represented as a single payment type queue for a person instead of being recorded wrong. Sales flow at machine speed; the entries that change what the business reports wait for judgment. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Catalog 4 - **List Items** Retrieves catalog items with category and item-ID filtering, cursor-paginated up to 250 per page. The resolution step that maps external SKUs to POS variants. - **Get Item** Retrieves one item's full details: variants, pricing, SKUs, category, tax assignments, and stock-tracking settings. - **Create Item** Creates a catalog item with a name and at least one priced variant, optionally with category, stock tracking, and a POS button color and shape. Runs after a human confirms the catalog gap is real. - **List Categories** Retrieves the account's item categories, cursor-paginated, for keeping external catalogs aligned with POS structure. ### Customers 3 - **List Customers** Retrieves loyalty customers with email, phone, and ID filtering, cursor-paginated. The match step before any sale is recorded. - **Get Customer** Retrieves one customer's full profile: contact details, points balance, total spend, visit count, and custom fields. The read that powers lifecycle segmentation. - **Create Customer** Creates a loyalty customer who can immediately earn and redeem points. The registration step that makes online shoppers full loyalty members. ### Receipts 3 - **List Receipts** Retrieves sales and refund receipts filtered by store, customer, and date range, cursor-paginated. The export behind reporting and accounting flows. - **Get Receipt** Retrieves one receipt's full detail by receipt number: line items, payments, taxes, discounts, store, customer, and totals. - **Create Receipt** Records a sale or refund with store, line items, and a payment. Accepts one payment type per receipt, so split payments route to a person. Refunds run behind this page's human gate. ### Inventory and Store 4 - **List Inventory** Retrieves in-stock quantities for variants across stores, filterable by variant and store. The read behind continuous stock watching. - **List Stores** Retrieves the account's business locations with names, addresses, and contact details. Store IDs anchor receipts and inventory filters. - **List Payment Types** Retrieves the configured payment types whose IDs build the payments array on new receipts. - **List Employees** Retrieves employees with names, contact details, and store assignments, for attributing sales and staff-aware routing. ## Frequently Asked Questions ### What can FlowRunner do with Loyverse? FlowRunner agents can run List Items, Get Item, and Create Item in Loyverse, plus 11 more actions. ### Does connecting Loyverse to FlowRunner require OAuth? No. Loyverse connects to FlowRunner with an API key, no OAuth flow required. ### Can Loyverse trigger a FlowRunner workflow automatically? Loyverse doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Loyverse?** This integration exposes Loyverse to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/loyverse. Site index: https://flowrunner.ai/llms.txt