To make a product return request form in Notion, create a Returns database with properties for the customer’s email, order number, delivery date, item, reason, photos and preferred resolution, then add a Form view and share it on the web. Add an ID property as the return number, a formula that checks whether the request is inside your return window, and a button that approves it.
That gives a small shop a working returns desk in about an hour. The parts most templates leave out are the eligibility check and the legal floor your policy can’t go below.
What a Notion product return request form should ask
A Notion product return request form should collect everything you need to approve or decline without emailing the customer back: who they are, which order, which item, why, and what they want. Every follow-up email adds a day to the return.
Notion’s forms help page says a question’s type is the equivalent of a property type, so plan the database first:
| Form question | Question type | Property in the database |
|---|---|---|
| Your email | ||
| Order number | Short text | Title |
| Delivery date | Date | Date |
| Which item? | Short text | Text |
| Reason | Multiple choice | Select (Faulty, Damaged in transit, Wrong item, Not as described, Changed my mind) |
| Photos | Files & media | File |
| What would you like? | Multiple choice | Select (Refund, Replacement, Store credit) |
| Anything else? | Long text | Text |
One request per item is easier to handle than one per order. Two items from the same order can have different reasons and different outcomes.
Step 1: build the Returns database
The Returns database holds one page per return request. Create a full-page database called “Returns” with the properties from the table, then add the ones only your team uses.
- Return no., an ID property. Notion’s database properties page says it creates a numerical ID for each item that is unique and can’t be changed by hand. That’s your RMA number.
- Requested on, a Created time property, which records when the request came in and can’t be edited.
- Status, with
Requested,Approved,Item received,RefundedandDeclined. - Within window, a formula, covered in step 3.
Keep all four off the form. Customers shouldn’t see or set them.
Step 2: add the form view and share it publicly
The form view is the page your customers fill in. In the Returns database, select + next to your views, choose Form, and add a question for each row of the table.
Notion’s forms guide lists files & media among the question types, so customers can attach photos. Each file follows your workspace plan, and the pricing page lists up to 5 MB per file on Free and up to 5 GB on paid plans. A phone photo can pass 5 MB, so on Free ask for a screenshot or a smaller image in the question description.
Under Who can fill out, choose Anyone on the web with link. Your customers don’t have Notion accounts. Web responses are automatically anonymous, so make email and order number Required. Notion says respondents then have to answer them before they can submit.
On the submit screen, write a confirmation that tells people what happens next, like “We reply within two working days. Don’t send the item back until you get a return number.” Turn on the email copy so each request reaches your inbox.
Step 3: check the return window with a formula
An eligibility formula tells you at a glance whether a request falls inside your return window. Notion’s formula reference says dateBetween returns the difference between two dates in a unit such as days, and if returns one value when a condition is true and another when it isn’t.
Add a formula property called Within window:
if(dateBetween(prop("Requested on"), prop("Delivery date"), "days") <= 14, "Yes", "Check")
Change 14 to your own policy. A request made a week after delivery shows Yes. One made a month later shows Check, which doesn’t mean decline. A faulty item can still be owed a remedy after your change-of-mind window closes.
The formula trusts the delivery date the customer typed. Check it against your shipping records before refunding.
The legal minimum your return policy has to meet
Your return policy sets the window in the formula, but in some markets the law sets a floor under it. If you sell to the EU or the UK, build the form around those rules first. This is a summary of official guidance, not legal advice.
| Rule | EU | UK |
|---|---|---|
| Change of mind, online orders | Cancel within 14 days of delivery, no reason needed | Refund if told within 14 days of receiving the item |
| Faulty items | Trader pays the cost of returning a defective product | Full refund if faulty, not as described or doesn’t work; repair or replace within 6 months |
| Common exceptions | Made-to-order or personalised goods, perishables | Personalised, perishable and sealed hygiene items, unless faulty |
The EU rules come from the Your Europe returns page, which also says the buyer usually pays return postage after a change-of-mind cancellation unless the seller agreed to cover it. The UK rules come from GOV.UK, which says you must refund within 14 days of getting the item back and that misleading customers about their rights is illegal.
A “Faulty” request outside 14 days still needs a look. “Changed my mind” on day 20 usually doesn’t.
Step 4: approve returns with a button
An approve button moves a request forward in one click. Notion’s buttons page says the Edit pages in action edits pages and properties in a database you choose.
- Add a Button property called
Approvewith the action Edit pages in, set to this page, StatusApproved. - Make a
Declinedbutton the same way. - Add a view called To review, filtered to Status is
Requestedand grouped by Within window.
To email the customer from the button, add Send mail to pointing at the email property, with the return number and where to send the item. That action needs a paid plan. On Free, copy the email address and reply from your inbox.
Anyone with Full access or Can edit permission can click buttons, so keep edit access to the people who make refund calls.
Where a native Notion returns form falls short
The native form handles a low-volume shop well. It struggles in three places.
- Branching costs Business. Asking for photos only when the reason is Faulty or Damaged needs conditional logic, which Notion offers only on Business and Enterprise.
- The customer gets no receipt. The submit screen emails you, so customers keep no copy of what they sent.
- Order numbers go unchecked. Notion can’t match them against your store, so a typo slips through until you search for it.
My take: at a few returns a week, the native form plus the formula is enough. Skip the paid add-ons. Once returns hit the dozens, move to a helpdesk or your store’s own returns app.
If you need photos only for damage claims without moving to Business, nDBForms writes each response to your Notion database and has conditional logic on Pro. For related set-ups, see file uploads on Notion forms, the Notion order form, and confirmation emails for Notion forms.
FAQ
Can customers without a Notion account fill out a return form?
Yes. Share the form with Anyone on the web with link. Those responses are anonymous, so make name, email and order number required questions.
Can customers upload photos of a damaged product?
Yes. Add a files & media question. Each file follows your workspace plan limit: up to 5 MB on Free and up to 5 GB on paid plans.
How do I give each return an RMA number?
Add an ID property to the returns database. Notion fills it in automatically for every new request, and nobody can change it by hand.
Does Notion email the customer when a return is approved?
Not from the form itself. The submit screen only emails you a copy. A button with the Send mail to action can email the customer, but that action needs a paid plan.