Choose a site inventory system using custody and availability

Illustrative example: an MEP contractor has 50 individually identified drums at one site. Assume they contain the required cable specification, but record usable length separately because drums need not contain equal lengths. The categories below do not overlap.

The useful answer is 27 potentially available drums, followed by their identities and remaining lengths. A report saying “40 company-owned drums” still overstates immediate availability. A report subtracting ten client-owned drums and five holds without knowing whether those sets overlap may also be wrong in a different case.

Make ownership and status independent fields. A client-owned drum can also be on hold. Reservation is a further relationship to a package; it should not erase the drum’s location or owner.

Now ask whether the available stock can serve the actual cable runs. In a second illustrative check, two released drums hold 180 metres and 140 metres. Their combined 320 metres exceeds a 250-metre requirement, but neither can supply a single 250-metre run if the approved design requires it without a joint. The system should show the individual lengths and leave the installation decision with the engineer. An aggregate quantity alone cannot answer it.

Walk a real movement from supplier to site store, then from store to subcontractor and back. At each handover, identify who records dispatch, who acknowledges receipt and which evidence establishes acceptance.

For a transfer between sites, “sent” and “received” are separate events. Material should remain visible while travelling. For a partial cable issue, the remaining length and drum identity matter. For unused returns, the person receiving the material needs to confirm quantity and condition. A return entered by the issuer without acknowledgement may make the ledger look healthier than the store.

ERPNext’s stock-entry documentation illustrates explicit movement purposes and a transit mechanism. Treat this as an example of what to demonstrate, not proof that a standard installation covers your client-owned stock, inspections or project reservations.

The minimum master data usually includes a stable item identifier, specification, stock unit, approved conversions and location hierarchy. Serial, batch, heat or drum identifiers should follow the material’s traceability needs. Do not force a uniquely identified pump and a box of low-value consumables through an identical process merely to simplify a screen.

A site app may make capture easier but leave finance copying totals each month. An ERP may hold a good ledger while users postpone entries because the interface is slow at the gate. The decision depends on where records currently fail, not on which category sounds more comprehensive.

Ask who will maintain the integration when item codes change or a subcontractor leaves. Include implementation, devices, support, training, data cleanup and exit exports in the comparison. A cheap licence can still require substantial reconciliation work.

Give each shortlisted option the same anonymised scenario and expected results. Receive the 50 drums, apply ownership and hold statuses, reserve eight, issue part of one drum, return unused cable and transfer another drum to a second site. Then count the original store.

Introduce three deliberate problems. First, replay an offline issue after connectivity returns; the balance must not reduce twice. Second, have two users attempt to issue the same remaining length. While disconnected, neither device can know the other's latest action, so test the agreed allocation or reservation controls as well as the conflict review on reconnection. Third, enter a correction after the count cutoff; the historical report should retain its original version and show the approved change.

Have the storekeeper perform the capture and the QS investigate the resulting balance. Watching an implementer execute a rehearsed sequence tells you less about ordinary use. Record clicks or elapsed time only alongside correctness: a fast issue into the wrong work package creates more work downstream.

For each failure, ask whether the remedy is configuration, custom development, a manual control or a product limitation. Get that answer in the proposal. “Supported” is too broad if it depends on an extension that nobody has priced or tested.

The stores owner should control physical movement evidence. The quality owner should control release from inspection holds. The package owner should authorise reservations and reallocations. Finance should govern valuation and ledger adjustments. Client-owned material needs the authority defined in the relevant agreement.

Restrict stock adjustments more tightly than ordinary capture. Preserve the previous value, reason, source document and approver. A system that allows a user to make the count agree by editing yesterday’s issues weakens the very control being purchased.

Also decide what an offline user can see and do. A downloaded quantity can become stale. The interface should show its last refresh and route conflicts for review when it reconnects. A stale cache should not silently release a held item.

After a representative trial, the team should be able to reproduce stock by owner and location, distinguish held and reserved quantities, and trace issues through returns or consumption. Measure unresolved transfer age, corrections per movement and time required to prepare a reconciliation. Keep rejected and incomplete transactions in the measures so the trial cannot succeed by ignoring difficult records.

1. Map one material’s ownership, custody, location and release states.
2. Count and reconcile its opening position before importing it.
3. Run the same receipt-to-return challenge in every shortlisted option.
4. Price the missing controls and the ongoing support responsibility.
5. Use a bounded reconciliation pilot if integration behaviour is the remaining uncertainty.