Binance-P2P-Bot zur Preisanpassung

Repricing is different from setting a standing price

A standing price remains fixed until a merchant edits it. Repricing starts again whenever PituBot evaluates the selected market for an active bot. The aim is not to change on every cycle; it is to decide whether a new candidate is valid under the current strategy.

A competitor price change is only one possible trigger. An offer can disappear, become inactive, leave the selected payment-method set, change its quantity or transaction range, or no longer match the side being compared. Any of those changes can alter which offer is relevant.

• Competitor price change
• Competitor disappearance or inactivity
• Quantity, limits, payment, or side mismatch

The repricing timeline

At time A, PituBot sees a valid comparable offer and computes a candidate within your configured range. At time B, that offer becomes inactive; the bot removes it from the comparison and may retain the current price if no suitable replacement exists. At time C, a new eligible offer appears; the bot computes again and only updates if the new candidate survives every rule.

This timeline is why a skipped run is useful information. It can mean the market moved but the remaining offer failed a filter, the candidate hit a boundary, or a final account-level safety condition rejected the position.

• Observe
• Filter
• Calculate
• Apply strategy rules
• Perform final safety check

A repricing bot should be able to decrease

If the relevant market moves down and the candidate remains inside the ad's boundaries, repricing should be able to decrease the price. A bot that only moves upward can drift away from the intended position and make the strategy commercially unreasonable.

The reverse is also true: an increase is not automatically correct merely because another price is higher. The configured floor or ceiling, side-specific filters, and final placement rule remain more important than the direction of the last change.

• Both upward and downward movement are possible
• Direction does not override the strategy
• No update is valid when the allowed range is empty

Illustrative repricing timeline

Illustrative BUY timeline: at 09:00 a selected comparable BUY ad is 0.998 USD per USDT and a rule produces a candidate near that market. At 09:05 the competitor disappears, so the bot keeps the current price rather than using an unrelated SELL listing. At 09:10 a new matching BUY offer appears at 0.996 USD per USDT; the bot evaluates a lower candidate, but only applies it if the BUY maximum, payment filters, and same-side account rule all permit it.

Illustrative SELL timeline: a new eligible SELL offer can justify a different candidate, but the SELL floor still prevents an update below the merchant's permitted range. These examples are illustrative and do not predict a particular exchange result.

When a boundary is reached

When a candidate would cross a configured minimum or maximum, PituBot should stop at the boundary or leave the price unchanged according to the valid rule set. A boundary is not a target to overcome; it is a limit chosen by the merchant.

Review boundaries after changing the underlying ad, available balance, payment methods, or market objective. A repricing rule is only as current as the assumptions that support it.

Read how auto-pricing configuration sets the bounds used by repricing.

Repricing is a sequence of events

Repricing is not one permanent setting. A recalculation can follow a changed comparable price, an offer disappearing from the filtered list, a changed available amount, or a change in whether the offer still matches the selected payment method and transaction conditions. The correct response can be a move up, a move down, or no movement at all.

For example, if the formerly best comparable offer disappears, the next valid offer may become the reference. If that next offer is outside the configured range, repricing stops at the boundary rather than following the list indefinitely. The activity history is the place to review which condition produced a change or a skip.

Zu prüfende PituBot-Steuerungen