These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- E-commerce ERP
- Features
- Purchasing and receiving
Purchasing and receiving
Purchasing and receiving for the order and stock cycle.
OverviewOpen purchase orders×
E-commerce ERP · Purchasing and receiving
New
Open purchase orders
Purchase orders
Approved3
VND-153WRH-140
380
12 OctVND-141WRH-140
830
11 OctVND-223WRH-110
220
06 OctAdd
Partially received3
VND-016WRH-120
640
11 OctVND-154WRH-130
940
16 OctVND-085WRH-130
410
13 OctAdd
What you can do
Keep the decision attached to the record
An approved purchase order is a supplier commitment, while a goods receipt is evidence of an arrival. Keep those decisions separate. The warehouse and entity on the receipt determine where accepted goods belong. Purchasing Manager works from the supplier commitment, promised date and order lines. Warehouse Manager records the physical arrival at the named warehouse. The receipt separates received, accepted and rejected quantities, so the team can see both what the supplier still owes and what stock may become usable. An approved purchase order alone does not change an inventory position.
How the work is organized
- Approve the commitment. Review supplier, entity, product, quantity and unit cost on the purchase order.
- Record the arrival. Use the goods receipt and its lines for the packing slip and actual received amounts.
- Separate accepted stock. Keep rejected amounts on the receipt and post only accepted quantities as stock movements.
What to agree during setup
Agree who may approve supplier orders and who records arrivals at each warehouse. Choose how the receiving team identifies the purchase order from the packing slip. Rehearse an arrival with fewer units than ordered and another with rejected units. Compare the receipt line to the purchase order line before updating received progress, then check the stock position after any posted movement.
Give the receiving team a supplier order with a promised date and a matching packing slip. They should be able to tell which lines arrived, which were accepted and which remain outstanding. Purchasing Manager should review the rejected line before the warehouse posts any stock receipt.
Check the handoff on an actual case
A supplier sends fewer units than promised. The receiving team records the arrival and each line’s received and accepted quantity; the Purchasing Manager sees the remaining commitment on the purchase order. Rejected units remain visible on the receipt rather than being silently added to usable stock.
The Warehouse Manager should see the receipt’s warehouse and accepted quantities. Purchasing Manager should still see the outstanding supplier quantity on the order. If the received and accepted amounts differ, keep the exception on the receipt for review rather than treating the whole arrival as usable.
What your team sees
- Open purchase orders — The main queue for supplier delivery, with its status and source context.
- Receiving exceptions — Related follow-up work that needs a second check.
Follow the work through
- Follow this handoff: Check the linked stages and exception path.
- Review the data model before importing open records.
What it keeps track of
Data model- Suppliers
- Entity purchasing counterparties.
- Purchase orders
- Approved supplier commitments with promised arrival.
- Purchase order lines
- Ordered supply quantities and received progress.
- Goods receipts
- Arrival and acceptance evidence for purchased supply.
- Goods receipt lines
- Received, accepted and rejected quantities per receipt.
- Warehouses
- Physical sites hosting entity-owned stock positions.
Who uses it
Permissions- Purchasing Manager
- Owns supplier commitment and receipt exceptions.
- Warehouse Manager
- Records arrivals and posted stock results.
- Finance Manager
- Can use the approved purchasing context when reviewing related money records.
Set up E-commerce ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.