Stock Allocations - AllocationPrice - Extend Decimal Places

Wish the API had something it doesn't? Post here!
Forum rules
  • Check the documentation first. Before posting questions, please check the documentation to ensure it doesn't already cover what you need.
  • No spam. All automated messages, advertisements, and links to competitor websites will be deleted immediately.
  • Post in relevant sub-forums only. Messages posted in the wrong topic area will be removed and placed in the correct sub-forum by moderators.
  • Respect other users. No flaming or abusing fellow forum members. Users who continue to post inflammatory, abusive comments will be deleted from the forum after two warnings are issued by moderators.
  • Harassment. No threats or harassment of other users will be tolerated. Any instance of threatening or harassing behavior is grounds for deletion from the forums.
  • Adult content. No profanity or pornography is allowed. Posts containing adult material will be deleted.
  • Bandwidth. All images and signatures must be 500 x 500 pixels or smaller. Posts containing over-sized images and signatures will be removed.
  • Illegal content. No re-posting of copyrighted materials or other illegal content is allowed. Any posts containing illegal content or copyrighted materials will be deleted.
Post Reply
GTacs
Posts: 29
Joined: Tue Jun 07, 2022 12:48 pm

Stock Allocations - AllocationPrice - Extend Decimal Places

Post by GTacs » 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,
GT
Post Reply