Answer the question
In order to leave comments, you need to log in
What is the best way to build a database schema for inventory control of goods?
Good day, there is a task to implement warehouse accounting.
With operations: Acceptance of goods (each acceptance has a purchase price), write-off, sale and return of goods.
A reasonable question arises how to design it competently so that in the end you don’t get a huge amount of piling up (for example, in returns you need to know the information about acceptance and sale) and with updates it still looks difficult, they made an acceptance for 1k goods - received 1k updates.
Please tell me your vision on this task or reading \ examples of this.
Answer the question
In order to leave comments, you need to log in
In this scheme, at least the inventory and posting operations are still missing
+ there should be two returns: from you from the buyer and from you to the supplier,
+ relocation is possible - if there are several warehouses
+ picking / disassembling is possible
+ you need to immediately understand whether batch accounting is needed, batches, expiration dates, etc.
Describe all business processes. Make a card (folder) for each.
Accordingly, you will have 2 stacks that are relevant and what you will implement.
Next, describe the entities that are in the business process, these are fields, restrictions, related work.
Then prioritize and start making MVP.
Next, build up the "meat" in the form of a functional.
By the way why not 1c:erp ,SAP, dynamics 365?
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question