Choose construction inventory software by tracing a material from the central store to a site, then through receipt, issue and reconciliation. Keep material demand separate from movement and consumption. A useful site record should explain where stock is, who received it and which evidence supports a quantity leaving the available balance.
Start with a material your team can count consistently. Define the stock unit, central store, site location and responsible people before the software demonstration. Site transfers deserve their own evidence because dispatch and receipt are different events. A material showing as sent should not automatically be treated as confirmed stock at its destination.
How should stores and sites appear in the stock record?
ERPNext Stock Entries record item movement between warehouses. ERPNext Material Transfer represents movement between internal warehouses. The ERPNext Stock Entry documentation offers a concrete way to discuss internal locations. Ask the demonstrator how your proposed central store and site store map to the system’s warehouse records. Retain the business meaning alongside the software name.
ERPNext Material Receipt adds items to the target warehouse. ERPNext Material Issue deducts items from the source warehouse. These documented receipt and issue effects are different from an internal transfer. Decide which event each proposed entry represents. A transfer to a site store should not be labelled consumption merely because material has left the central store.
Define the issue point in the operating brief. For your process, does an issue mean release to a named work area, a responsible crew or confirmed consumption? Record the intended meaning and the evidence needed. The software entry purpose cannot decide that operating definition for the business.
What should a two-step site transfer prove?
ERPNext Add to Transit supports a two-entry warehouse transfer. The transit workflow makes dispatch and destination recording a useful demonstration pair. Ask the demonstrator to identify the source, transit and destination records, then show how the second entry relates to the first. The receiving person should be able to find the expected shipment without retyping it as unrelated stock.
At dispatch, record the item, quantity, unit, destination and accompanying reference. At receipt, record what was actually counted and any discrepancy. Keep the expected and received quantities distinct. An unresolved shortage should remain visible for investigation rather than disappearing into an edited dispatch total.
| Event | Operational question | Evidence to compare |
|---|---|---|
| Material request | What does the site need? | Approved requirement and project |
| Dispatch | What left the source store? | Transfer reference and counted quantity |
| Transit | What has not yet reached the destination? | Linked outstanding transfer |
| Receipt | What did the site actually receive? | Receiver and accepted quantity |
| Issue | What left the site’s stock balance? | Purpose, responsible party and quantity |
| Reconciliation | Why does the count differ? | Movement history and investigation note |
Why must requests and projected quantities remain separate?
Submitting an ERPNext Material Request records demand without creating stock or accounting entries. An ERPNext Material Request can identify the project behind a requirement. The Material Request documentation describes demand planning rather than physical arrival. Include a project reference in the requirements where material belongs to a specific job. Ask the site team to explain what a request authorises and what evidence is still required before they treat material as present.
ERPNext distinguishes current warehouse stock from projected incoming and outgoing quantities. Inspect both values with the relevant source documents. A projected quantity is useful planning context, but the team should locate the incoming movement behind it. Keep a delayed transfer or unresolved receipt visible instead of assuming every expected quantity is available for today’s work.
An ERPNext request marked Ordered is covered by submitted Purchase Orders, not necessarily received stock. This status distinction is especially useful during a site readiness review. Ask the demonstrator to show the ordered, received and still-outstanding records separately. A request dashboard can support planning without becoming a substitute for the storekeeper’s receipt evidence.
Original site worksheet: dispatch, shortage and issue
This hypothetical exercise uses bags of an imaginary dry construction material, counted in bags throughout. The central store begins with one hundred bags. A transfer dispatches thirty to Site A, but the receiving count finds twenty-eight. The figures illustrate record reconciliation and are not a recommended stock level or a report of an actual project.
Dispatch row. Record the opening central quantity, dispatched quantity and transfer reference. The hand calculation leaves seventy bags at the central store. Ask the demonstrator to show the corresponding source movement and the intended transit or destination treatment. Inspect the unit together with the quantity.
Receipt row. Record twenty-eight accepted bags at Site A and retain the original dispatch expectation of thirty. The difference is two bags. Give the discrepancy a responsible investigator and a source reference. Do not automatically describe it as theft, damage or consumption; the evidence in this exercise establishes a difference, not its cause.
Transit row. Ask the demonstrator to explain where the two unresolved bags appear in the configured workflow. Record the actual answer and compare it with the proposed process. Keep any correction subject to the business’s approval route. A demonstration that simply forces the transfer to complete leaves the central reconciliation question unanswered.
Issue row. Record a fictional authorised issue of twelve bags from the twenty-eight received. The resulting site balance is sixteen bags before any other movement. Identify the work reference and the person responsible for the issue. Keep the issue purpose visible so the entry does not become an unsupported statement about final consumption.
Count row. Now propose a physical site count of fifteen bags. Compare that count with the expected sixteen and open a separate one-bag discrepancy. Do not combine it with the two-bag transfer difference. They arose at different points and need different evidence. The worksheet preserves those distinctions even if a summary report shows only an overall variance.
Project row. Link the original requirement and the later movements to the fictional project through the demonstrated configuration. Ask a colleague to reconstruct demand, dispatch, receipt and issue using the records alone. If they cannot identify which event changed stock, improve the record design before considering live migration.
How should changed requirements and corrections be controlled?
Stopping an ERPNext Material Request does not cancel its existing downstream documents. The Material Request guidance makes a stopped request a separate decision from cancelling linked work. If a site no longer needs material, inspect the existing transfer or purchasing documents before assuming the stop has reversed them. Record each required action with its own owner.
For stock corrections, retain the original movement evidence and the reason for the proposed change. Rehearse the approved correction route in a test copy. Avoid changing quantities merely to make a status or report appear complete. The useful outcome is an explainable stock record, including unresolved exceptions where the facts remain incomplete.
The final brief should define site locations, stock units, transfer references, receiving responsibility and the meaning of an issue. Add the enquiry route for shortages and the person who approves corrections. These operational decisions are as important to the evaluation as the application’s movement screens.
For related planning, see business systems requirements and software development. To discuss the site workflow, get started with the reconciliation worksheet and the transit, receipt and issue questions still requiring a demonstration. That gives the inventory decision a clear construction-site outcome.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.