[BUG] getInventorySummaries does not work if sellerSkus contain ',' character

[hamduc7]

The getInventorySummaries function cannot work if the SKU contains ",":

API: /fba/inventory/v1/summaries
granularityType=Marketplace
granularityId=NOT_IMPORTANT
marketplaceIds=A3KFBWWTZ2P8CN -->ANY MARKETPLACE
sellerSkus=abc,d

Note the 'abc,d' is an SKU

URL of the content on GitHub
https://developer-docs.amazon.com/sp-api/docs/fbainventory-api-v1-reference

Because the sellerSkus is a list of values, separated by a comma. But the SKU itself has a comma that causes a problem

How to solve this?

[hamduc7]

@puppsupr

[marvs]

Same issue here. We tried the following on the sellerSkus parameter but it still didn't work:

• Adding a backslash \ before the comma
• Using HTML encoding
• Using URL encoding
• Double URL encoding

[hamduc7]

This issue is important but still have not received any comment from Amazon

[Adrian-T-AMZN]

Hello @hamduc7,

Thank you for bringing this to our attention.

In order to correctly resolve this issue, please open a support case so we can pursue the investigation and provide the following details:

• Full request and full response of the API operation (Not truncated), file in .txt format
• Operation
• Timestamp
• Request ID
• Application ID

Once you do so, please post the Case ID so we can keep track of the situation.

Thanks,
Adrian T.
Selling Partner API Developer Support

[marolt]

Hi @Adrian-T-AMZN,

we opened a support case a while ago, but it did not get resolved.

Here is the response from the support:

I understand that you are having issues with SKU's with commas since the system does not recognize as valid parameters.

When using the SKU's, please avoid using the commas since this cause the system do not recognized the entries.

For more information I will suggest to review the following page:
https://developer-docs.amazon.com/sp-api/docs/fbainventory-api-v1-reference

Can you please take a look at this case log?
All the requested information is provided there.
CASE ID: 9784299241

Thanks!

[kennedyjustin]

This is still occurring, is there an eta for when we will get a fix similar to the searchCatalogItems fix?

[jesusvalle]

Same problem here. Those SKUs with commas cannot be ordered via searchCatalogItems, for example.

[VeskeR]

Bumping it up, having the same issue.
Seller has couple of products for which there is a comma “,” in the SKU, and we cannot make requests for such products using Search Catalog API

[jacobglanz]

Hi @Adrian-T-AMZN,

we opened a support case a while ago, but it did not get resolved.

Here is the response from the support:

I understand that you are having issues with SKU's with commas since the system does not recognize as valid parameters.

When using the SKU's, please avoid using the commas since this cause the system do not recognized the entries.

For more information I will suggest to review the following page:
https://developer-docs.amazon.com/sp-api/docs/fbainventory-api-v1-reference

Can you please take a look at this case log? All the requested information is provided there. CASE ID: 9784299241

Thanks!

You won't get a straight answer from their support team, they suck too. This a common problem and it's not going away soon, as they state on their website.

Solution: You should use the Reports API.
To replace the getInventorySummaries API, Use combination of the "GET_FBA_MYI_ALL_INVENTORY_DATA" and the "GET_RESERVED_INVENTORY_DATA" reports to get this data.

The problem is that Amazon uses a comma to separate 1 SKU from another (sku1,sku2,sku3), so when a SKU contains a comma (like this 'sk,u1') amazon will interoperate this 1 SKU into as 2 separate SKUs.

The first solution is to use ASIN instead of the SKU (A ASIN can't have a comma), and if the API doesn't accept ASIN than you should use the API report. And if there is no Report for that than I guess your screwed.

Yeps 2023

[lachesis]

This is insane. The MWS API didn't have this problem. We were all forced to switch to SP-API before they resolved this. We do not have any control over what SKUs our users select. This definitely needs to be fixed by Amazon.