I've got a table in one of my bases where I keep a list of what we charge customers for items. We're a services company, so nothing is set in stone, but we use this table for a guideline (and the prices rarely change much, if ever).
I haven't updated the design of this particular table in a while, so I'm reviewing it now and not 100% sure of the best approach.
I have a second table where I actually keep every single item we ever put on an invoice. 44 in total. And then we just reference the table with pricing, but mainly because it has more granular information. For example, I might have a "Facility Fee" as an invoice item, but then I have multiple "Facility Fee" entries in the Price table for different durations. I now realize it's a bit silly to split things out in the manner we've done...at least how we're during it currently.
Invoice table (each "Item" is a possible invoice item). Very simple, but more things link off of here in a separate process.
Then the prices table looks like this:
It's grouped by category, then just has some information to help identify what you're looking at to set a price.
It's a table that's a few years old now and very basic in setup, so I know I'm not making the most out of it. It's not linked to any records at all, for example. The remaining fields you can't see in the screenshot are just more fields with info. Nothing linked. I'm just not sure how to improve it.
My initial thought was to essentially the pricing table as a table that tracks pricing variants, essentially. So each entry in the invoice table would be linked to any pricing "variants" in the costs table. For example with Facility Rental, we could have "Facility Rental" as an invoice item, and then link it to every major variant. 1 hour, 2 hour, 1 day, 2 day, whatever.
But that's my only idea. Not sure if anyone else has any better ones or any experience with tracking internal pricing info via airtable.