Internal requests for stock, prioritized and ready for purchasing
Employees and departments raise a demand for the products they need — with quantity, unit, priority, and a responsible person. Purchasing selects the demand into a request for quotation; receipts and deliveries reference it until it is fulfilled.
Built for
- Employees & team leads — Ask for what you need with quantity, unit, and priority — no email chains.
- Department heads — Raise department-level demands and see which are still open.
- Purchasing teams — Work from a prioritized queue and pull demands into RFQs without re-typing.
- Warehouse staff — Issue or receive stock against the demand so the requester is served.
What Demands does inside ERPS X
Demands is the requisition application in the ERPS Inventory department. A demand states who needs something — Demand By an Employee or a Department, with the employee name or department recorded — who is Responsible for it, the Demand Type, and the product lines: Product, Quantity, and UOM.
Each demand carries a Priority of Highest, Medium, or Lowest and free-text Notes, so purchasing can see at a glance what is urgent and why. Demands are listed, edited, and reviewed from one screen; users with Editor or Full Access rights can add new ones.
Fulfilment happens in the applications next door. On a Purchase Request for Quotation, the buyer selects the demand and its lines are pulled in. Receipts and Deliveries transfers carry a Demand column, so goods arriving or being issued can be tied back to the request that started it.
Employees & team leads
Ask for what you need with quantity, unit, and priority — no email chains.
Department heads
Raise department-level demands and see which are still open.
Purchasing teams
Work from a prioritized queue and pull demands into RFQs without re-typing.
Warehouse staff
Issue or receive stock against the demand so the requester is served.
Everything Demands gives your team
Each feature below is part of the application as it ships in your ERPS X workspace — no add-ons, no separate licences.
Employee or department
Choose whether the demand is raised by a named employee or a whole department, and record who is responsible.
Priority levels
Mark each demand Highest, Medium, or Lowest so purchasing works on the right thing first.
Product lines
Add one or more products with quantity and unit of measure from the product master.
Notes
Explain the need — project, machine, customer — in free text on the demand.
Selected into RFQs
Purchase quotations have a Select Demand field that brings the demand lines onto the RFQ.
Referenced on transfers
Receipts and Deliveries transfers show the demand a movement belongs to.
A closer look at Demands
The screens, records, and controls you will actually work with day to day.
Demand header
- Demand By: Employee or Department
- Employee Name or Department
- Responsible user
- Demand Type (Product Demand)
- Priority: Highest / Medium / Lowest
Lines & notes
- Product from the product master
- Quantity per line
- UOM per line
- Notes for context
- Edit demands as needs change
Fulfilment & control
- Select Demand on a purchase Request for Quotation
- Demand reference on Receipts transfers
- Demand reference on Deliveries transfers
- Demands list with view and edit
- Access by department and application; Editor / Full Access to add
The Demands workflow
From first setup to daily use — the path your team follows inside the application.
Raise the demand
Choose Employee or Department, name the responsible person, and set the priority.
List the products
Add each product with quantity and unit of measure; add notes explaining the need.
Purchasing picks it up
On a Request for Quotation, select the demand — its lines are pulled in.
Goods arrive or are issued
Receipts or Deliveries transfers reference the demand as stock moves.
Close the loop
The requester's need is met; the demand and its documents stay linked for review.
Where teams use Demands every day
Production line needs components
A department demand for raw materials, marked Highest, goes straight into an RFQ.
Maintenance requests spares
An engineer raises a demand for parts; the warehouse issues from stock or purchasing buys.
Office consumables
Admin raises a Lowest-priority demand for supplies that purchasing batches monthly.
Sales needs stock for a customer
A demand with notes naming the customer order so purchasing understands the deadline.
Warehouse issuing stock
A Deliveries transfer references the demand so the movement is explained.
Manager reviewing open requests
Scan the demands list by priority and responsible user to see what is outstanding.
What changes when Demands runs on ERPS X
Outcomes you can expect once the application is live for your company.
Requests in one place
No more requisitions lost in email or on paper.
Faster purchasing
Demand lines are pulled into RFQs instead of re-keyed.
Clear priority
Highest, Medium, Lowest tells everyone what to do first.
Named responsibility
Every demand has a requester and a responsible user.
Traceable fulfilment
RFQs, receipts, and deliveries carry the demand reference.
Controlled access
The Demands application is granted per department, with adding limited to editor rights.
Works with the rest of your ERPS X workspace
Demands shares one database with every other application in your company workspace. No connectors, no exports — the same record everywhere.
Popular with
Demands — common questions
What does a demand record?
How does a demand become a purchase?
Can stock be issued from the warehouse against a demand?
Who can raise a demand?
Is Demands the same as Replenishment?
Turn requests into orders without the paperwork
Start a 14-day trial, activate ERPS for your company, and let your teams raise their first demands from the Inventory menu.