A missing product should be a question.

What happens when the integration cannot identify the product?

product_identity_required · 422

With product_identity_policy=require_known, the calculation service refused the line without a known tax code or SKU. It did not return an invented zero-tax answer.

What this execution establishes

Tests the explicit strict policy. The API also has an allow_generic policy; this does not claim every request refuses missing identity.

Executed using the published version’s source hashes. The Virginia lifecycle cases use a disclosed 5.3% snapshot and fixture address handling; they do not claim a live geocoder or current production-rate test.

Reproduce and review

Primary source: Virginia Tax: sales tax rates and locality lookup. Source review: 2026-10-21. Transaction date: 2026-07-26.

Make it your test

Bring a SKU that your current mapping cannot classify.

Evaluate this in my workflow →

Review it independently.

Use the same disclosed inputs and record failures as carefully as successful results. The public reproduction needs no account. A private API evaluation requires authorized sandbox access; the local reference environment is not a claim about every live configuration.

Publish your own findings with the pack version, date, limitations and any relationship to Prophit.ai. An untested competitor result stays untested. Continue to the API quickstart or check current pricing.

Run the public examples again.

No account or key needed. This runs the address lookup and package writer afresh with the disclosed inputs. It does not run your own transactions or submit a return.

Public reproduction script · Instructions

Evidence you can inspect. Limits you can see.

The business data is synthetic. The address example uses a small official-derived historical Illinois sample. The other executions use an isolated sandbox database, disclosed inputs and the same service implementations used by the application. No customer records, filings, payments or competitor credentials were used.

The pack distinguishes local component execution from hosted API execution. The optional replay script records your own sandbox results, including failures; it does not recreate the private reference database or certify a provider. Confirm supported coverage and effective dates before evaluating a real workflow.

Sales Tax Engine · Sales Tax Compliance · API coverage contract · Current pricing