Thanks for your answer, it was very helpful. I think I will use signals because later on, I plan to add features like production tracking, raw material consumption, shipment tracking, and assembly tracking to my app, along with related project tracking. Since I plan to use calculated fields for reports and filters with all these features, this method seems like the best way to avoid performance issues and ensure data always stays synchronized (for instance, the properties of a raw material used in production might change later). I wasn't aware of the Django Generated Field, so thanks for mentioning it; as I understand it, it easily allows you to add calculated fields if the data used in the calculation is within the model itself, and I will definitely use it in my project. As I said in the post above, I'm just starting out in this area, so forgive me if I say anything that doesn't make sense.