Use SushiSwap to swap treasury tokens on the network where they are needed, then supply liquidity only when expected trading fees justify holding both assets. For payouts and regular transfers, the operating decision is the amount the recipient must receive after the trade, not simply the amount sent into it.

What happens when a treasury swaps?

A treasury swap takes tokens from an onchain liquidity pool and changes the pool’s price as its balances change. In a constant product pool, the reserves follow x × y = k: taking more of the output asset makes each additional unit cost more. Think of two inventory bins joined by a price curve; a large withdrawal from one bin moves the price before the bin is empty.

That matters when you turn operating funds into payout inventory. At the execution point, SushiSwap lets the team swap tokens or supply a pool on supported networks, so the trade and the decision to earn fees can sit in the same treasury workflow. The SushiSwap DEX still settles each swap against available liquidity; a displayed rate for a small trade says little about the output from a larger one.

A router may split a trade or pass through more than one pool. Compare the final token amount and gas cost for the complete route, since an extra hop adds another pool fee and another place for price impact. Ethereum and Avalanche are separate settlement domains: holding an asset on one does not put it in a pool on the other. A transfer between networks requires a separate cross-chain mechanism and reconciliation.

How do you execute a treasury swap?

Execute the swap by fixing the settlement network and token contracts, checking the amount out, limiting adverse movement, and reconciling the confirmed transfer. Keep the payout obligation in the destination token as the reference amount throughout these steps.

1. Confirm the network and token contracts. Match the source balance, destination token contract and recipient’s required network against the payment instruction. Tickers are insufficient: tokens with the same symbol can have different contracts or exist on several networks. Reserve the network’s native asset for gas so the wallet can complete the swap and any subsequent transfer.
2. Size the trade against the quote. Compare the SushiSwap route’s expected output with the amount required and with an external reference price. For example, a direct swap of 1,000 units into a pool holding 100,000 units of each asset returns about 987.16 output units at a 0.3% pool fee, before gas. Roughly 1.28% of the apparent one-for-one value is gone through fee and price impact; splitting the order over time may help if liquidity replenishes, but separate transactions add gas and execution risk.
3. Set the minimum amount received. A slippage tolerance of, say, 0.1% to 0.5% is a starting range for a liquid pair, while volatile or thin pairs may need a different limit. This protects against price movement between signing and inclusion; it does not undo the price impact already built into the quote. If the minimum output would leave a payout short, reduce the trade size or fund the difference before signing.
4. Approve the intended spend. Give the swap contract a bounded token allowance under the team’s signing policy, then verify the spender address in the transaction request. An unlimited allowance saves later approval transactions but leaves a larger amount available to that contract. For a multisignature wallet, allow for the time between proposal and execution: an old quote can be stale even when every signer approved it correctly.
5. Submit and reconcile the trade. Check the transaction receipt for the actual output, network fee and token movements, then record them against the treasury instruction. A transaction can revert when the minimum output is missed; gas is still spent, and no payout inventory was acquired. If the swap succeeds, make the recipient transfer as its own controlled action and reconcile that transaction separately.

When should treasury supply liquidity?

Supply liquidity when expected fee income exceeds inventory risk, gas and the work of managing the position. A pool needs both assets, so depositing payout inventory also commits treasury to holding its paired asset. At sushiswap.co, that decision applies to the same assets a team might otherwise keep available for swaps or transfers.

SushiSwap pools can use different designs. A v2-style position spans the full price range and its fee share follows the treasury’s share of pool liquidity; a concentrated position puts capital inside a chosen price range and earns fees only while trading occurs there. Where available, concentrated pool fee tiers commonly include 0.01%, 0.05%, 0.3% and 1%. The higher fee per trade is useful only if enough volume reaches that pool.

Before depositing, compare three concrete inputs:

• Expected trading volume multiplied by the pool fee and the position’s active share.
• The value of the assets after price changes, compared with simply holding the original amounts.
• Gas, range resets and the time needed to restore funds for scheduled payouts.

The second calculation is often decisive. If one asset doubles against the other, a full-range constant product position ends about 5.7% below the value of holding the original pair, before earned fees. A narrow concentrated position may earn more while price stays inside its range, but can end up almost entirely in one asset and stop earning fees after price leaves it.