User data type: create 2 data types or use only 1

Need help Database
1

Hi all, in my platform I need 2 types of users (Buyer and Seller). So far I’ve always used 2 different data types I created. However, I’ve only now realized I could have also used just one: the “User” data type that is by default already been created by Bubble. I need an advice if it’s fine to continue with my set up or better to change it using the User data type and using then the Option set to identify the 2 different type of users. Thanks for the help!

2

It depends a bit on your scenario (for example, buyers and sellers could be a company or organization with multiple users, in which case new data types can make sense), but from your description alone you’ll most likely make it a lot easier for yourself if you stick to using the built-in User type and separate them by using an option set or something else.

It’s sometimes worth in scenarios like this to pause for a second and ask yourself whether a user could be both a buyer and seller though. Not sure if that’s applicable in your case, but if it is (or will be in the future), you could use a list field (containing both buyer and seller), a yes/no for each role or in some cases disregard roles altogether and just have users being able to both buy and sell regardless of their role. For example, on a site like eBay, I’d expect to be able to buy and sell using the same account.

But you want a clear separation between buyers and sellers, then an option set and single field on the User is one perfectly fine way to do that.

1 Like
3

I’d recommend using only one data type — the default “User” that Bubble provides. Even if your buyers or sellers are companies, it’s best practice to keep them under the same User type and distinguish them with an Option Set (e.g., “Buyer” or “Seller”).

You can then store their additional or company-specific data in separate related tables (like “Buyer Profile” or “Seller Profile”) linked to the main User. This approach keeps your database cleaner, avoids duplication, and makes user authentication and workflows much easier to manage.

1 Like
4

Thanks a lot! Clear