-
Notifications
You must be signed in to change notification settings - Fork 756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not get prepDetails for sku that contains '+' #4659
Comments
Oh that's interesting. Do you have to encode the + maybe? I think + may encode in HTML as %2B So if your SKU is ABC+123 you would say: ABC%2B123 You could try that? You could also try: ABC+123 I don't know if that's the cause, or if Amazon is just not accepting + but it's worth a shot. |
Sorry GitHub UN-encoded my second example. %2B = + But you can also do: & plus; (WITH NO SPACE AFTER & -- I had to do that so GitHub didn't display it as a +) |
Hi @neiloyv, |
Yes, thank you. Additional URL encoding helped. |
Some SKUs may exceed 40 in length after conversion, resulting in an error message [Member must have length less than or equal to 40,Member must have length greater than or equal to 1] |
We try to get prep details for the SKU that contains '+': "NEW+SKU 03.03.25"
We make Get request:
AWS CALL --> GET https://sellingpartnerapi-na.amazon.com/inbound/fba/2024-03-20/items/prepDetails?marketplaceId=ATVPDKIKX0DER&mskus=NEW%2BSKU%2003.03.25
and received that error message:
AWS CALL { "errors": [ { "code": "BadRequest", "message": "ERROR: The following MSKUs are not valid: [NEW SKU 03.03.25].", "details": "" } ]}
According to the error message, the SKU is [NEW SKU 03.03.25] - so there is no ‘+’ anymore. Does it mean that api uses the wrong SKU for the search?
The text was updated successfully, but these errors were encountered: