SHARKRULE / Learn

Trading bot risk controls: one order, one budget, the whole account

A trading bot needs more than a limit on each order. Define what the rule may spend in total, what it may still hold, and how its commitments overlap with other activity in the same account. Count outstanding buys before approving another one. A budget controls authorization; it does not guarantee a maximum loss or a successful exit.

SharkRule · Reviewed

Write down what each limit actually counts

Use this worksheet to review a Spot automation rule. These are control definitions to check, not a claim that every application offers every setting. For each limit, record the unit, scope, time period, treatment of fees and exact reset condition. A label such as ‘budget’ is incomplete without those details.

For a cumulative purchase cap, completed purchases keep counting after an asset is sold. For a reusable exposure cap, a confirmed sale may create room for another purchase. Those policies permit different behavior. Record which one you authorized; a restart or a profitable sale must not silently create a new spending period.

Four separate questions for the same rule
ControlQuestion to answerWhat it does not establish
Per-order capHow much may a single buy commit, including the defined costs?How much repeated buys may spend
Total spending capHow much may all buys commit during the approved run or period?How much remains invested after sales
Position limitHow many asset units, or how much measured value, may remain held and committed to buys?A guaranteed loss ceiling or exit price
Account reviewWhat do all rules, manual holdings and outstanding orders commit together?That separate bot budgets are isolated balances

Worked example: a permitted order size can still exceed the total

All numbers are hypothetical generic quote-currency units, not allocations, assets or settings to adopt. Define a cumulative run budget of 200 including a 10-unit cost allowance: fees already charged plus money reserved for remaining costs. This worksheet allows at most 60 of purchase value per order. Completed buys used 90 before fees, and one accepted buy can still use 50 before fees. No sale replenishes this example’s cumulative budget.

Remaining purchase room = 200 − 90 − 50 − 10 = 50. A proposed buy of 60 meets the individual order cap but would commit 90 + 50 + 10 + 60 = 210, exceeding the total by 10. The worksheet rejects it. It does not automatically raise the budget or select a smaller trade.

The same budget as the outstanding order changes
Confirmed statePurchase value spentRemaining buy commitmentCost allowanceRoom within 200
Before another fill90501050
20 of the pending buy fills110301050
The remaining 30 is confirmed canceled11001080
  1. When 20 fills, move it from the outstanding commitment to spent value. Counting both the original 50 and the new 20 would count the fill twice.
  2. Release the remaining 30 only after checking the final order state and fills. A cancellation request alone is not confirmation.
  3. The confirmed cancellation frees unspent room; it does not erase the 110 already purchased. Keep any acquired assets in the position review.
  4. Move charged fees from reserved to paid within the cost allowance, without adding them to purchase value as well. The combined allowance stays 10 only for this example; recompute if actual costs or necessary reserves change. A fixed allowance does not bound market slippage.

Check holdings across the account, not just this bot

An asset can be held through another rule or a manual purchase. Record all of it once. A pending sell is not yet a reduction in holdings, and the part of a holding reserved for that sell is not an additional asset.

For a separate hypothetical unit limit of 12, suppose the account holds 8 units, including 2 reserved for a sell. Outstanding buys could add 3. Another buy of 2 would bring the total to 8 + 3 + 2 = 13, so it fails that limit even if its cash budget fits. Do not calculate 8 + 2 + 3 + 2: the reserved 2 are already inside the 8.

Where Binance’s MAX_POSITION filter applies, it counts free and locked base-asset balances plus open buy quantities. That exchange check is separate from your chosen budget.

If you measure exposure in money instead of units, specify the valuation price and timestamp. Price changes can increase measured exposure without a new purchase. A count of open positions alone also says little about their value. Review the combined commitments of all bots rather than giving each the same apparently available balance.

Treat an unknown order as unresolved spending

Binance’s account documentation provides separate free and locked balances, order queries and trade history. Reconcile these views before reusing a reservation.

Binance documents that a timeout can leave execution status unknown; it is not proof of failure. Check the original order’s outcome.

For SharkRule’s Binance workflow, an ambiguous order must block further Binance submissions until its status and fills are reconciled. Do not treat a retry, browser refresh, new rule or new API key as a fresh allowance. Keep the order identifier, timestamp and budget entry while investigating. Never include an API secret in that record.

Decide what pausing and stopping will leave behind

In SharkRule’s current live Spot guidance, pausing new buys leaves exit rules active for existing positions. Stopping ends both new buys and automatic exits; it does not sell the remaining holdings. Neither action reverses orders already sent. Read the current status and check the exchange afterward.

Write a stop procedure that names the rule, the orders to inspect and who will reconcile the remaining holdings. A request to cancel only concerns the unfilled remainder; it does not undo a completed trade. Avoid indiscriminately canceling other strategies’ orders in a shared account.

Common mistakes that change the authorized budget

  1. Treating an exchange’s minimum order size as permission to increase a user’s cap. If no valid order fits, stop for review.
  2. Subtracting only completed buys while ignoring outstanding orders and costs, or counting the filled portion twice.
  3. Confusing cumulative spending with current holdings. Selling can reduce exposure without restoring a cumulative purchase allowance.
  4. Assuming that a stop-loss instruction guarantees a loss ceiling. Gaps, slippage, partial fills and non-fills can prevent the intended exit.
  5. Assuming a daily limit resets in your local time, or a restart clears previous spending. Record the actual timezone and reset policy.

Complete this checklist before an explicit start

A useful next step is to compare your completed worksheet with the amount per buy and maximum buys shown for your Shark. If you are preparing an eligible Binance connection, use the Binance setup guide in Related guides below to check permissions before deciding whether to start. Keep withdrawal permission disabled for this order-only workflow.

  1. Name the exchange account, Spot pair, rule and current mode. Check account and geographic eligibility.
  2. Write the per-buy amount, maximum buys, total authorization and whether costs are included. State whether proceeds can be reused.
  3. List filled purchases, remaining buy commitments and current holdings. Include other rules and manual activity in the account review.
  4. Specify what blocks a new buy: exhausted budget, position limit, missing data or unresolved order status. Check which controls the current dashboard actually offers.
  5. Confirm what pause and stop do, how open orders will be checked and what remains after stopping.
  6. Review the supported controls and permissions before explicitly starting. An account connection or reading a guide is not an authorization to trade.

What these controls cannot promise

A budget cannot prevent asset losses, guarantee execution or make funds at an exchange immune to outages, custody problems or access restrictions. Fees and slippage reduce funds; a limit order may never fill. A simulation can help inspect rule behavior, but modeled execution does not establish real fills or future results.

SharkRule is independent software, not affiliated with or endorsed by Binance. Available controls depend on the current dashboard, account and location. We are not financial advisors. This worksheet explains mechanics and tradeoffs, not which asset, allocation, position size or strategy to choose.

Frequently asked questions

Is a 60-unit order cap the same as a 60-unit bot budget?

No. Several separate 60-unit orders can commit more than 60 in total. Specify the total allowance, its period and whether completed purchases continue counting after sales.

Does a canceled order restore the full original amount?

Only the confirmed unfilled remainder can be released from the outstanding commitment. Completed fills remain purchases, costs still matter and acquired assets remain in the position review.

Does pausing a Shark sell its holdings?

No. Current live Spot guidance says pausing new buys retains exits for existing positions. Stopping also ends automatic exits and does not sell remaining holdings. Check status, open orders and balances directly.

Does a budget tell me the most I can lose?

It describes a defined authorization, not a guaranteed loss outcome. Check its scope: other holdings, other bots, fees and the exchange account may expose additional funds to risk. An exit instruction does not guarantee a price.

Official documentation and references

Prepared with AI assistance from the linked official documentation. Examples are hypothetical; no live account tests or return comparisons were performed.