3 min readNov 15, 2026by jakub
Customer Coupons
Give one customer a code that only they can use. Customer Coupons ties Magento's own cart price rule codes to an email address, so a code forwarded, posted on a coupon site or guessed gives everyone else the same "isn't valid" answer as a made-up code, while the customer it was issued to gets the discount in the cart, at checkout and on the order.
Latest version: 1.0.0 — changelog

Who it's for
- CRM and lifecycle teams sending one-to-one offers. Issue a code per address from the admin, a CSV file of up to 50,000 rows, the customer grid, the command line or a REST call; a repeated call or file with the same issuance key never issues twice.
- Stores whose codes leak. A personal code is checked against the shopper's identity every time totals are collected and once more when the order is placed, so a shared code earns nothing.
- Stores that sell to guests. A guest whose checkout email matches the recipient gets the discount (on by default, switchable per website); a guest without an email is asked to enter it or sign in.
- Stores with privacy obligations. Erase a recipient's coupon data on request, delete unusable coupons automatically after a set number of days, and plug into qoliber's GDPR Suite.
Why it matters
- Promotions stay with the customers you chose, instead of draining margin on a coupon site.
- Fewer "where is my code" tickets: customers find every code under My Account → My Coupons, and you can resend the email from the grid.
- Safe to automate: issuing is idempotent with an issuance key, so an integration or import can retry without creating duplicate discounts.
- Clear control: revoke a code and it stops working at once, even in a cart where it was already applied, while the record stays for your reports.
See it in action
- You issue a coupon from your CRM:
POST /V1/qoliber/customer-coupons/issuewith{"request":{"rule_id":12,"email":" [email protected] ","issuance_key":"crm-campaign-42/ann"}}. You get{"code":"7GQ2XK9PLMZD","is_replay":false,…}for[email protected], and repeating the call with the same key returns the same code instead of a second one. - You upload the same CSV of 10 addresses twice, with an
issuance_keycolumn. You get 10 coupons, and the second upload reportsIssued: 0. Already issued: 10. Failed: 0. - Ann's code is tried by someone else. They get "The coupon code isn't valid. Verify the code and try again.", the same answer as for a code that never existed; a shopper who isn't signed in is told "Sign in to use this coupon code." when guest redemption is off.

What you can do
| Feature | Benefit |
|---|---|
| Managing issued coupons | See every personal coupon with its recipient and status, revoke one or a filtered selection, resend the email, export the list. |
| Issuing personal coupons | Give a customer a code from the admin, a rule, the customer grid or an existing printed code, with an optional email. |
| Importing coupons from a CSV file | Issue thousands of personal codes in one upload, checked row by row before anything is created. |
| Coupon report | See per rule how many codes were issued, used, expired and revoked, and the orders they brought. |
| What shoppers see | Customers find and apply their codes in My Account; everyone else gets no hint the code exists. |
| Coupon emails | Send the code when it is issued and remind the customer before it expires, per store view. |
| Privacy: erasure and retention | Answer erasure requests in one step and delete unusable coupons automatically. |
| Command line, cron and queues | Script issuing, revoking and imports, and know what runs on its own. |
| Turning the module off safely | Make personal codes unusable before disabling, so they never become public codes. |
| REST and GraphQL API | Issue, search and revoke from other systems; headless storefronts list a customer's coupons. |



Competing solutions
The right-hand column describes common practice among marketplace extensions, not any particular vendor.
| Qoliber | Typical marketplace extension | |
|---|---|---|
| GitLab access | Full access to the module's GitLab repository — source, history, issues and merge requests | Varies by vendor |
| Packagist installation | Installed and updated with Composer from our private Packagist (qoliber.repo.packagist.com) | Varies by vendor |
| Slack access to the development team | A shared Slack channel with the developers who build and maintain the module | Usually ticket-based |
| Unit tests | 215 PHPUnit unit tests (90 classes) in the repository | Not typically published |
| Integration tests | 262 Magento integration tests (101 classes), run before every release | Not typically published |
| E2E Playwright tests | 97 Playwright end-to-end tests (78 spec files) on Luma and Hyvä, run before every release | Not typically published |
| Documentation | Full docs portal: install, configuration, usage, troubleshooting, developer guide, API reference | Varies by vendor |
| Hyvä support | qoliber/customer-coupons-hyva: the My Coupons page for Hyvä themes | Varies by vendor |
| PHP / Magento range | PHP 8.1 to 8.5; Magento Open Source and Mage-OS 2.4.7 and later | Varies by vendor |
- Hyvä-native: a Hyvä companion module renders My Coupons with CSP-safe Alpine.js.
- API-first: every admin task has a REST endpoint, and the customer's coupon list is in GraphQL.
- No SaaS: everything runs inside your store; no code, address or order leaves it.
Good to know
- Personal coupons can't be used when shipping to multiple addresses; the shopper is asked to check out to one address.
- A coupon belongs to an email address, not to a customer account: changing a customer's email does not move their coupons.
- With guest redemption on, a matching checkout email doesn't prove the guest owns that mailbox. Set it to No for a website to require a signed-in account.
- On Magento 2.4.7, Magento counts coupon usage after the order, in its
sales.rule.update.coupon.usagequeue consumer; keep the consumers running so single-use codes are marked used. Magento 2.4.8 and later and Mage-OS count it when the order is placed.
Supports Magento Open Source and Mage-OS 2.4.7 and later (tested on Magento 2.4.7-p3 and Mage-OS 3.5), PHP 8.1 to 8.5, Luma and Hyvä 1.3 to 1.5.
Install Customer Coupons · Configure it · Partner with qoliber