Current BehaviourThe Purchase Order API currently returns:
- Order unit price (invoice price at time of ordering)
- Received quantity
It does not return the unit price at the point of receipt, even where this differs from the order price.Desired BehaviourAn additional field —
received_unit_price (or equivalent) — should be returned on the Purchase Order API, representing the actual price per unit at the time of delivery.Business ImpactPrice variances between order and receipt are common, particularly for seasonal and commodity items (e.g. fresh fish, meat, truffle-based products). Without the received unit price, it is impossible to accurately calculate the true cost of goods received. This affects food cost reporting, GP calculations, and purchase reconciliation for any customer using the ADACO inventory integration with a third-party platform.ExampleBeef mince ordered at £10/kg. Delivered and invoiced at £11/kg. The API returns the order price of £10/kg and a received quantity of 5kg, giving a calculated cost of £50. The true received cost is £55. The £5 variance is undetectable and unreconcilable with current API output.
Proposed SolutionAdd a
received_unit_price field to the relevant Purchase Order API response, populated with the unit price recorded at the point of goods receipt.PriorityHigh — this is a fundamental data gap that prevents accurate purchase reporting across all customers using the API integration.
Download Our App
Comments