← All posts

How to make sure a supplier price rise never makes you sell at a loss

16 novembre 2026

A supplier raises its rate and you keep selling at the old price. The panel syncs costs every hour and refuses an order that would lose money. Add a price guard to be stricter. Video and screenshots.

Costs synced every hour, worst-case cost checked per order, and a price guard cap per 1000

Prefer to watch? The video covers everything below in about a minute and a half.

1 min 32 s, English voice-over with captions. Screens are from a demo copy of the TopSocialBot panel; provider names and prices are sample data.

The problem

Suppliers change their rates without telling you. Your price stays where it was, every order now loses a few cents, and you find out days later from a report, after the loss is already real.

Three layers of protection

LayerWhat it doesYou set it?
Hourly cost syncSupplier rates refresh every hour, so the margin you see is current.No, always on
Worst-case checkBefore an order is accepted, the panel works out what it costs if the most expensive provider on its route has to deliver it. If that is not below what the customer pays, the order is refused.No, always on
Price guardYour own cap: the highest cost per 1,000 you accept on this service.Yes

See your margins

The Services list shows price, cost and margin for every service. Two filters above it, Low margin and At or under cost, list the services a price rise has hit.

Services list with price, cost and margin for each service
Price, cost and margin on one line.
Low margin and At or under cost filters above the services list
The two filters to check after a supplier changes its rates.

See the worst case

Open the service's forwarding rule and use Try an order. Under the result, the panel shows the worst case: the cost and margin if the dearest backup has to deliver.

Trial result with the line If backups have to step in, the worst cost and margin
With a backup at $0.55, the worst case is still a 54.2% margin.

Add a price guard

Below the rules, fill in Price guard: max cost per 1000 (USD). Orders whose worst-case cost is above it are refused.

Price guard field set to 0.50
A guard of $0.50 per 1,000.

If a provider already on the route costs more than the guard, the editor warns you on the rule at once, before you publish: with this guard, orders on that rule would be refused.

Warning on the rule that the worst-case cost is above the price guard
The backup costs $0.55, the guard is $0.50.

Either raise the guard above your dearest backup or remove that backup. Then add a note and Publish.

History showing the new version live with the note
Live with a guard of $0.60.

Where to set the guard

A little above your dearest backup, and well below your price. Too tight, and a small rate change starts refusing orders; too loose, and it never triggers. When a supplier does raise its rate past the guard, orders on that service are refused until you change the price, the guard or the provider, which is the point: you decide, instead of losing money quietly.

Questions

What does the customer see when an order is refused?

The order is not placed and nothing is charged.

Do I need a guard on every service?

No. The worst-case check already stops any order that would cost more than its price. The guard is for keeping a minimum margin, not just avoiding a loss.

What to do next

About the author

Marcus Reed

Head of Storefront Operations

Former SMM panel operator. Writes about launch timelines, payment routing, and what resellers need before day one.