In this article (13 sections)
- What is a requote in forex?
- How does a forex requote work?
- Instant Execution vs Market Execution
- Requote vs slippage vs order rejection
- Why do requotes happen?
- What does “no requotes” mean?
- What should you do when you receive a requote?
- How to check requotes in MT4 and MT5
- How to evaluate broker execution quality beyond requotes
- Common requote misconceptions
- Worked example: hypothetical GBP/USD requote
- Frequently asked questions
- Key takeaway
A forex requote occurs when an order submitted at a requested price is not accepted at that price and a new executable price is returned for the trader to accept or reject. Requotes are most closely associated with Instant Execution. They are different from slippage, where a trade is filled at a different price, and from rejection, where no trade is executed.
What is a requote in forex?
Under an execution model that uses a requested price, the trader sends an order using the displayed or specified price. If that price cannot be accepted under the broker/server rules when the order is processed, the platform may return another executable price. The trader can then accept or reject that new price, or let the offer expire depending on the implementation.
The important point is that the trade has not yet been filled. A requote describes the returned-price step before execution. Exact behaviour depends on the instrument, broker configuration and execution mode.
How does a forex requote work?
- The platform captures and submits the requested price.
- The request reaches the broker or trade server while the market may continue moving.
- The server checks whether the requested price is acceptable under the execution and deviation rules.
- If it is not acceptable under an Instant Execution workflow, a new price can be returned as a requote.
- The trader accepts or rejects the new price. Accepting the new price does not mean the original price was filled.
Requested-price example
Suppose GBP/USD is shown at 1.27000 when a buy order is sent. If the acceptable price has moved beyond the permitted deviation before the server accepts the request, the original price may be refused and a new price returned. Until the trader accepts and the order is filled, this is a requote, not slippage.
Instant Execution vs Market Execution
MetaTrader documents four execution modes in MT5: Instant, Request, Market and Exchange Execution. The broker defines the execution mode for each symbol. Requotes are specifically associated with the requested-price logic of Instant Execution; Market Execution uses a different price-handling model.
| Execution mode | Price handling | Classic requote? | Other possible outcomes |
|---|---|---|---|
| Instant Execution | Order is sent with a requested/current price. If it is not accepted, new prices can be returned. | Yes | Fill, requote, rejection; deviation tolerance matters. |
| Request Execution | Trader first requests a price, then confirms or rejects execution at that quoted price. | Not the same Instant-Execution requote flow | Confirmation or rejection after requested quote. |
| Market Execution | Broker determines the execution price without another price-negotiation step with the trader. | Not the normal mechanism | Slippage, rejection and fill-policy outcomes can still occur. |
| Exchange Execution | Order is sent to an external trading system/exchange. | Not the Instant-Execution requote model | Exchange/fill-policy outcomes depend on the instrument and venue. |
Platform note: MetaTrader 5 currently documents all four modes; MetaTrader 4 documents Instant, Request and Market Execution. Symbol execution mode is broker-configured.
Requote vs slippage vs order rejection
| Outcome | What the trader sees | Filled? | Core distinction |
|---|---|---|---|
| Requote | A new executable price is offered for acceptance or rejection. | Not yet | New price is presented before execution. |
| Slippage | The final fill differs from the reference or requested price. | Yes | The difference exists in the executed price. |
| Order rejection | The order is declined or not executed. | No | No fill occurred; a replacement price should not be assumed. |
A single trading session can contain all three outcomes across different orders. Do not call every changed price a requote and do not describe every non-fill as slippage.
Why do requotes happen?
| Cause | Mechanism | What the trader may see | What to check |
|---|---|---|---|
| Fast price movement | The requested price becomes stale before server acceptance. | New price offered or order not accepted at the original price. | Event timing, volatility, execution mode and journal messages. |
| Tight maximum deviation | Even modest movement exceeds the allowed tolerance in Instant Execution. | More frequent new-price prompts. | Deviation setting and whether it is appropriate for the tested process. |
| Latency / processing delay | More time passes between observed quote and server processing. | Requested price may no longer be current. | Network quality, timestamps and server messages. |
| Thin or changing liquidity | Available quotes change quickly or become less accessible. | Requested price becomes harder to accept. | Trading time, symbol conditions and broker execution policy. |
Maximum deviation: what the setting changes
In MetaTrader Instant Execution, deviation is the amount of price movement the trader agrees to accept without a new-price prompt. A larger tolerance can make a requote less likely because more movement is accepted automatically. That is a trade-off, not a free improvement: the trader is allowing a wider range of prices to be executed without another confirmation step.
What does “no requotes” mean?
A “no requotes” claim often means the execution workflow does not normally return a changed price for manual acceptance. Market Execution is the clearest example of this different workflow. However, removing the requote step does not guarantee the price shown on screen, and it does not eliminate slippage, rejection, partial-fill or fill-policy risk.
| Claim | Reasonable interpretation | What is not guaranteed |
|---|---|---|
| “No requotes” | The order flow does not normally use a manual new-price acceptance step. | Original displayed price, zero slippage or zero rejection. |
| “Market execution” | The broker determines the available execution price without extra price negotiation. | A fill at a specific price or a fill in every market condition. |
| “Fast execution” | Order processing may be designed for low latency. | Best total cost, no adverse slippage or no failed orders. |
Broker marketing language should be checked against the legal execution policy for the exact account, entity and symbol. A label by itself does not establish execution quality.
What should you do when you receive a requote?
- Compare the returned price with the original requested price and decide whether the trade still fits the original setup and risk plan.
- Do not accept automatically just because the order was already submitted.
- Check the platform journal, order history and timestamps for the execution message.
- Confirm the symbol’s execution mode and, for Instant Execution, the maximum-deviation setting.
- If requotes are frequent, review timing, connection quality, broker documentation and a meaningful sample of execution outcomes rather than chasing price during one fast move.
How to check requotes in MT4 and MT5
MetaTrader documents requotes under Instant Execution. In MT4 and MT5, use order/deal history and the terminal or platform journal to review timestamps and execution messages. MetaTrader also notes that a requote message is written to the journal. Check the symbol execution type because the broker configures it and it can differ across instruments or accounts.
Platform-specific caution
Maximum-deviation controls are relevant to Instant Execution. Do not assume the same setting changes Market Execution in the same way. Interface labels and broker configuration should be checked again when screenshots are produced.
How to evaluate broker execution quality beyond requotes
| Metric | Why it matters | Evidence to review |
|---|---|---|
| Requote frequency | Shows how often the new-price workflow occurs under the observed conditions. | Platform journal/order sample by symbol and execution mode. |
| Positive & negative slippage | Avoids judging execution only by adverse fills. | Matched requested/reference and fill prices. |
| Rejection rate | Shows how often orders are not executed and, where available, why. | Order logs and broker disclosures. |
| Fill speed / latency | Helps identify whether timing may contribute to stale requests. | Consistent timestamp method and server/location context. |
| Spread + commission | Captures direct transaction cost rather than focusing on one execution message. | Account statements and current pricing terms. |
| Execution policy | Explains legal and technical order-handling rules. | Current policy for the exact legal entity/account. |
Do not invent universal “good” or “bad” thresholds. Any comparison should define the date range, account, instrument, order type, trade size, server location and measurement method.
Common requote misconceptions
| Misconception | Correction |
|---|---|
| A requote proves broker manipulation. | A requote describes an execution response, not motive. Review frequency, policy and comparable execution evidence before drawing conclusions. |
| No requotes means no slippage. | False. Market Execution can avoid the classic requote step while fills still differ from the reference price. |
| Market Execution is always better. | Not universally. Execution modes prioritise different trade-offs and broker implementation matters. |
| Increasing deviation fixes execution. | A wider tolerance can reduce new-price prompts, but it also accepts more price movement automatically. |
| Any rejected order is a requote. | False. Rejection means no execution; a requote returns a new price before execution. |
Worked example: hypothetical GBP/USD requote
This example illustrates execution mechanics only. It is not a live market claim or trading recommendation.
| Input / event | Illustrative value | Interpretation |
|---|---|---|
| Requested price | GBP/USD 1.27000 | Trader submits a buy order under Instant Execution. |
| Maximum deviation | 1.0 pip | Illustrative tolerance before a new-price prompt may be returned. |
| Available ask when processed | 1.27025 | The market has moved 0.00025 from the requested price. |
| Difference | 2.5 pips | 0.00025 / 0.00010 = 2.5 pips for a standard non-JPY quote. |
| Instant-Execution outcome | New price such as 1.27025 returned | The requested price is outside the illustrative 1.0-pip tolerance. |
| Trader choice | Accept or reject | Until accepted and filled, this is a requote rather than slippage. |
Under Market Execution, the same order would be sent without a requote negotiation step. It might fill at an available price different from 1.27000, which would create slippage, or encounter another broker/fill-policy outcome. Real execution depends on broker configuration, instrument, liquidity, order size, server timing and market conditions.
Turn Trading Calculations Into Real Trading Decisions
Use your calculated risk levels, position sizing, and technical analysis together with live forex trading signals and market commentary from The Forex Complex.
Frequently asked questions
What is a requote in forex trading?
A requote is a new executable price returned for acceptance or rejection when the original requested price is not accepted under the relevant execution workflow. The trade has not yet been filled.
Why did my forex order get requoted?
The requested price may have moved outside the acceptable range before processing. Fast markets, tight deviation settings, latency and changing liquidity can all contribute, depending on the broker and execution mode.
Is a requote the same as slippage?
No. A requote presents a new price before execution. Slippage is the difference between a reference or requested price and the price at which the trade was actually filled.
Can a broker have no requotes and still have slippage?
Yes. Market Execution can avoid the classic new-price prompt while the final execution price can still differ from the reference price.
How can I reduce requotes?
Review the symbol’s execution mode, Instant-Execution deviation tolerance, connection quality, market conditions and timing. Each adjustment has trade-offs, and none guarantees the requested price.
Are frequent requotes a sign of a bad broker?
Not by themselves. Review the pattern over a meaningful sample alongside slippage, rejection rates, total costs, latency and the broker’s disclosed execution policy.
Key takeaway
A requote is a specific pre-execution event: the original requested price is not accepted and a new executable price is returned. The useful diagnostic question is not simply whether a requote occurred, but which execution mode was used, how deviation was configured, what the order log shows and how the broader execution record compares across fills, rejections, slippage and transaction costs.
