Requirements: supplier portal
- Client: a Swiss food company
- Project type: web application
- Excerpt
This document describes what the solution must do. How it will be built is for the vendor to set out in their specification.
1. Background and goals
The company cooks in its own kitchen and buys ingredients, fruit and vegetables from several suppliers.
- G-01Orders, stock and purchase orders live in one system.
- G-02Before every order, it is clear what is in stock.
2. Users and roles
- Purchasing: places orders with the suppliers
- Kitchen and stores: book deliveries in, see the stock
- Admin: maintains suppliers, items and users
3. Functional requirements (excerpt)
- F-01An item list holds ingredients, fruit and vegetables, each with its supplier and unit.
- F-02Purchasing creates orders per supplier. The system turns each one into a purchase order.
- F-03The system keeps the stock level per item.
- F-04A booked delivery raises the stock of the items delivered.
7. Acceptance criteria (excerpt)
- A-01An order for three items from one supplier produces exactly one purchase order with three lines.
- A-02After a delivery is booked in, the stock shows the quantity delivered.
8. Scope
- Which dishes get cooked is planned in a separate kitchen system. That planning is not part of this contract.
