A return shipping label is mechanically just a normal label with the addresses swapped: the customer's address becomes the sender, your address becomes the destination. You buy it the same way you buy an outbound label — enter both addresses, set the package weight, compare rates, purchase — then email the file to your customer to print and tape on the box. If they never use it, an unused label can typically be voided for credit, so sending one costs you nothing until it actually moves.

What is a return label, mechanically?

There is no special "return product" you need to unlock. When you generate a return label you are creating an ordinary shipment where:

The from-address is your customer's address — exactly as it appeared on the outbound order.
The to-address is your return address — your home, studio, or wherever returns should land.
The weight and dimensions are the original parcel's, assuming the customer reuses the packaging, which most do.

Once purchased, you get the same artifacts as any label: a printable file and a tracking number. Email the label to the customer (a PDF attachment works fine), and the tracking number is yours to watch — you will know the moment the return is scanned into the carrier network, and roughly when to expect it back.

Two practical touches that prevent most return headaches:

Tell the customer to cover or remove the old label. A box with two live barcodes goes wherever the first scan says, which is sometimes back to them.
Ask them to drop it off rather than leave it out. A return that gets an acceptance scan at a counter has a clean paper trail from minute one.

How do you buy a label from the customer's address back to yours?

On GoatLabels the flow takes about a minute:

Start a new shipment and enter the customer's address in the sender field and yours as the recipient. Address validation runs at quote time, so a typo in either address surfaces before money moves — the same residential/commercial badge you see on outbound labels applies here too.
Set the parcel details from the original order. If you shipped it, you already know the weight; reuse it.
Compare rates across USPS, UPS, FedEx, and DHL and pick the service. Returns are rarely urgent, so the cheapest ground option usually wins — the same logic covered in cheap shipping labels. Each quote is one all-in price, so what you see is what your wallet is debited.
Buy, then send the file to the customer with one line of instructions: print, tape over the old label, drop off at the carrier.

If the original order came through a DM or a marketplace message rather than a store, Billy can draft the return the same way it drafts outbound labels — paste the thread or screenshot the original order, tell it you need the addresses reversed, and review the draft before you buy. Nothing is purchased until you confirm.

The one field worth double-checking on every return: the from address. If the customer has moved, or the outbound order went to a gift recipient, the return needs to start where the package actually is now — ask before you buy.

Should you send the label upfront or only on request?

Both are legitimate; they optimize for different things.

Upfront (label included or sent immediately on approval) minimizes friction. The customer never waits, never negotiates, and never has to figure out shipping themselves. Retailers use it because a smooth return keeps the customer. The cost exposure is real but smaller than it looks: an emailed label that never gets used can be voided, and on GoatLabels a voided label returns to your wallet as instantly spendable credit rather than a card refund crawling back through a processor.

On request (customer contacts you, you approve, then send) adds one conversation but gives you a checkpoint: you confirm the item qualifies, catch the "actually, can I exchange instead?" cases, and skip buying labels for returns that dissolve on their own once the customer re-reads the size chart.

A sensible default for a small shop: approve first, then send the label immediately after approving. You keep the checkpoint without making the customer feel processed.

Who pays for return shipping — and what do small stores usually do?

There are three honest models, and each fits a different shop:

Approach	Your cost exposure	Buyer experience	Best for
Prepaid label, seller pays	Full return postage on every approved return	Smoothest — parity with big-retail expectations	Higher-margin goods, fit-dependent items like apparel, shops competing on service
Prepaid label, cost deducted from refund	Near zero — postage comes out of the refund	Convenient but the smaller refund needs clear disclosure upfront	Low-margin shops that still want an easy, trackable flow
Buyer arranges their own return shipping	Zero	Most friction; you also lose visibility until a tracking number appears	Rare-return categories, very small operations, buyer's-remorse-heavy niches

The middle row is the quiet workhorse for small sellers: you keep control of the label (so tracking exists and the package actually comes to the right address) while the economics stay survivable. Whatever you choose, write it into your store policy before the first return asks — a policy invented mid-dispute reads as improvisation because it is.

One caution on the third model: a buyer left to arrange shipping may under-declare weight or skip tracking entirely, and a return with no scan history is unresolvable when it goes missing. If the item matters, sending your own label is cheap insurance on the evidence trail alone.

What happens if the customer never ships it?

This is the pleasant surprise of the prepaid model: mostly, nothing. A purchased label that never receives a scan is an unused label, and unused labels can be voided — the mechanics are covered in void a shipping label. Carriers set an outside window for unused-label refunds, so build a habit around it: if a return label has shown no movement after a couple of weeks, close the return in your records and void the label rather than letting it age past the window. On GoatLabels the void lands back in your wallet as spendable credit, ready for the next outbound order.

Set the expectation on the customer side too. A line like "this return label is valid for 14 days" in your return email gives the return a natural deadline — that number is your policy choice, just set it comfortably inside the carrier's void window rather than at its edge.

The inverse failure also happens: the customer ships it, but it comes back to them or stalls. Because you bought the label, you hold the tracking number — watch it, and if the parcel misroutes, you have the same tools as any shipment, including the playbook in package returned to sender.

FAQ

Do I need a special account feature to create return labels? No. A return label is a standard label with the addresses reversed; any GoatLabels plan can buy one, rate-shopped across USPS, UPS, FedEx, and DHL like any other shipment.

How do I get the label to the customer? Email the label file as an attachment with one-line instructions: print it, tape it over the old label, drop the box at the carrier. If they cannot print, they can take the PDF to a print counter — or you can mail them a printed copy for high-value returns.

What if the customer never uses the label? Void it for wallet credit once you have closed the return. Carriers set an outside window for voiding unused labels, so do not let dormant return labels age indefinitely — sweep them on a schedule.

Should the return use the same carrier as the outbound shipment? Not necessarily. Rate-shop the return like any label; the cheapest ground service usually wins because returns are rarely time-sensitive. The only constraint is drop-off convenience for your customer.

Who pays for the return label? Your policy decides: you absorb it, you deduct it from the refund, or the buyer ships on their own. Deducting the label cost from the refund — clearly disclosed — is the most common small-shop compromise between service and margin.