SHARKRULE / Learn

Price alert or automated trading rule: what actually authorizes an order?

A price alert tells you that a condition was observed. An active automated trading rule can authorize a configured action within the limits you approved. Neither an alert nor a submitted order proves that a trade filled. To understand what happened, trace the observation, permission, order and fills separately.

SharkRule · Reviewed

First identify what the alert is allowed to do

A notification-only alert sends a message; it leaves the trading decision with you. Coinbase explicitly describes its price alerts as notifications that do not place orders. A rule that can submit orders needs a separate definition of the action and permission to use the connected account. Enabling phone notifications and granting trading access are different permissions.

Some tools can send an alert to another application through a webhook. TradingView documents this as delivery of a message to an external app. That app may have separately authorized trading actions, so inspect the configured destination before calling an alert notification-only. Message delivery still does not prove exchange execution. This explanation does not establish a TradingView connection or an alert-only mode in SharkRule.

Worked example: one condition, two independent paths

All times, prices, quantities and fees here are invented for an unnamed Spot market. They are not settings or a trade size to adopt. Suppose a notification and an already authorized rule both observe a price at or below 100. The rule permits one buy limit order for 0.50 units at a maximum unit price of 100, within a hypothetical total allowance of 50.10 including costs. Assume the exchange filters pass; no real asset is suggested.

The table supplies the complete sequence for this example. The notification is not an input to the rule. The illustrative delays are not measured service speeds.

Hypothetical event record; all times UTC
TimeEvent recordedWhat it establishes
09:59:00User reviews and starts the ruleOne configured action is authorized; nothing has traded
10:00:00Both watchers observe 99.90The stated price condition is true at this observation
10:00:01Rule checks limits and submits order AA request was sent; the outcome still needs confirmation
10:00:02Exchange reports order A as NEWAcceptance, not a completed purchase
10:00:03Order A fills 0.20 at 99.80A partial purchase; 0.30 remains
10:00:05Phone receives the price notificationMessage delivery; it did not cause or confirm the fill
10:00:08Remaining 0.30 fills at 100.00; FILLEDThe original 0.50-unit order is complete

Check quantities and costs against the order, not the message

The two fills belong to one order: 0.20 + 0.30 = 0.50 units. Their purchase value is (0.20 × 99.80) + (0.30 × 100.00) = 19.96 + 30.00 = 49.96 quote-currency units. The weighted average is 49.96 ÷ 0.50 = 99.92, which differs from the observed alert price of 99.90. Two fill reports do not authorize two new orders.

Assume solely for this calculation a 0.1% fee charged in the quote currency, with no fee rounding: 49.96 × 0.001 = 0.04996. Total debit is 50.00996, leaving 0.09004 of the example’s 50.10 allowance. Actual rates, fee currencies, rounding and minimum orders differ. A limit price constrains unit execution price, not the bill including fees; an allowance is not a loss guarantee.

Binance distinguishes NEW, PARTIALLY_FILLED and FILLED in its Spot order statuses. Real reports may arrive without your screen displaying every intermediate state. Use the order identifier, cumulative executed quantity and individual fills; do not infer the outcome from a notification count. If the final 0.30 never fills, only 0.20 was bought until further evidence says otherwise.

Before explicit start, answer these permission questions

A useful rule review connects the condition to a precise authority to act. These are questions to resolve, not a claim that every tool exposes every setting.

  1. Name the exchange, account, Spot pair and price source. Record the condition and evaluation timing so two different markets are not mistaken for the same signal.
  2. Identify the destination: a message to you, an instruction to an application, or an order at the exchange. Check any downstream action attached to an alert.
  3. Specify the buy or sell action, order type, quantity or spending amount, and any price boundary. A threshold alone leaves these decisions unanswered.
  4. Review the per-action and total spending limits, fee treatment, existing commitments and allowed repetitions. A second notification must not silently expand the approved budget.
  5. Verify account and geographic eligibility and the required trading permission; keep withdrawals disabled for a SharkRule exchange connection. Put credentials only in the intended secure connection form, never in an alert message.
  6. Confirm whether this is simulation or real trading, review duration and pause/stop behavior, then decide whether to start. Record the rule version and start time; connecting an account alone is not an explicit start.

An alert arrived but no trade is visible: find the last proven event

Keep a short record: market and observation time; notification destination and delivery time; rule version and start state; order identifier and submission time; exchange status, filled quantity and fees. Mark absent evidence unknown instead of turning it into a zero fill.

Binance warns that a request timeout can leave execution status unknown. Reconcile the original order before a replacement that could duplicate it. For SharkRule’s Binance workflow, an ambiguous order blocks further Binance submissions until reconciled; a new rule or connection must not bypass that check.

Which evidence is missing?
Last proven eventNext check
Price notification onlyWas any order action configured and explicitly started? A notification-only path ends here.
Active rule observed the conditionInspect budget, permissions and the recorded reason for waiting or rejection; do not increase limits merely to force a trade.
Order submitted, outcome unknownInspect the original order’s status and fills. Missing confirmation is not permission to resend.
Accepted or partly filled orderInspect cumulative fills and the remaining order. A request to cancel does not undo fills or prove cancellation.

Common mistakes and limits of the comparison

Do not confuse notification settings with trading authorization, the observed price with an executable quote, or exchange acceptance with completion. Turning off a phone alert does not revoke an independently running rule. Closing a SharkRule browser tab does not stop an active rule either. Inspect the dashboard and any orders already sent.

Automation can act without you reading a message, but it cannot guarantee price, timing, a full fill or a profit. Fees, slippage, non-fills, connection failures and exchange outages remain possible; acquired assets can lose value. This example teaches evidence and permissions, not which asset or strategy to trade. SharkRule is independent software, not a financial or investment adviser, and is not affiliated with or endorsed by the exchanges or TradingView.

Next step: compare connection permission with permission to start

Use the localized Binance setup guide linked in Sources and Related guides to check how connecting an account differs from authorizing a Shark. Compare its permission checklist with the condition, action and budget shown for one available rule. The current guide confirms that connecting checks access and does not place an order; real trading needs a separate review and explicit start. Only proceed if the dashboard offers that connection and rule for your account and location. Reading the guide creates no order.

Frequently asked questions

Can a price alert buy automatically?

A notification-only alert cannot. An alert routed to a separately authorized trading application may initiate an order workflow. Inspect the destination and permissions rather than relying on the word alert.

Does receiving the alert before seeing a fill mean it caused the trade?

No. Delivery times alone do not show causation. The example’s rule and notification monitor independently. Check the saved configuration and order record to establish which event initiated the order.

Does an accepted order mean the whole amount was bought?

No. Acceptance, partial fills and completion are different states. Check the executed quantity and fills for that order, including any unfilled remainder and fees.

If I delete an alert, does that cancel my order?

Do not assume so. An alert, an active automation rule and an exchange order are different objects. Check the relevant controls and final exchange state; completed fills cannot be undone by deleting a message.

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.