US reselling guide
How cook groups work
Cook groups combine software and people. Monitoring tools detect changes on retailer pages; staff and members add context; the reseller decides whether to buy and where to sell.
From product page to Discord ping
A monitor checks a retailer page repeatedly for changes in stock, price, or product data. When a rule is triggered, the system posts an alert to a Discord channel with a link. Better groups reduce duplicate alerts and add product-specific context.
What happens after the alert
Members check the exact SKU, price, quantity limit, shipping terms, likely selling price, fees, and demand. Speed matters, but skipping the margin check is how a "cook" becomes dead inventory.
Where human expertise matters
Automation can detect availability. It cannot reliably judge every reprint, local demand shift, return risk, or marketplace restriction. Experienced staff and a focused member community add that layer.
A practical notification workflow
Start by muting categories you do not trade. Keep a small set of product watchlists and enable notifications only for stores you can use. Test that the direct link opens the intended SKU, not a search page or a different variant.
After a ping, move through three gates: availability, economics, and rules. If stock is unavailable, stop. If the full-cost margin is insufficient, stop. If the purchase or resale violates retailer or marketplace requirements, stop. Faster notifications do not remove these gates.
How to evaluate feed quality
- Log the alert timestamp and whether the stock was still available when you opened it.
- Note missing variants, wrong prices, duplicate notifications, and expired links.
- Check whether staff explain fees and market risk instead of only listing an optimistic resale price.
- Compare a normal sourcing week with launch-day activity.
- Ask how to report an inaccurate alert and whether corrections are visible.