Stock Allocations - AllocationPrice - Extend Decimal Places
Posted: Tue Aug 26, 2025 10:01 am
Hi,
I have started working with the Stock Allocations endpoint and am now using this data in Power BI. However, I’ve noticed that this endpoint only provides the AllocationPrice value to two decimal places, whereas the Receipts endpoint offers significantly more precision.
This can result in considerable discrepancies when working with larger quantities.
For example, the Receipts endpoint returns a unit price of 0.434426 for an item and a quantity of 3660, which totals £1,589.99.
In contrast, the Stock Allocations endpoint rounds the unit price to 0.43, which leads to a total of £1,573.80, a difference of over £16, which can be quite significant in reporting.
The only workaround at the moment would be to join several tables and retrieve the unit price from a different source, which adds complexity and reduces report efficiency. This could be avoided entirely if the AllocationPrice field in the Stock Allocations endpoint offered greater decimal precision.
Could you please look into this and, if possible, update the API to support extended precision?
Thank you in advance for your support.
Regards,
I have started working with the Stock Allocations endpoint and am now using this data in Power BI. However, I’ve noticed that this endpoint only provides the AllocationPrice value to two decimal places, whereas the Receipts endpoint offers significantly more precision.
This can result in considerable discrepancies when working with larger quantities.
For example, the Receipts endpoint returns a unit price of 0.434426 for an item and a quantity of 3660, which totals £1,589.99.
In contrast, the Stock Allocations endpoint rounds the unit price to 0.43, which leads to a total of £1,573.80, a difference of over £16, which can be quite significant in reporting.
The only workaround at the moment would be to join several tables and retrieve the unit price from a different source, which adds complexity and reduces report efficiency. This could be avoided entirely if the AllocationPrice field in the Stock Allocations endpoint offered greater decimal precision.
Could you please look into this and, if possible, update the API to support extended precision?
Thank you in advance for your support.
Regards,