#bc-_docs

1 messages · Page 1 of 1 (latest)

ionic veldtBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1440491914825830605

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

void depot
#

Was unable to fill that last bit but here is the completion:

Further, should there be 1 product containing all tiers as different prices, or 1 product per tier within an individual SaaS?

#

@mighty mural CC

crisp basin
#

hello! Sorry, about taking a while to respond! I'm not quite certain what specific tax implications you're concerned about, can you share a little bit more?

void depot
#

No problem/rush at all! Ah, my CPA advised me that all SaaS under one stripe account is fine but they said some of their clients need to do some hacky stuff to discern the products when everything is under one roof, but i am still learning the platform and wasnt sure how e.g. 1099s are issued. But the main focus of this question is how best to structure the Stripe products/prices under the single entity

#

I am having a hard time understanding how Stripe users with this use case of N disparate products under 1 company model everything

crisp basin
#

so I can't really comment on the tax bits here, and it sounds like you already have a CPA to advise you on that.

The question now that you really have, is how to structure the Stripe products and prices? You mentioned that your clients might need to do some hacky stuff to discern the products - but I'm not too sure why?

void depot
#

The CPA's clients -- sorry for confusing you on the tax bits, ignore all that

#

Generally speaking, how do your (Stripe) customers organize products in this way: 1 company, multiple completely different SaaS products? Do they have multiple accounts/orgs, 1 account/org with multiple products, ...

And further how do they break up the products? 1 per tier, 1 product containing all tiers, ...

crisp basin
#

hmmm, generally I agree with what our docs say in that :

You must use separate Stripe accounts for projects, websites, or businesses that operate independently from one another.

I would say you would want to use orgs if you want to be able to see all the details of the accounts under your org from a unified view.

In general, create a couple of test accounts, try things out, and see what best fits your needs. You're not locked into anything while testing.

In terms of how to organize your product, can you describe what you're selling? When you mention tiers, it actually refers to something very specific within Stripe and it may not be the same thing as what you are talking about i.e. https://stripe.com/resources/more/pricing-models-explained-types-of-pricing-models-and-when-to-use-them#tiered-pricing

void depot
#

Okay, that aligns with what hobbes (tagged earlier) was thinking. But we have about 40 products planned. So we would need to make 40 accounts long-term? Instead of just a single org with 40 products (or sets of products)? That seems like an operational headache

Thanks! Those are helpful links. Yes! Tiers as defined there is what I'm talking about. Here is an example, we have a product called Backfeed, currently using polar.sh for payments: https://backfeed.omni.dev/pricing

It appears you suggest creating 1 product per tier, correct? If so this is also what hobbes was thinking!

#

Btw, the products will also have cross-billing benefits, e.g. a discount on product A if a customer pays for product B

crisp basin
#

are you saying that all 40 products are for different sites?

void depot
#

Yeah so we have a company Omni LLC, and there will be an ecosystem of different software products on different websites

Completely different products under one legal roof, with cross-app features & benefits

Think TanStack but for business software basically

#

Or think ~40 SaaS startups wrapped into 1 company

crisp basin
#

If you want to handle the discount / split yourself for cross billing. Then the alternative would be to consider Connect whereby you are the platform, and the different software products would be on different connected accounts. You can take a look at our guide(s) to Connect here : https://docs.stripe.com/connect. For example, you would build your own cart on your platform, charge the customer, a total amount, then make separate transfers to connected account A for product A, and connected account B for product B

i think it's difficult for me to provide very specific advice now, maybe it might be better for you to try things, and then let us know more specifically what you tried to do, but cannot achieve

void depot
#

Interesting, okay we will keep playing around. Appreciate that! Finally, could you advise on the product breakdown for tiers? Stripe users tend to make a single product per tier with the most success, correct?

crisp basin
#

i don't think it's about single product per tier with the most success 😅 It's more about their business model.

So for example, if you want to use a price with tiers, this means the unit cost changes with quantity.

If you want to charge customers a single price per item, what we call either flat rate or per seat pricing

#

so there is no such thing as a single tier, because that would essentially be flat rate or per seat

void depot
#

Most success as in least headaches with stripe, but i see that its contextual

#

Frankly i am a bit more confused about stripe now but i will keep digging in the docs lol thank you for your time

#

I think my confusion stems from knowledge gap, i didnt even see some of the links you sent prior

crisp basin
#

i do strongly recommend just creating a test account. Stripe Billing is complicated, and the fastest / easiest way to understand things is really to just test things out

void depot
#

Thanks, we do have a test account, will play with it

#

in fact playing with it lead me to ask that question 😂

crisp basin
#

feel free to reach out again here in case you tried something, and it's not doing what you expect. Or want to do something, but not sure how to go about it. It's easier for us to help if you have concrete examples of what you are trying to achieve

void depot
#

Backfeed has free tier, basic tier (monthly/annual), team tier (monthly/annual); per-seat pricing for basic/team

Currently we have this

I wasn't sure if we continue down this path or if the best way is to split it up into 3 different Stripe products (Backfeed Free, Backfeed Basic, Backfeed Team)

You answered my question about the multiple products I think, it sounds like we have to use one stripe account

2025-11-18_18-02.png
#

Hope that helps, any further questions we'll experiment from playing with stripe further!

crisp basin
#

hmmm, so I'm looking at this guide : https://docs.stripe.com/products-prices/how-products-and-prices-work

I think one thing to also consider is what do you expect to show on the Invoice? Only the Product name will show, so if you intend to show Backfeed Free, Backfeed Basic and Backfeed Team, then you will need separate products for each of them

And maybe also consider also, internally within your own systems, do you consider Backfeed free, basic and team as different products? How do you as a company do reporting for example for Backfeed?