Statistiques marchand Binance P2P

Metrics to review before making a decision

The statistics view can summarize order count, BUY volume, SELL volume, average BUY price, average SELL price, estimated margin or spread, date range, and completed-order information. A payment-method breakdown adds another useful layer: it shows which methods contributed to the synced activity.

Each metric answers a different question. Order count shows activity frequency. Volume shows scale. Average price provides context for the period. Estimated margin is a calculated indicator, not a substitute for external fees, accounting records, or a guaranteed profit measure.

• Completed-order count
• BUY and SELL volume
• Average BUY and SELL price
• Estimated margin/spread
• Payment-method breakdown

Choose the right historical period

Use the available date filters to compare a recent operating period with a broader one. A short period can show a current change, while a longer available history can reveal whether that change is unusual. The maximum historical period depends on the active plan and what has been synced for the account.

The dashboard cannot show orders that have not yet been synced or that fall outside the selected period. If a figure looks incomplete, check the collection status, selected pair, date range, and whether the order is completed before drawing a conclusion.

• Selected pair
• Available date range
• Sync state
• Completed-order status

Read BUY and SELL data separately

A blended total can hide different behavior on each side. For example, BUY volume may rise while SELL count remains stable, or average SELL price may move while the payment-method mix changes. Separate columns help the merchant ask what changed before acting on a total.

The statistics table can also show an estimated margin per unit and total profit estimate where data is available. Treat these as PituBot estimates that may exclude bank-transfer, payment-method, and other external fees.

• Do not treat a total as a single explanation
• Check both volume and count
• Check average price alongside payment-method mix

Illustrative 30-day analysis

Illustrative example: a 30-day view shows 26 completed BUY orders, 32 completed SELL orders, distinct BUY and SELL average prices, and a concentrated payment-method breakdown. The merchant sees that total volume increased, but the order count did not rise proportionally.

The next question is not “did automation create profit?” It is whether order size, selected payment method, price range, or availability changed. The merchant can inspect the order list and strategy context before making an adjustment.

Use statistics as operational evidence

Statistics are useful for reviewing patterns, testing a change carefully, and discussing a workflow with a team. They are not tax, legal, investment, or accounting advice. Reconcile important settlement decisions with your exchange records and your own professional advice.

PituBot does not claim data export on this page because availability should be confirmed in the product before relying on it. The current dashboard is designed for viewing synced statistics and orders.

See how merchant statistics fit into the wider PituBot bot workspace.

Metrics to review before making a decision

Start with completed-order count because it shows how many synced orders contribute to the selected view. Then compare BUY and SELL volume, their respective average prices, and the estimated margin indicator. A total can hide a meaningful difference between the two sides, so side-specific figures should be read before drawing a conclusion.

Next, inspect the selected date range and payment-method breakdown. A high average price may be concentrated in one payment method or a short period. PituBot’s statistics are useful operational evidence, but important settlement, tax, legal, and accounting decisions should be reconciled against your own records and appropriate professional advice.

• Use completed orders and the selected period as the basis for comparison
• Read BUY and SELL averages separately before reviewing totals
• Use payment-method breakdowns to explain, not merely observe, a change

Contrôles PituBot à vérifier