MILabs
Integrations

Review request automation with Zettle point-of-sale data

How a review request automation works with Zettle, from a completed sale or visit to a short, opt-out aware message that staff can edit.

Updated 2026-08-04

Review request automation with Zettle

Zettle is a point-of-sale system from PayPal. Many of the businesses that use it, such as salons, wineries and cafes, want more reviews without asking every customer by hand. A review request automation can handle that step. The workflow watches for a completed visit or sale, then prepares a short message in the business's own voice and sends it by email or SMS. Zettle records the payment, while the request is handled by a connected tool such as Zapier, Make or n8n. Because Zettle exports and account settings differ between businesses, the first step is to confirm which events and contact details the account can supply. The owner or team lead keeps control of the wording, timing and linked review sites. Customers who have opted out are skipped before anything is sent. The build adds no new till process for staff, and card payment handling stays under Zettle and PayPal's terms.

How it works

  1. Confirm which Zettle reports and transaction exports the account can provide, and note the completed-visit signal the business relies on.

  2. Choose the connected system that holds bookings or job status, and map the event that marks a visit as finished.

  3. Write message templates in the business's own voice, then set a delay and a do-not-contact check before any request is sent.

  4. Run a test batch to staff-only addresses, review the log, and then switch the workflow on for live customers.

good questions, straight answers

Frequently asked questions

Can a review request automation work with Zettle data exports?
It can, where the account offers the reports or transaction exports the workflow needs. A connected tool can then use a completed sale or visit to start a request. Check first which report types the current Zettle account can produce. Customer contact details may not appear in every export, so the business may need to keep them in its booking or job system. Test the workflow against a copy of a real export before any message goes out.
What should I back up in Zettle first?
Before any automation touches Zettle data, export the sales and transaction reports the account allows, and store them in a secure place outside the workflow. Keep a dated copy of the current message templates, the opt-out list and the review site links. Note which settings the till uses, such as products and payment types, so changes can be traced. Do not store card numbers or customer names in shared documents. Confirm with the account holder what the terms allow before making copies.
How does a review request automation connect to Zettle?
It connects through the business's booking, job or visit system rather than through the card terminal itself. The workflow reads a completed visit or sale from whichever source the account can supply, then checks the customer's opt-out status. A message template is filled in with the customer's first name and sent by email or SMS. Zettle keeps handling the card payment as before. Where a direct link is not available, a scheduled export can feed the same steps, though with a delay.
Do I need a developer to connect a review request automation to Zettle?
Not always. Many of these workflows are assembled in a no-code tool such as Zapier, Make or n8n, provided the booking or job system offers a connector or a webhook. A developer is useful when the data needs cleaning, when the export format changes, or when the business wants custom checks on opt-outs. Staff should still review the message wording and the linked review sites. The answer depends on what the account and systems can provide.
How does a review request automation stay in step with Zettle?
It stays in step by checking the connected records on a regular schedule and by reviewing the workflow whenever Zettle changes its reports, exports or product settings. Zettle and PayPal update their products over time, so a feature that works today may change. Staff should confirm the current report types before each season's campaign, and keep a short log of what was sent. Any AI step, such as drafting wording, should be checked against the current product before it is relied on.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.