Know what stock you can actually use with Frappe ERP

At a glance

Frappe ERP lets receivers distinguish accepted and rejected quantities so buyers and finance can work from a clearer account of the delivery. Start with reliable item codes and purchase units, then connect requests to approval and receipt. Test replenishment once your team can explain the stock it has.

See what is usable

The delivery arrived, but part of it is damaged. Your buyer sees stock on the way to production while the receiver is still separating usable goods. Frappe ERP's Purchase Receipt records distinguish received, accepted and rejected quantities. Put that distinction into the receiving process so the next decision starts with what your team can actually use.

Watch a receiver count a real delivery. If staff copy the ordered quantity into the receipt, the stock report will repeat that mistake more neatly. Write down what the receiver can confirm and who decides what happens to damaged goods.

For the first release, prefer a clear process over aggressive automation. Once the team can explain an exception, you can decide which steps should run without intervention.

Use clear codes and units

Give buying and the warehouse a shared way to identify each item. Use one code for the same stock item, keeping the supplier's description as a reference rather than creating another item for a different spelling. Assign a person to review new codes so the receipt, reorder request and invoice remain easy to connect.

Purchase and stock units also need a rule. Frappe's Purchase Receipt documentation includes a unit-of-measure conversion factor when the purchasing unit differs from the stock unit. Test the supplier pack you actually receive. A valid number in the conversion field can still be the wrong business assumption.

Review warehouse meaning with operations and finance. A location should tell users something useful about custody or availability. If rejected goods share a physical area with usable stock, the system procedure must still prevent staff treating everything in that area as ready to issue.

Choose the right supply action

Frappe Material Requests can cover purchase, transfer or manufacture. That lets your buyer distinguish a need for new supply from a need to move stock already held elsewhere. Start with the required item and warehouse, then choose the purpose that reflects the next action. A shortage at one location need not become an unnecessary purchase.

The documentation notes that Material Request is optional and useful for centralized buying. Decide whether your business needs that request stage rather than adding a document merely because it exists. If requests are mandatory internally, explain who can raise one and what happens to urgent demand.

Include a required-by date and the intended warehouse. Have buyers review duplicate or obsolete requests before turning them into orders. A system can preserve demand accurately while the original requester no longer needs it.

Make purchasing authority clear

Frappe's role permissions and configurable workflows let you separate preparing a purchase from approving it. Put your authority policy into those controls, with a clear substitute for an absent manager. The buyer should be able to see the next permitted step without resolving every approval through email.

Test rejection and correction with normal accounts. Frappe warns that a configured workflow replaces the normal Save and Submit behavior, and cancellation needs an appropriate transition. An approval process that cannot correct a mistaken document will encourage staff to seek informal workarounds.

Keep the policy readable outside the software. A manager should be able to explain why an order needs approval without asking a developer to interpret a condition.

Keep the delivery story intact

Frappe Purchase Receipts record accepted and rejected quantities and their warehouses. Use those fields to preserve the receiver's count, including goods that arrived but cannot be used. Buyers then have a recorded distinction to discuss with the supplier, and finance has a receipt to check against billing.

Use a partial delivery in acceptance testing. Then receive the remaining quantity on another occasion and review the purchase order status. Add a return to the supplier. These are different events, and your team should be able to follow each one without rebuilding the story from email.

Frappe also allows receipts without a purchase order when the relevant Buying Settings permit them. Decide whether your control policy allows that route. The availability of a shortcut does not mean it belongs in your operating procedure.

Finance should review how the receipt connects to billing. A received quantity and an invoiced quantity answer different questions; your acceptance test should show how staff investigate the mismatch.

Receipt example (hypothetical, not an ERPNova result): you order 20 cartons of 12 units, or 240 units. The supplier delivers 18 cartons, containing 216 units, and the receiver rejects 9 damaged units. That leaves 207 usable units, 9 rejected units and 24 units not yet delivered. Keep those quantities separate when reviewing the supplier invoice. A report showing only 216 received units would overstate the stock available to production by 9 units.

Build on reliable stock records

Frappe can create Material Requests automatically when configured reorder conditions are met. Once your stock records are dependable, use that capability to give buyers a repeatable way to review replenishment. The proposed request still reflects your data and policy; it is not an independent forecast.

Test an item that already has a supplier order on the way. Ask the buyer to explain the proposed request and what changes if the delivery is late. Recheck the rules when demand or lead times change; the settings approved at launch are not a permanent buying policy.

• Test the purchasing unit against the stock unit using a real pack size.
• Receive less than ordered, reject part of the delivery and return goods.
• Confirm who may receive without an order.
• A buyer should be able to explain a replenishment request using the records available on screen.

Connect receiving with finance

Bring ERPNova a receipt your buyer and warehouse interpret differently. In an ERP audit, we can assess how Frappe ERP should record the quantities and approvals, then identify any reporting or integration work. Ask for a receiving test that ends with finance explaining the supplier balance.

For production demand, continue with the BOM and manufacturing guide. For rollout sequencing, use the implementation roadmap.