Skip to content
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

hit error 'The following MSKUs are not available for inbound' when calling function -> CreateShipmentPlan #4552

Open
kidd0203 opened this issue Jan 22, 2025 · 2 comments
Assignees
Labels
answer in docs The answer can be found in documentation FBA Inbound Issues related to FBA Inbound APIs

Comments

@kidd0203
Copy link

Remember that in the v0 of the inbound fulfillment API, the SKU will be converted to FBA automatically if it is not when calling function -> CreateShipmentPlan. But in the version 2024-3-20, I hit error 'The following MSKUs are not available for inbound'.
I can't find any API function to convert the item to FBA. the only choice I have is to do it manually in the amazon seller central.

@puppsupr puppsupr self-assigned this Jan 22, 2025
@puppsupr puppsupr added answer in docs The answer can be found in documentation FBA Inbound Issues related to FBA Inbound APIs labels Jan 22, 2025
@lucasrossell
Copy link

They have informed us previously that you'll need to update all the old listings either on Seller Central or by using the endpoint putListingsItem from the listingsItems API

@puppsupr
Copy link

puppsupr commented Jan 22, 2025

Hi kidd0203,
The new APIs doen't generate FNSKU. The pre-req to use the FBA Inbound v2024 APIs is to convert your listings to FBA listings using JSON Listings Feeds API or Listings API or the Seller Central UI. This is expected behavior. You can't create an FBA shipment without first having made a SKU be an FBA SKU.

Sample request ->

  1. Using Listings Items API: Perform a PATCH operation on the listing:

    • Endpoint: /listings/2021-08-01/items/:sellerId/:sku?marketplaceIds=marketplaceIds&issueLocale=en_US
    • Request Body:

{
"productType":"PRODUCT",
"patches":[
{
"op":"add",
"path":"/attributes/fulfillment_availability",
"value":[
{
"fulfillment_channel_code":"AMAZON_NA" // as per region
}
]
},
{
"op":"delete",
"path":"/attributes/fulfillment_availability",
"value":[
{
"fulfillment_channel_code":"DEFAULT"
}
]
}
]
}

  1. Using JSON Listings Feed:

{
"header":{
"sellerId":"xxxxxxxxxx",
"version":"2.0",
"issueLocale":"en_US"
},
"messages":[
{
"messageId":1,
"sku":"xx-xxx-xxxx",
"operationType":"PATCH",
"productType":"PRODUCT",
"patches":[
{
"op":"add",
"path":"/attributes/fulfillment_availability",
"value":[
{
"fulfillment_channel_code":"AMAZON_NA" // as per region
}
]
},
{
"op":"delete",
"path":"/attributes/fulfillment_availability",
"value":[
{
"fulfillment_channel_code":"DEFAULT"
}
]
}
]
}
]
}

Set the fulfillment-center-id to the appropriate region:

  • AMAZON_NA, AMAZON_EU, AMAZON_IN, or AMAZON_JP depending on the seller's marketplace.

@puppsupr puppsupr added the closing soon This issue will be closed soon label Jan 22, 2025
@github-actions github-actions bot removed the closing soon This issue will be closed soon label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answer in docs The answer can be found in documentation FBA Inbound Issues related to FBA Inbound APIs
Projects
None yet
Development

No branches or pull requests

3 participants