Registering proactively vs. waiting for a nexus event: which strategy is less risky?

There’s a genuine strategic question here: register in states ahead of your likely nexus events, or wait until you’ve actually crossed a threshold or created physical presence and then register? Both approaches have real trade-offs. The right answer depends on your growth trajectory, channel mix, and confidence in your threshold-monitoring.

The case for registering proactively

You avoid the compliance gap problem. If you register before you hit nexus, you’re already configured and collecting by the time you’re obligated to. There’s no period where you owed tax and weren’t collecting it, and no retroactive exposure to manage.

You eliminate audit risk for those states. Once registered and collecting, your compliance record starts clean from day one. There’s no window where inventory or sales were in a state and your registration wasn’t.

It’s cleaner as you scale. Sellers who add channels, expand to FBA, or start doing wholesale often find that nexus events in multiple states happen simultaneously. Getting ahead of it prevents the scramble.

The case for waiting

Registration creates filing obligations. The moment you have a permit in a state, you have to file, even if you have zero sales in a given period. Most states require zero returns. If you register in 15 states preemptively and then sales don’t materialize in 8 of them for 6 months, you’re filing 8 zero returns every period.

There’s an opportunity cost. For small sellers, registration fees add up. More importantly, monitoring and filing across unnecessary states consumes time and money that could be deployed elsewhere.

Nexus thresholds can be managed. If you’re selling $30K into a state and the threshold is $100K, you have runway. Registering now doesn’t help your customer; it just creates overhead.

The risk of waiting: the threshold timing problem

Waiting only works if you catch the nexus event the moment it happens. In practice, most sellers catch it late, sometimes months late, sometimes years late.

The specific scenarios where waiting fails:

Amazon FBA inventory: Amazon moves your inventory between fulfillment centers without notice. Your nexus in a state begins the day your inventory arrives, not the day you check the Inventory Ledger report. Sellers who wait to monitor find out after the fact that they’ve had nexus in Nevada or Indiana for 18 months.

Economic nexus thresholds: If your sales are growing, you can cross the $100K threshold in a state mid-month and not realize it for weeks. The obligation to collect started the day you crossed, and every sale after that but before you registered is technically uncollected tax.

Combined channels: Marketplace sales (Amazon, Etsy) often count toward your threshold in most states. A seller tracking only Shopify revenue thinks they’re at $60K in Ohio; their combined total (Shopify + Amazon) is $115K. They’ve had nexus for months.

The risk of registering proactively: filing burden

Over-registration is a real thing. A seller who registers in 30 states because they “might” have nexus there is creating 30 state permit relationships, 30 compliance calendars, and potentially 30 zero-return obligations per period. For a seller filing quarterly in all 30 states, that’s 120 returns per year, many of them zero.

The filing burden of over-registration can create its own compliance problems: missed zero returns generate failure-to-file notices even when you owe nothing.

The practical framework

Most tax advisors recommend something between pure proactive and pure reactive:

Register immediately when you have confirmed nexus — FBA inventory in a state, a remote employee starting, economic threshold crossed. No delay.

Monitor actively for states where you’re approaching nexus, in the $50K–$80K range on a $100K threshold, or about to hire someone remotely. Set a calendar alert or use a platform with threshold monitoring.

Don’t register speculatively in states where you have no reasonable near-term nexus path. The zero-return burden isn’t worth it.

Use a VDA if you discover you should have registered earlier. Don’t register directly to “fix” a backlog, that creates retroactive exposure without the lookback protection a VDA provides.

The SST exception to the burden calculation

For sellers who qualify as remote sellers and use a CSP platform, SST member states have a different calculus. Registration in SST states is often simpler (handled through the SST Central Registration system), filing is covered by the program, and the compliance overhead is lower than for non-SST states. Sellers on a CSP platform may find proactive registration in SST states more attractive precisely because the ongoing burden is lower.

The bottom line

Waiting isn’t inherently wrong, it’s a reasonable strategy if you have robust, real-time threshold monitoring across all channels and you’re confident you’ll catch nexus events the moment they happen. Most sellers don’t have that confidence because they’re tracking one channel and ignoring the others.

Proactive registration in states where nexus is clearly coming (your FBA footprint, states where you’re at 70%+ of threshold) is almost always worth the filing overhead. Speculative registration in states with no near-term nexus path is usually not.

See: VDA vs. registering retroactively without a VDA: which is safer? if you’ve already discovered a compliance gap.