FAQs
FAQs
Should I build my own billing or use a platform like Stripe? Use the platform. Billing is a solved problem with brutal edge cases (proration, tax, dunning, currency, compliance), and hand-rolling it means owning all of those forever. Configure a mature commerce platform around how you sell, and spend your effort on the catalogue and integration, not on reinventing invoicing.
How do I change a price for new customers without affecting existing ones? Create a new price and leave the old one in place. Existing subscriptions keep referencing the price they were created with, and new sign-ups use the new one. You almost never edit or delete a live price, you add and deprecate, which is exactly why products and prices are configured as separate objects.
Do I really need a CRM integration if I am small? You need the link defined even if you do not need the full sync yet. Set the shared identifier between commerce and CRM from the first sale so the records are tied. The richer field sync can come later, but retrofitting the identifier across a thousand existing customers is far more painful than setting it once at the start.
How much of my churn is actually involuntary? Enough to be worth fixing, and you will not know your number until dunning is configured to measure it. Failed-payment churn is customers who wanted to keep paying, which makes it the cheapest churn to recover. If you have not switched on smart retries and a recovery sequence, assume a recoverable slice of your churn is leaking quietly.
Inclusive or exclusive pricing, which should I display? Pick one and apply it everywhere. B2B sellers commonly display tax-exclusive prices, since business buyers expect to see the net amount and reclaim the tax. B2C and consumer-facing sellers often display inclusive prices, because the shown number is the number the buyer pays. The failure is mixing the two across products, which makes invoices look wrong to everyone.
When do I have to start collecting tax in a new region? When you cross that region's registration threshold, and the obligation usually starts from that point, not from when you get around to it. This is why the tax engine should watch your registration status and why you revisit the configuration on a cadence. Treat each new region as a trigger to check your obligations rather than a thing to handle once.