Short answer
Before buying a loyalty connection, ask the provider to show a complete sale, a reward, and a refund using the checkout tools and plans you have. Confirm how the right customer gets credit, what happens when an update fails, and who fixes mistakes. Get the supported tasks and ongoing help in writing.
Start with the checkout you already use
A point-of-sale system, or POS, is the tool you use to record sales at checkout. A loyalty integration is a connection that passes the needed records between that tool and your rewards program.
The connection might let a paid purchase earn points or let staff apply an earned reward. Those are separate jobs. A connection that does one may need more work to do the other.
List your register software, devices, online store, booking tool, and payment provider. Include their exact plans and versions. Then write down the customer task you want to make easier. You may not need a connection to every tool on the list.
Check the rewards already offered by your checkout provider first. If they cover your needs and staff can use them, keeping that setup may be the simplest choice. Our customer loyalty software comparison explains how to build a shortlist.
Compare the ways to connect rewards and sales
Start with what your provider supports today. Ask which parts are ready to use, which need setup, and which would need to be built.
| Approach | When to consider it | What to confirm |
|---|---|---|
| Checkout’s own rewards | The program already covers the way you sell. | Supported purchases, refund rules, staff steps, and plan costs. |
| Supported connector | A provider has an existing connection for your exact tools. | Which records and actions it handles, required plans, and who supports it. |
| Custom connection | An important task is missing and the vendors allow the needed access. | What must be built, tested, maintained, and paid for after launch. |
| Separate reward card | A simple stamp or visit process is enough. | Who adds stamps, checks purchases, prevents repeat use, and corrects mistakes. |
A manual step can be reasonable for a small program. Watch it during a normal shift before deciding whether the extra work justifies an automatic connection.
Read the product’s limits behind the promise
Official product pages show why the exact setup matters. These examples were checked on November 17, 2026. They describe those products, not connections included in every Rehost project.
- Square: its Loyalty API documentation describes connecting Square Loyalty to outside applications. An API is a way for software tools to exchange information. The same documentation says program settings are managed in Square Dashboard. API access alone does not establish that a finished connection meets your needs.
- Smile: its Shopify POS page describes earning and using points in store with one balance shared with the online store. Ask to see that flow with the exact store and checkout setup in your proposal.
- Refunds: Square’s rewards and refunds guide says the effect on points depends on both the program type and the refund type. Ask about full refunds, partial refunds, and canceled sales separately.
Request a list of supported tasks, rather than accepting a logo or the word integrated as the whole answer. Also confirm whether the demo uses the same plans and features you would buy.
Check how the right customer gets the reward
Ask how a purchase is linked to a loyalty account. Staff may need to look up a phone number, scan a code, or use a customer record already attached to the sale.
Have the provider show what happens when two records look alike, a customer changes their contact details, or no account is found. Staff should have a clear way to resolve a mistake without giving one person another person’s points.
If customers use your website, app, and physical checkout, confirm how those routes reach the right account. Ask which tool keeps the final sales record and which keeps the reward balance. Agree how differences are found and corrected.
Ask for a full purchase and refund in the demo
Use test records and the provider’s supported test setup. You can review the buying decision without sharing real customer or payment details.
Example only: a test customer makes an eligible purchase and earns points once. They use an available reward on a later sale. The provider then shows a refund and explains what happens to the earned points and used reward.
- Find the customer. Check the account at the register and in the customer view.
- Finish the sale. Confirm when credit appears and which items, discounts, or charges count.
- Use a reward. Check the sale price and the remaining balance. Ask how repeat use of the same reward is prevented.
- Change the sale. Show a cancellation, a full refund, and a partial refund. Check earned points and redeemed rewards separately.
- Repeat an update. Ask how the system avoids adding points twice if the same sale update arrives again.
Include online and in-store sales if you need both. A successful example on one route does not establish that the other is supported.
Decide what staff do when a connection stops
Ask how staff can tell whether an update is delayed or has failed. Confirm who gets the warning, how missing activity is found, and how it is applied once without creating extra rewards.
Get a simple fallback for a busy shift. It might mean recording a missed purchase for later review or pausing a reward action. Do not promise customers that every offline action will work unless the provider has shown it.
Name who can change a balance and who can review that change. Ask what staff can see in the activity record when a customer says points are missing. Include support hours and the route for urgent help.
Put the connection and upkeep in the quote
The quote should name the tools, plans, supported actions, testing, staff training, and person responsible for each part. Check whether vendor permission or a separate subscription is needed.
Include setup work, required outside plans, ongoing support, and changes caused by vendor updates. Ask what happens if access changes or one provider stops supporting the connection. Our loyalty program cost guide helps you compare the first year with the regular running cost.
If you are also moving an existing program, treat that as separate work. The loyalty program migration guide covers records, balances, and unused rewards that may need to move before the new connection goes live.
When does the Rehost monthly bundle fit?
Rehost is worth comparing when you need a fully built website, customer app, and loyalty program together. All three are included in one monthly business bundle, with Rehost handling the agreed software work.
Connections depend on your tools, vendor access, and the written scope. Ask Rehost to confirm the checkout tasks, test process, outside costs, and ongoing help before agreeing to the work. A monthly bundle does not mean every checkout system or feature can be connected.
Review current bundle pricing and terms. If you mainly need a simple reward card, the small-business loyalty app buyer’s guide covers lighter options too.
FAQ
Does my loyalty program have to connect to the POS?
No. A separate stamp or visit card may cover a simple program. Compare the staff work and error checks with the cost and upkeep of a connection.
Does API access mean the connection is ready?
No. It means a vendor offers a way for software to exchange certain information. Confirm the permitted actions, required plans, work to build or set up the connection, and the tests it must pass.
Will refunds always reverse loyalty points automatically?
Do not assume so. The result depends on the tool, program rules, refund type, and connection. Ask the provider to show full and partial refunds and explain how staff correct an exception.
Bring your checkout details and one everyday sale
Write down the tools you use and the purchase customers make most often. Add one refund or missed-reward example. Those details give a provider a clear starting point for a useful demo and quote.
Explore Rehost’s website, app, and loyalty bundle, then check the monthly pricing and written terms.