Returns that start as angry emails skip the order number. The form should require the order ID, a reason, and enough address context (ZIP or postcode) so warehouse can issue an RMA instead of playing detective.
Not the sales hunter’s phone.
Unblock only with a human override in email.
Footer, receipt, and packaging insert.
Then send the label from your usual tool.
A return request is the customer asking permission to send goods back. US retailers often issue an RMA and a label; UK distance-selling rules give consumers a cooling-off window that still needs a process. The form is the ticket: order number, what is wrong, and where the parcel currently sits.
This is not a prepaid-label printer. Loop Returns and similar products print labels. You can start here if volume is low and a human still decides whether the item is eligible.
No order number means no RMA. Make it required even if they complain.
Link your returns policy next to the button. The form does not replace the policy.
Chat is fast and leaves no SKU. A form is slower and complete.
The URL support already pastes. Now it captures structured data.
Worth it at Shopify scale. This form is for catalogs that are not there yet.
Threads get lost when the original mailer was a no-reply.
Retail still does this. Offer the web path for US and UK mail-order.
Static shops that invoice offline still owe customers a returns URL. Publish the form and send notifications to warehouse@.
Pickup ZIP versus postcode tells you which carrier account to use. Do not default everything to USPS when the parcel is in Manchester.
Not in this HTML. A person or a later automation decides.
Policy in copy. Collect acknowledgement with a checkbox you add after copy if legal wants it.
Ask for a link in details.
Say who pays duty. Silence here creates chargebacks.