PO line items show different status in API versus UI

Hi there,

We noticed a bug in the ShipHero API where PO changes in the UI are not reflected in the API.

For example, we have a PO where all but one of the line items have been received (see screenshot):

However, when requesting this specific PO via the GraphQL API, every line item is still marked “pending.” Here’s the request_id for the example PO: 647b750fc374cc486951472e.

May we get some insight into why this is happening?

All the best,
Colin

Hey @cschouten,

Thanks for bringing this to my attention.
I’ll look into this and get back to you shortly.

Best,
RayanP

Hey @cschouten,

Thanks for hanging in there!

I’ve escalated this issue as a bug to our Engineering Team. Looking forward to updating you on a fix when possible.

Best,
RayanP

Hi @sh-agent,

May we get an ETA for a fix? This is significantly impacting our operational analytics.

All the best,
Colin

Hey @cschouten,

Thanks for hanging in there!
I’ll share the urgency of this resolution with the team, but at the moment I don’t have an ETA.

Please let me know if you have any questions or concerns.

Best,
RayanP

Please keep us posted as soon as you hear back. Thanks @sh-agent!

All the best,
Colin

1 Like

Hey @cschouten,

Thanks for hanging in there!

Updating this thread as well with the response I received.

The issue of having the line items return statuses such as “received” or “under received” will not be done. That is a calculation that is done on our front end. Therefore, no table exists in our database with that information to pull. You can discern that value through the API by comparing the expected and received quantity.

Please let me know if you have any questions or concerns.

Best,
RayanP

Thanks for the update, @sh-agent.

May I get some context into why this won’t be done? May we get some insight into this calculation you are doing on the frontend since no table exists in your db to pull this info?

All the best,
Colin

Hey @cschouten,

Thanks for hanging in there!

The above reply is the context I was given when asked. I think the reasoning behind that decision is that you’re able to tell if a line item is “under received”, “received”, or “over received” using the Public API already.

Ex:
if the quantity expected is 50 but you’ve received 40, it’s under received.
if the quantity expected is 50 but you’ve received 50, it’s received.
if the quantity expected is 50 but you’ve received 60, it’s over received.

Please let me know if you have any questions or concerns.

Best,
RayanP

1 Like

Thanks @sh-agent. We’ll build some logic in our data ingestion to handle those line item statuses.

1 Like