DN AI Trading Series · Small-order troubleshooting · Checked 5 November 2026
A rejected small order can feel like a funding problem. The useful first question is more precise: which condition did this particular order fail? Adding money will not repair a price increment, and a bot’s total allocation is not the size of every order it submits.
This guide follows our small-budget AI trading comparison. That article considers whether a setup can justify its costs. This one examines the submitted order: its units, increments, minimums and entered funding assumptions.
Separate quantity, value and bot capital
Use two named units. In a fictional BASE/QUOTE market, quantity is measured in BASE and the limit price is QUOTE per BASE. Multiplying them gives the order’s quote value, also called its notional. A number such as “10” is incomplete until its unit and purpose are clear.
| Term | Unit or meaning | Question to answer |
|---|---|---|
| Base quantity | Units of the asset being bought | How much of the asset does this order request? |
| Limit price | Quote units per base unit | What price limit is being submitted? |
| Order notional | Price × quantity, in quote units | Does the order meet the applicable value bound? |
| Tick and step | Price and quantity increments | Do the proposed numbers fit the supplied grids? |
| Available quote funds | The amount entered for this check | Does it cover the notional plus the entered quote allowance? |
| Bot allocation | Capital assigned to a strategy | How is it divided across that strategy’s orders and other requirements? |
Kraken’s support documentation explicitly distinguishes a quote-currency cost minimum from a base-currency order-volume minimum. Its WebSocket v2 instrument schema separately describes minimum quantity, minimum cost, price increments and quantity increments. [2][3]
Compare the proposed order with a rounded-down illustration
Start with the exact numbers you intended to submit. Keep the exchange’s current rules and your units beside you. The tool starts blank; Load fictional example supplies the invented case above. A blank minimum or allowance is unknown, not zero.
The two columns stay separate. The illustration floors each value to its active increment; it does not change the input fields, submit a replacement order or decide whether the changed trade still fits your strategy. Record an inactive rule only when the actual scope is documented, and keep every excluded rule visible.
DN Spot Limit Order Check
Check a requested BUY spot LIMIT price and base quantity against the arithmetic rules you enter. The separate floor-down calculation never replaces your inputs or increases the order.
All values are reader supplied. The tool does not fetch current filters, prices, balances or permissions, and does not place an order. Use ordinary decimals such as 0.05; do not use scientific notation or thousands separators.
Blank means unknown. Enter the quote-cost allowance explicitly, including 0 if that is your assumption. The same fixed allowance is added in both columns; it is not a fee quote, does not infer the asset charged for fees, and does not count toward minimum notional.
Scenario labels and explicitly inactive rules
Only exclude a rule if your documented scenario treats it as inactive. These choices do not disable venue filters. An unchecked rule with a blank value remains unknown. A zero active tick or step is an error; zero is never automatically interpreted as inactive.
No rules are explicitly inactive. A blank active rule remains unknown.
As requested
Required values are unknown
The modeled checks are incomplete because required values remain unknown.
- Limit price (QUOTE/BASE)
- Unknown
- Base quantity (BASE)
- Unknown
- Order notional (QUOTE)
- Unknown
- Fixed quote-cost allowance (QUOTE)
- Unknown
- Notional + allowance (QUOTE)
- Unknown
- Entered funds (QUOTE)
- Unknown
- Funds less entered requirement (QUOTE)
- Unknown
Rounded down, display only
Required values are unknown
The modeled checks are incomplete because required values remain unknown.
- Limit price (QUOTE/BASE)
- Unknown
- Base quantity (BASE)
- Unknown
- Order notional (QUOTE)
- Unknown
- Fixed quote-cost allowance (QUOTE)
- Unknown
- Notional + allowance (QUOTE)
- Unknown
- Entered funds (QUOTE)
- Unknown
- Funds less entered requirement (QUOTE)
- Unknown
The calculation never rounds upward and does not edit your requested price or quantity. Both grids start at zero in this model.
An active increment or requested value is unknown or invalid, so a complete rounded-down calculation is unavailable.
- The requested price is unknown or invalid.
- The requested quantity is unknown or invalid.
- Display calculation only. Requested inputs are not replaced. A lower BUY limit may not fill.
Entered arithmetic checks
“Modeled active checks pass” covers only the checks below. It is not an accepted or approved order. Both grids start at zero in this model. Swipe the table sideways on a small screen.
| Check | Entered rule | As requested | Rounded down, display only |
|---|---|---|---|
| Positive limit price | Greater than 0 QUOTE/BASE | UnknownEnter a known positive value. | UnknownThe requested price is unknown or invalid. |
| Positive base quantity | Greater than 0 BASE | UnknownEnter a known positive value. | UnknownThe requested quantity is unknown or invalid. |
| Price tick alignment | A known positive increment | UnknownThe value or its active grid increment is unknown or invalid. | UnknownThe value or its active grid increment is unknown or invalid. |
| Quantity step alignment | A known positive increment | UnknownThe value or its active grid increment is unknown or invalid. | UnknownThe value or its active grid increment is unknown or invalid. |
| Minimum quantity | A known entered minimum | UnknownThe order value or entered minimum is unknown or invalid. | UnknownThe order value or entered minimum is unknown or invalid. |
| Minimum notional | A known entered minimum | UnknownThe order value or entered minimum is unknown or invalid. | UnknownThe order value or entered minimum is unknown or invalid. |
| Entered quote-budget coverage | Known quote funds and quote-cost allowance | UnknownBlank allowance is unknown, not a zero fee. This check covers only the entered amounts. | UnknownBlank allowance is unknown, not a zero fee. This check covers only the entered amounts. |
What this result does not check
- Minimum and maximum price bounds, maximum quantity and notional, and dynamic price bands are not modeled.
- Market or account status, permissions, order-type eligibility and other venue, exchange or account filters are not modeled.
- Actual fee amounts, the asset charged for fees, existing holds and other account reservations are not inferred or validated.
- The fixed quote-cost allowance is a reader assumption. The same amount is used in both columns and is not part of order notional.
- The values and rule scope may change. This tool does not retrieve current venue data or check when the reader observed it.
- A lower BUY limit can change execution behavior and may not fill. The comparison does not suggest a replacement order.
Reference documentation date: 2026-11-05. That date does not verify or date any price, filter, balance or allowance entered here.
Calculations and downloads run locally, without account credentials or browser storage. JSON preserves decimal values as strings. Import the CSV value column as text when using spreadsheets to preserve exact decimals. A download does not submit an order.
The initial table remains visible without JavaScript. JavaScript with exact BigInt arithmetic is needed to edit inputs and download calculations; no floating-point fallback is used.
1. Confirm the product, pair and order units
Record the exchange product, exact pair, side and order type. A spot limit buy and a derivatives closing order can use different fields and conditions even when their market names look familiar. Confirm whether the bot’s “size” means base quantity, quote spending or something else.
Binance’s exchange-information endpoint exposes the symbol’s base and quote assets, trading status, order types and filter list. It also exposes precision fields separately. Read the actual symbol data instead of copying a documentation example or assuming every pair has the same filters. [4]
API field names need equal care. Coinbase Advanced Trade documents separate base_increment, quote_increment and price_increment values. A field named “quote increment” should not be casually renamed “price tick” in your adapter. [5]
For a no-code bot, preserve the submitted-order preview and the original error details. For a custom integration, preserve the serialized request with credentials removed. The useful evidence is the order the connector actually sent, which may differ from a rounded number shown on its dashboard.
Check: can you state the unit of every submitted amount? If not, resolve that first. Comparing a base quantity with a quote-currency minimum can produce a convincing calculation of the wrong condition.
2. Check quantity and order value separately
A minimum quantity asks how much base asset is in the order. A minimum value asks what that quantity is worth under the rule’s applicable price calculation. Meeting one does not logically establish the other.
For a simple limit-order model, write the conditions independently: quantity ≥ minimum quantity and price × quantity ≥ minimum notional. Keep their units beside them. Kraken’s cost-minimum explanation is a useful reminder that its cost threshold is denominated in the quote currency. [2]
Consider an invented minimum value of 10 QUOTE. At a supplied limit price of 2 QUOTE per BASE, a quantity of 4 BASE has a value of 8 QUOTE. At a price of 2.5, the same quantity has a value of 10. These are arithmetic examples, not suggested prices or quantities.
The practical implication is that a quantity copied from another order may not satisfy the same value threshold after the price changes. A minimum-value failure is also different from a maximum-value failure. Record the specific bound instead of treating any size-related error as a request to buy more.
Check: retain both the quantity result and the notional result. An unknown minimum remains a missing fact, even when another check passes.
3. Check increments instead of merely shortening decimals
A decimal-place count and an increment are different concepts. A fictional price tick of 0.05 permits 2.30 on a zero-origin grid, but not 2.33. Both numbers have two decimal places. Formatting a number to two places therefore does not solve the increment check.
Quantity has its own grid. With an invented step of 0.01, 4.26 is aligned and 4.263 is not. With a step of 0.03, a different set of values is allowed. Treat the actual increment as data rather than inferring it from the number of digits you see.
Kraken’s v2 schema distinguishes order increments from precision and display-precision fields. That distinction matters when an interface shows a rounded amount that is not the exact amount used in a request. [3]
The DN model uses zero-origin grids: price and quantity must each be exact multiples of their active increments. Binance Spot documents these remainder checks. The model does not assume every other venue or product has the same grid-origin convention. [6]
Check: validate the exact submitted decimal strings. The checker uses base-ten integer arithmetic so a value such as 0.3 on a 0.1 grid is not rejected because of a binary floating-point remainder.
4. Recheck the complete order after rounding
Rounding changes the order. It is not a final cosmetic step. After changing either price or quantity, recompute every affected condition, including minimum quantity, notional and the entered funding requirement.
| Measure | Proposed order | Rounded-down illustration |
|---|---|---|
| Limit price, QUOTE per BASE | 2.349 | 2.30 |
| Quantity, BASE | 4.263 | 4.26 |
| Notional, QUOTE | 10.013787 | 9.798 |
| Price tick: 0.05 | Conflicts | Matches |
| Quantity step: 0.01 | Conflicts | Matches |
| Minimum quantity: 0.1 | Matches | Matches |
| Minimum notional: 10 | Matches | Falls short by 0.202 |
The example also enters 20 QUOTE of funds and an explicit quote-cost allowance of zero. Zero here is an invented calculation input; it is not a claim that trading is free. Neither column proves that a venue would accept the order.
Both price and quantity were reduced, yet the outcome did not become an all-purpose improvement. The proposed version fails the two grids. The floored version fits them but fails the minimum value. Raising a value to fix that shortfall would create another proposed trade requiring a fresh decision and a fresh set of checks.
The calculator deliberately does not generate a larger order. A lower buy limit can also change whether the trade fills. If the permitted order cannot fit the size and price you intended, leaving the trade unplaced is a valid outcome of the review.
Check: compare the complete before-and-after calculations. Keep the original intent visible instead of allowing a connector to silently rewrite it.
5. Use available funds and an explicit cost assumption
An account’s total value is not automatically the quote balance available for this order. Coinbase explains that funds reserved for open orders are held and do not appear in available balance until execution or cancellation. [7]
That does not make canceling an unrelated order the right response. First identify the balance, reservation and strategy scope. A protective order or another bot’s allocation may have a purpose that this attempted buy does not override.
The tool performs one transparent budget calculation: notional + entered quote-cost allowance ≤ entered quote funds. For an independent fictional example, a 10-QUOTE notional plus a 0.20 allowance requires 10.20 QUOTE. Entered funds of 10.10 leave a 0.10 shortfall. The allowance does not increase the notional used for the minimum-value check.
Real fee handling can differ from that simple assumption. Binance’s commission documentation describes received-asset calculations and possible BNB payment. A buy fee deducted from received base asset can, by arithmetic, reduce the inventory available for a later sale. Do not assume every fee is charged in quote currency. [8]
Check: identify the actual available-to-trade amount and the product’s charging and reservation rules. The fixed quote allowance is your explicit scenario input, not a fetched fee estimate or a complete account buying-power calculation.
6. Check the bot’s allocation across its orders
A strategy’s creation minimum and an individual order’s minimum are different levels of the problem. A bot may spread its allocation across multiple entries or maintain both base and quote assets. Its total balance does not show whether each planned order fits the relevant conditions.
Pionex’s current public bot finder says its Spot Grid minimum depends on the pair’s order-size rule, lower and upper prices, and grid count. It directs readers to the amount displayed in the app before confirmation. That is a product-specific dependency, not a universal bot minimum. [9]
For any setup, inspect how capital is allocated to individual orders, what remains reserved and whether later planned actions have funding assumptions. Do not replace that review with “total capital divided by the number of grids.” A strategy can have unequal order sizes, different prices or an initial asset allocation that makes the shortcut misleading.
Changing the number of grids, range or order sizes changes the strategy. Those parameters should have a reason beyond making a creation screen accept a smaller balance. The technical minimum also says nothing about whether subscriptions, fees and operating work are economically justified.
Check: identify whether the rejection came from the bot’s configuration requirement or the venue’s individual-order rule. Use the relevant layer’s evidence.
7. Refresh the rules and keep the original error
Use the current rule source for the exact product. An old tutorial, a saved screenshot or a cached configuration can describe a condition that has changed. Record when the rules were observed so you can explain what the bot was using.
Bybit’s current V5 spot instrument schema offers a concrete example: minOrderQty is deprecated and no longer checked; the documentation points to minOrderAmt. It also distinguishes limit-order and market-order maximum quantities. Importing a derivatives field or an older spot rule can therefore produce the wrong local check. [10]
Preserve the original error code and message. Binance’s error guide says price and lot-size failures can concern a lower bound, upper bound or increment. A single filter name is not a complete diagnosis, and receiving one error does not show that every other condition passed. [11]
Finally, review the rules outside this calculator: price bounds, maximum quantities and values, changing price bands, trading status, account permissions and the selected order configuration. A passing arithmetic subset does not establish that the request is accepted, and acceptance would not establish a fill.
Check: retain the pair and product, order type, exact proposed values, rule snapshot, observation time, original error and resolved order status. If a new request is still appropriate after that review, it is a separate action under your own account controls.
Where to find the rules without mixing product schemas
Use this table to locate current documentation, not to preload the checker with presumed live limits. The fields below belong to their named interfaces. A similarly named field elsewhere may have different units, scope or order-type applicability.
| Interface | Useful rule fields | Boundary to preserve |
|---|---|---|
| Binance Spot | Current exchangeInfo symbol metadata and filter list. [4] |
Read the symbol’s actual filters and supported order types; documentation sample values are not current limits. |
| Kraken Spot | REST AssetPairs includes ordermin, costmin and tick_size. WebSocket v2 uses fields including qty_min, cost_min, qty_increment and price_increment. [12][3] |
Keep the REST and v2 field names distinct. Their documentation does not establish a universal cross-venue modulo-origin rule. |
| Coinbase Advanced Trade | Product metadata includes base, quote and price increments, minimum/maximum sizes and trading-state flags. [5] | Read the selected product and order configuration. A list of base and quote fields is not one formula for every payload. |
| Bybit V5 Spot | Spot-specific lotSizeFilter, minOrderAmt, precision fields, priceFilter.tickSize and order-type maxima. [10] |
Use the Spot section. Do not substitute linear/inverse fields or deprecated spot quantity minimums. |
Why a market order needs a different check
The limit price used in this worksheet is a supplied number. A market order has no submitted limit price to reuse in the same calculation. Binance documents separate market applicability flags and price-reference logic, including a reference price or the specified fallback. A current ticker price is not automatically that rule’s evaluation price. [6]
Switching the order type changes the request and its execution behavior. Do not treat “use market instead” as a formatting repair. The same caution applies to changing leverage, switching instruments or increasing the allocation purely to clear a technical minimum.
Keep a small, reusable rejection record
A useful record connects the original intent with the final observed state. Save the exact product and pair, order type, redacted request values, original response, current rules and their observation time. Add the calculation that explains any proposed change. Keep account credentials and credential-bearing URLs out of exported notes.
If any part of an order filled, use the separate cancellation and partial-fill guide to reconcile what remains. If you decide to retire the bot, the bot exit checklist covers orders, holdings, access and ongoing services.
For a strategy that is still being tested, return to the paper-to-live checks before changing its operating scope. Solving one rejected order does not validate the surrounding strategy.
Methodology: what the DN checker calculates
The model is a deterministic arithmetic demonstration. It accepts eight decimal-string inputs: price, quantity, price tick, quantity step, minimum quantity, minimum notional, quote funds and a fixed quote-cost allowance. Labels identify the units; they do not connect to a real market. All live values and any inactive-rule choices remain reader supplied and unverified.
Entered quote requirement = notional + quote allowance
Floored price = floor(price ÷ tick) × tick
Floored quantity = floor(quantity ÷ step) × step
Positive active increments use a zero-origin grid. The minimum is a separate bound; it is not added to the grid origin. Each floor operation uses exact decimal coefficients, and the tool then recalculates the affected conditions. It never rounds upward to repair a shortfall.
The implementation parses ordinary decimal strings into base-ten integer coefficients and scales, using BigInt for arithmetic. It preserves the submitted strings in exports and rejects unsupported input formats rather than silently translating currency symbols, scientific notation or thousands separators. Its input-length limits are software limits, not venue precision rules.
Blank values remain unknown. An explicit zero allowance means zero additional quote cost in that scenario. An inactive rule is visibly excluded; recording it does not disable a venue rule. A missing active increment prevents its floor calculation. Rounding to zero cannot produce a positive order.
The checker reports the active modeled conditions that match, conflict or remain unknown. It omits maximum bounds, price bands, market status, account permissions, actual fee assets and rates, reserved funds, venue-specific internal adjustments and execution behavior. In particular, its fixed quote allowance is not an exchange fee calculator.
JSON and CSV exports contain the inputs, calculated comparison, rule exclusions and source references. They do not constitute a venue receipt. Calculations run locally in the page; the tool does not contact an account, store a trading credential or place a trade.
Frequently asked questions
What is an AI trading bot’s minimum order size?
It depends on the product, pair and order type. A base-quantity minimum, a quote-value minimum and the capital required to create a bot are separate conditions. Check the current rules for the specific setup.
Why can rounding down make an order fail?
Reducing price or quantity reduces their product. An order that previously met a minimum value can fall below it after rounding. Recompute the complete set of affected checks after each change.
Is limiting the number of decimal places enough?
No. A value can have the permitted number of decimal places and still fail an increment. On a zero-origin grid with a 0.05 tick, 2.30 is aligned while 2.33 is not.
Can I use this calculator for market orders or sells?
This version models a spot limit buy using supplied zero-origin increment rules. It does not model market orders, sells, margin or derivatives. Lowering a sell limit would change the minimum acceptable sale price and requires a separate decision.
Does passing the modeled checks guarantee acceptance?
No. The tool does not verify live rules, maximum bounds, dynamic price bands, trading status, permissions, actual fees or account reservations. Acceptance and execution are also separate outcomes. A result describes only the supplied arithmetic conditions.
Should I add funds whenever a small order is rejected?
A rejection is not a reason by itself to increase exposure. More funds will not repair the wrong units or an invalid increment. Identify the failed condition and keep the intended budget and strategy constraints intact.
What if the original order timed out?
Reconcile its status through the trusted venue records before considering another request. A timeout can leave execution unknown. This calculator cannot determine whether the original order traded or prevent a duplicate order.
Primary sources
Product and API scope matter. These sources were checked on 5 November 2026; their sample numbers are not live inputs to the calculator.
- General REST API Information — Binance Spot
- Cost minimum for trading — Kraken
- Instruments — Kraken Spot WebSocket v2
- General — Binance Spot REST API: Exchange information
- Get Product — Coinbase Advanced Trade
- Filters — Binance Spot
- Order management — Coinbase Advanced
- Commission Rates — Binance Spot
- Pionex Trading Bot Finder — minimum-investment FAQ
- Get Instruments Info — Bybit V5
- Error codes for Binance Spot
- Get Tradable Asset Pairs — Kraken Spot REST
About the Author
