amzn / selling-partner-api-models

This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Apache License 2.0
571 stars 730 forks source link

[BUG] GET_FBA_ESTIMATED_FBA_FEES_TXT_DATA don't take marketplaceIds param into account #1308

Closed aaalekseev closed 7 months ago

aaalekseev commented 3 years ago

GET_FBA_ESTIMATED_FBA_FEES_TXT_DATA returns listings for all marketplaces regardless marketplaceIds param provided.

In the returned listings there is not marketplaceId property - so it is not possible to match listings with corresponding marketplaces.

yuql commented 3 years ago

GET /reports/2020-09-04/reports,type:GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE has same bug, marketplaceIds param invalid

ellis commented 3 years ago

Where I'm having a problem with this is in Europe, where we're getting the data for DE, ES, FR, IT, NL, SE, UK all mixed into a single report. Either the report add a column for marketplace or it should respect the marketplaceId parameter.

There is a currency column, which lets us unambiguously assign rows to SE and UK, but for the Euro countries, we'd need to try to lookup the titles, but that would be super inconvenient and not completely reliable.

@yuql I vaguely remember struggling with this problem too, and not finding a complete solution. I think the reason that the marketplaceId is ignored in the EU is because some rows are not specific to a country. But they really should make sure that the country is specified on every row where possible (I think there are some where it's probably just missing because of sloppy programming).

github-actions[bot] commented 2 years ago

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.

mott7 commented 2 years ago

This is still an issue rendering the report useless in the EU marketplace as there is no way to distinguish which marketplace the data relates to.

I agree with ellis's suggestion. Either add a column for marketplace or it should respect the marketplaceId parameter

Please fix.

AmandeepSingh179 commented 1 year ago

Facing the same issue. Can anyone from Amazon support team look into it?

IBee21 commented 1 year ago

This has been such a problem for years. Please fix it!!

mott7 commented 1 year ago

Ridiculous that this hasn't been fixed! Renders this report useless to anyone selling in multiple marketplaces with the same SKU.

@sungolivia @amazon please fix this by adding in a column with the marketplaceID

philsmy commented 1 year ago

Just to add my voice to this. I cannot see the point of this report given this issue.

mott7 commented 1 year ago

The ludicrous thing is that it would take 10 seconds for a developer at @amvreddy-amazon to fix

philsmy commented 1 year ago

There used to be a sneaky way to figure out which EUR marketplace it was because of the way they broke up charges but that seems to be gone. So we’re actually going backwards

nrueckmann commented 1 year ago

Still broken

github-actions[bot] commented 7 months ago

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] commented 7 months ago

closed for inactivity

JeffOfTheJungle commented 3 months ago

This should not be closed, it is still an issue with the report