Need a suggestion
In the context of my repair management app, I am considering the addition of a "warehouse parts" feature. To implement this, I've decided to create a separate panel, both for UI simplification and code separation. Moreover, this decision aligns with my plan to develop a SaaS app offering different subscription levels, with and without the warehouse functionality.
In the version without the warehouse, I still need the ability to input the parts used for each repair. The key distinction lies in how these parts will be managed: automatically, if the warehouse is present, and as text fields if it's not. The data from both versions will contribute to the generation of invoices.
To accommodate both scenarios, I am considering adding a table named "repair_parts" with fields such as repair_id, part_type, part_name, quantity, price, cost, discount, and tax.
If the warehouse is present, the form will be of a certain type; otherwise, it will be similar but different. This approach ensures data consistency, allowing for seamless integration if a user decides to activate the warehouse functionality later on.
What are your thoughts on this? In the case of 'without warehouse,' do I simply need to create a table and a model, or do I also need a resource?
0 Replies