Setting Up Tax Profiles

Tax profiles give sellers an explicit way to describe how products should be treated for tax.

Go!BrightCart calculates and records tax. Sellers are responsible for registration, filing, and remittance. Tax reports are operational records, not filing outputs.

Why this matters

• Shared products can carry a base tax profile.
• Store listings can override that profile when a storefront needs a different treatment.
• If neither is assigned, checkout may fall back to generic behavior that is harder to reason about later.

Good operating defaults

• Use product tax profiles for the most common classification.
• Use the product editor's simple taxability choice for most products, then switch to advanced profile selection only when a specific profile matters.
• Use listing overrides only when the same product must be taxed differently in one store.
• Keep profile names plain and operational, such as General Physical Goods or Digital Downloads.

Where to configure tax

• Seller-level tax behavior lives in /dashboard/settings?tab=tax.
• Product-level taxability and profile assignment live in the product editor.
• Store-specific exceptions live in the listing editor as tax profile overrides.

Where to audit tax

• Seller-facing tax reporting lives in /dashboard/orders/tax-report.
• Order exports and tax report exports are operational records for review and reconciliation.
• Use those reports to review collected tax by date, store, geography, product, and profile, not as a tax filing output.

What to review before launch

• Seller tax mode is intentional.
• Stripe Tax is enabled if automated tax calculation is required.
• Each tax profile contains a usable provider tax code.
• Products and listings that need explicit handling actually have a profile assigned.