How it works, in enough detail to check
This page is the short version of everything the product does: what a credit buys, what gets recorded, when a message is sent, and where the whole thing stops. Where there is a number, it is here.
What a credit buys
One credit tracks one product in one marketplace for 30 days. The same product in a second country is a second credit — a credit is spent on the pair of product and country, not on the product alone.
Creating an account grants five credits, valid for 365 days. Credits you buy are valid for 30 days from the purchase, the same length as one tracking period: buy a large pack and you have 30 days to spend it, and whatever is left lapses. Both kinds are prepaid. There is no subscription and no recurring charge.
Credits are not refunded when you stop tracking. The credit is spent the moment tracking starts. Renewing a track spends one more credit and adds 30 days, measured from the existing expiry if that date has not passed yet, so renewing early costs you no time.
Your balance is the sum of every unexpired entry, credits added and credits spent. Card payments run through Stripe and PayPal handles PayPal, both automatically. Bitcoin and bank transfer are accepted too, and both are confirmed by hand, so they take longer to appear.
Adding a product
Paste any Amazon product URL, or the ten-character ASIN if you already have it. Short Amazon links are resolved for you. Then pick the marketplaces you want it checked in and confirm the credit.
The marketplaces are Bolivia, Peru and the United States. All three are amazon.com priced for delivery to that destination — the listing is the same listing, and the country is applied as a delivery address rather than as a different store. Other countries exist in our database but are switched off, and asking for one of them is rejected before any credit is touched.
Adding a product from a signed-in account is rate-limited: ten additions a minute before your email is verified, fifty after. Verifying your email address is also what lets you create a price alert or add a notification recipient at all. Until then a track is created but left switched off.
How landed cost is computed
Base price plus shipping plus import fees equals the total. All four numbers are stored as four separate fields on every observation, so you can read any one of them on its own instead of only the sum.
None of them are modelled or estimated by us. All four are read off the Amazon product page with the delivery destination already set. The import fee is the figure Amazon itself shows for that destination, not our guess at what customs will do.
This is also why the comparison is worth doing. All three marketplaces read the same amazon.com listing with a different delivery destination, so what the comparison isolates is shipping and import fees — which is exactly the part a sticker price hides.
Alert conditions, and how they combine
There are seven conditions. A value reaching a number or falling below it. A value reaching a number or rising above it. A drop of a given percentage or more. A rise of a given percentage or more. A product becoming available. A product becoming unavailable. And one that fires on every newly recorded price, for when what you want is a log rather than a filter.
A value or percentage condition points at one field: the total, the base price, the shipping fee or the import fees. So "tell me when shipping changes even if the item price does not" is a real alert you can build. The availability conditions watch the product itself. One caveat worth knowing: a percentage condition only resolves a previous value for the total and the base price, so a percentage condition aimed at shipping or import fees will never fire. Use a value condition there instead.
Conditions combine with AND or OR. With OR the alert fires if any one of them matched. With AND every one has to match on the same check. The default is OR.
A cooldown keeps the noise down: sixty minutes unless you change it. It is counted per tracked product rather than per alert, so one restless listing goes quiet without silencing the same alert on everything else you track.
Channels, and how each one is verified
Four channels deliver: email, Slack, Telegram and WhatsApp. You add a recipient once, verify it, and from then on any alert can point at it. Each channel is verified differently, because each one can be faked differently.
An email recipient is verified by a link valid for 24 hours, unless the address is the one your account already verified, in which case it is trusted straight away. A Slack destination is verified by actually posting a test message to it at the moment you add it; if that post fails, no verified recipient survives. WhatsApp and Telegram both use a six-digit code valid for ten minutes. For Telegram the easier route is the deep link, which captures the conversation when you start the bot so you never handle an ID by hand.
Five recipients per account, three per alert. Editing a recipient's address or number resets it to unverified, and that is deliberate. Nothing is sent to a recipient unless it is both verified and switched on.
Every send leaves a trace you can read: which provider handled it, the status code it returned, its own error text, and how long it took. When a message does not arrive, that page tells you where it stopped instead of leaving you to guess.
What the price history actually contains
A row is written when there is something worth writing: when the price data differs from the last available reading, or when availability changes. Otherwise the most recent row's timestamp moves forward and no new row appears. The history is a record of observations, not a tick for every check, so gaps in the chart are normal rather than missing data.
Every recorded observation is kept. Expiry does not delete it: when a track's 30 days run out, checking stops and the record stays exactly where it was. Spending a credit to resume continues the same series.
The public statistics have exact definitions. Total checks is the number of recorded rows for that product and country. Availability rate is the share of those rows where the product was actually available. Days tracked is the span between the first row and the last. Minimum, maximum and average are computed only over rows where the product was available and the total was above zero, so a long stretch of being out of stock does not drag the average down.
How often checks run is an operational setting we tune rather than a fixed number, so we do not publish one. What the history gives you instead is the record: every observation that was worth recording, with the date attached.
The limits, stated plainly
Amazon does not always show a price. A check can come back with the product genuinely out of stock, a price Amazon withheld, a listing not available for that destination, or a bot wall. We record which of those it was instead of filing them all as "unavailable", but a blocked check is still a check with no price.
There is no tax handling. No VAT is calculated, added or shown on an invoice. Coverage is three delivery destinations, not the whole Amazon world.
And the things we do not do at all, so you can rule us out quickly: no buying, no cart, no checkout, no affiliate links, no coupon hunting, no sales-rank or review tracking, no keyword or category monitoring, no Buy Box intelligence, no mobile app. If a guide here left your question open, write to [email protected].