Collector sourcing on eBay often fails on timing rather than knowledge. A listing with a misspelled brand, a generic title, or poor photos may be worth investigating, but you only benefit if you see it, price it correctly, and decide before another buyer does. This article walks through one sourcing workflow that combines narrow searches, search monitoring, and a written buy-price limit.
This is an illustrative worked example, not a customer case study. The collector, listings, and numbers below are hypothetical. They show the method and the arithmetic. They do not report a real buyer's results, and nothing here predicts what you will find or earn.
The hypothetical scenario
Imagine a part-time collector-reseller who knows two categories well: vintage Lego sets and lots, and 35mm film cameras. They already check sold comparables and keep notes on target prices. Their problem is coverage. Checking a dozen searches by hand several times a day is tiring, easy to skip, and leaves gaps when they are busy.
They also ignore shipping until the last moment. A listing that looks cheap can stop qualifying once delivery to their address is added. The goal in this scenario is to review relevant new listings sooner and reject unsuitable ones faster. Monitoring can help with the first part. The second part still depends on their own pricing judgment.
Step 1: Write narrow searches for the gaps you understand
Monitoring a vague search only sends you irrelevant results more often. Start from the listing problems you can actually evaluate:
- Common misspellings and generic titles. For example, a precise search for
Lego 6285and a broader one forlego pirate ship, to catch titles that omit the set number. - Mixed lots where one identifiable item may carry most of the value, such as
vintage lego lot pirates. Lots need more manual review, so keep them separate from single-item searches. - Camera bodies with incomplete titles, such as a model search with the Buy It Now format and a used-condition filter applied in eBay's own search page.
These are query examples, not a claim that any of them currently contains an underpriced listing. Run each search manually first. If most results are irrelevant, refine it before monitoring it. The underpriced-listing checklist explains how to pair a precise search with a broader one.
Step 2: Turn each search into a hunt
TruffleHunt turns a supported eBay search results URL into a hunt. It checks that search through eBay's official API and can alert you to new listings and to fixed-price listings whose item price plus quoted shipping falls below the total you were last alerted at. The search automation guide covers the setup steps and which eBay filters carry over.
The available interval, marketplaces, and delivery channels depend on the plan:
| Plan | Relevant limits |
|---|---|
| Forager (permanent free plan) | Up to 3 active hunts, 30-minute minimum interval, 1 marketplace per hunt, email alerts, 1 connected eBay Developer account |
| Hunter | No hunt-count cap, 5-minute minimum interval, 1 marketplace per hunt, email, Telegram and Discord, 1 connected account |
| Hunter Pro | No hunt-count cap, 1-minute minimum interval, up to 5 marketplaces per hunt, email, Telegram and Discord, up to 10 connected accounts |
TruffleHunt currently supports 24 eBay marketplaces. Searching another marketplace only helps if the item can be delivered to you and the price still works after shipping, import charges, and currency conversion. Bulky, fragile, or hard-to-authenticate items are often poor candidates for cross-border buying. Check current plans for the latest limits.
In this scenario, the collector routes alerts to the channel they actually read. If you use Telegram on a plan that includes it, the Telegram setup guide shows how to connect it and send a test message.
Step 3: Check your API budget before shortening the interval
Ongoing monitoring runs on your own eBay Developer credentials, so it uses that application's eBay API allowance. A new eBay Developer application commonly starts with 5,000 Browse API calls per day, but eBay sets the actual limit for each application and it can differ. Where eBay reports the limit for your connected account, TruffleHunt uses that figure instead of assuming a fixed number.
The number of checks per day follows from the interval: 1,440 minutes divided by the interval. Each check of a marketplace uses at least one API call, and more if additional results pages are requested.
| Hypothetical setup | Checks (API calls) per day |
|---|---|
| 1 hunt, 1 marketplace, every 30 minutes | 1,440 ÷ 30 = 48 |
| 1 hunt, 1 marketplace, every 5 minutes | 1,440 ÷ 5 = 288 |
| 6 hunts, 1 marketplace each, every 5 minutes | 6 × 288 = 1,728 |
| Same 6 hunts if every check needs 2 results pages | 1,728 × 2 = 3,456 calls |
The last row would fit within a 5,000-call allowance, but not with much room for faster intervals or more marketplaces. Give a short interval to your most time-sensitive search, and a longer one to broad lot searches that you review less urgently. On Hunter Pro, connecting more than one Developer account adds whatever allowance eBay grants each of those applications. It does not create a fixed total.
Step 4: Set a maximum buy price before alerts arrive
Decide your limit before you see a tempting listing. The following worksheet is hypothetical. It is not an appraisal of any camera, a published eBay fee schedule, or a customer result. Replace every figure with your own researched assumptions.
| Planning input for one camera body | Illustrative amount |
|---|---|
| Expected resale price, from matched sold comparables | $240 |
| Selling fees | $32 |
| Outbound postage and packaging | $18 |
| Testing, cleaning, and allocated labor | $20 |
| Reserve for defects and returns | $25 |
| Desired contribution after these allowances | $45 |
| Maximum acquisition budget | $100 |
| Estimated purchase tax | $6 |
| Typical quoted inbound shipping | $14 |
| Maximum item price at that shipping quote | $80 |
The acquisition budget is 240 − 32 − 18 − 20 − 25 − 45 = 100. With $6 tax and $14 shipping, the item-price ceiling is 100 − 6 − 14 = 80. The $45 contribution is a planning target, not a guaranteed return.
Now apply it to three hypothetical alerts. The alert total is item price plus quoted shipping. Tax and any repair allowance are added separately, assuming the same $6 tax estimate for each:
- Alert A: $72 item + $14 shipping = $86. Adding $6 tax gives $92, which fits the $100 budget, subject to condition and seller checks.
- Alert B: $59 item + $38 shipping = $97. Adding $6 tax gives $103, which exceeds the budget. The lowest item price of the three still fails.
- Alert C: $65 item + $12 shipping = $77, listed as “shutter sticks, untested”. Adding $6 tax and a $35 repair estimate gives $118. It fails at this valuation and needs a separate parts-or-repair calculation.
Unknown shipping is not free shipping. Confirm delivery to your address and check duties, currency conversion, and other costs before buying. The landed-cost guide lists what to add beyond the quoted subtotal.
Step 5: Triage each alert the same way
A consistent review order keeps fast decisions from becoming careless ones:
- Identify the item. Compare markings, set numbers, and photos with the title. List what is included and what is missing.
- Check condition and authenticity. Read defects, testing statements, and return terms. Treat “untested” as unknown condition, not working condition.
- Confirm the cost to your address. Recalculate with the actual quote, tax, and any repair allowance.
- Review the seller. Read recent feedback. Where they are offered in your hunt editor, seller feedback alert filters can suppress some alerts, and on Hunter Pro you can block specific sellers. Neither one certifies a listing.
- Decide and record why. Buy, make an offer where available, watch, or pass. Note the reason so you can refine the search later.
If an existing listing is more interesting once it gets cheaper, the price-change tracking guide explains which fixed-price changes can trigger an alert.
What to measure in your own trial run
We are not reporting outcomes for this scenario. If you test a workflow like this, record a few numbers over a fixed period so you can judge it on your own categories:
- Alerts received per hunt, and how many you actually reviewed.
- How many reviewed alerts passed your buy-price worksheet, and why the rest failed: shipping, condition, seller, or price.
- Purchases made, and the realized result after each item sells, compared with the planned contribution.
- Time spent on sourcing compared with your previous manual routine.
A few weeks of data from a handful of searches is a small sample. Use it to adjust searches and intervals, not as proof that a category will keep producing the same opportunities.
What monitoring does and does not change
Monitoring replaces repetitive manual checking. It does not replace category knowledge. A polling interval is the minimum time between checks, not a promise of how soon after listing you will see an item. eBay data availability, your API allowance, processing, and notification delivery all affect timing, and other buyers may still see a listing first.
TruffleHunt does not buy items, place bids, authenticate goods, or judge resale value. Price-drop alerts apply to fixed-price listings, and price history starts when a hunt first observes a listing. In this scenario, the collector still passes on most alerts. The workflow helps because each alert arrives with a written limit already set, so the decision takes less time.
Try the workflow with one search
Create an account to monitor your first eBay search. If onboarding offers you the free trial hunt, you can test a search without API keys or a card. Continued monitoring uses your own eBay Developer credentials. Forager is a permanent free plan, separate from that onboarding trial; check current plans for hunt limits and delivery options.
Start with the one category where you can price an item confidently from a photo and a title. That is where faster alerts are most useful.