Skip to main content
Question

Best Base Setup Options

  • November 11, 2025
  • 3 replies
  • 39 views

Forum|alt.badge.img+1

Hello!

I’m looking at building a forecasting tool for a seasonal sales business and I’m not sure the best way to set up the base table

 

My dream is a Forecast App/Page (currently happy with out Softr interface) that;

 

#1. has a list of all products, with 2024 sales, 2025 sales, and then an editable field for 2026 Forecasted Sales

#2 can be expanded upon to see a listing of customers and their purchases of said product (ideally with quantities and gross margin)

#3. The forecasting and customer sales data is only visible to the relevant salesperson (sales code)

 

My question is; what is the best way to set up the database. Currently I have different tables for Salesperson, Customer, Items, 2024 Sales, 2025 Sales (this is over 6000 entries), and then a forecast table that summarizes total item sales per sales code for 2024 and 2025 and has that 2026 Forecasted Sales column.

 

Am I on the right track, it seems like I’m running into issues when linking things together to get that layered visibility on the interface (I can absolutely see 2024/2025 sales and the editable forecast) but cannot get that expanded details.

 

I also could be rambling, so I’m open to questions/comments/advice/jokes etc.

 

thanks! 

 

3 replies

TheTimeSavingCo
Forum|alt.badge.img+31

Hm, I’d recommend having a single Sales table and a Date field instead of having multiple Sales tables; this’ll be much easier to manage / do reporting on in the long run

---

#1. has a list of all products, with 2024 sales, 2025 sales, and then an editable field for 2026 Forecasted Sales

I assume each Sales record is linked to the Product?  In which case, you could create a rollup field from the linked Sales table(s) and sum up the totals?

---

#2 can be expanded upon to see a listing of customers and their purchases of said product (ideally with quantities and gross margin)

Hmm, you’d need a junction table for this where each record represented the sales for a single Product for a single Customer for a single year, with links to the right tables.  This would let you create a List view to see the information you want

You could also try using a Pivot element in an Interface, but then it wouldn’t be expandable or usable in Softr?  Not sure what data aggregation tools Softr has!

---

#3. The forecasting and customer sales data is only visible to the relevant salesperson (sales code)

If this was an Interface you’d just filter the data by the logged in use: https://support.airtable.com/v1/docs/interface-designer-permissions?highlight=interface#filtering-data-by-current-user

I’m pretty sure you can also filter by the logged in user in some form for Softr as well

===

I also do free half hour calls and we’d hop on a screenshare and get through as much of this stuff as we can if you’d like!  You can grab a time here: calendly.com/adamc_airtable/30min


Forum|alt.badge.img+1
  • New Participant
  • 2 replies
  • November 12, 2025

You're on the right track! To improve layered visibility, link your tables through shared keys like sales_code, item_id, and customer_id. Use rollups or filtered views to show 2024/2025 sales and editable 2026 forecasts per product, then expand to customer-level data. Ensure visibility is scoped by salesperson using conditional filters in Softr or Airtable.
 


Mike_AutomaticN
Forum|alt.badge.img+28

Hey ​@m_tron,

To ​​​​@TheTimeSavingCo’s point re: I’m pretty sure you can also filter by the logged in user in some form for Softr as well. This is completely possible, and you might want to check out the video below.
 


Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel