orders-returns-and-warranty

$npx mdskill add Significant-Gravitas/skills-catalog/orders-returns-and-warranty

Use this when a customer asks where their stuff is or wants it back. Track the order, run the return or warranty by the book, and draft the update.

SKILL.md

.github/skills/orders-returns-and-warrantyView on GitHub ↗
---
name: "orders-returns-and-warranty"
description: "Use when a customer asks where their stuff is or wants it back: track the order, run the return or warranty by the book, and draft the update."
triggers: ["where is my order", "track this order", "start a return", "warranty claim", "send a replacement", "issue a return label", "order status for a customer"]
version: "1"
---

# Orders, returns and warranty

Use this when a customer asks where their stuff is or wants it back. Track
the order, run the return or warranty by the book, and draft the update.

## What you need first

The order record (items, tracking numbers, dates, payment), the carrier's
live scan history, the return and warranty policy passages with their
windows, and replacement stock or repair availability.

## Track against the carrier, not the promise

Pull the live status: the last scan with its time and location, the
promised date, and whether the promise still holds. Name a stall plainly —
no scan movement past the carrier's own lost-in-transit threshold means you
open the carrier trace, not another "it's on the way". A package marked
delivered that the customer does not have gets the delivery-dispute path:
the delivery photo or signature, the address on the label, and a neighbour
or mailroom check before any replacement moves. Never invent a scan event
or a date the carrier has not given.

## Qualify the ask against the passage

Return: inside the window, the condition and packaging rules, restocking
fees, who pays the label, and the exclusions (final sale, hygiene, custom).
Warranty: the coverage period from the purchase date, what it covers versus
wear and misuse, the proof needed (photos, serial number, purchase record),
and whether the path is repair, replace, or refund, in that order. Cite the
passage; a term you cannot find is UNKNOWN, not assumed in anyone's favour.

## Resolve by the book

Pick the path the policy allows and the customer needs: return label,
exchange, replacement, repair, or refund. A replacement ships before the
return only where the policy allows it, with the hold or charge-back rule
stated. Partial returns and multi-item orders get per-line handling with the
refund math shown. Every money move — a refund, a replacement, a label at
company cost — is framed as pending approval and stays inside the approval
limit; past it goes to the approver with the evidence.

## Draft the update

Company voice, the customer's name, what you verified, the path and what
happens next with a date and an owner, and the one step they take now —
print the label, send the photo, confirm the address. Stage it against the
order for the owner's yes.

## Output

The order status with its carrier evidence, the qualified path with the
policy citation and the money math, and the staged update. No refunds,
replacements, or labels without the owner's yes.

## When the records are thin

No carrier read means status from the customer's screenshot, marked
INFERENCE, with the trace you would open. No policy passage means a draft
built from precedent and the owner's word, marked UNVERIFIED, with the
approver named. Never guess a ship date or a coverage term.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.