Store Credit, Gift Cards and Reward Points
Hyvä POS is in closed beta
Hyvä POS is currently in a closed beta (pilot phase) with a small group of merchants. It is not yet generally available: the App Store release follows the pilot, and features and configuration may still change, possibly in backwards-incompatible ways, before the general release. Want to take part? Sign up at hyva.io/pos.
A gift card bought online redeems at the register, points earned at the counter spend online, and a refund can land as store credit on the customer's account.
At the Register
With a customer attached to the sale, the register shows their balances: store credit, gift cards, reward points. Each can be applied to the sale:
- Gift cards: scan or type the code; the balance applies to the sale. Partial redemption leaves the rest on the card.
- Store credit: apply any amount up to the balance.
- Reward points: spend points converted to currency per your vendor module's rules. With Adobe Commerce the points are a tender; with Amasty they apply as a discount on the sale, as Amasty applies them in the webshop. Point earning on register sales follows whatever your vendor module does on order save; the POS does not add its own earning rules.
Refunds work in the other direction: a return can settle as store credit instead of cash or card.
Balances come from one unified lookup that returns all three types with their labels, currency conversion for points, and expiry dates where the vendor module tracks them. The debit happens server-side when the order saves, inside the module's transaction with an idempotency ledger, so a retried offline order cannot double-charge a gift card.
Your Existing Modules Keep Working
Credits run on a provider system. On Adobe Commerce, the native store credit, gift cards and reward points work directly. On Open Source, install the bridge for the vendor module you already run (Aheadworks, Amasty, Mirasvit), and the POS uses it: the same gift-card codes, the same balances, the same rules as your webshop. You pick the active provider per feature in the global settings.
Vendor Coverage
| Vendor | Store credit | Gift cards | Reward points |
|---|---|---|---|
| Adobe Commerce (native) | Yes | Yes | Yes |
| Amasty | Yes | Yes | Yes |
| Aheadworks | Balance only | Balance only | Balance only |
| Mirasvit | Balance only | No module | Balance only |
The Aheadworks and Mirasvit bridges (0.2.0) are proofs of concept: they show balances, but nothing can be spent at the register. When the register asks what a sale may spend, both answer that spending is not supported, and the order save takes nothing from the wallet.
One provider is active per feature (Stores → Configuration → Hyvä POS → Advanced → Credit & Return Providers); with nothing configured, the first installed provider is auto-detected. What each bridge covers, what it leaves out and how far along it is: bridge modules. If your vendor is not bridged yet, the contract is open: see building bridges.