Reference · built on requestOperator by FibricFinance & billing

Nexus Threshold

Sales and order counts by state tracked against economic nexus thresholds, with registration and collection proposed when one is crossed.

Request accessPricing ↗

About

States set economic nexus thresholds as a sales amount, an order count, or both, measured over a period each state defines. This operator keeps the running count. It reads orders from Shopify and BigCommerce with the shipping address state and the order total, resolves addresses with no state code through the Census Geocoder, and sums by state over the window each state uses. It reads where you already collect: nexus declared in Avalara AvaTax and the nexus regions on your TaxJar account.

When a state's running total approaches or crosses the threshold you have entered for it, it proposes the next step: register, then declare nexus in the tax engine so collection starts. A person approves each step. The record shows the count on the day the line was crossed.

This is a reference listing. It documents what Fibric would read from Nexus Threshold and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shopify orders with shipping_address province_code, total_price, financial_status, and cancelled_at, so refunded and cancelled orders are handled by your rule
  • BigCommerce orders and their shipping_addresses sub-resource, for the state and total on each order
  • Nexus already declared for your company in Avalara AvaTax, with effectiveDate and endDate on each jurisdiction
  • The regions returned by TaxJar's nexus regions endpoint, each with region_code and country_code
  • State geographies from the Census Geocoder for orders whose address has a postal code but no state code
  • The thresholds and measurement periods you enter per state, and the date each was last reviewed
  • Steps already approved, so a state you registered in is not proposed again

Proposed actions

  • Target capability: propose a watch-list entry when a state's sales or order count reaches the share of threshold you set, with the running totals shown
  • Target capability: propose registration in a state once its threshold is crossed, with the crossing date and the totals that crossed it
  • Target capability: propose declaring nexus in Avalara AvaTax for the registered state, with the effectiveDate you approve
  • Target capability: propose adding the state to your TaxJar nexus regions so calculations include it
  • Target capability: propose a review of a state where sales have fallen below threshold for the period, with the option to end nexus

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • See the state you are about to cross

    Shopify orders are summed by province_code over each state's period. When a state reaches the share of threshold you set, a watch-list proposal shows sales, order count, and the days left in the period.

    With Shopify

  • Declare nexus once registration is done

    After you confirm registration, a proposal to create nexus in Avalara AvaTax with the effectiveDate you choose is raised. Approve it and collection follows on the engine's schedule.

    With Avalara AvaTax

  • Keep TaxJar's nexus list in step with BigCommerce sales

    BigCommerce orders by shipping state are compared with the regions TaxJar returns. A crossed state missing from the list is proposed as an addition.

    With BigCommerce, TaxJar

  • Resolve the address with no state

    Orders whose shipping address carries a postal code but no state are run through the Census Geocoder and assigned the state it returns before the count.

    With Shopify, Census Geocoder

Requirements

  • A commerce connector with order totals and shipping addresses: Shopify, BigCommerce, or both
  • A tax engine connector where nexus is declared: Avalara AvaTax or TaxJar
  • The threshold, the measure (sales, orders, or either), and the period for each state, entered and dated by you
  • A rule for cancelled, refunded, marketplace, and exempt orders, since states differ on whether they count
Authentication
It holds no store or tax-engine credentials. It reads orders and nexus through the commerce and tax connectors you attach, with the scopes you grant, and reads the Census Geocoder without a key.

Limits

  • It counts what you tell it counts. State thresholds change; the figures you enter are what it measures against, and it shows their review date.
  • Registration with a state is done by a person on the state's site. It proposes the step and records it; it does not file.
  • Avalara notes that nexus changes may not take effect immediately. Collection starts when the tax engine applies the change, not when you approve.
  • It declares nothing and registers nowhere on its own. Each state waits for approval.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Nexus Threshold ↗

Questions and answers

What am I approving at each step?
Three separate things, in order: that a state is worth watching, that you will register there, and that nexus is declared in the tax engine from a date you pick. Each is its own proposal with the totals behind it.
What does the record show if a state audits us?
Per state: the threshold and period you entered and when, the running totals by day, the date the line was crossed, each approval with the person and time, and the effectiveDate declared in the tax engine.
Will it start collecting tax on its own?
No. It never changes a tax engine setting until a person approves, and then it makes the one change approved. Registration itself is done by a person on the state's site.
Ask about Nexus Threshold

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy