Used Item Listing for Marketplaces

Write an honest secondhand listing that minimizes tire-kicker inquiries.

Prompt · 4 variables

I want to list my used {{target item}} on a local secondhand marketplace. The usage period is {{usage period}}, and my asking price is {{desired target price}}.

Please write a ready-to-post listing. Do not just list the pros—place all scratches, defects, and missing parts at the very beginning of the description.

Format: A single-line title (Item Name + Condition Summary), followed by three short body paragraphs in this order: ① Honest Condition Details, ② Usable Highlights / Why It's Still Good, ③ Transaction Terms. Keep the total length around 100 words.

Here is an example of the tone I want. Please match this style: Example Title: 2 Folding Camping Chairs / Chipped paint on legs Example Opening Line: Used for 3 years; paint is chipped near the bottom of the legs. Still structurally solid with no issues for sitting.

Do not invent unstated details like original retail price, warranty period, or original packaging—omit them entirely if not provided. Avoid exaggerations like "Mint condition" or "Must-sell urgent deal." Fix the last line to: "[Preferred Pickup Location] / [Shipping Available: Y/N] / [Price Firm or OBO]".

Item condition details: """ {{current status}} """

Copy, then paste here · ChatGPT and Claude open with the prompt filled in Open in ChatGPT ↗Open in Claude ↗Open in Gemini ↗ Edit in builder Download classroom card

Why it is written this way

Context
I want to list my used {{target item}} on a local secondhand marketplace. The usage period is {{usage period}}, and my asking price is {{desired target price}}.
Task
Please write a ready-to-post listing. Do not just list the pros—place all scratches, defects, and missing parts at the very beginning of the description.
Format
Format: A single-line title (Item Name + Condition Summary), followed by three short body paragraphs in this order: ① Honest Condition Details, ② Usable Highlights / Why It's Still Good, ③ Transaction Terms. Keep the total length around 100 words.
Example
Here is an example of the tone I want. Please match this style: Example Title: 2 Folding Camping Chairs / Chipped paint on legs Example Opening Line: Used for 3 years; paint is chipped near the bottom of the legs. Still structurally solid with no issues for sitting.
Constraints
Do not invent unstated details like original retail price, warranty period, or original packaging—omit them entirely if not provided. Avoid exaggerations like "Mint condition" or "Must-sell urgent deal." Fix the last line to: "[Preferred Pickup Location] / [Shipping Available: Y/N] / [Price Firm or OBO]".
Input
Item condition details: """ {{current status}} """

When you ask AI to write a secondhand listing, it usually outputs generic sales hype. Fluff like "gently used" or "pristine condition" might attract initial messages, but buyers will likely back out on the spot when they see the item in person or demand a refund later. This prompt is designed to bring flaws front and center to eliminate wasted trips.

Specifying "scratches, defects, and missing parts at the very beginning" in the Task instruction is key. If you simply ask for an "honest description," the AI will tuck the flaws away at the very end. Setting the sequence ensures buyers see the flaws without scrolling; anyone who still messages you is already accepting of the condition.

Providing an Example locks in the desired tone. Listings packed with hype read very differently from factual, straightforward writeups. Showing just a sample title and opening line is enough for the AI to emulate the exact sentence length and candid tone.

Setting Constraints prevents two common issues: hallucinated details (like inventing an original purchase price or warranty status, which causes disputes) and omitted deal terms. Standardizing the last line to cover location, shipping, and negotiation policy significantly cuts down on repetitive messages asking "Will you ship?".

Wrapping the item condition inside """ delimiters is intentional. If terms like "priced to sell" or "no lowballs" are mixed into the condition notes, the AI might misinterpret them as formatting instructions and alter the entire prompt's tone. Separating data from instructions keeps your input treated purely as factual reference.

Unfamiliar terms? See Aha AI: few-shot, output-format

Compared with a bad example

Common bad example

Write a listing to sell my camping chairs secondhand. Used for 3 years, selling for $30.

Without condition details provided, the AI fills in the blanks with generic praise like "Excellent condition with barely any wear." Posting that will lead to arguments on the spot when the buyer notices chipped paint. The lack of deal terms also invites repetitive inquiries.

Variations

When precise sizing matters (clothing, shoes)

When precise sizing matters (clothing, shoes)

I want to sell my used {{target item}}. Usage period: {{usage period}}, desired price: {{desired target price}}.

Since fit is crucial for this item, buyers often ask about measurements. Please place blank measurement placeholders at the very top of the listing for me to fill in (e.g., [Shoulder Width], [Total Length]). Then follow with Condition → Highlights → Transaction Terms, keeping the entire text around 100 words.

Item condition details: """ {{current status}} """

AI cannot guess exact garment dimensions, so leaving structured brackets prevents hallucinations. Listing measurements upfront drastically reduces sizing inquiries.

Responding to lowball offers

Responding to lowball offers

I listed {{target item}} for {{desired target price}}, and a buyer sent an offer asking for a discount.

Please write two short, 2-line response templates: one politely declining, and one stating the lowest price I am willing to accept. Keep the tone courteous yet firm so it does not invite endless back-and-forth haggling.

Vague negotiation replies drag out conversations. Having both decline and counter-offer templates ready lets you quickly copy and paste the right response.

Related prompts

Last updated 2026-09-02 · Found a mistake? Let us know