When does opening a new fulfillment node create sales tax nexus?
The most common pattern: a brand plans a new fulfillment center around throughput and shipping speed and forgets that the first pallet creates a registration obligation in that state regardless of whether a single order ever ships from it. The launch project tracker covers receiving, racking, WMS integration, and SKU allocation. The state DOR registration sits in finance, often outside the launch project entirely, and the launch ships on the operations timeline while registration ships on the finance calendar. The gap between the two is the exposure.
The statutory basis is consistent across every state with a sales tax. Storage of tangible personal property in the state makes the brand “engaged in business” there, which creates the registration obligation under the state’s remote-seller and physical-presence provisions:
- California. “Every retailer engaged in business in this state… [including any retailer that] maintains, occupies, or uses… a warehouse or storage place.” (Cal. Rev. & Tax. Code §6203)
- Texas. “A retailer is engaged in business in this state if the retailer… maintains, occupies, or uses… an office, place of distribution, sales or sample room or place, warehouse, storage place, or any other place of business.” (Tex. Tax Code §151.107(a)(3))
- Pennsylvania. Maintaining a place of business in the Commonwealth, including a warehouse or any place where tangible personal property is stored, makes the seller a “vendor” for sales tax purposes. (72 P.S. §7201(b))
- New York. Maintaining “a place of business in the state,” including through inventory storage, makes the seller a “vendor” for sales tax purposes. (NY Tax Law §1101(b)(8))
- Florida. “A dealer maintaining a place of business in this state” covers warehousing of tangible personal property. (Fla. Stat. §212.06)
- Washington. “Engaging in business in Washington” includes maintaining “a stock of goods.” (RCW 82.08.052)
The provisions do not distinguish between owned, leased, and contracted storage. An owned warehouse, a new 3PL node at ShipBob or ShipMonk, and a forward-staging position at a Flexport partner facility all create the same trigger. They differ in contract mechanics and discovery dynamics, not in nexus result.
The economic-vs-physical-nexus distinction matters for sequencing. South Dakota v. Wayfair, Inc., 138 S. Ct. 2080 (2018) added economic nexus on top of the physical-presence trigger; it did not replace physical nexus. Every sales tax state continues to assert both. A brand opening its first West Coast node in California may sit well below California’s $500,000 economic threshold (Cal. Rev. & Tax. Code §6203) and still have full California physical nexus from the moment the first inventory lands. The economic threshold becomes irrelevant once physical presence has been established. See Economic nexus vs. physical nexus, explained for ecommerce operators for the foundational treatment.
Registration timing after inventory lands, state by state
State registration deadlines for physical nexus split into two patterns: before-next-taxable-transaction states, which require the brand to register before processing another order from a state where presence has been established, and fixed-window states, which provide a specific grace period after a triggering event.
The default across most states is the before-next-taxable-transaction pattern. The state’s enforcement posture is that the brand must register and configure collection before any order is processed from the new physical presence. A brand opening a node on March 15 and processing the first order from that node on March 18 should have completed registration by March 18, not on a calendar that runs through the next month-end close.
| State | Registration timing | Statute / source |
|---|---|---|
| California | Before next taxable transaction (Cal. Rev. & Tax. Code §6203). | CDTFA Wayfair guidance |
| Texas | Permit and collection by the first day of the second month after the threshold month for economic nexus; before next taxable transaction for physical nexus (Tex. Tax Code §151.107; 34 TAC §3.286). | Comptroller remote-seller guidance |
| Pennsylvania | Before next taxable transaction (72 P.S. §7201(b); Act 13 of 2019). | PA DOR online-retailer guidance |
| New York | Before next taxable transaction (NY Tax Law §1101(b)(8)). | NY DTF nexus publication |
| Florida | Before next taxable transaction (Fla. Stat. §212.06). | FL DOR remote-seller TIP |
| Washington | Before next taxable transaction (RCW 82.08.052; WAC 458-20-193). | WA DOR remote-seller guidance |
| Illinois | Before next taxable transaction (35 ILCS 105; 35 ILCS 120). | IL DOR FY 2026-12 Bulletin |
| Georgia | Before next taxable transaction (O.C.G.A. §48-8-2(8)(M.1)). | GA DOR out-of-state seller guidance |
Two state-specific patterns are worth pulling out because they recur in mid-market remediation. First, Texas’s second-month rule for economic nexus is sometimes incorrectly read as also governing physical nexus. It does not. The fourth-month grace applies only to the dollar-threshold trigger; physical nexus through inventory storage continues to require registration before the next taxable transaction. Second, California’s enforcement posture is the most aggressive on lookback when registration follows inventory placement. A brand that registers in California three months after the first pallet lands faces three months of unregistered exposure that the CDTFA can assess, plus penalties under Cal. Rev. & Tax. Code §6591. The bigger the customer’s downside risk, the bigger the upfront caveat: in California, Washington, and Texas, late registration after physical presence has been established produces real exposure, and the operating posture is registration before placement, not after.
Registration is the recurring cost of node expansion. TaxCloud’s native Shopify, Shopify Plus, BigCommerce, and QuickBooks Online integrations route the new-state registration through one consolidated process, and Certified Service Provider filing infrastructure absorbs the new state into the filing calendar without the finance team standing up a separate state-by-state workflow. The brand owns the operational decision about where to open the node; the registration and filing chain runs through one platform rather than tracking parallel processes by state.
The pre-move checklist for opening a new fulfillment node
The brands that handle node expansion cleanly run a pre-move checklist that puts registration upstream of inventory placement. The brands that absorb avoidable exposure run the same checklist backwards, registering after the first state letter. The work is identical; the sequencing is the only variable.
The defensible sequence is six steps, ordered by when each action needs to land relative to the inventory arrival date.
- 30 to 45 days before inventory arrival: confirm the destination state’s registration timing and lookback rules. Pull the state’s remote-seller and “engaged in business” guidance from the DOR site. Confirm whether the state requires registration before the next taxable transaction (the default) or operates a fixed-window grace period (Texas’s second-month rule for economic nexus). Confirm whether the state extends lookback when registration follows physical presence (California, Washington, and Texas have the most aggressive posture). If the brand is already approaching the state’s economic threshold, the combined trigger date matters for the workpaper.
- 30 days before inventory arrival: initiate registration in the destination state. State registration windows vary from same-day (most states with online portals) to two to four weeks (states requiring paper applications or business-license verification). Initiate the registration so the seller permit is in hand before the first pallet lands. Configure collection in each active sales channel (Shopify, Shopify Plus, BigCommerce, Amazon, Walmart, TikTok Shop) for the new state at the same time the registration confirms.
- The week the node goes live: update the nexus map. Add the state to the brand’s monitored-state list, the filing calendar, and the audit documentation trail. The map should reflect the trigger date (the inventory arrival date), the registration date, and the date collection was configured in each active channel. The gap between trigger date and registration date is what an auditor scrutinizes; the gap between registration date and channel-configuration date is what creates inadvertent uncollected liability after registration is complete.
- The week the node goes live: update the 3PL or warehouse contract. If the new node sits inside a 3PL relationship that grants the provider discretion over future inventory placement, add a 30-day nexus-disclosure clause requiring the 3PL to notify the brand before placing inventory in any state where the brand is not currently registered. Pair this with a quarterly inventory-state report deliverable. Does 3PL warehouse inventory create sales tax nexus in 2026? covers the full contract clause set. The pre-move conversation is the right moment to negotiate this; once the relationship is operational, the negotiation leverage drops.
- 30 days after node goes live: reconcile the first-month transaction data. Pull the first month of orders shipped from the new node and confirm tax was collected on every taxable transaction in the destination state. Reconcile against the Shopify or BigCommerce tax report, the marketplace facilitator reports for any active channels, and the 3PL’s per-state shipment report. Any uncollected transactions during the registration-to-channel-configuration gap are unregistered exposure that surfaces at audit; the workpaper should document the period, the amount, and the remediation plan.
- Quarterly thereafter: refresh the nexus map against the 3PL’s inventory-state report. Active 3PL networks redistribute inventory based on demand patterns; a January node map at 5 states can be a June node map at 9 states. The quarterly cadence catches new-state placements before they accumulate to a state letter. See How should a mid-market ecommerce brand monitor nexus exposure across 50 states? for the full operating cadence by revenue band.
A practical note on step 2. The thirty-day window before inventory arrival is the right target, but several states allow same-week registration through online portals. Brands operating on a faster expansion cadence (a new node every quarter, or a delivery-promise launch that requires four nodes in sixty days) can compress the cycle by maintaining a standing list of confirmed-registration-timing documentation per state, so the pre-move research is already complete the next time a node opens in a known state. This is the monitoring layer where the nexus map functions as a forward-looking planning tool, not a backward-looking audit defense. TaxCloud’s monitoring view tracks the physical footprint state by state, surfacing the registration status of each state on the candidate-node list before the operations decision is final.
How same-day and next-day delivery commitments silently set the nexus footprint
The delivery-promise drives the footprint backwards. A brand committing to next-day delivery in 20 metros pre-positions inventory in 6 to 10 states, and each placement is a nexus event. The operational decision (delivery speed) silently sets the compliance footprint, and the decision rarely runs through the finance or compliance team before the commitment ships externally.
The math is straightforward once the decision is named. Two-day delivery in the lower 48 generally requires 4 to 6 strategically positioned fulfillment centers; carrier ground-shipping time-in-transit zones map to those positions cleanly. Next-day delivery in the top 20 metros typically requires 6 to 10 centers, depending on which metros the brand prioritizes and which 3PL network the brand contracts with. Each center is physical nexus in its state, regardless of whether sales volume in that state ever crosses the relevant economic threshold.
A worked example. A Shopify Plus brand at $40M ARR launching a next-day delivery promise to the top 20 metros may need inventory in California, Texas, Illinois, Pennsylvania, New Jersey, Georgia, Florida, Nevada, Arizona, and Washington to hit the service-level commitment. That is ten states of new physical nexus, attached to the delivery promise, with no necessary relationship to the brand’s existing sales-volume footprint in those states. A brand with $80,000 in Pennsylvania revenue and an Arizona node has full Pennsylvania physical nexus (from any pre-existing presence) and full Arizona physical nexus (from the new node), regardless of whether Arizona sales ever cross $100,000.
The decision shape is unfamiliar because it crosses team boundaries that typically do not coordinate on this question. The growth team owns the delivery promise as a marketing and conversion lever. The operations team owns the network execution. The finance team owns the nexus map and the registration calendar. The pattern is that growth ships the delivery commitment in Q1, operations executes the network expansion in Q2, and finance learns about the resulting nexus expansion at the Q3 footprint review, three quarters into accumulated unregistered exposure.
The cleaner sequence routes the delivery promise through the nexus map before the commitment ships. For each target metro, the question is whether the brand is already registered in the state where the fulfillment center for that metro will sit. If yes, no nexus impact, only operational change. If no, the registration timeline becomes part of the delivery-promise launch plan, sitting upstream of marketing announcement and customer-facing service-level commitment.
A brand registered in 25 states can layer in next-day delivery to most major metros with little new nexus consequence. A brand registered in 8 states cannot. The delivery promise constrains the operating model differently at each scale, and the constraint needs to land in the planning conversation, not in the surprise-letter conversation nine months later. The economics also shift at scale. A brand at $80M ARR running next-day delivery on a 9-node 3PL network has compliance infrastructure as a fixed input; the delivery promise scales without proportional compliance cost. A brand at $20M ARR adding the same delivery promise picks up nine new state registrations, nine new filing calendars, and nine new audit exposure surfaces, on top of the inventory and 3PL costs.
The operating model: registration apparatus that scales with node expansion
A $20M to $80M Shopify or Shopify Plus brand running active node expansion needs three things in steady state: a pre-move registration sequence, a current nexus map that updates as nodes come online, and the registration apparatus and filing chain that absorbs the new states without parallel state-by-state finance work.
The pre-move sequence is the operational discipline covered in the H2-3 checklist. Run it the same way every time, regardless of whether the new node is an owned warehouse, a new 3PL contract, or an additional placement inside an existing 3PL network. Storage is the trigger; the contracting structure does not change the analysis.
The current nexus map is the planning tool, not the audit-defense artifact. The map should surface the registration status of each state on the candidate-node list before the operations decision is final, so the finance and compliance team is a participant in the node-selection conversation, not a downstream recipient of decisions already made. The quarterly footprint reconciliation against the 3PL’s inventory-state report catches placements that landed outside the planned sequence, including any silent relocations the 3PL made under contractual discretion. See How should a mid-market ecommerce brand monitor nexus exposure across 50 states? for the cadence model.
The registration apparatus and filing chain are the infrastructure that determines whether node expansion compounds compliance work or absorbs into a stable footprint. For a brand registered in 25 states with quarterly node expansion, the monthly filing volume across those states is the recurring operational cost; adding state 26 should not double the work. TaxCloud is built for that operating model: calculation across 13,000+ jurisdictions through one API with native Shopify, Shopify Plus, BigCommerce, and QuickBooks Online integration, the registration apparatus that absorbs new-state registrations as nodes come online, the monitoring view that tracks the physical footprint quarter to quarter, consolidated SST filing across the 24 member states (23 full members plus Tennessee as an associate member), and the audit documentation trail tying each registration to the inventory-arrival date that triggered it.