Tradovate Order Rejected: Products Permitted Limit

You send an order on ES or CL, and Tradovate kicks it right back with a rejection that points at the product itself not being permitted on the account. Nothing wrong with your size, your margin, or the session, the contract you're trying to trade simply isn't on the account's allow-list. That list is a Tradovate risk control called Products Permitted, and when it's switched on, only the products you've explicitly added can trade. Everything else gets refused before it ever hits the exchange. The fix is quick: add the contract to the Products Permitted list, or turn the restriction off entirely.

What the "Products Permitted" Rejection Means

This is a risk check, not a market or connectivity problem. Products Permitted is a per-account allow-list inside Tradovate's Risk Settings. When it's enabled, you're telling the account: only trade these specific products. Any order for a contract that isn't on the list gets rejected pre-trade, it never routes to the exchange. So if the list holds only NQ and you fire an ES order, ES bounces. The account is doing exactly what it was configured to do.

That's the key difference from the other rejections that look similar on the surface. A “maximum order quantity” bounce is about how many contracts you sent. An “insufficient margin” bounce is about money. A Products Permitted bounce is about which instrument you tried to trade at all. Once you know it's the product filter, the fix is narrow and fast, you're either editing one list or flipping one switch.

One more thing worth nailing down early: this filter works at the product level. The list is built from products such as NQ, ES, or CL, not from a single expiration like ESU5. Add a product and its active contract is covered. If your rejection is instead about a contract that's expiring or a continuous symbol, that's a rollover problem, not a Products Permitted problem, and it needs a different fix.

Top Causes of the "Products Permitted" Rejection

1. The Allow-List Is On and Your Symbol Isn't on It (Most Common)

The everyday case: at some point Products Permitted got enabled on the account with a short list of products, and now you're trying to trade something outside it. Maybe you set it up months ago to keep yourself disciplined on one instrument, or a saved risk template carried it over. The contract you want is perfectly tradable, it's just not on your account's approved list yet.

2. You Restricted the Account to a Single Product and Forgot

Traders who want to force focus sometimes permit only their main instrument, say, NQ, so a moment of boredom can't turn into a random CL scalp. That's a smart guardrail right up until the day you legitimately want to trade a second product and forget the gate is there. The rejection is your own past setting talking.

3. A Prop Firm Limited the Account to Specific Products

Evaluation and funded accounts frequently ship with a fixed set of tradable products baked into the firm's risk profile. Some programs allow the full futures board; others restrict you to, for example, equity index futures and exclude energies, metals, or crypto. Which products are allowed varies by firm and by account type, so check your firm's current rules rather than assuming. On these accounts the permitted list is the firm's, not yours.

4. Micro vs. Mini, Close Symbols, Separate Products

Here's the trap that catches people who think they've already added their instrument. In the permitted-products picker, a micro and its mini are typically separate entries. Permit NQ and your MNQ order can still be rejected, because MNQ is its own product. If you trade both sizes, both need to be on the list. Confirm the exact entries on your own screen, since the way products are grouped can shift between platform versions.

5. An Automated Strategy Sending a Product Outside the Set

If the rejections come from a bot, a TradingView alert, or a copied strategy, the culprit is often a symbol mismatch: the strategy is firing a product your account was never set up to trade. One alert on the wrong instrument and the permitted-products filter refuses it every time it triggers, which can look like a broken automation when it's really a one-line list issue.

How to Fix the "Products Permitted" Rejection: Step-by-Step

Fix A: Add the Product to the Permitted List (Accounts You Control)

If the account is yours to configure, a personal live or demo account rather than a locked prop account, add the contract to the allow-list:

Fix B: Turn the Restriction Off Entirely

If you don't want a product allow-list at all, you'd rather trade the whole board freely, just disable the filter:

Heads up: Tradovate's risk panel lives under Application Settings › Accounts › Risk Settings, and the control you want is Products Permitted. Exact button placement, the label wording, and how the add-product search behaves can vary a little by platform version and by whether the account is prop-managed, so confirm against your own screen before you change anything.

Fix C: Prop / Evaluation Accounts (You Can't Self-Edit)

On an evaluation or funded prop account, the permitted-products list belongs to the firm, and the controls in Tradovate will be greyed out or ignored. To trade a product that's being rejected:

Fix D: Watch the Lock State Before You Change Anything

Tradovate can lock risk settings once an account hits a limit, and if that lock is active, your edits won't stick until the next trading session begins (roughly the 5:00–6:00 PM ET reset window). There's a bigger warning too: a manually locked risk profile is deliberately hard to reverse, and Tradovate support can't simply unlock it for you. So before you lock a narrow permitted-products list, be sure it's the list you actually want to live with.

Troubleshooting Table

Prevent This With PickMyTrade

If the rejection is hitting automated orders, a TradingView alert, a bot, or a copied strategy firing a product your account won't accept, the cleanest fix is to make sure the right symbol goes out in the first place. PickMyTrade sits between your alert and Tradovate and shapes each order before it routes:

• Symbol mapping, translate a strategy's ticker to the exact Tradovate product symbol, so an alert lands on the instrument your account is actually set up to trade.
• Symbol validation, check each incoming alert's contract before it's sent, so a stray or wrong-product signal doesn't get blasted into a permitted-products wall over and over.
• Fixed sizing & risk filters, keep quantity and account state inside the rules you're cleared for, so the same alert doesn't trip a size cap right after you clear the product one.
• Multi-account routing, send one alert to several Tradovate accounts, each with its own product setup, instead of firing an identical symbol everywhere and eating rejections on the ones that don't allow it.

The result: the order that a permitted-products filter would have bounced goes out on the correct, allowed instrument and routes cleanly, so your automation keeps working instead of silently rejecting on every trigger.