-
Notifications
You must be signed in to change notification settings - Fork 185
Add "No returns" as a suggestion for "Return policy" #47
Description
One of the observed trends from the Duo Search data is that free-text fields lead to "messy" situations, despite the bulk of the cases being "organised". Return policy is a good example, presented below.
I've collected all the different return policies that Duo Search has scraped since the beginning. It's available here for your perusal. There are 1813 distinct return policies, but when you look into them there are literally hundreds of duplicates for "No return" (small sample shown below):
"No Returns.",
"no refunds.",
"no returns.",
"All sales final.",
"No returns.",
"There is no way back!",
"There is no way back...!",
"No Returns on digital items.",
"Returns are a no-go.",
"No returns. No tradeback. Nothing.",
"no refunds, will resend once if not recieved",
"no returns, if u dont recieve will resend once",
"no returns, if you don't recieve will resend once.",
"no returns, if you don't recieve, will resend once.",
"No Returns",
"No returns",
"no refunds",
"No returms",
"No return",
"No refunds on digital items",
"No refund",
"No warranty and no returns.",
"No returns or refunds",
"Returns accpeted.",
"No returns on food items.",
"No return policy",
"No Refund",
"NA",
"N/A",
"Non Refundable",
"No Return",
In an effort to make free text fields more consistent across OpenBazaar stores (and more machine readable) having pre-set options for the return policy would help. My suggestion would be to a have few preset options, plus a "Custom" field for those that require free text. For example:
- "No returns"
- "Full refund available"
- "Full refund available, minus shipping costs"
- "Custom..."
This hybrid strategy could work for many fields, including condition, weight, refundPolicy and category.