Seat Promo Hub

Editorial Policy

How we verify codes, who writes our reviews, how ratings stay independent of commissions, where fee figures come from, and how to report errors.

Last updated: October 29, 2026

This page explains how Seat Promo Hub verifies codes and writes reviews. It is the standard we hold ourselves to and the one you can hold us to.

1. How we verify codes

Every code marked "Verified" on the Site was tested by a member of our team on the date shown next to it. The test is the same every time:

  1. Open the platform's site or app in a clean browser session with no stored cookies, from a US location.
  2. Pick a real event with tickets on sale and add tickets to the cart.
  3. Enter the code at checkout and record whether the platform accepted it, the discount it applied, and the fee line items before and after.
  4. Save a screenshot of the checkout screen with the order number and personal details cropped out.
  5. Record the platform, event type, date, time, tester initials and result in our verification log.

We stop before paying unless the code requires a completed order to confirm, in which case we buy the cheapest qualifying ticket and keep the receipt.

A code that fails this test is not published. A code that works is published with its verification date, its known conditions (first order only, minimum spend, app only, excluded events) and the discount we actually saw.

2. Re-testing and removal

Codes on pages that receive paid traffic are re-tested at least every seven days. All other codes are re-tested at least every 30 days and whenever a reader reports a failure. When a re-test fails, we remove the code from the active list within one business day. If a platform tells us a code has ended, we remove it the same day.

Removed codes are not deleted silently. For 30 days they appear in an "Expired" section at the bottom of the page with the last date they worked, so a reader who saw the code elsewhere knows it is gone. After that they move to the log only.

Codes submitted by readers go through the same test before publication. Reader reports that a code failed are checked within one business day; if we can reproduce the failure, the code comes down.

3. Who writes and tests

Our writers and testers are employees and contractors of Sellencer GmbH who buy tickets themselves and have done so on every platform we cover. Each review names its author. We do not accept content written by ticket platforms, their agencies or public relations firms, and we do not publish paid articles presented as editorial. We use software to help draft and check text, but a named person tests every code, decides every rating, and is responsible for every page.

4. Independence from commissions

We earn a commission if you buy through our links. It does not change your price, and it does not change our ratings. The specific rules:

  • Testers and writers do not see commission rates for the platforms they review.
  • Ratings, fee figures and the "best for" verdicts in comparisons are decided before anyone looks at what a platform pays.
  • Commission can affect the order of comparable verified offers, as the Affiliate Disclosure explains. It cannot affect whether an offer is listed, whether it is marked verified, or its rating.
  • No platform reviews, approves or previews our content. When a platform disputes a fact, we re-check it against their published terms and correct it if we were wrong; we do not change opinions on request.
  • Sponsored placements, if we run any, are labeled under the Advertising Policy and are never counted in ratings.

5. How ratings are formed

Each platform rating is built from five parts, weighted as shown:

  • Total price after fees (35%): what the same seats cost at checkout across platforms for a sample of events in each category, re-sampled quarterly.
  • Fee transparency (20%): whether fees are shown up front or only at checkout, and whether an all-in pricing toggle exists.
  • Buyer protection (20%): what the platform's published guarantee covers, including cancelled events, invalid tickets and late delivery, and how refunds are paid.
  • Checkout and delivery (15%): how reliably tickets were delivered in our test purchases, and how long transfers took.
  • Support (10%): response times and outcomes from our own support contacts over the past six months.

Scores are rounded to the nearest half star. The methodology is reviewed every January, and changes are noted at the bottom of each review.

6. Where fee and policy figures come from

Fee percentages, guarantee terms, refund rules and delivery policies are taken from each platform's own help center and terms of service, and from what we observed at checkout. Each figure on a review page is dated and links to the help page it came from. Where a platform does not publish a fee percentage, we report the range we saw in our checkout sample and say so. Where a policy varies by event, we say "varies by event" rather than guess. We do not use figures from other coupon sites or from press coverage without checking them against the platform.

7. Update cadence

  • Codes on paid-traffic pages: re-tested every 7 days.
  • All other codes: re-tested every 30 days.
  • Fee figures and policy summaries: re-checked every 90 days and whenever a platform announces a change.
  • Platform ratings: re-sampled quarterly.
  • Full review rewrite: at least once a year.

The "Last verified" date on each page is the date of the most recent code test on that page, not the date the page was last edited.

8. Corrections

When we get something wrong, we fix it and say so. Factual errors are corrected as soon as we confirm them, usually within one business day, and a dated correction note is added to the page. Typos and formatting fixes are made without a note. If an error appeared in an ad or a social post, we correct the post and pause the ad. We do not remove pages to hide errors.

9. How to report an error

Email [email protected] with the URL, what you think is wrong and, if you have it, a link to the platform page that shows the correct information. We reply within two business days. If you are a platform and believe a figure about you is out of date, write from a company address and point us to the current help page; that is the fastest route to a fix.

10. Contact

Sellencer GmbH, Kolonnenstraße 8, {{SUITE_OR_UNIT}}, Berlin, BE 10827, Deutschland. Editorial questions and corrections: [email protected].