@ScottWorld is right, but a bit terse. :winking_face: There’s no right or wrong way to set up your base; there are only ways that meet your business requirements.
With all data in a single table you can use Views and Filters to separate the product lists logically (instead of physically). This will undoubtedly provide you with some really great agility in managing your data.
If you go the route of multiple tables (similar to multiple tabs in a spreadsheet context) I’m pretty sure you want to start by learning about Roll-Ups.
But… how are you able to use Excel given the requirement that different clients and people need to be segregated from a universal view of the data?
Let’s now circle back to the known requirements.
Product data are managed and viewed by different clients.
Client (a) should not be able to see Client (b)'s product data.
Formulaic properties of Client (a) are generally not the same as for Client (b).
If these are the key requirements, there is a way to do this in Airtable with a single table using views and filters and security settings.
Certainly, without deeper insight into the nature of the solution and the scale of users and data, it’s unreasonable to assume this approach is best. However, in almost every case where Airtable users attempt to carry the schema baggage of an Excel sheet into a database-like tool such as Airtable, they achieve vast data management benefits by embracing a data model that leans into a unified database architecture while delivering on requirements through logical views and filters.
I recommend you at least explore the idea of a single “products” table where Grouping gives you the sums you want (literally an instant’s worth of effort) and where Views and access settings keep users and their data separated.