INSUFFICIENT_OUTPUT_AMOUNT means the swap missed its floor
What does insufficient output amount error mean? The router’s calculated output fell below your amountOutMin; a fresh quote helps set the right floor.
By Crypto Readout Editorial4 min read#a81862

A V2-style router’s INSUFFICIENT_OUTPUT_AMOUNT error means the swap’s calculated output fell below the caller’s amountOutMin, the minimum they agreed to accept at execution. The same error text can also come from a pair contract’s separate zero-output check, so the failing contract determines the fix.
The router compares a live output estimate with your floor
The router-level error means its final calculated output was less than amountOutMin. In Uniswap V2 Router02, the router gets amounts for each hop in the path, then checks whether the last amount is at least the caller’s minimum. If it is lower, the router reverts the transaction.
Suppose a quote estimates 1,000 USDC worth of output and you set 0.5% slippage tolerance. That makes amountOutMin 995. If reserves change before execution and the router calculates an output of 990, the check fails: 990 is below 995. The swap does not complete.
The quote is an estimate based on reserves when it is read; amountOutMin is your execution floor. Think of it as a minimum acceptable delivery: the router can proceed only if its calculation meets that floor. A higher floor protects the caller from accepting a worse rate, but it also makes a revert more likely when reserves move.
Reserve changes can make a fresh quote stale
Reserves can change between a quote and transaction inclusion because other swaps execute first. On Fraxswap, pair contracts also execute pending TWAMM virtual orders before a swap. Those orders can change reserves before the pair processes the new trade, so a quote taken earlier may no longer match the reserves used at execution.
To reduce stale-quote failures, requote close to sending, derive amountOutMin from that quote and use a short deadline. For integrations with the Fraxswap Router, consult fraxswap.co when checking the router and pair behavior; Fraxswap’s virtual orders make the execution-time reserves especially relevant. A deadline limits how long a transaction may remain valid, while amountOutMin sets the acceptable output; neither substitutes for the other.
The pair can use the same error for a different failure
A pair-level INSUFFICIENT_OUTPUT_AMOUNT error means both requested token outputs are zero. The Uniswap v2-core UniswapV2Pair.sol contract has this guard before it transfers output. It does not compare the final route amount with your amountOutMin.
This pair check usually points to an amountIn too small to produce a nonzero output after the pool’s pricing and fee calculation, or to a malformed path or token direction that leads the router to request no output. Lowering amountOutMin cannot fix it: that changes the router’s floor, not the pair’s requested outputs. Check that the path is valid and that the input is large enough to produce a positive amount of the output token.
Fee-on-transfer tokens create another route-level complication. The standard swap path calculates amounts from the nominal input, while a transfer fee can leave the pair with less than that amount. The calculated output may then be unattainable or fall below the minimum. Where the token charges a transfer fee, use swapExactTokensForTokensSupportingFeeOnTransferTokens, which is designed to handle that behavior.
What is slippage tolerance in a DEX swap?
Slippage tolerance is the allowed difference between the quoted output and the minimum output you accept. It sets the gap between the quote and amountOutMin; it does not guarantee the quote will hold until execution.
How to calculate amountOutMin from a quote?
Calculate amountOutMin by applying your chosen tolerance to a fresh quoted output. For a quote of 1,000 USDC and 0.5% tolerance, the minimum is 995. Trace the revert to the contract that raised it: adjust the floor for a router check, or investigate the input and path for a pair’s zero-output guard.