download dots

↩️ Handle Returns and Exchanges Cleanly

Run the shop from one place, including the second and third one. These prompts build the working parts of a retail business: stock that is right across every location, purchase orders that arrive before you run out, gift cards and loyalty, staff rotas, and the numbers you should see every morning.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Handle Returns and Exchanges Cleanly

Copy

Returns are handled on a notepad and I have no idea which products cause them. Build me a returns app. Record each return with the product, quantity, the original sale if known, the date, the reason from a short list such as faulty, wrong size, changed mind or damaged in transit, and a free note. Set the outcome as refund, exchange or credit. If the item is sellable it goes back into stock at its location automatically. If it is faulty it moves to a separate quarantine location and never counts as available. Show return rate by product, by supplier and by reason, as a percentage of units sold rather than as a raw count. Add an AI agent that reviews returns and tells me which products are returning well above normal for their category and whether the reason suggests a supplier problem, a sizing problem or a description problem. Automate a scheduled monthly returns report and an alert when a product crosses a return rate threshold I set. Two logins: staff who process returns, and an owner who sees the analysis.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Handle Returns and Exchanges Cleanly

Record returns with reasons, restock sellable items, isolate faulty stock, and surface products returning above normal.

// the spark catches · intelligence awakens · the answer unfolds

Returns handled on a notepad lose stock and hide a product problem. This records the reason, restocks what is sellable, and shows the pattern.

What's Included

  • A reason on every return which is the data worth having.
  • Sellable stock returned to shelf and faulty stock kept separate.
  • Return rate by product and supplier so the cause becomes clear.
  • An assistant that flags a product returning far above normal.

How To Use

  1. Always capture the reason. It is the only useful part of a return.
  2. Separate sellable from faulty immediately or the count will be wrong.
  3. Track return rate by supplier as well as by product.
  4. Raise a supplier claim on faulty stock rather than absorbing it.

Adjust stock through multi-store inventory, and raise the claim with supplier prompts.