Commerce domain knowledge for autonomous selling agents. Pricing, copywriting, fulfillment strategy, conversion tactics, post-sale handling. Use when deciding what to sell, how to price it, or how to optimize a product page.
Use when an autonomous agent is making commerce decisions: what to sell, how to price it, what to write on the product page, how to optimize for conversion, or how to handle post-sale.
This skill owns the WHAT and WHY. The listbee skill owns the HOW (API calls).
Work through these six decisions in sequence when setting up or updating a product. Each decision has a dedicated reference with decision trees, defaults, and examples.
1. Offer Design → references/offer-design.md
Decide what you are selling before you price it. Is this a single item or a bundle? Managed delivery or agent-fulfilled? Fixed content or personalized per buyer? These answers determine your fulfillment mode, which locks in constraints for every decision that follows.
2. Pricing → references/pricing.md
Set a price only after the offer shape is clear. Use the per-category defaults table as your starting point. Apply the $X9 rule. Consider anchoring if you have multiple tiers.
3. Product Page Copy → references/product-page-copy.md
Write the name and description once pricing is set — price awareness sharpens copy. Use the title formula and description structure. Stay within character targets.
4. Conversion Tactics → references/conversion.md
After copy is written, decide whether any conversion levers apply: stock limits, edition numbering, checkout field reduction. Apply only what is honest and necessary.
5. Fulfillment Strategy → references/offer-design.md (fulfillment section)
Revisit fulfillment mode with the final offer shape in hand. If agent-fulfilled, plan your
webhook handler and any fulfill() callback logic. Cross-reference: for fulfillment field
names and API mechanics, see listbee skill → references/fulfillment.md.
6. Post-Sale Handling → references/post-sale.md
Decide your refund window, redelivery stance, and upsell approach before the listing goes live. Changing these after orders arrive is operationally painful.
When no other signal overrides, use these defaults. They are tested baselines — deviate only with a specific reason.
| Decision | Default |
|---|---|
| Price ending | $X9 (e.g. $29, $49, $99) — never round numbers |
| Title structure | [Adjective] + [Thing] + [For Whom / Benefit] |
| Description structure | Hook sentence → bullet list of inclusions → who it's for |
| Stock | null (unlimited) unless scarcity is real and verifiable |
| Checkout fields | Zero — only add fields required for fulfillment |
| Fulfillment mode | Managed if content is static; agent-fulfilled if content is generated per buyer |
| Refund window | 48 hours for digital products |
| Currency | USD, always in cents (1900 = $19.00) |
These defaults optimize for conversion, trust, and operational simplicity. They are not opinionated about your business model — they are the lowest-friction baseline.
This table defines exactly what each skill decides. Do not blur the line.
| Decision | This skill (commerce-best-practices) | listbee skill |
|---|---|---|
| What to sell | Yes — offer shape, category, fulfillment mode | No |
| Price amount | Yes — range, psychology, anchoring | No |
| Price field value | No | Yes — price field in cents |
| Title and description text | Yes — formulas, examples, length targets | No |
| Whether to use stock limits | Yes — scarcity judgment | No |
| Stock field value | No | Yes — stock field (int or null) |
| Which checkout fields to add | Yes — minimize, justify each one | No |
| Checkout field definitions | No | Yes — checkout_schema field |
| Fulfillment mode selection | Yes — managed vs agent-fulfilled | No |
| Fulfillment API mechanics | No | Yes — deliverable, fulfill() callback |
| Refund policy stance | Yes — defaults and trade-offs | No |
| Refund processing | No | Yes — order management API |
| Upsell strategy | Yes — when and how to link | No |
| Creating related listings | No | Yes — listings API |
Rule of thumb: if the decision involves an API field name, value, or call — it belongs in
the listbee skill. If it involves a trade-off, judgment, or strategy — it belongs here.
| Category | Price range | Fulfillment | Checkout fields |
|---|---|---|---|
| Digital download | $5–50 | Managed | 0 |
| Template / document | $10–30 | Managed | 0 |
| AI-generated content | $15–100 | Agent-fulfilled | 1 (the prompt / spec) |
| Physical goods | $15–200 | External (ship yourself) | 2–3 (address) |
| Service / consulting | $25–500 | Agent-fulfilled or external | 1–2 (brief / date) |
For full decision trees and examples, read the relevant reference file.