Current behavior: Auto-Tax rules (geographic tax detection) work correctly when a purchase is made through a native GHL Funnel / 1-step order form. However, when the exact same product is purchased through a Form Builder payment form, no tax is calculated or collected — regardless of the buyer's country and the Auto-Tax configuration on the product. Expected behavior: Auto-Tax should apply identically regardless of where the payment form is hosted — whether it's a Funnel order form or a Form Builder form. The tax amount collected from the buyer should be consistent across all payment surfaces. Impact: Businesses selling through Form Builder forms are unknowingly collecting payments without tax, creating compliance issues. This is particularly critical for EU-based businesses subject to VAT obligations, where the correct tax amount must be collected at the point of sale — not added manually after the fact. Steps to reproduce: Create a product with Auto-Tax enabled (e.g. 20% VAT for EU buyers) Purchase via a Funnel 1-step order form with an EU billing address → tax is correctly applied ✅ Purchase the same product via a Form Builder payment form with the same EU billing address → no tax is applied ❌ Environment: Tested April 2026, Stripe test mode, EU buyer (FR), product price €200 ⚠️ Note: This is not just a feature request — this is a legal liability issue for both GHL and its customers. GHL markets its Auto-Tax system as a solution for tax compliance. EU-based businesses are relying on this feature to meet their VAT collection obligations under EU law. When Auto-Tax silently fails on Form Builder payments, those businesses are unknowingly under-collecting tax — exposing themselves to penalties, back payments, and audits. A platform that advertises tax compliance tooling has a responsibility to ensure that tooling works consistently across all its own payment surfaces. An inconsistency of this nature — where the same product, the same tax configuration, and the same buyer country produces different tax outcomes depending solely on which GHL form type is used — is not a minor UX gap. It is a systemic compliance failure. This also creates direct legal exposure for GHL itself. If a GHL customer is audited and penalized by tax authorities because Auto-Tax failed silently on Form Builder payments, that customer has legitimate grounds to seek damages from GHL for marketing a compliance feature that does not work as advertised. This is not a theoretical risk — it is a foreseeable consequence of shipping an inconsistent tax system under the banner of "Auto-Tax compliance." We strongly urge the GHL team to treat this as a critical bug fix, not a backlog feature request.
