Set discount eligibility, dates and usage limits
Open the discount’s **Offer Details**. Before editing, decide which products, categories, clients or client groups should qualify and whether the offer will be public at checkout. Publicly displayed checkout discounts currently have different supported limits.
Configure eligibility
Use **Client eligibility** to choose the all-client, specific-group or specific-client scope. Select the intended product/category scope for product offers. Review **Gateway eligibility** when the offer should depend on a payment method.
Purchase and usage rules
Under **Minimum purchase**, choose no minimum, a minimum quantity or the displayed minimum purchase amount. Under **Usage limits**, optionally use **Limit total uses** or **Limit to one use per client** where supported. These limits are distinct from how a discount is applied within one qualifying order.
Dates and stored behavior
Under **Active dates**, set **Start date and time**. Enable **Set end date** when an expiry is intended and set **End date and time**. Review the form’s displayed timezone context, save and reopen. Existing stored offer behavior should not be assumed to stack with every other promotion; the current native form does not expose a combinations editor.
**If a customer cannot use the offer:** check the current date, customer/group, cart product/category, minimum amount/quantity, gateway and recorded usage. An offer name or visible code does not prove that cart qualifies.
For **Show this discount at checkout**, total and per-customer usage limits are not supported in the reviewed implementation; saving a public checkout offer with those limits is rejected. Keep a restricted private code private rather than removing its limits accidentally.
**Expected result:** the intended customer/cart qualifies during the saved active period, while unrelated customers and purchases do not.