A special group of documents in the r_k StoreHouse Pro application consists of Requests.
A Request is a document that defines the list of goods and their required quantity for performing economic activities in an enterprise department (sale, production, purchase, return).
There are four types of Requests:

  1. External Request — a document created manually or imported from r_keeper, for processing the sale of dishes.

  2. Return — a document created manually or imported from r_keeper, for processing returns of previously sold items or container buybacks.

  3. Internal Request — a document created manually, for processing requests for the supply or production of goods for the organization's departments.

  4. Child Request — a document automatically created based on an external, internal, or another child request, for processing the production chain according to specified routes.

Request Processing (the "Create Delivery Notes for Request" function) is the automatic creation, based on a request, of active documents according to specified rules, which will change the balance of goods as a result of economic activities (sale, production, purchase, return).

Requests created manually and imported from r_keeper are processed identically.

When processing external requests, the following are generated:

  • Assembly ("Complectation") — a delivery note for the production of dishes according to specified sets for subsequent write-off.

  • Delivery Note (Expense) — a delivery note for processing the write-off of produced and sold dishes, as well as for writing off sold goods that do not require production.

  • Receipt Payment Document -- a document for receiving funds as a result of services rendered.

When processing returns, the following are generated:

  • Receipt Note — a note for receiving returned goods from a customer back into stock.

  • Expense Payment Document -- a document for writing off funds as a result of processing returns of goods or services at their sale price.

When processing internal and child requests, the rules of routes defined on product cards are taken into account. The following documents are generated:

  • Internal Transfer — a delivery note for transferring goods, if a request is made to transfer an insufficient quantity of goods to another department.

  • Assembly ("Complectation") — a delivery note for the production of dishes/semi-finished products by another department, if the requesting department does not have production functions and makes requests for production to other departments.

  • Receipt Note — a delivery note for the supply of goods from suppliers, if requests are used to place orders with suppliers.

Before processing requests of any type, it is recommended to perform the Estimated Consumption operation. As a result of this operation, you will be presented with the stock levels of goods that will be written off before and after the estimated consumption.
If negative stock levels appear as a result of executing the expense, you can either write off with compensated entries or investigate the cause of their appearance, eliminate it, and then proceed with the expense write-off.

For organizations whose sales document processing fits into the scheme "Assembly ("Complectation")" + "Delivery note," working with internal and child requests is NOT REQUIRED.

Since the procedure for creating requests does not differ based on the type of request being created, we will first consider the general procedure for creating requests. Subsequently, we will look at how to work with external requests, returns, internal requests and child requests.