Coupon Rules: First Order, Scope, and Who Funds the Discount
Besides type, value, and usage limits (see Coupons), coupons now have four extra rules:
- First order only: a coupon for new customers, in your shop or with one seller
- Seller: the discount only applies to one seller's products (multivendor shops)
- Category: the discount only applies to products in one category
- Discount paid by: who pays for the discount on seller products (multivendor shops)
Every rule is empty by default. A coupon that uses none of them works exactly as before: same discount, same order totals, same seller earnings.
Fields in the coupon form
| Field | Choices | Shown |
|---|---|---|
| First order only | No · First order in the shop · First order from the seller (needs a seller to be picked) | always |
| Seller | one of your sellers, can be cleared | multivendor shops |
| Category | one of your product categories, can be cleared | always |
| Discount paid by | Not set (shop pays, as today) · Shop / marketplace pays · Seller pays | multivendor shops |
The coupon list has a Scope column (the seller or category name, or All items). In the Dashboard app the fields read First order only, Only for seller, Only for category, and Discount paid by.
Coupons in this form are created by you and the staff allowed to. If you turn on seller vouchers, sellers can also create their own vouchers: always for their own products only, and always paid by the seller.
First order only
| Choice | The coupon is refused when |
|---|---|
| First order in the shop | the customer already has any order in your shop |
| First order from the seller | the customer already has an order containing a product of the coupon's seller |
Only Paid, On delivery, and Delivered orders count. Orders waiting for payment, canceled, or expired never count, so an order canceled after payment also stops counting.
An order whose session was canceled by the provider or the provider did not attend does not count either, even though the order stays Paid. It still counts when it holds another line that went ahead, such as goods, a completed session, or a session the customer did not come to.
This rule needs a known customer, like every coupon: an order without a customer cannot use any coupon.
- guests on the storefront are asked to log in first: "Log in to use this coupon."
- at the till and in the Dashboard, pick the customer first. The Dashboard shows "This coupon needs a customer: pick one first."
Unpaid orders do not count, so two orders both waiting for payment can each carry a first-order coupon. For a trial coupon that is really once per person, also set Max Uses per Customer to 1.
Seller and category scope
A coupon without a scope takes its discount from the whole order subtotal, as before. A coupon with a Seller or Category takes its discount only from the matching products:
- Seller: products of that seller
- Category: products in that category
- both set: a product must match both
Minimum Transaction, the percentage, and Max Amount are worked out on the total of the matching products, so the discount can never exceed what the matching products are worth. Tax and service charge are still computed on the subtotal minus the discount, as before.
Example: an order holds a session from Seller A for Rp 300.000 and a product from Seller B for Rp 200.000. A 20% coupon for Seller A gives a discount of Rp 60.000 (20% of Rp 300.000), not Rp 100.000.
If the order holds no matching product, the coupon is refused: "This coupon doesn't apply to the items in this order". Product type coupons give no order discount, so the scope rules do not change them.
Customers see the scope on coupon cards and on the checkout voucher: Only for the seller's or category's name (for example "Only for Studio Sekar"), and First order only or First order from this seller only.
A seller coupon in a shop that later turns multivendor off matches no product, so it cannot be used.
Who pays for the discount
This choice only changes money on products that belong to a seller. Your own shop's products are not affected.
| Discount paid by | Seller commission is computed on | Who pays for the discount |
|---|---|---|
| Not set (every existing coupon) | the price before the discount, as before | the shop |
| Shop / marketplace pays | the price before the discount ("Sellers are paid on the full price."). Same numbers as Not set, but each line's share of the discount is also recorded | the shop |
| Seller pays | the price after that line's share of the discount ("The seller’s earnings are computed on the discounted price.") | the seller |
Example: a Seller A session of Rp 300.000, 10% commission, with a Rp 60.000 discount.
| Discount paid by | Commission base | Shop commission | Seller earnings |
|---|---|---|---|
| Not set or Shop / marketplace | Rp 300.000 | Rp 30.000 | Rp 270.000 |
| Seller | Rp 240.000 | Rp 24.000 | Rp 216.000 |
When the discount is split over several lines, each matching line gets a share in proportion to its value. For rentals the deposit is left out of this split, and seller earnings never go below zero. Each line's share of the discount can show in the order detail, and the Sellers report (see Sellers) uses the same numbers.
Update the app
Coupons with a Seller or Category need the latest app version, because older versions compute the discount on the whole subtotal. Etalasse refuses such orders with "Update the app to use this coupon.", so no order is recorded and the till never collects the wrong amount. The coupon form reminds you: "Customers and cashiers need the latest storefront and POS app to use a coupon limited to a seller or category. Older apps ask them to update."
Before you use scoped coupons:
- update the POS app on every till device, including Cashier in the Dashboard app
- remind customers who use your shop's app on their phone to update it
Coupons without a scope, including first-order coupons without a seller or category, keep working on every app version. In the Dashboard a total that does not match shows "The total for this coupon did not match. Reload the page and try again."
Messages customers may see
| Storefront message | Cause |
|---|---|
| "Log in to use this coupon." | a coupon used without a customer (guest) |
| "This coupon is only for your first order in this shop." | the customer has ordered in your shop before |
| "This coupon is only for your first order from this seller." | the customer has ordered from that seller before |
| "This coupon doesn't apply to the items in this order." | no product matches the scope |
| "Update the app to use this coupon." | a scoped coupon used from an older app version |
In the Dashboard, both first-order cases read "This coupon is only for a first order, and this customer already ordered."
Limits
- refunds on the Refunds screen keep the existing method: the coupon discount is spread over every refunded item, not only the matching ones. The total refunded never exceeds what was paid, and seller earnings still follow the order line's record. A one-session refund recorded automatically on a provider cancel uses that line's own share of the discount
- a deleted seller or category shows the scope as empty, but the coupon keeps its choice