LoyalKit Cards for small business
Run a loyalty program without replacing or integrating your POS
Understand the tradeoffs of a standalone loyalty workflow and when its speed, portability, and simpler setup make sense.
A loyalty program can run beside an existing point-of-sale system instead of connecting to it. LoyalKit uses a customer pass in Apple Wallet or Google Wallet and a separate staff action, so a business can keep its register and launch without importing products or transaction data.
The customer scans your shop's join QR code.
They add the branded card to Apple Wallet or Google Wallet.
Staff add stamps or points and the Wallet pass updates.
What “without POS integration” means
The POS remains responsible for products, totals, discounts, taxes, refunds, receipts, and payment. LoyalKit remains responsible for loyalty identity, stamps, points, rewards, staff permissions, and recorded loyalty activity.
Staff finish the sale in the POS, then record the qualifying loyalty action with the LoyalKit iPhone scanner app or web dashboard. Nothing is automatically read from the receipt. Nothing in LoyalKit changes the POS transaction.
The exact counter workflow
- Complete the customer's sale in the existing POS or register.
- Apply the business's written loyalty rule to decide whether the sale qualifies.
- Ask the customer to open their Apple Wallet or Google Wallet loyalty pass and show its individual QR code.
- Scan the pass QR with the LoyalKit iPhone app. Authorized staff can instead find the customer in the web dashboard.
- Confirm the customer record and choose the permitted stamp, points, or redemption action.
- Verify the recorded activity and tell the customer their updated progress.
The customer's pass QR identifies the loyalty record. It is not a payment QR, does not contain the sale total, and does not use NFC to read a purchase. The customer-side digital loyalty card overview explains the pass and supported-device experience.
Manual versus integrated loyalty
| Area | LoyalKit standalone workflow | POS-integrated loyalty |
|---|---|---|
| Setup | Keep the existing checkout and configure loyalty separately | Depends on the POS vendor, plan, and integration setup |
| Customer identification | Scan the Wallet pass QR or use authorized dashboard search | May identify from a POS account, phone number, or connected pass |
| Earning | Staff select the correct loyalty action | May calculate automatically from transaction data |
| Refunds | Staff follow the written correction process | May reverse loyalty from connected refund data |
| Line-item rules | Best kept simple enough for reliable manual entry | Can fit product, category, discount, and tax conditions when supported |
| POS changes | Loyalty records are not inherently tied to the register vendor | Migration depends on the POS ecosystem and export options |
| Staff workload | One additional action at qualifying checkout or redemption | Can be lower after a correct integration is configured |
| Failure mode | Missed or incorrect manual action | Sync, mapping, configuration, or integration failure |
When a standalone workflow is a good fit
Manual loyalty can fit when the business wants to keep its current register, the rule is quick to apply, staff can accept one short action, and a technical integration is unnecessary. It can also fit a business evaluating loyalty before committing to a larger checkout migration.
A fixed stamp for a clearly defined visit or item is usually easier to run manually than a formula based on the whole receipt. Flexible points can still work if staff use simple earning presets or can enter an authorized amount consistently.
Use a standalone loyalty program when
- The business wants to keep its current POS or cash register.
- The earning rule is clear without importing receipt line items.
- A short staff action is acceptable at qualifying checkout and redemption.
- Managers can define staff permissions and review corrections.
- The business values a loyalty record that is separate from the POS vendor.
- Customers commonly use compatible iPhones or supported Android phones for Wallet passes.
When an integrated product is better
Choose a supported POS-integrated loyalty product when the program requires automatic spend conversion, item- or category-level rules, refund reversals from transaction data, cashier prompts inside the register, receipt-linked attribution, or a single vendor for checkout and loyalty support.
Integration can reduce manual work, but only when the POS and loyalty provider support the exact workflow. Confirm supported countries, hardware, plan level, data ownership, migration, refund behavior, and what happens during an outage before choosing it.
LoyalKit should not be presented as a substitute for those requirements. Its value is a separate Wallet-based loyalty workflow, not hidden POS automation.
Staff training and controls
Removing a technical integration makes the operating process more important. Train staff on what qualifies, when to record the action, how to confirm the customer, who can redeem, and how to correct an eligible mistake. Keep iPhone scanner access limited to authorized staff, remove access when someone leaves, and review unusual activity.
An Android customer can carry a Google Wallet pass. The staff scanner app is for iPhone, with the web dashboard as the separate authorized alternative. See the Apple Wallet and Google Wallet loyalty-card comparison for that device distinction.
Stamp and points choices without transaction data
A digital punch card can be a strong standalone format when one qualifying purchase or visit earns one stamp. Points can fit varied actions, but the business must define a reliable manual rule. Avoid asking staff to calculate a complex percentage from subtotal, tax, discounts, excluded products, and refunds while a queue is waiting.
Pricing and commitment
LoyalKit costs $25 USD month to month or $240 USD per year, plus applicable tax, after a 14-day trial. Both billing schedules include the same standard loyalty features. Visit LoyalKit Cards pricing for cancellation, tax, and refund details.
Will LoyalKit change anything in my POS?
No. LoyalKit does not replace, modify, or read transactions from the checkout system. Loyalty actions are recorded separately.
Does LoyalKit integrate with Square, Toast, Clover, Shopify POS, or Lightspeed?
No technical integration with those systems is claimed. LoyalKit can run beside them because staff record loyalty separately, but there is no automatic transaction sync or vendor certification.
Can staff award different point amounts?
Yes, when authorized staff can determine and enter the correct amount consistently. Complex automatic receipt calculations are outside a standalone workflow.
What happens after a POS refund?
The POS handles the refund. Authorized staff must follow the business's written LoyalKit correction process because refund data is not synchronized automatically.
What happens if the business changes POS later?
Because LoyalKit is separate, its loyalty records and Wallet passes are not inherently tied to the previous POS vendor.