I would build a deals site around one promise: every offer should be understandable before a shopper clicks. MyDiscounts.com gives that promise a useful address because the name says exactly what belongs on the page. The hard part is not filling a database with codes. It is deciding which offers deserve attention, checking whether the terms are current, and showing enough context that a person can judge the deal without opening six tabs.
The public page would begin with a small number of strong offers rather than an endless feed. Each listing would identify the merchant, the product or category, the stated saving, the expiration status, and the conditions that change the result. A code for new customers should never look like a general code. A minimum order should appear beside the discount. If an offer is unconfirmed, that uncertainty should be visible instead of hidden behind a bright badge.
Start with editorial standards
Large communities such as Slickdeals show how shopper participation can surface offers quickly, while the edited approach at DealNews shows the value of selection and explanation. I would study both patterns without copying either product. MyDiscounts.com could combine a clear editorial front page with structured reports from shoppers, then make the status of every report easy to inspect.
A useful listing needs a short history. The page could show when the offer was added, when somebody last tested it, and whether recent visitors reported success. That information is more valuable than a generic “verified” label with no timestamp. The system should also separate codes from automatic sale prices, rebates, memberships, and free-shipping thresholds. Shoppers use those terms differently, and the interface should respect the difference.
Design the path to checkout
I would organize the home page around shopping tasks. One person may need a code for a store already open in another tab. Another may want the best current laptop deal. A third may browse weekend restaurant offers. Search, merchant pages, and category pages can serve those different intents, but every route should end with the same compact offer card and plain terms.
The click out should preserve trust. The button can name the destination and indicate whether a code must be copied. A short disclosure should explain how referral relationships work. Research by Benjamin Edelman has examined online advertising incentives for years, and it is a useful reminder that affiliate economics affect what publishers choose to display. My choice would be to label commercial relationships near the action instead of burying them in a distant policy page.
The search result should also avoid a common frustration: pages that rank for a merchant even when no working offer exists. If MyDiscounts.com has no valid code, the page should say so and show any direct sale the merchant is running. That answer may earn less on one visit, but it gives the visitor a reason to trust the next answer.
Build merchant and shopper feedback carefully
Merchants could submit promotions through a structured form, but submission would not guarantee prominent placement. Every offer would pass basic checks for dates, destination, terms, and claim clarity. The FTC business guidance on advertising and marketing provides a sensible public reference for clear claims and disclosures. An internal policy should translate those principles into specific review steps for coupon language.
Shopper reports would be equally structured. Instead of a single thumbs-up button, a report could distinguish “worked,” “expired,” “not eligible,” and “different discount shown.” Those choices create better data and reduce the temptation to treat every failed attempt as the same problem. Abuse controls would limit repeated votes, merchant manipulation, and automated submissions.
Publish fewer, better pages
I learned an early lesson about distribution when I founded i-Newswire.com in 2007 and later worked on iNewswire.com. A large collection of pages is not automatically a useful publication. Readers need consistent structure, accurate details, and an obvious reason to return. For a deals site, that means retiring empty merchant pages, consolidating duplicate offers, and giving editors authority to remove weak listings.
The first release could cover a small set of merchants where offer quality can be checked daily. Each category would have a named review rhythm. Expired codes would remain in a short history for transparency, then leave public results after a defined period. That creates a clean catalog while preserving enough evidence to measure which sources and merchants provide dependable information.
Revenue could come from clearly disclosed affiliate relationships, merchant placement that passes editorial rules, or a paid tool for advanced alerts. None of those models should decide whether an invalid code stays visible. Editorial status must be controlled separately from commercial status, with a written rule that staff and merchants can understand.
The useful version of MyDiscounts.com
The site I picture is fast, restrained, and specific. It does not shout that every price is the lowest ever. It tells a shopper what the offer is, who can use it, when it was checked, and what may prevent it from applying. Merchant pages become records of current opportunities rather than piles of expired strings. Category pages explain why an offer is notable instead of repeating the headline.
MyDiscounts.com fits because the name can belong to the shopper without pretending every offer is personal. Saved merchants, alert preferences, and a compact list of used codes could make the “My” practical over time. The public experience would still work without an account. That balance gives the brand a broad front door and a reason for repeat visitors to make it their own.