Does CoinRoutes Have Pre-Trade Risk Controls?
CoinRoutes
Yes. CoinRoutes provides pre-trade risk controls that check and constrain orders before they reach an exchange — including hard and soft order-size limits, gross and net exposure tracking, reduce-only mode, venue and instrument whitelisting/blacklisting, and per-venue quantity caps — and they can be configured at the admin level so they apply automatically rather than depending on per-order input. For institutions, that pre-trade layer is the difference between a fat-finger or a runaway strategy being stopped before it executes versus discovered after.
Why pre-trade controls matter
Risk controls fall into two camps: pre-trade (checks applied before an order is sent) and post-trade (monitoring and reconciliation after the fact). Post-trade is essential, but it can only tell you what already happened. Pre-trade controls are what actually prevent bad orders — a mis-keyed size, an order on a forbidden instrument, a position increase that should have been reduce-only — from ever reaching the venue.
What CoinRoutes checks before an order goes out
Order-size limits (hard and soft)
Limits can be set at the strategy (global) level or per-symbol. Hard limits reject an oversized order outright; soft limits raise a warning that the trader must confirm before proceeding. This is the front-line defense against fat-finger errors — a desk can cap order size on its key currencies so an extra zero never makes it to the exchange.
Gross and net exposure tracking
The platform tracks consolidated exposure across connected venues and strategies, so limits can be enforced against gross and net position — not just single-order size. This keeps the aggregate book inside its mandate, not only individual tickets.
Reduce-only
A reduce-only flag ensures an order can only close existing exposure, never open new positions. It is a critical guardrail for unwind and de-risking workflows where accidentally adding to a position would be exactly the wrong outcome.
Venue and instrument restrictions
Compliance rules let you whitelist or blacklist specific trading pairs, set notional limits per venue, and restrict instrument types. Regulated entities use this to enforce position limits and keep traders inside an approved universe of venues and instruments.
Per-venue quantity caps
Exchange-level maximum quantity controls prevent any single venue from receiving an outsized share of a parent order — useful for managing venue-level counterparty risk and staying inside exchange rate limits.
Permissions and access
User permissions can be scoped (view-only, trading, admin) and traders can be restricted to specific account groups or strategies, so access itself is a control.
Pre-trade vs. post-trade at a glance
| Control type | Examples | What it does |
|---|---|---|
| Pre-trade | Order-size limits, reduce-only, venue/instrument whitelist, per-venue caps, exposure limits | Stops non-compliant orders before they reach the exchange |
| Post-trade | Exposure/holdings monitoring, reconciliation, reject monitoring, alerts | Surfaces what happened and flags breaks after execution |
Both matter; the pre-trade layer is what prevents incidents rather than reporting them.
Configured once, applied automatically
A key institutional requirement is that controls don't rely on a trader remembering to set them per order. CoinRoutes supports configuring risk controls at the admin level so they apply automatically across the relevant strategies and traders — the limits, restrictions, and permissions are enforced by the system regardless of how an individual order is entered, whether via the UI or the API. Real-time reject monitoring and in-app notifications then surface any order that trips a control.
This article describes platform capabilities at a general level; specific control names, scopes, and behaviors evolve with the product. Confirm the exact configuration available for your account during onboarding.
Frequently asked questions
Does CoinRoutes have pre-trade risk controls? Yes. It applies checks before orders reach an exchange — order-size limits (hard and soft), gross/net exposure limits, reduce-only, venue and instrument whitelisting/blacklisting, and per-venue quantity caps — and these can be set at the admin level.
What's the difference between a hard and a soft order-size limit? A hard limit rejects an oversized order outright; a soft limit warns the trader and requires confirmation before the order proceeds. Both guard against fat-finger errors.
What does reduce-only do? Reduce-only ensures an order can only close existing exposure, never open or increase a position — a key guardrail for unwind and de-risking workflows.
Can risk controls be enforced without per-order input? Yes. Controls can be configured at the admin level so they apply automatically across strategies and traders, enforced whether orders are entered via the UI or the API.
Want pre-trade controls enforced across your desk automatically? Book a demo to see how they're configured.
Related reading: What Is Portfolio and Risk Management Software for Digital Assets? · Risk Controls vs Clarity (PMS): What You Need for What · How to Evaluate a Crypto EMS · What Is a Crypto Execution Management System (EMS)?
