Deceptive Policy Guidance: Retail-Routing Reclassification

I’d like to share my experience developing a trading algorithm on Alpaca. I’m an amateur solo developer, trading my own cash and retirement funds in personal accounts. I’m certainly not a “professional trader” in the literal sense.

My strategy relied on preferential routing accorded to retail flow. I invested hundreds of hours developing and optimizing my code for Alpaca’s particular execution patterns. In mid-September, I was abruptly notified that my trading activity had been classified as “non-retail.” My accounts would be forced onto a different routing arrangement, initially with a brokerage commission of $0.004 per executed share.

That fundamentally changed the economics of what I had built. Alpaca explained that its concern was the volume and pattern of entering and canceling orders. My fill rates were substantially higher than the below-1% example in its published guidance (generally between 20-30% fill rate), and I operated well within the published API rate limits. I recognize that Alpaca never stated that staying within the published limits would guarantee retail eligibility, but this simply reinforces my point. How are users meant to conform to boundaries that Alpaca refuses to define precisely? Suffice it to say, I took great care to understand and follow Alpaca’s published guidance, and this did not prevent my reclassification.

I repeatedly offered to reduce or modify my activity. I asked what changes would be necessary to remain eligible for retail routing, and whether a revised profile could be evaluated under agreed limits. I expected that this would be a reasonable possibility because Alpaca had previously explained on this forum that affected customers would receive “an option to change their order characteristics back to ‘retail’” or negotiate commissions. Instead, I received this response:

“We are unable to maintain or reinstate retail routing for these accounts, and the non-retail designation will remain in effect.”

I was not offered conditions for reassessment or an opportunity to work toward an acceptable profile. I have since moved my funds to other brokerages, although I would have preferred to find a workable arrangement.

I’m sharing this because other developers may be weighing a similar investment of time and energy developing trading algorithms for use on Alpaca. In my experience, operating within the API limits and being willing to adapt did not produce a path to reassessment. The opportunity described in the earlier forum statement was not offered to me.

Perhaps their policy has changed, or there are exceptions that haven’t been explained. I would have welcomed clarification from Alpaca, or a conversation with someone able to review a concrete proposal for a reduced trading profile. Alas, despite repeated offers to modify my activity, Alpaca was unwilling to discuss conditions for restoring retail routing.

Has anyone here successfully navigated the reclassification process? I expect that there won’t be any change in Alpaca’s position (they made it clear they were not open to negotiation). However, I’ll update this thread if there is a substantive response or resolution.

@danielpi Thank you for sharing your experience here in the forums. It highlights issues that other traders should be aware of. Importantly, a non-retail designation is based on order characteristics, not on whether the account holder is a “professional”. Yours was a unique case involving trading across multiple accounts, placing a very large number of orders, and not a typical order profile.

Alpaca reviews activity against retail order-flow criteria and execution-partner requirements, which may include order patterns that go beyond published criteria. Determinations are made on an account basis and, once an account is designated non-retail, that designation may remain in place.

We’re not able to discuss individual account reviews on the forum — if you’d like to continue the conversation, please reply to your existing support thread (or open a new one), and the support team can follow up privately.

@Dan_Whitnable_Alpaca Thank you for your thoughtful reply. The concern I’m raising is not simply that my trading pattern was deemed “non-retail.” What I regard as deceptive is the discrepancy between Alpaca’s earlier public statement describing an opportunity to change order characteristics back to retail and the categorical response I received when I repeatedly requested that opportunity.

You say that the trade desk’s objection to my algorithm was my volume and trading across multiple accounts. I would have happily throttled my volume or ceased trading on my IRA accounts if that would have allowed me to retain the retail designation. Those are substantial changes that would have directly addressed the concerns you identified. The point is that I was never offered an opportunity to discuss conditions for continued retail eligibility. I was simply informed that the designation would remain in effect and that continued trading would incur fees. To quote from the support exchange verbatim, I was told flatly:

retail eligibility cannot be reconsidered for these accounts, nor can we offer a pathway or monitored period to reinstate retail access. This decision is final and non-negotiable.

I’ll follow up on the existing support thread as you suggest, and update this thread with the outcome.