Guide Listings and moderation
Classifieds listing moderation: policies, reason codes and review queues.
Classifieds moderation checks each listing against written policies before it appears in search. Good programs define rules per category, give every decision a reason code, queue uncertain cases for human review, test rules on reference examples before activation and track appeals and reversals. This Youzu guide shows how.
Published by Youzu · Editorial policy
- Published
- Reading time
- 9 min read
Key points
- Start from the written policy and turn each line into a rule a listing can be checked against.
- Keep a reason code on every decision that the seller, the reviewer and an appeal can read.
- Check a rule on reference listings before activating it, and see which listings it would flag.
- Review false positives as rule refinements, never as silent rule changes.
- Keep appeals and reversals per rule, so weak rules show up early.
In this guide
What moderation covers
Classifieds sites and marketplaces publish what sellers write and photograph. Listing moderation is how they keep listings that break their rules out of search, and how they explain each decision to the seller it affects. It covers prohibited and restricted items, images that do not show the product, misleading titles, contact details that move a sale off the platform and anything else the policy names.
Moderation is not a separate world from catalog quality. A watermark on a photo, a title that names a different product than the photo shows and a sofa listed under a catch-all category are all things a moderation rule can catch, and all things that make a listing harder to find. The difference is the consequence: a policy decision can hold or remove a listing, so it needs a reason and a way to appeal.
Large marketplaces publish their policies in a form sellers can read, organized by category and by type of problem.[1][2] Reading 2 or 3 of them side by side is a useful way to check that your own policy covers the obvious cases before you write rules.
From written policy to rules (CSV template)
A written policy line is meant for people. A rule is meant to be checked against a listing. Turning one into the other means deciding 5 things for every line:
- What it checks: the title, the description, the images or a combination.
- Where it looks: for images, the first image or all images; for text, the title or the title and description.
- Which categories it applies to: a rule for prohibited items may cover every category, a rule about measurements only furniture.
- What happens on a match: hold for review, reject with a reason, or approve with a note.
- Which reason code it records: the label the seller and the reviewer will see.
The template in the checklist section below has one row per rule with exactly these columns. Filling it in with your trust and safety team is the fastest way to find policy lines that cannot be checked as written and need rewording.
Reason codes
A reason code is a short, stable label for why a listing was approved, rejected or sent to review. It is the most useful thing a moderation program can add, because it turns a decision into something a seller can act on and a team can count.
| Reason code | Rule | What the seller is told |
|---|---|---|
| IMAGE_WATERMARK | Image must show the product itself; no watermarks | Replace the photo with one that has no watermark. |
| IMAGEPRODUCTNOT_SHOWN | Image must show the product itself; no watermarks | Add a photo that shows the item you are selling. |
| TEXTCONTACTDETAILS | No contact details in the title or description | Remove phone numbers, emails and requests to contact you elsewhere. |
Keep codes stable once sellers see them, write the seller message in plain words and never reuse a code for a different problem. A code that means 2 things cannot be counted.
Group codes into a short hierarchy: a family such as images or text, then the specific problem. Families let you report by type of problem; specific codes tell the seller exactly what to change.
Review queue anatomy
Listings a rule flags wait in a review queue. A queue item needs enough information for a reviewer to decide without opening 5 other tools: the listing, the rule that flagged it, the reason, the severity and the status. Sorting by status, then severity, then rule keeps the most important open items at the top.
Worked example
Review queue
| Listing | Finding | Severity | Rule | Status |
|---|---|---|---|---|
| 2. Linen sofa, 2000 mm | Image shows a watermark | Low | Image must show the product itself; no watermarks | Open |
| 3. Oak coffee table | Image does not show the product | Low | Image must show the product itself; no watermarks | Open |
| 5. Accent chair, plum | Image shows a watermark | Low | Image must show the product itself; no watermarks | Open |
| 4. Oak side table | Contact details in the description | Low | No contact details in the title or description | Open |
| 6. Velvet sofa, navy. Contact me directly | Contact details in the title | Low | No contact details in the title or description | Open |
Each decision has a consequence that the reviewer should see before deciding: approving a held listing publishes it, rejecting it keeps it unpublished with its reason code, and marking a finding as a false positive questions the rule rather than the listing.
Testing a rule before activation
A rule that has never been run is a guess about how many listings it will catch. Before activating a new rule or a new revision, run it against a reference set of listings and look at which ones it would flag. The reference set should include listings that must be flagged, listings that must not, and the borderline ones your reviewers argue about.
Scope changes the result more than wording does. In the example below, the same image rule flags none of 6 listings when it checks no images, 3 when it checks the first image and 5 when it checks all images. Choose the scope, then preview the effect.
Worked example
Test a rule before you activate it
Image scope
Rule impact preview
Rule 1: Image must show the product itself; no watermarks
Image 1
Image 2Listing 1Terracotta armchair, wooden legsNot flagged
Image 1
Image 2Listing 2Linen sofa, 2000 mmFlaggedSeverity LowImage shows a watermark · Rule 1
Image 1
Image 2Listing 3Oak coffee tableFlaggedSeverity LowImage does not show the product · Rule 1
Image 1
Image 2Listing 4Oak side tableNot flagged
Image 1
Image 2Listing 5Accent chair, plumFlaggedSeverity LowImage shows a watermark · Rule 1
Image 1
Image 2Listing 6Velvet sofa, navy. Contact me directlyNot flagged
This revision would flag 3 of 6 listings.
Preview only. Nothing has changed.
Worksheet
Sketch 3 rules for your own policy
Would flag 2 of 8 listings.
Would flag 2 of 8 listings.
Would flag 2 of 8 listings.
The 8 sample listings and the rules that would flag them Listing What a reviewer sees Flagged by 1. Oak dining table A table photographed in a living room. Not flagged 2. City bike, good condition The description asks buyers to phone the seller directly. Rule 1 3. Leather sofa A phone number is written on a card in the photo. Rule 1 4. Replica sword, decorative The title names a replica weapon, and the photo shows it. Rule 2 5. Camping set The photo shows a hunting knife beside the tent. Rule 2 6. Designer floor lamp The photo is copied from a shop's product page. Rule 3 7. Wool rug The photo carries another seller's watermark. Rule 3 8. Kids' bike, half price today The title carries a price offer. Not flagged
Read as text
Activate an exact revision, not 'the latest version', so a decision can always be traced to the rule text that produced it. Keep the reference set small enough that a reviewer can look at every listing it flags, and add to it whenever an appeal shows a case the rule handled badly.
False positives and refinements
Every rule flags some listings it should not. When a reviewer marks a finding as a false positive, the useful question is why: was the rule too broad, was the scope wrong, or was this a case the policy never considered? The answer becomes a proposed refinement of the rule.
Refinements should be drafts that a person reviews, tests on the reference set and activates as a new revision. A rule that changes itself after every reviewer click cannot be explained to a seller or audited by the policy owner.
Appeals and reversals
Sellers will disagree with decisions. An appeal route that quotes the reason code, lets the seller add context or a new photo and reaches a different reviewer is the fairest design and the cheapest to run. Major platforms describe how sellers can request a review of a rejected listing, which is a good benchmark for your own wording.[2]
- Show the reason code and the rule in the appeal form.
- Send appeals to a reviewer who did not make the first decision.
- Record the outcome as upheld or reversed, with the reason.
- Feed reversed decisions back into rule refinement, per rule.
What to track
Track these per rule and per category, set your own baselines and watch how each one moves after a rule change:
- Listings flagged, approved, rejected and still open.
- False positives marked by reviewers.
- Appeals received, upheld and reversed.
- Time from submission to decision, for held listings.
- Listings removed after publication that no rule flagged.
Youzu helps marketplaces, classifieds and retailers turn raw seller and supplier product data into structured, reviewable catalog records, and policy checks are part of that work. You define the rules; Youzu applies them and routes exceptions to your reviewers. No tool makes a marketplace compliant on its own, so keep legal review of the policy with your own counsel.
Boundaries
What Youzu does not do
- Youzu does not make a marketplace compliant. You define the rules; Youzu applies them and routes exceptions to your reviewers.
- Youzu rules do not change by themselves. False-positive feedback can produce a draft rule refinement that you review and activate.
- Youzu publishes no accuracy figures. Measure accuracy on your own sample against your own labels, with critical errors reported separately.
Checklist
Policy-to-rules template
One row per rule: the policy line it comes from, what it checks, where it looks, the categories it applies to, the action, the reason code and the severity. The first rows are the 2 rules from this guide's example.
A CSV file of 3 rows, named youzu-policy-to-rules-template.csv. No form to fill in first.
| Policy line | Rule | Checks | Scope | Categories | Action on match | Reason code | Severity | Owner |
|---|---|---|---|---|---|---|---|---|
| Photos must show the item for sale | Image must show the product itself; no watermarks | Images | First image | All | Hold for review | IMAGE_WATERMARK | Low | Trust and safety |
| Photos must show the item for sale | Image must show the product itself; no watermarks | Images | First image | All | Hold for review | IMAGE_PRODUCT_NOT_SHOWN | Low | Trust and safety |
| Sales stay on the platform | No contact details in the title or description | Text | Title and description | All | Reject with reason | TEXT_CONTACT_DETAILS | Medium | Trust and safety |
FAQ
Questions buyers ask
Short answers to the questions teams ask about this topic.
Both patterns work. Checking before publication stops clear violations before shoppers see them but delays listings; checking after publication keeps listings flowing and removes problems later. Many teams check high-risk categories before publication and the rest after, and record a reason code for every decision either way.
A reason code is a short, stable label for why a listing was approved, rejected or sent to review, such as a watermark on an image or contact details in the text. Codes let sellers fix the right thing, keep reviewers consistent and show which rules cause the most appeals and reversals.
Run every new rule or revision against a reference set before activating it, and look at which listings it would flag. Narrow the scope first, for example to the first image or to the title, before rewording the rule. After activation, review false positives per rule and turn them into tested refinements.
No tool does that on its own. Regulation sets obligations for your business, and your counsel decides how your policy meets them. A moderation system applies the rules you write, records the reasons and routes exceptions to your reviewers, which helps you show what you did and why.
You define moderation rules as versioned rulesets with severity levels, image scope and reference images, test them, preview which products an activation affects, then activate an exact revision. Marking a finding as a false positive can generate a draft rule refinement for you to review and activate; active rules never change automatically.
Last reviewed
Sources
Prohibited and restricted items, eBay Help. ebay.com/help/policies/prohibited-restricted-items/prohibited-restricted-items. Accessed . Back
Commerce Policies, Meta Transparency Center. facebook.com/policies_center/commerce. Accessed . Back
About this guide
Published by Youzu · Editorial policy
- Published
Every guide defines its terms, works through one example and cites the public sources it relies on, with the date each source was checked.
Guides explain methods. They do not rank Youzu above other approaches, and an example is never presented as a customer result.
More in all guides and the catalog glossary.
Related
Keep reading
Product
Listing moderation for marketplaces and classifieds
Define moderation rules with severity, image scope and reference images, test them, preview their impact and review flagged products in a queue.
Product
Listing quality, checked before search
Check listings before search: unsupported attributes stay empty, title and image mismatches raise a warning and your rules flag what is out of policy.
Industry
Listing quality for classifieds
Classifieds listing moderation with your own rules applied to listing text and images, a reason behind each flag and uncertain cases sent to review.