[BUG] [SP-API] [Issue] Missing shipment-item-id in GET_AMAZON_FULFILLED_SHIPMENTS_DATA_INVOICING report

[stayhero]

I'm submitting a...

[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

GET_AMAZON_FULFILLED_SHIPMENTS_DATA_INVOICING

Expected Behavior

We used to receive the column shipment-item-id in the above report.

Current Behavior

The column shipment-item-id is empty for most orders (at least for orders on the Amazon.de german marketplace). The column was not removed but it is just empty.

Context/Screenshots

We need the values of the column to distinguish (i.e. previously imported) order items from new ones.

A sample report ID is 685193019440.

Your Environment

We simply use the SP API for reports to create and retrieve the GET_AMAZON_FULFILLED_SHIPMENTS_DATA_INVOICING reports.

We are observing this behavior for reports since Friday, March 24, 2023.

[hinavinayak]

We are looking into this with the Report Authoring Team.

[rosalie-Janssen]

This is also happening on the _GET_AMAZON_FULFILLED_SHIPMENTSDATA. Originally is was only for Europe but now happening for the US as well.

[rachelleborowicki]

We are experiencing the same on GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL.

[BCampanile]

Has there been any movement on fixing this issue?

[compumatic]

this same issue exists when downloading the Amazon Fulfilled Shipments report manually from Amazon Fulfillment Reports in Seller Central

[BCampanile]

rachelleborowicki and compumatic: have either of you been able to resolve this problem or find a work around?

[compumatic]

unfortunately no resolution here yet... I only noticed it yesterday and thought I had a problem with my database or import script for the file. last night I realized the Shipment Item Id data was missing (column exists but no values) and this seems to have started a few days ago. I thought I was crazy until I found this bug report. I sent a message to Amazon seller support last night and they completely misunderstood the issue and gave a non-responsive answer, so I sent a clarifying response this morning.

as noted in the original submission "We need the values of the column to distinguish (i.e. previously imported) order items from new ones." this is obviously a critical field as I see no other way of uniquely identifying records and avoiding either missing parts of an order (where fba splits into more than one shipment) or duplicating order entries. I'm assuming this is a bug that will be fixed and applied retroactively to reports and not a feature change? does anyone have a creative workaround if Amazon does not correct this?

[BCampanile]

Compumatic I agree precisely. We have opened a ticket with very similar wording. I spent the entire day yesterday looking for a solution or work around. It is particularly bad timing with today being month end. Any thoughts/ideas/solutions would be appreciated.

[compumatic]

Amazon support just responded with: apologies yadda yadda yadda... In this case the specialized team has let us know that this issue has been recognized as a widespread issue, they are currently working hard to get this solved ASAP. apologies yadda yadda yadda...

good news is they acknowledge the issue, bad news is no resolution or timeline provided.

[compumatic]

it looks like this field is starting to populate again on new reports today, still waiting and hoping they will go back and fix prior report dates...

[call-me-ghosty]

We fixed this for several customers of ours, by just creating an md5-hash out of order-id and order-item-id and writing it into the shipment-item-id field. So we are getting an unique identifier like the one Amazon used to populate before.

[BCampanile]

call-me-ghostly: If Amazon adds back the shipment-item-id to the orders missing the data, your md-5 hash won't match theirs will it? Won't duplication occur?

[call-me-ghosty]

call-me-ghostly: If Amazon adds back the shipment-item-id to the orders missing the data, your md-5 hash won't match theirs will it? Won't duplication issues?

We are overwriting whatever is given in the field, by that we are just using our identifier for further logic

[compumatic]

I thought the issue is that more than one record can have the same order-id and order-item-id, so if you made a hash out of those values wouldn't that hash be the same for both records?

[call-me-ghosty]

I thought the issue is that more than one record can have the same order-id and order-item-id, so if you made a hash out of those values wouldn't that hash be the same for both records?

We did‘nt met this issue by now, but thanks for the hint.

[rosalie-Janssen]

I know Amazon started populating the reports again , but has anyone heard anything about the older data. Looks like anything from 3/23 until the fix day is still not populated.

[compumatic]

I gave up on waiting. I imported the records that were missing this field data to a temporary table and created my own unique record values for this field, then I processed them and moved on...

[JsonSong89]

I thought the issue is that more than one record can have the same order-id and order-item-id, so if you made a hash out of those values wouldn't that hash be the same for both records?

We did‘nt met this issue by now, but thanks for the hint.

you can't do that ,sometimes the one order item quantity_shipped is 2 but the shipment has two item with 1 quantity ,so the order-id order-item-id are same

[yogeshbablu89]

Issues seems to be fixed as of 04/14 even for older dates(03/21 to 03/31).

[johnkw]

Yes this does seem to be fixed.

FYI, while this bug was happening, we just ignored the records completely if they had a blank shipment-item-id. During the bug it seemed after some period the field was correctly being restored, so the net result was just our reports were being delayed by a few days.

[github-actions[bot]]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

[github-actions[bot]]

closed for inactivity