Next step · What to do next

Add discount codes safely

What you may see

I want to offer a discount code to customers

Why this step

A discount code is money; it must be limited, checked on the server and recorded so it cannot be abused or stacked by mistake.

Before you start

What kind of discount (percent or fixed), for whom, until when, how many times?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Add discount codes safely

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
A discount code is money; it must be limited, checked on the server and recorded so it cannot be abused or stacked by mistake.

DO THESE STEPS, IN THIS ORDER
1. Model codes with type, value, start and end (Kuwait time), minimum order, total uses, uses per customer, and active flag.
2. Validate and apply the code on the server only, with clear messages (expired, used, minimum not met), rounding fixed to the fils, and never below zero.
3. Record each use against the order; limit attempts per address to stop guessing; show a simple report.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Valid, expired, used-up and below-minimum codes each behave correctly in tests, and the order total matches.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not apply discounts in the browser.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Model codes with type, value, start and end (Kuwait time), minimum order, total uses, uses per customer, and active flag.
Validate and apply the code on the server only, with clear messages (expired, used, minimum not met), rounding fixed to the fils, and never below zero.
Record each use against the order; limit attempts per address to stop guessing; show a simple report.

Do not do this

Do not allow unlimited stacking of codes.
Do not apply discounts in the browser.

Fix it Customers could change the price in the browser before paying

Try another entry