Connecting Loyverse to Make.com lets you generate a PDF receipt after every completed sale and email it to the customer automatically. The workflow requires a Make.com account, a Loyverse API token, and an email service module — no code required and setup takes under an hour.

Why Automate Loyverse Receipt Delivery?

Paper receipts get lost. Email receipts get ignored when they arrive late. The gap between those two outcomes is where Make.com’s scenario-based automation fills in — triggering a formatted PDF the moment a sale closes, not minutes later when a staff member remembers to follow up.

Loyverse is a capable free POS system for retail and hospitality operators. Its webhook and API layer is well-documented, which makes it a straightforward trigger source inside a Make scenario. When you wire the two together, every transaction produces a paper trail your customer receives before they reach their car.

Beyond customer experience, automated receipts reduce disputes, simplify bookkeeping, and free the staff member who would otherwise handle follow-up emails. If you’re thinking about other automations that are now easy to build without a developer, receipt automation is one of the fastest wins available.

What You Need Before You Start

Before building the scenario, confirm you have the following:

• Loyverse account with API access enabled. Log into your Loyverse back office, navigate to Integrations, and generate an API token. Keep this token — you’ll paste it into Make.com.
• Make.com account. A free tier works for low-volume stores. Higher transaction volumes benefit from a paid plan with more operations per month.
• An email service connected to Make.com. Gmail, Outlook, or an SMTP connection all work. Gmail is the fastest to configure for most small operators.
• A PDF generation service. Make.com does not natively render PDFs. You’ll need a module from a service such as PDF.co, PDFMonkey, or DocuPilot — all of which have Make.com native connectors.
• Your receipt template. Most PDF services accept an HTML template with variable placeholders. Design yours to include your logo, business name, itemized line items, totals, and tax figures.

If you’re evaluating whether Make.com is the right platform for this build, the Make vs. Zapier pricing and feature breakdown covers the key differences in connector depth and operation costs.

Step 1: Enable the Loyverse Webhook in Make.com

Make.com connects to Loyverse via its REST API using a polling trigger or a webhook. For real-time receipt delivery, a webhook trigger is the correct choice — it fires the scenario the moment Loyverse records a completed receipt rather than waiting for a scheduled check.

1. Inside Make.com, create a new scenario and choose Loyverse as the trigger module.
2. Select the trigger event Watch Receipts (or the equivalent event in your Make.com Loyverse connector version).
3. Paste your Loyverse API token when prompted. Make.com will validate the connection immediately.
4. Run a test transaction in Loyverse to confirm Make.com receives a sample payload. You should see item names, quantities, prices, totals, taxes, and customer data if a customer profile was attached to the sale.

Note the exact field names in the payload. You’ll map these to your PDF template in the next step. Common fields include receipt_number, receipt_date, line_items, total_money, and customer_email.

Step 2: Map Receipt Data to a PDF Template

Add a PDF generation module after the Loyverse trigger. The exact module name depends on the service you chose, but the configuration pattern is the same across all of them.

1. Create your HTML receipt template inside the PDF service’s dashboard. Use placeholder variables like {{receipt_number}}, {{line_items}}, and {{total}} — the exact syntax varies by service.
2. In the Make.com module, map each Loyverse output field to the corresponding template variable. Drag the field name from the Loyverse output panel into the correct variable field.
3. For line items, use Make.com’s Array Iterator module to loop through each item in the sale before passing the data to the PDF module. This ensures a receipt with five items generates five rows, not a single concatenated string.
4. Test the PDF module with your sample payload. Download the resulting PDF and verify every field renders correctly before moving on.

Common mapping mistakes and how to catch them are covered in the guide on evaluating a Make scenario before it goes to production — the same checklist applies to manually built scenarios.

Step 3: Add the Email Module

With a working PDF output, the final step is attaching that file to an outbound email.

1. Add a Gmail (or your chosen email service) module after the PDF generator. Select Send an Email.
2. Map the To field to the customer email address from the Loyverse payload. If Loyverse returns a customer object, the field is typically nested as customer.email.
3. Write a subject line. A simple format works well: Your receipt from [Business Name] — #{{receipt_number}}.
4. In the Attachments section, map the PDF file output from the PDF generation module. Make.com passes the file as a binary data bundle — most email modules accept this directly in the attachment field.
5. Add a short plain-text or HTML body. Keep it brief: confirm the purchase, reference the receipt number, and provide a contact method for questions.

If you want to route the email differently based on transaction type — for example, send a different template for refunds — add a Router module between the PDF generator and the email module. The guide on routed error handling in Make explains the Router module logic in detail.

Step 4: Add Error Handling

A receipt automation that silently fails is worse than no automation at all. Add a fallback path so that any scenario error generates an alert rather than disappearing.

1. Right-click any module in the scenario and select Add error handler.
2. Choose the Rollback or Resume strategy depending on whether a failed email should halt the scenario or allow subsequent modules to continue.
3. Add a notification action in the error path — a Slack message or a backup email to your operations address works well.
4. Log failed transactions to a Google Sheet or Airtable row so you can manually resend receipts to affected customers.

For most small operators, a simple error-to-Slack notification is sufficient. Larger transaction volumes benefit from the structured approach described in the AI-built error handler case study.

Step 5: Test With Live Transactions

Before activating the scenario for production traffic, run at least three complete test transactions in Loyverse using a real email address you control.

• Verify the PDF renders correctly with real product names and prices.
• Confirm the email arrives within 30 seconds of the Loyverse transaction completing.
• Check that multi-item receipts display all line items correctly.
• Test a transaction where no customer email is on file — confirm the scenario handles a null email field without breaking the entire workflow. Add a Filter module before the email step that only proceeds when a customer email exists.

Once all three tests pass, toggle the scenario to Active in Make.com and set the scheduling to Immediately (webhook) or a short polling interval if you’re using the API trigger instead.

How to Customize the Receipt Template

A receipt is a customer touchpoint. The default template from most PDF services is functional but generic. Spend 30 minutes on these customizations before going live:

• Logo: Upload your business logo as a hosted image URL and reference it in the HTML template header. Avoid base64-encoded images — they inflate file size and sometimes break PDF rendering.
• Brand colors: Update the CSS in your HTML template to match your primary brand color for headers and borders.
• Return policy or contact line: Add a single line at the bottom of the receipt with your return policy summary and a contact email or phone number.
• Receipt numbering: Use the Loyverse receipt_number field directly rather than generating a separate ID. This keeps your records consistent across Loyverse and your email archive.
• Tax line display: Loyverse returns tax as a separate field. Display it as a distinct line item above the total rather than embedded in the subtotal to meet most jurisdictional receipt requirements.

How to Know It Worked

The workflow is functioning correctly when all of the following are true:

• Every completed Loyverse sale where a customer email exists triggers an outbound email within 60 seconds.
• The attached PDF opens without errors and displays the correct receipt number, date, itemized list, subtotal, tax, and total.
• The scenario execution log in Make.com shows no errors for the last 50 runs.
• Your error-handling notification has not fired in the past seven days of normal operation.
• A manual spot-check of 10 emailed receipts matches the corresponding Loyverse records exactly.

Common Mistakes

Using a polling trigger instead of a webhook. A five-minute polling interval means customers wait up to five minutes for a receipt. Switch to the webhook trigger for real-time delivery.

Skipping the Array Iterator for line items. Without iterating the line-items array, your PDF will show only the first item in a multi-item sale — or concatenate everything into a single unformatted string. Always add the Iterator module before the PDF generator.

Not filtering for missing customer emails. If a sale is completed without a customer profile attached, the email field returns null. An unhandled null value breaks the email module and can halt the entire scenario. Add a filter that checks for a non-empty customer email before the email step.

Hardcoding business details in the scenario instead of the template. If your business name or address changes, you want to update the PDF template — not hunt through scenario module fields. Keep all static business information inside the template.

Skipping error handling entirely. Automation without error handling is a liability. A single bad transaction can silently break the scenario and leave every subsequent customer without a receipt until someone notices. The five minutes it takes to add a Slack alert to the error path is worth it.

Scaling This Workflow

Once the basic receipt automation is stable, several extensions are worth considering:

• CRM logging: Add a module that writes each transaction — customer email, receipt number, total, date — to a CRM or spreadsheet for sales reporting.
• Loyalty follow-up: Add a conditional branch that sends a loyalty offer email to customers who have made more than five purchases. Map the Loyverse customer visit count field to trigger the condition.
• Refund receipt variant: Build a parallel workflow that watches for refund events in Loyverse and generates a refund confirmation PDF with the same branding.
• Accounting sync: Route transaction data to QuickBooks, Xero, or another accounting integration alongside the email receipt. This turns one trigger into two outputs without doubling your build complexity.

For operators thinking about where receipt automation fits in a broader ops improvement plan, the OpsMap checklist is a useful framework for sequencing which workflows to build next.

Additional Reading

• Make.com FAQ: Everything Zapier Users Ask Before Switching
• What Is a Make Scenario? The Plain-English Guide for Zapier Users
• Make vs Zapier: A Straight Pricing and Feature Breakdown for 2026
• 10 Automations That Are Finally Easy to Build With Make + AI — No Developer Needed
• How to Set Up Routed Error Handling in Make With AI Assistance
• How an AI-Built Error Handler Reduced Technician Research Time From 20 Minutes to a Glance
• 7 Questions to Ask Before You Automate Anything (The OpsMap Checklist)
• How to Evaluate a Make Scenario Built by AI Before It Goes to Production
• How to Build a Make Scenario With Claude: A Step-by-Step Walkthrough
• Make vs N8N: When Self-Hosting Stops Being Worth It