ERP discovery · Warehouse operations · ERPNext implementation
Why We Recommend Starting ERP Discovery in the Warehouse
A process presentation says, “We receive the goods and update stock.” At the receiving desk, the story may involve a handwritten count, a missing item code and a spreadsheet updated after lunch. Those details belong in the ERP discussion.
By Craft Interactive · Published 4 November 2026
What is observation-led ERP discovery?
Observation-led ERP discovery means watching representative work, asking the people doing it to explain their decisions, and checking the related records before defining system requirements. It connects the intended process with what actually happens.
For trading, distribution and manufacturing businesses, we recommend making the warehouse an early part of discovery. Goods, documents and decisions meet there. A receiving delay can affect availability. A picking substitution can affect the invoice. A returned item can affect stock and customer credit.
Management workshops still matter. They establish objectives, budgets, responsibilities and constraints. Operational observation gives those conversations concrete evidence.
Our recommendation: Observe a transaction, verify the records, then agree the requirement with the people responsible for the process.
Follow the goods and the information
Physical work and system updates do not always happen at the same time. A pallet may reach the shelf before the receipt is entered. A picker may discover damage before anyone updates the available quantity.
Observe
Where the goods go, what people check and when work waits.
Ask
Why the step exists and what happens when the normal route does not work.
Verify
Whether the documents, timestamps and quantities support the explanation.
A useful walkthrough follows both journeys. It shows when the business physically receives, moves or dispatches goods—and when colleagues can see that event in the system.
A warehouse walkthrough that changes the requirements
Imagine Harbour Industrial Supplies, a fictional UAE distributor. Its team wants better stock accuracy and faster order processing. Those goals are sensible, but they do not yet tell us what needs to change.
A proposed discovery walkthrough follows a supplier receipt, a customer pick and a returned item. The observations below are illustrative, not reported client findings.
At receiving: the supplier counts cartons, the business sells pieces
A delivery contains 10 cartons with 12 pieces in each carton. The supplier document shows 10; the stock record needs to reflect 120 pieces. Staff write the conversion on paper before someone enters the receipt.
The requirement becomes specific: confirm the purchase unit, stock unit and item-specific conversion, then test a receipt of 10 cartons and a later sale of individual pieces.
If carton sizes vary by item or supplier, we must establish which conversion applies. A general instruction to “automate receiving” would miss that decision.
At storage: the shelf name exists only in someone’s memory
Staff know an item is “behind the blue rack”, while the system records only “Main Warehouse”. Experienced employees find it quickly; a new colleague needs help.
Before creating hundreds of locations, we ask how frequently goods move and how much detail the team can maintain. The useful location structure is the one that supports picking and counting without creating unnecessary transactions.
At picking: a shortage is solved through a private message
The picker finds fewer usable units than expected and messages a salesperson. A substitute is agreed, but the printed pick instruction still shows the original item.
Discovery should identify who may authorise a substitution, whether customer acceptance is required, and how the final dispatch and invoice reflect the actual item supplied. The message is evidence of a missing handoff.
At returns: the item arrives before the decision
A customer returns a unit. It is placed beside normal stock while the team decides whether it is damaged, repairable or suitable for resale.
We would ask where undecided returns belong, who inspects them and what evidence permits release. The physical receipt and the customer’s credit also need separate decisions.
Turn observations into requirements we can test
A discovery note should distinguish what was observed from what someone believes caused it. One delayed receipt does not prove that every receipt is delayed.
Record the transaction reference, observed event, timing, staff explanation and any unanswered question. Then review further examples before treating a finding as a recurring issue.
| Observation | Requirement to agree | Acceptance test |
|---|---|---|
| Cartons are converted to pieces by hand. | Validated units and conversion factors. | Receive 10 cartons of 12 and confirm 120 pieces in the correct stock location. |
| Stock location depends on staff memory. | A maintainable location structure. | A trained user can find, move and count the item using the recorded location. |
| A substitution is agreed outside the order record. | Clear authority and updated transaction details. | The approved substitute appears consistently in dispatch and billing records. |
| Returned goods sit beside released stock. | A controlled hold-and-release process. | An unreleased return cannot be dispatched through the tested operating routes. |
| Goods move before the system is updated. | A practical recording point and named owner. | Compare physical movement and posting times during a representative pilot. |
Each requirement needs an owner and an agreed priority. Where the proposed solution needs configuration, training, equipment or custom development, record that explicitly.
Ask about workarounds without blaming the people using them
A handwritten note may keep dispatch moving when a shared terminal is occupied. A private spreadsheet may provide information that an existing report does not show.
Removing the workaround before understanding its purpose can make the job harder. We recommend asking:
- What does this note or spreadsheet help you remember?
- What information is missing when you need to act?
- Which decisions require another person’s confirmation?
- What changes during a busy shift or an urgent delivery?
- What happens when the person who normally knows the answer is away?
Include the employees who receive, pick and count stock, alongside their supervisors. Arrange observation around site safety rules and normal work, and agree before recording photos or video.
How these findings shape ERPNext implementation
For an ERPNext implementation in Dubai or elsewhere in the UAE, operational findings help define the configuration and the data preparation required.
Item data and units
Confirm item identities, descriptions, units and conversion factors before importing them. ERPNext supports units of measure; the business still needs to establish which values are correct for its products and transactions.
Warehouse structure
ERPNext’s warehouse structure can represent locations below a physical building. Decide the appropriate level of detail from picking, movement, counting and reporting needs.
Opening stock and reconciliation
Agree the stock-count method, transaction cut-off, location mapping and responsibility for resolving differences. ERPNext provides Stock Reconciliation for opening stock and reconciliation, but the tool cannot establish whether the source count is trustworthy.
Devices and the recording point
Check where users will enter or scan information, whether labels are readable and whether connectivity is reliable. Test proposed devices with the intended ERP workflow. Mobile interfaces, offline operation and integrations should be confirmed within the agreed scope.
Software capabilities are part of the solution. Clear ownership, accurate master data and a workable recording routine make those capabilities useful.
Bring the findings back to the meeting room
Warehouse observations need discussion with sales, purchasing, finance and management. A local workaround may be caused by a decision made elsewhere.
Before configuration begins, the discovery output should include:
- A current process map: physical movements, documents, decisions and handoffs.
- An evidence-based issue list: confirmed findings, their impact and open questions.
- An agreed future process: responsibilities, controls and exception handling.
- A data preparation plan: item codes, units, locations, balances and owners.
- Acceptance scenarios: transactions that prove the proposed process works.
Avoid redesigning the whole business around one walkthrough. Validate findings across relevant shifts, sites and transaction types, especially where their operating conditions differ.
What if the business does not have a warehouse?
Start where its core work happens. For a service company, follow a customer request through scheduling, delivery and billing. For a project business, examine progress recording, purchasing and cost approval.
The principle remains the same: combine the people’s explanation with representative work and records before deciding what the ERP must do.
Frequently asked questions
Does warehouse discovery replace management workshops?
No. Observation helps explain how work happens. Management workshops establish objectives, priorities, authority and the decisions needed to change the process.
Who should join an operational walkthrough?
Include the people performing the selected work and its process owner. Involve sales, purchasing, finance or IT when the transaction crosses their responsibilities.
Can ERP discovery be done remotely?
Parts of it can. Guided video walkthroughs, screen sharing, sample documents and transaction reviews can provide useful evidence. Record which physical conditions or activities still need direct verification.
How do we avoid treating one incident as a general problem?
Separate the observation from the suspected cause. Check additional transactions, ask relevant colleagues and measure frequency before deciding on a broad change.
Should we customise ERPNext as soon as a gap appears?
First confirm the requirement and its cause. Consider standard functionality, configuration, data correction and process improvement before agreeing custom development.
Let’s begin with the work your team knows best
Bring a receipt, a picking problem or a return that regularly needs extra explanation. We can discuss how to turn those operating details into clear ERPNext requirements.
Product references
The walkthrough is illustrative. For the ERPNext capabilities discussed, see the official documentation for Units of Measure, Warehouses and Stock Reconciliation.
