Why a service disappears from the price list
You bookmarked service 6607, came back a week later, and it is not there. Nothing went wrong — you are seeing a supplier catalogue change, and it is worth understanding because it explains most of the surprises on a panel.
The catalogue is not ours
Every service on this price list comes from a supplier's API. A sync runs regularly, asks for the current catalogue, and updates what you see: prices, minimums, maximums, descriptions, and which services exist at all.
When a service disappears, the supplier stopped offering it. When a price moves, they repriced it. Neither is a decision made here, and neither comes with notice — the API simply returns a different list than it did yesterday.
Why suppliers retire services
- The source dried up. Most services are a supplier's own arrangement with somebody further upstream. When that ends, the service ends.
- The platform changed something. An Instagram or YouTube change can make a delivery method stop working overnight, and a service that cannot deliver is withdrawn rather than left to fail.
- It was replaced. Very often the same thing reappears under a new number with "V2" or "New" in the name and a slightly different price. The old number is gone; the service is not.
- Quality collapsed. A responsible supplier pulls a service whose drop rate has gone through the roof. This is the case you are glad about, even though it looks the same from here.
What happens to an order already placed
Nothing. An order that has reached the supplier has its own id on their side and is fulfilled from there. A service disappearing from the catalogue does not cancel work already in progress, and the status sync keeps tracking it to completion exactly as before.
What you lose is the ability to order it again. If it was the service you relied on, this is the moment to find its replacement rather than to wait for it to return.
Prices move both ways
Supplier costs change constantly, and the sync recalculates sell prices from cost using the commission rules. That means:
- A price you saw last week is not a price you are owed this week.
- An order already placed was charged at the rate shown at the time, and is unaffected by later movement.
- A price that fell is as common as one that rose — competition upstream is fierce, and cheap services get cheaper.
Minimums and maximums move too
The range on a service is the supplier's, and it changes with their stock. A service you used to order 50,000 of might quietly cap at 10,000 because that is what they can now fill. This is a good change badly disguised: a supplier lowering a maximum is a supplier declining to take money for something they cannot deliver.
How to work with a moving catalogue
- Search by keyword, not by number. "Instagram Followers Real" survives a renumbering; service 6607 does not.
- Note what you liked about a service — the speed, the refill window, the drop behaviour — rather than only its id. That is what you are looking for in a replacement.
- Re-check the price before a large order. The number on the page is current; the number in your memory may not be.
- If you resell, pull the catalogue through the API rather than hard-coding ids on your own site. Ids are the thing that changes most.
When the whole list looks different
Occasionally a supplier reorganises everything at once — new categories, new numbering, renamed services. The sync follows it, and for a day the price list can feel unfamiliar. Nothing was deleted here; the upstream catalogue changed shape, and this is a mirror of it.
The search box is the answer to most of this
Searching by keyword finds a renamed service in seconds. Searching by a number you wrote down last month finds nothing, and tells you nothing about why.
Why not just keep the old one on the list?
Because it would not work. A service id that the supplier no longer recognises does not sit there harmlessly — an order against it is rejected the moment it is submitted, after the customer's balance has already been reserved. The order fails, the money comes back, and everybody has spent effort discovering that a line on a menu was fiction.
Removing it is the honest behaviour, even though it is the one that generates the question.
How often this happens
More often than most people assume. A catalogue of a thousand services typically sees a handful of additions and withdrawals every week, and price movements on far more than that. Most go unnoticed because most services are not the one you use.
The sync runs regularly for exactly this reason: a price list refreshed once a month would spend most of the month wrong, quoting prices that no longer exist and offering services that were withdrawn weeks ago. A list that changes under you is the honest version.
The one case worth a ticket
If a service you use disappeared and you cannot find its replacement, ask. Suppliers frequently rename rather than retire, and the new number is often obvious to someone who watched the catalogue change but not to someone searching for a name that no longer exists.
What is not worth a ticket is a price that moved. The rate on the page is the rate, it came from upstream, and there is no version of it held back for anyone.
If you resell on top of this
Pull the catalogue through the API on a schedule rather than copying it once. Match on your own stored supplier id, not on names, and handle a service that has vanished by deactivating it rather than erroring — your customers should see it disappear from your list the way you see it disappear from this one.
The point
A panel is a shopfront onto somebody else's warehouse. Understanding that explains disappearing services, moving prices, changing limits and the occasional overnight reshuffle — and it explains why the catalogue is refreshed automatically rather than curated by hand. A hand-curated list would be a list of things that may no longer exist.
Comments
No comments yet — be the first.
