A shopper buys two items, uses a discount code, and ships them to another state. One item later comes back. The same seller also receives marketplace orders and has wholesale customers who submit exemption documents. A checkout calculator can return a number quickly. The business still has to determine whether the order was classified correctly, preserve what happened when it changed, and reconcile the transaction to the return.
For U.S. sellers evaluating sales tax automation tools, the most useful demonstration follows one order all the way through. It starts with product and destination data, goes through tax calculation and any later adjustment, and ends with a report that explains what was included in filing.
Confirm where and how the business is in scope
Create a list of jurisdictions and channels your tax team has reviewed. Include your website, marketplaces, retail locations, wholesale orders, and other routes to customers. Document who determines registration or collection obligations and what role the vendor plays. A dashboard can surface information for review. Your team still needs an approved position before configuring collection.
Ask for a written description of coverage by jurisdiction and service. The Streamlined Sales Tax Governing Board describes the role of Certified Service Providers in determining taxability, sourcing, and calculation for sales sourced to Streamlined member states. If you are considering that program or another managed service, check the applicable states, eligibility, and responsibilities for your business.
Separate registration, calculation, filing, and remittance in the evaluation. Ask which tasks you perform, which the provider performs, and which require an additional service. A vendor may support calculations for a jurisdiction while offering a different process for filing there. Confirm the exact operating model before committing.
Give the tax engine an order that exposes data gaps
Select a small group of products from your catalog. Include items that your tax team expects to treat differently, a bundle or discount where relevant, and at least one order with shipping charges. Record the expected treatment under your approved rules. Ask the operator to show the classification code, destination data, calculation date, and result for each line.
Test what happens when data is incomplete. Submit an order with an address the system cannot resolve and another with an unmapped item. Check whether checkout can detect the problem, who sees the exception, and what the buyer experiences. Decide how your business will handle an unavailable tax service or uncertain calculation, with input from the teams that own sales, operations, and tax.
Then change the destination between checkout preview and shipment. Walk through recalculation under your approved process and verify which address and transaction date appear in the committed record. If orders can split across locations or shipments, ask how the system stores the inputs for each part. You need enough evidence to reproduce the result without relying on the customer’s current address.
Keep exemption records tied to the transactions they support
A wholesale order is a useful test because the tool must connect customer information, supporting documentation, and approved treatment. Use an example with a document that applies to one customer entity but not another. Ask the vendor to show who can approve it and which orders rely on it.
Test a missing or expired document using the workflow your tax team specifies. Check what the sales representative sees, whether checkout applies the expected treatment, and where staff can review or resolve an exception. Give an auditor’s role access to a sample order and ask them to retrieve the relevant document and effective dates. Avoid a setup in which the final tax result can be viewed but the supporting decision lives in a separate inbox.
Consider what happens when a customer changes their business name or shipping location. Can the system keep prior transactions tied to the evidence used at the time? Can the tax team review the new information before it affects future orders? These transitions matter more than how quickly an employee can upload a document during a demo.
Follow returns, marketplace orders, and settlement adjustments
Process the original sale and then return one item. Compare the resulting tax adjustment with the source order and your expected treatment. Add an exchange and a cancellation before shipment if those occur in your business. Verify that the tax engine and commerce platform agree on the affected lines and whether the adjustment reached the filing data.
Include a marketplace order and a direct order in the same report. Ask the provider to identify the channel and relevant collection information so your team can apply its approved reporting treatment. An order count may be correct while the underlying channel treatment is wrong. Use marketplace and store reports to reconcile the totals independently.
Ask how the integration handles retries. If an order or return is sent twice after a connection interruption, check whether the tax record is duplicated. If the tax engine receives an order but the commerce platform fails to finalize it, inspect the exception queue. Operators need a way to find the mismatch, correct it, and verify the final record without guessing which system succeeded.
Run a filing reconciliation before you buy
| Reconciliation step | Evidence to compare |
|---|---|
| Confirm order completeness | Commerce and marketplace exports versus committed tax records |
| Validate adjustments | Refunds, cancellations, exchanges, and approved corrections |
| Review exclusions or special handling | Channel identifiers, exemption evidence, and tax team decisions |
| Verify filing and payment | Approved return, submission acknowledgment, and payment records |
Ask the provider to prepare or export one test period. Begin with known channel totals, then explain each difference between gross sales, amounts classified for reporting, and the tax figures. The exact report treatment depends on the jurisdiction and your approved process. The tool should make the data and reasoning behind the result available for review.
Include an amended return or late transaction in the discussion. Ask who acts, what evidence is retained, and how the correction reaches the relevant period. Compare fees for transactions, filings, registrations, certificates, extra channels, and support where applicable. Include the time your team spends mapping new products and resolving exceptions.
Choose the tool that can explain an ordinary order
Run a small pilot on one channel with a variety of products and order changes. Compare checkout results with expected examples, count unresolved transactions, and measure how long the team needs to prepare a reconciliation. Have someone in customer support explain the tax line on a refund using the records they can access.
The outcome to look for is a clear record from the first calculation through the final return. When a customer changes an order, the tax team should be able to explain the original amount, the adjustment, and where both appear in reporting. That is the workflow sales tax automation needs to support after the checkout screen closes.