ERPNext Order Management: One Order, Five Departments

ERPNext · Order management · UAE trading

One Customer Order, Five Departments: How We Connect the Entire Journey with ERPNext

A customer places one order. Inside your business, it becomes a stock check, a supplier commitment, a picking task, a delivery and an invoice. The difficult part is making sure every team is working from the same promise.

By Craft Interactive · Published 28 October 2026

How does ERPNext connect a customer order?

ERPNext links the Sales Order to the documents used to buy, receive, dispatch, invoice and collect payment for goods. Each department records its part of the transaction, while authorised colleagues can follow the related records. The result is a traceable order journey, provided the team uses the links and keeps transactions current.

We approach this as a working process. Sales needs a dependable delivery date. Buyers need a clear shortage. Warehouse staff need the right item and quantity. Finance needs evidence of what was supplied and what remains unpaid. A useful ERP implementation makes those handoffs explicit.

Meet the order: 100 valve kits for a maintenance contractor

Harbour Tools Trading is a fictional UAE distributor. Its customer, Gulf Facilities Services, orders 100 identical valve kits at AED 250 each. The customer needs 60 kits immediately and agrees to receive the remaining 40 after replenishment.

100 kits Customer order quantity

60 + 40 Available now + to be purchased

AED 25,000 Total goods value before tax

For this example, the 60 kits are usable, uncommitted stock in one warehouse. There are no existing incoming purchases. The agreed billing plan is one invoice per delivery, with payment due 30 days from each invoice date.

Both businesses and all figures are fictional. Amounts below exclude taxes, freight and discounts to keep the operational example clear; live transactions must use the applicable tax and accounting configuration.

01 / SALES

Record what we actually promised

The sales coordinator converts the agreed quotation into a Sales Order. The item code, unit of measure, quantity, price, customer purchase order reference, delivery address and payment terms become a shared starting point.

Before promising all 100 kits immediately, sales checks availability with the warehouse and confirms the replenishment date with procurement. A stock balance alone does not prove that goods are free to promise: reservations, quality holds and other commitments matter.

The handoff: 100 kits ordered; 60 approved for the first dispatch; 40 awaiting purchase. The customer has accepted the split delivery and the agreed dates are recorded.

A Sales Order records the commercial commitment. It does not, by itself, mean that goods have moved, an invoice has been posted or money has arrived.

02 / PROCUREMENT

Buy the shortage with the customer order in view

The buyer checks that the missing 40 kits are not already covered by another incoming purchase. In our example, they are not, so the team creates a Material Request for the shortage and progresses it to a Purchase Order through the agreed purchasing process. ERPNext also supports creating a Purchase Order from a Sales Order where that route fits the transaction.

The important control is quantity. The customer ordered 100; the business needs to buy only 40. Buyers review any quantities carried into a new document before submitting it. They confirm the supplier, unit cost, receiving warehouse and expected date, while retaining the source references.

If the supplier cannot meet the date, procurement flags the exception before sales repeats the original promise. We define who owns that update and how it reaches the customer; a linked document cannot replace the conversation.

The Purchase Order is the supplier commitment. Receiving the goods and recording the supplier invoice are separate events.

03 / WAREHOUSE

Turn available stock into a verified picking task

The warehouse prepares the first 60 kits against the customer order. A Pick List helps organise the items and warehouse locations to pick. Staff check the item code and quantity before packing. Where stock reservation is supported and enabled in the deployed version, the team can use the configured reservation process to protect allocated stock.

When the supplier’s 40 kits arrive, the receiving team checks the delivery against the Purchase Order and records a Purchase Receipt. They record what actually arrived and was accepted, rather than assuming the ordered quantity is correct.

If five kits are damaged, those five must not silently become available for the customer. The receiving exception needs its own record and follow-up. For our main example, all 40 arrive in acceptable condition and can proceed to the second pick.

The stock movement: Start with 60 kits, dispatch 60, receive 40, then dispatch 40. The ending quantity for these kits is zero, assuming no other movements.

04 / DELIVERY

Dispatch in two stages without losing the remaining quantity

The first Delivery Note is created for 60 kits against the Sales Order. After replenishment, the second covers the remaining 40. Submitted Delivery Notes record the relevant stock movements and keep the quantities connected to the order.

The delivery coordinator checks the address, site contact, unloading arrangements and agreed delivery window. Signed delivery evidence or another agreed acknowledgement is retained against the relevant record. Any courier tracking, mobile proof of delivery or external transport integration needs to be included in the implementation scope.

We distinguish dispatch from customer acceptance. Posting a Delivery Note does not prove that a truck arrived at the site or that the customer accepted every kit. If a delivery is refused or short, the team records the exception and uses the appropriate return or correction process.

After the first shipment, the operational answer is straightforward: 60 dispatched, 40 still to deliver. After the second, all 100 are dispatched—but finance may still be waiting for payment.

05 / FINANCE

Connect the invoice to the goods, then the payment to the invoice

Following the agreed billing plan, finance creates a Sales Invoice from each Delivery Note: AED 15,000 for the first 60 kits and AED 10,000 for the remaining 40, before applicable taxes. The document links help finance trace the billed quantities back to the order and dispatch.

Finance also checks the supplier invoice against the purchase and receipt records before recording the payable. The customer receivable and supplier payable remain separate obligations, even when both relate to the same sale.

When the customer pays the first AED 15,000, finance records a Payment Entry and allocates it to the first invoice. In this simplified example, AED 10,000 remains outstanding. It is overdue only after its own due date has passed.

The final payment settles the second invoice when correctly recorded and allocated. Finance then matches the accounting entries to the bank activity through its reconciliation process. A submitted payment record and a bank reconciliation answer different questions.

Delivered, invoiced and paid are three different milestones. An order can be fully delivered and billed while money is still due. A sales order’s completion status should never be used as a substitute for checking invoice outstanding balances.

One order, five clear handoffs

Team	Main records	Question the next team can answer
Sales	Quotation and Sales Order	What did we agree to supply, where and when?
Procurement	Material Request and Purchase Order	Which shortage is covered, and when is it expected?
Warehouse	Purchase Receipt and Pick List	What has been accepted, and what is ready to pick?
Delivery	Delivery Notes and delivery evidence	What was dispatched, and what did the customer accept?
Finance	Sales Invoice and Payment Entry	What was billed, what was paid and what remains due?

These are connected records, not one screen that every employee must edit. Permissions should give each team the information and actions it needs while protecting sensitive pricing, banking and accounting data.

What happens when the order changes?

The strongest test of a connected workflow is an exception. Before going live, we recommend rehearsing situations that happen in ordinary trading businesses:

A supplier is late: procurement updates the expected date, sales agrees the revised plan with the customer, and the remaining delivery stays visible.
The customer changes the quantity: review related purchases, deliveries and invoices before using the supported amendment or closure process. A verbal change must not leave the old commitment circulating.
Goods are returned: record the physical return and any required credit separately, linked to the original documents.
A payment is short: investigate the difference and leave the genuine unpaid balance visible. Do not mark an invoice settled simply because some money arrived.

The exact correction steps depend on which documents are submitted and the controls configured in your ERPNext environment.

How we shape the workflow around your business

For an ERPNext implementation in Dubai or elsewhere in the UAE, we start with the route an actual order takes through your teams. Trading companies with multiple warehouses, supplier lead times and credit customers need clear decisions at each handoff.

Our implementation discussion covers item and customer data, warehouses, approval responsibilities, permissions, document formats and exception handling. We then test the agreed process with the people who will use it. As open-source ERP software, ERPNext offers room to adapt the system, but every customisation still needs a defined purpose and ongoing maintenance.

Standard document links provide the foundation. Automatic notifications, specific approval rules, a combined order dashboard or courier connections require configuration or additional work according to the agreed scope. We make those decisions visible before treating them as part of the finished workflow.

Four useful measures after go-live

Orders with a promised date at risk and a named person following up.
Dispatched quantities that have not yet been billed under the agreed billing policy.
Customer invoices approaching or passing their payment due dates.
Receiving discrepancies and delivery exceptions still awaiting resolution.

Reviewing these measures together helps teams resolve the next action, rather than asking each department to rebuild the order history from email.

Frequently asked questions

Can ERPNext handle partial deliveries?

Yes. A Sales Order can be fulfilled through multiple Delivery Notes. In our example, one covers 60 kits and another covers 40. The team must check the linked quantities and record any exceptions accurately.

Does every customer order require procurement?

No. An order that can be fulfilled from usable, available stock may proceed directly to picking and delivery. Purchasing is needed when the replenishment decision calls for it.

Does creating a Sales Order reserve stock automatically?

Do not assume so. Check the stock reservation features, settings and process in your deployed ERPNext version. A confirmed order and a protected stock allocation are different controls.

Can an order be complete while the invoice is unpaid?

Yes. Delivery and billing progress do not establish payment settlement. Finance should review the related invoice balances and payment allocations.

Is the same process suitable for every UAE trading business?

The core documents are reusable, but the route varies. Advance payments, direct supplier delivery, multiple warehouses, returns and approval requirements should be tested against your business process before deployment.

Let’s follow one of your orders together

Bring an order that required a stock check, a supplier purchase or a split delivery. We can map the handoffs and show where ERPNext can connect the work.

Discuss your ERPNext workflow