Skip to content
Guides

Does a loyalty program need POS integration?

Revisit team8 min read

Cover for Does a loyalty program need POS integration?

Which setup fits your checkout?

Start with one real order from your busiest shift. Work out who identifies the customer, where the bill total comes from and who corrects a mistake after the customer leaves. The answers will tell you whether you can run loyalty beside your existing point of sale (POS), use the loyalty features built into the POS, or connect the two systems.

SetupHow staff award loyaltyWhere to check a refundA good fit when
Standalone loyalty scannerAfter payment, staff scan a card in a separate browser or app and apply the earning.Check the original receipt and the corresponding loyalty entry. Follow the program's reversal procedure.The reward is easy to calculate and the extra step fits the checkout.
Loyalty built into the POSStaff attach the member to a sale and the POS applies its configured rule.Test what the POS reverses when the full order or selected items are refunded.Most sales use one POS and its loyalty rules match the business.
Custom API integrationA backend sends eligible order events to the loyalty system and records the result.Send the refund against the original order and reconcile any refusals.Several sales channels share a program or manual reconciliation takes too much work.

A standalone scanner can work alongside a cash register, a receipt app or a restaurant POS. Revisit's counter scanner runs in the browser on a device with a camera. Staff can use it to scan the customer's card while taking payment in the existing checkout system. Revisit also offers a developer API in pilot for businesses that need a custom connection. Ask about pilot access and vendor support before scheduling an integration. Revisit restaurant checkout · Revisit developer API

Put the same order through all three setups

Use an ordinary order and a rule your cashiers can explain. Say a café awards one point per ৳10 of eligible spend, with a fictional ৳450 qualifying order and 100 points needed for a reward. Write down whether the spend is before or after discounts and which charges count. Keep the same order and rule throughout the demo.

Award the 45 points

Standalone scanner. Take payment through the normal checkout, open the member's card in the loyalty scanner and enter the eligible bill amount. Confirm that 45 points were added once. Time the entire step from asking for the card until staff can start the next order. Include the time it takes a customer to find the card on their phone.

POS loyalty. Add the member to the transaction and complete the payment. Check the points entry against the final receipt. Run a second sale with a line-item discount or a delivery fee to verify that the POS uses the amount your program promises.

API integration. Link the checkout's customer to their loyalty membership and send the eligible earning when payment is confirmed. Keep a durable order reference. If the checkout loses its connection after sending the earning, retry safely and confirm that the same order awards points once. Revisit uses a request idempotency key and a durable source event ID for its loyalty actions. Follow the field and amount units for the specific API operation.

Refund ৳100 of the order

Under the sample rule, a ৳100 partial refund leaves ৳350 of eligible spend, or 35 points. The correct change is to take back 10 of the 45 points.

Standalone scanner. The person processing the refund finds the original loyalty earning and checks which corrections the program supports. If the counter offers only a full void for that earning, send the partial correction to the manager's agreed process. Avoid a casual adjustment without the original receipt or a record of who made the correction.

POS loyalty. Run a genuine partial refund in the demo. Verify whether the POS recalculates the earning, reverses all points, or expects someone to make a correction. Ask what happens when the return is processed at a different branch. The relevant proof is a receipt and a matching loyalty entry.

API integration. Reference the original earning and send a refund reference that can be used again if the refund event is retried. In the Revisit API, supported spend-based points reversals use the original earning rule to recalculate points on the amount kept. A refund that would take back benefits the customer already spent can require owner review. Log the refusal and route it to someone who can investigate. A payment refund and a loyalty reversal are separate actions. Check both records before closing the case.

Redeem a 100-point reward

Use a member who already holds at least 100 points. Ask staff to show the reward and the resulting balance in the same transaction. Then cancel the sale and check what happens to the reward.

With a standalone scanner, staff need an agreed order for checking the reward, applying it to the bill and confirming the loyalty redemption. With built-in POS loyalty, check whether the reward is spent when the order is opened, when it is paid or when the cashier confirms the benefit. For an integrated checkout, a reservation can hold the benefit during payment, confirm it on success or release it on cancellation when the loyalty system supports those actions.

Do one more test with two tills. Have both try to use the last available reward from the same test account. Verify that only one can complete and that staff know what to tell the other customer. For more counter examples, see the guide to duplicate stamps and disputed rewards.

When does a custom integration pay off?

Estimate the work the business performs today. Track how many loyalty orders the counter handles, how long the extra step takes, and how often a refund needs someone to reconcile two systems. Ask the vendor for the setup cost, ongoing support cost, which outlets it covers and who responds when orders fail to sync.

Consider this illustrative comparison. A shop handles 80 loyalty orders a day. A timed checkout trial shows the manual loyalty step takes an extra 12 seconds per order. That is 16 minutes of counter work per day, or about eight hours over 30 days. Integration may remove the bill re-entry, while staff may still need to identify the member or explain the reward. Repeat the timing with the proposed system to estimate the actual saving.

The same time can have different value. Eight hours spread across quiet shifts may be easy to absorb. A dozen seconds on every order during the lunch rush may be the reason staff stop offering loyalty. A refund queue across several branches can also justify integration even when checkout itself runs smoothly.

What should you ask your POS vendor?

Send the vendor one order and ask them to show the customer's balance before and after each action. Screenshots of the feature menu tell you what is available. A completed workflow tells you what your staff can rely on.

Ask the vendorEvidence to request
Which sales earn and what bill amount is used?One sale with a discount, an excluded item and a service or delivery charge.
How do you link the customer at checkout?An existing member, a new member and a customer who has left their phone at home.
What happens when the payment succeeds but loyalty times out?A retried order that produces one earning.
How are refunds handled?A full refund and a partial refund, each with its original receipt and corrected ledger entry.
Can two outlets redeem the same balance?A live test of two tills claiming the last reward.
Can staff keep selling during a connection outage?A failed loyalty operation, a clear customer message and a record the next shift can reconcile.
Can I export the history if we switch systems?A sample export with orders, loyalty actions, branch and durable customer identifiers.

Ask who owns setup for your specific POS version. A POS vendor may support an API and a loyalty provider may also offer one. Someone still has to connect them, test the checkout and support the connection. Document who that person is before promising a launch date.

How should you pilot the change?

Pilot one branch, one reward rule and one cashier workflow. Keep a written record of the original balances if you are moving existing members. Run training transactions with test accounts, then have a shift lead review the first day's sales, voids and loyalty entries against the receipts.

Give staff a fallback for the first week. If the loyalty operation times out, they can finish payment, retain the order reference and explain how the shop will verify the earning. The shift lead checks the history before adding anything manually. That prevents a successful but delayed integration from awarding a second earning when service recovers.

Choose the setup that passes the checkout and refund tests with the least ongoing work for your team. Compare pricing and outlet support using the Bangladesh loyalty software guide, then rehearse the chosen workflow with the cashier training playbook.

Turn first visits into regulars.

Live in 2 minutes. Pay with bKash, Nagad or card. 7-day money-back.

We use cookies and analytics tools (Google Tag Manager, PostHog) to see which pages bring shops to Revisit. Privacy policy