Booking system (reservation) of goods (orders) Google spread sheet. Examples?

Question

Google Apps Script

Good day. Maybe someone has seen examples of scripts with such a not tricky functionality, something similar, maybe someone will undertake to implement it?
Three sheets:
1 - "product base" (three columns: brand, name, quantity (no article ??. Automatically generated? unique id?)
2 - "customer base" (organization name, city, phone\e-mail)
2.1 - "menu" (reserve itself) - (pair of buttons): "reserve", "edit", "delete" "history"
3 - "history"
1). button "reserve" - ​​show the form:
1.0 - id (unique) of the order.
1.1 issue list (product) - we take the data from the "base" sheet.
1.2 vyp.listom (client) - we take the data from the "customer base" sheet.
1.3 Quantity of goods.
1.4 Comment. to order.
1.5 The "+" button adds new fields (1.1, 1.2, 1.3, 1.4) to the form - an order can consist of several items.
1.6 "Book" button - places an order (on the orders sheet) - "writes off" the number of ordered units from the "quantity" column of the "base" sheet.
2). button "edit" - show the form (by order ID or client)
Here I think it is clear that all the data in the order needs / can be changed (at the same time add / remove (return) the number of goods to the "base").
3) "delete" button - form:
delete an order by customer or order ID. By check box in the form - return the number of units of the specified product in the order to the "base".
4 - order history. This is not a tricky base ..) TK is straight. But I think the meaning is clear. Thank you for any help.
just a list of orders with date, customer, qty.

Answer 1

Hello.
Here is a small example https://youtu.be/9WK1FM2_tDc Table https://goo.gl/4u23t7 (make a copy)
The idea is to keep a record in only one "History" sheet. On the "Warehouse" balances are displayed through the formula:

=QUERY('История'!B:E;"select B, C, sum(D) where E=true group by B, C")

Those. if there is an entry in the "History" without TRUE, then it can be considered "unposted".
The "Orders" sheet serves as an explanation for the "History", perhaps it is necessary to somehow expand the connection of these Tables, but it will still be conditional.
Explanations for the code . The backend needs a LockService to resolve the write queue.
You can make a form for viewing orders, with the ability to mark FALSE in the "History". Maybe even "Edit", but I think it's better to make a copy and write a new order, marking the old one as FALSE. It is also necessary to think over the regulations, because Tables are "non-rubber" and it is necessary to transfer leftovers as often as possible.
Explanations for the concept. Your representation, which is given above, is hardly suitable for implementation in Tables, just because there are no row identifiers, much less links between Tables. I suggest not deleting anything at all. It is better to do "transfer of balances" and other parameters to new Tables (or vice versa) in order to have a more complete picture of actions.
Please change the tags in the topic to Google script and Spreadsheets . With the current tag, the answer to the question should be something like this https://www.google.com/enterprise/marketplace/sear...