Drop Shipping Sales Tax: A Practical Guide

A common drop shipment has two sales but one physical delivery: a retailer sells to the customer, buys from a supplier, and tells the supplier to ship directly to the customer. Sales-tax treatment is not determined by the warehouse location alone. Analyze the retailer-to-customer sale and supplier-to-retailer sale for the destination state. Determine which party is the seller or retailer under that state’s law, whether the retailer or marketplace has collection responsibility, whether the supplier can accept a resale certificate, and whether special drop-shipper rules shift liability. California and New York illustrate why a single nationwide rule is unsafe.

This guide is part of Steady’s Business Taxes & the IRS library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

There are two transactions

The supplier sells to the retailer, and the retailer sells to the final customer, even though the product ships once.

Delivery state drives the first review

Destination sourcing is common for remote sales, but state and local sourcing rules must be checked.

Physical presence can create nexus

Inventory, employees, contractors, offices, or other in-state activity can matter even before an economic threshold is met.

Economic nexus thresholds vary

States differ on dollar amounts, included sales, measurement periods, and whether transaction counts remain.

Marketplace collection is not universal relief

A facilitator may collect on marketplace sales, while direct website sales can still create registration and filing duties.

Resale certificates are state-specific

The acceptable form, registration number, timing, good-faith standard, and drop-shipment exception vary.

Supplier exposure can shift

Some states can treat the in-state supplier or drop shipper as the retailer when the remote seller lacks required registration or documentation.

Returns may report marketplace or exempt sales

Even when another party collects tax, a registered seller may still need to report gross, marketplace, or exempt sales.

Step-by-step workflow

1. Map the transaction parties. Record customer, retailer, marketplace, supplier, fulfillment provider, ship-from, ship-to, invoice flow, and payment flow.
2. Identify the destination state. Determine the delivery jurisdiction and whether local sourcing adds county, city, district, or special rates.
3. Test physical nexus. Review inventory, supplier arrangements, employees, contractors, affiliates, trade shows, returns, and fulfillment activity.
4. Test economic nexus. Apply the state’s current threshold, included sales, lookback period, effective date, and registration deadline.
5. Determine product taxability. Classify the exact product, bundled service, shipping, handling, discount, and exemption.
6. Identify the collecting party. Separate direct sales from marketplace sales and verify facilitator collection by state and period.
7. Complete resale documentation. Give suppliers the certificate and registration information accepted by the destination state before the transaction when required.
8. Register and configure. Set up state and local accounts, product codes, sourcing, marketplace flags, exemptions, and effective dates.
9. Reconcile and file. Tie orders, refunds, marketplace statements, tax collected, exempt sales, returns, and payments by jurisdiction.
10. Monitor changes. Review thresholds, registrations, certificates, product rules, platform responsibilities, and new fulfillment locations regularly.

Worked example

An online retailer accepts a California order and asks a California supplier to ship directly to the consumer. The retailer is not registered in California. Under California’s specific drop-shipment rules, the supplier may be treated as the retailer and responsible for tax unless the facts and documentation provide relief. A New York shipment uses a different framework and forms. The business therefore maintains a state-by-state matrix instead of telling every supplier that an out-of-state resale number works everywhere.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Using the home-state permit nationwide. Confirm what each destination state accepts in a drop shipment.
• Testing only economic nexus. Physical presence can create a duty below the remote-seller threshold.
• Assuming the marketplace handles direct sales. Separate platform orders from the seller’s own website.
• Ignoring the supplier transaction. The resale leg can create tax or documentation exposure.
• Using one product code for everything. Taxability can differ by product, bundle, and state.
• Collecting before registration. States can restrict collection without a permit.
• Filing from cash receipts alone. Reconcile destination, refunds, exemptions, marketplace collections, and tax payable.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Practical implementation notes

State matrix

Track nexus, threshold, included sales, marketplace rule, sourcing, taxability, certificate, filing, and effective date.

Order evidence

Retain cart, invoice, ship-to, supplier invoice, tracking, tax engine result, exemption, and refund.

Marketplace reconciliation

Separate tax collected by the platform from seller-collected tax and verify return presentation.

Certificate control

Record form, jurisdiction, registration number, issue date, renewal, supplier, and validation.

Deeper planning points

California example

Special drop-shipper rules can shift liability. California explains that a drop shipper can become responsible when an out-of-state true retailer lacks the relevant permit and the retail sale is taxable. Use the current CDTFA rule for the actual facts.

New York example

The resale document follows a defined framework. New York describes two sales and uses Form ST-120 in specified registered-retailer situations. The bulletin was updated in March 2026, but the business should still confirm its exact parties and locations.

System setup

Configuration must follow the legal matrix. Map product tax codes, destination sourcing, registrations, marketplace flags, resale customers, effective dates, and filing accounts. Test sample orders in every material state before relying on automation.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.