search

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
611 stars 735 forks source link

[BUG] [SP-API] [Issue] - feeds get stuck "IN_PROGRESS" causing complete stoppage of updates for days (i.e. Inventory) #2633

Closed akg397 closed 1 year ago

akg397 commented 1 year ago

I'm submitting a...

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

SP-API Name and Version or Report/Feed Type

JSON_LISTINGS_FEED

Expected Behavior

Expected Behavior: Feed processing should complete with DONE or Fatal

Current Behavior

On occasion feeds get stuck "IN_PROGRESS" status for several days. Examples of stuck FEEDID: 209297019528, 209541019529, 209542019529, 210348019546 I believe the stuck feed issue have higher chance of occurring if feeds contains updates to multiple data points. Probably update time out and cause feed to get stuck.

Context/Screenshots

Once a feed get stuck in "IN_PROGRESS" - no further feeds will process. Can't send any more updates like inventory. Stuck feeds can only be cancelled by support - turnaround on ticket is few days.

Your Environment

alixleger commented 1 year ago

Same issue here, a feed is currently stuck "IN_PROGRESS" for almost 60 hours, blocking all our processing queue...

akg397 commented 1 year ago

Same issue here, a feed is currently stuck "IN_PROGRESS" for almost 60 hours, blocking all our processing queue...

In my experience - Once it stuck for more than 10 minutes - it will be stuck forever. You can't abort processing on your own. You will to open ticket to support - seems to be 3 days turnarround, worst case is 10 days. Add feed number here - may be we can get someone to look at the root cause

rodrifed commented 1 year ago

Hi @akg397,

Thank you for your message.

We suggest that you take a look at the Feeds API best practices in order to optimize your feeds workflows, which should help you prevent issues like the one you describe.

Thank you, Federico Selling Partner Developer Services

akg397 commented 1 year ago

I did look at "best practices " there is no solution there.

Hi @akg397,

Thank you for your message.

We suggest that you take a look at the Feeds API best practices in order to optimize your feeds workflows, which should help you prevent issues like the one you describe.

Thank you, Federico Selling Partner Developer Services

Hi @akg397,

We suggest that you take a look at the Feeds API best practices in order to optimize your feeds workflows, which should help you prevent issues like the one you describe.

I did look at "best practices " there is no solution to there

limeng92 commented 4 months ago

Hello, I am a developer. I need to synchronize inventory to Amazon in batches. I use the feed API to upload XML and modify it synchronously. I try to test the API debugging function. However, the feed I submitted before (304792019903) can be processed normally. The feed I submitted today is always in the IN_PROGRESS state. Have you encountered such a problem? How do you deal with it? Thank you.

ritikacd commented 4 months ago

Hello, I am a developer. I need to synchronize inventory to Amazon in batches. I use the feed API to upload XML and modify it synchronously. I try to test the API debugging function. However, the feed I submitted before (304792019903) can be processed normally. The feed I submitted today is always in the IN_PROGRESS state. Have you encountered such a problem? How do you deal with it? Thank you.

Hi @limeng92 Thank you for reaching out.

Please review Feeds API best practices to optimize your feeds submissions, which should help you prevent issues.

Can you specify the Feed Type used? How many messages are included in the stuck feed request?

Thanks, Ritika Chaudhary Selling Partner Developer Services

akg397 commented 4 months ago

Hello, I am a developer. I need to synchronize inventory to Amazon in batches. I use the feed API to upload XML and modify it synchronously. I try to test the API debugging function. However, the feed I submitted before (304792019903) can be processed normally. The feed I submitted today is always in the IN_PROGRESS state. Have you encountered such a problem? How do you deal with it? Thank you.

Sounds like the original issue I was having a year ago still happening. I had to minimize use of Feeds to avoid having this issue.

In my experience this happens if you submit a lot of feeds, like 1 or 2 a day is fine, but over 100 feeds and you are risking something on backend to bug out. Support wasn't helpful and would just send you to documentation. At times it will take a week to get support to clear out stuck feed.

My guess there is some disk space limitation per account on Amazon server - if you submit a lot of large feeds - it will run out of allocation and single feed will fail in unexpected way and cause complete stoppage of processing

ritikacd commented 3 months ago

Hi Team,

We are deprecating XML and flat file listings data (including pricing, inventory, relationships and images) submitted via the Feeds API and will no longer provide new features or categories in the legacy category XML format. If you have an application that uses XML and flat file listings data, you have until March 31, 2025 to migrate to the JSON-based Listings Items APIs or the JSON_LISTINGS_FEED submitted via the Feeds API. This deprecation does not impact any listings feeds submitted by sellers directly through Seller Central.

I’d recommend using the JSON based Listings Items API or JSON_LISTINGS_FEED Feed type to manage your listings integration. If you still have issues with Feeds being stuck in the queue, we can investigate the reason. Sometimes a message within the Feeds request has some issues with the data that could also impact processing of the Feed.

Thank you, Ritika Selling Partner API Team.

limeng92 commented 3 months ago

Hello, I have a request here, that is, how to modify the product to a pre-sale product through the Amazon sp-api document, and add the pre-sale inventory and pre-sale arrival time. Or modify the available inventory of the product, which requires batch update. May I ask how I can modify it? Can you give a specific case or the address of the docking api document? Thank you.

At 2024-07-18 06:39:01, "Ritika Chaudhary" @.***> wrote:

Hi Team,

We are deprecating XML and flat file listings data (including pricing, inventory, relationships and images) submitted via the Feeds API and will no longer provide new features or categories in the legacy category XML format. If you have an application that uses XML and flat file listings data, you have until March 31, 2025 to migrate to the JSON-based Listings Items APIs or the JSON_LISTINGS_FEED submitted via the Feeds API. This deprecation does not impact any listings feeds submitted by sellers directly through Seller Central.

I’d recommend using the JSON based Listings Items API or JSON_LISTINGS_FEED Feed type to manage your listings integration. If you still have issues with Feeds being stuck in the queue, we can investigate the reason. Sometimes a message within the Feeds request has some issues with the data that could also impact processing of the Feed.

Thank you, Ritika Selling Partner API Team.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

ritikacd commented 3 months ago

to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***> Hi @limeng92 Can you please elaborate your use case? You can update inventory for a single product using the Listings Items API or batch using the JSON_LISTINGS_FEED.

Thank you, Ritika Selling Partner API Team

rugved1991 commented 3 months ago

Hi @limeng92,

Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster.

Best, Rugved Solutions Architect, SP-API

limeng92 commented 3 months ago

Hello, how can I use the feedType of JSON_LISTINGS_FEED to batch update the inventory data of sku? Can you give me an example? Thank you

At 2024-07-22 09:07:01, "Rugved Dighe" @.***> wrote:

Hi @limeng92,

Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster.

Best, Rugved Solutions Architect, SP-API

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

limeng92 commented 3 months ago

Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [

{

"fulfillment_channel_code": "AMAZON_EU",

"marketplace_id": "A1F83G8C2ARO7P"

},

{

"fulfillment_channel_code": "DEFAULT",

"quantity": 1,

"marketplace_id": "A1F83G8C2ARO7P"

}

] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products.

At 2024-07-22 08:50:02, "Ritika Chaudhary" @.***> wrote:

to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***> Hi @limeng92 Can you please elaborate your use case? You can update inventory for a single product using the Listings Items API or batch using the JSON_LISTINGS_FEED.

Thank you, Ritika Selling Partner API Team

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

limeng92 commented 3 months ago

Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [

{

"fulfillment_channel_code": "AMAZON_EU",

"marketplace_id": "A1F83G8C2ARO7P"

},

{

"fulfillment_channel_code": "DEFAULT",

"quantity": 1,

"marketplace_id": "A1F83G8C2ARO7P"

}

] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products.

At 2024-07-22 09:07:01, "Rugved Dighe" @.***> wrote:

Hi @limeng92,

Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster.

Best, Rugved Solutions Architect, SP-API

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

ritikacd commented 3 months ago

Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [ { "fulfillment_channel_code": "AMAZON_EU", "marketplace_id": "A1F83G8C2ARO7P" }, { "fulfillment_channel_code": "DEFAULT", "quantity": 1, "marketplace_id": "A1F83G8C2ARO7P" } ] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products. At 2024-07-22 09:07:01, "Rugved Dighe" @.> wrote: Hi @limeng92, Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster. Best, Rugved Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Hi @limeng92,

Fulfillment_channel_code represents the name of the fulfillment channel. The DEFAULT value for this attribute means it is an MFN inventoy, AMAZON_NA, AMAZON_EU, and AMAZON_JP are the region specific values for FBA inventory. Legacy XML Feed & Listings Items APIs and JSON_LISTINGS_FEEDs are used to update MFN inventory only. For managing FBA inventory, please use Fulfillment Inbound API.

Migration guide tutorial will help you submit inventory using the Listings API, be sure to check it out.

Thanks, Ritika Solutions Architect, SP-API

limeng92 commented 3 months ago

Thank you very much for your reply. I have another question, which is how to use JSON_LISTINGS_FEED to batch update the available inventory of sku and turn some sku into pre-sale products, filling in the pre-sale inventory + pre-sale arrival time? Here I give an example. If you have time, can you help me check whether the data format is correct? Thank you. I only need to update these data, and the others do not need to be updated

Example:

{ "header": {

"sellerId": "A1PP0FEH11Rxxxx", //shop ID

"version": "2.0"

},

"messages":

[{ "messageId": 1, "sku": "ssnm002", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", : 10 //Available Stock }] },

{ "messageId": 2, "sku": "ssnm003", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", "quantity": 10 //Pre-sale inventory "restockDate" 2024-08-01 //Pre-sale arrival time }]

}]

}

At 2024-07-24 03:59:42, "Ritika Chaudhary" @.***> wrote:

Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [ { "fulfillment_channel_code": "AMAZON_EU", "marketplace_id": "A1F83G8C2ARO7P" }, { "fulfillment_channel_code": "DEFAULT", "quantity": 1, "marketplace_id": "A1F83G8C2ARO7P" } ] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products. At 2024-07-22 09:07:01, "Rugved Dighe" @.> wrote: Hi @limeng92, Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster. Best, Rugved Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Hi @limeng92,

Fulfillment_channel_code represents the name of the fulfillment channel. The DEFAULT value for this attribute means it is an MFN inventoy, AMAZON_NA, AMAZON_EU, and AMAZON_JP are the region specific values for FBA inventory. Legacy XML Feed & Listings Items APIs and JSON_LISTINGS_FEEDs are used to update MFN inventory only. For managing FBA inventory, please use Fulfillment Inbound API.

Migration guide tutorial will help you submit inventory using the Listings API, be sure to check it out.

Thanks, Ritika Solutions Architect, SP-API

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

ritikacd commented 3 months ago

Thank you very much for your reply. I have another question, which is how to use JSON_LISTINGS_FEED to batch update the available inventory of sku and turn some sku into pre-sale products, filling in the pre-sale inventory + pre-sale arrival time? Here I give an example. If you have time, can you help me check whether the data format is correct? Thank you. I only need to update these data, and the others do not need to be updated Example: { "header": { "sellerId": "A1PP0FEH11Rxxxx", //shop ID "version": "2.0" }, "messages": [{ "messageId": 1, "sku": "ssnm002", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", : 10 //Available Stock }] }, { "messageId": 2, "sku": "ssnm003", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", "quantity": 10 //Pre-sale inventory "restockDate" 2024-08-01 //Pre-sale arrival time }] }] } At 2024-07-24 03:59:42, "Ritika Chaudhary" @.> wrote: Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [ { "fulfillment_channel_code": "AMAZON_EU", "marketplace_id": "A1F83G8C2ARO7P" }, { "fulfillment_channel_code": "DEFAULT", "quantity": 1, "marketplace_id": "A1F83G8C2ARO7P" } ] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products. At 2024-07-22 09:07:01, "Rugved Dighe" @.> wrote: Hi @limeng92, Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster. Best, Rugved Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Hi @limeng92, Fulfillment_channel_code represents the name of the fulfillment channel. The DEFAULT value for this attribute means it is an MFN inventoy, AMAZON_NA, AMAZON_EU, and AMAZON_JP are the region specific values for FBA inventory. Legacy XML Feed & Listings Items APIs and JSON_LISTINGS_FEEDs are used to update MFN inventory only. For managing FBA inventory, please use Fulfillment Inbound API. Migration guide tutorial will help you submit inventory using the Listings API, be sure to check it out. Thanks, Ritika Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Hi @limeng92

There are some required attributes that are missing from your payload, such as ASIN and condition type. We recommend that you get latest JSON Schema for required and conditional required attribute to creating an offer using Product Type Definitions API. Make a call to getDefinitionsProductType using the PRODUCT product type and LISTING_OFFER_ONLY as the value for the requirements parameter to get the required attributes.

Here's the sample payload for creating inventory with restock date for JSON_LISTINGS_FEED feed type: 

{
  "header": {
    "sellerId": "AXXXXXXXXXXXXX",
    "version": "2.0",
    "issueLocale": "en_US"
  },
  "messages": [
    {
      "messageId": 1,
      "sku": "ABC123",
      "operationType": "UPDATE",
      "productType": "PRODUCT",
      "requirements": "LISTING_OFFER_ONLY",
      "attributes": {
        "condition_type": [
          {
            "value": "new_new",
            "marketplace_id": "ATVPDKIKX0DER"
          }
        ],
        "merchant_suggested_asin": [
          {
            "value": "BXXXXXXXXX",
            "marketplace_id": "ATVPDKIKX0DER"
          }
        ],
        "fulfillment_availability": [
          {
            "fulfillment_channel_code": "DEFAULT",
            "quantity": 5,
            "restock_date": "2024-07-31"
          }
        ],
        ... (more attributes, if applicable)
      }
    },
    ... (more messages, if applicable)
  ]
}

This sample payload will help you build your production payload. Before submitting the data through Feeds API, you can also test your Listings submission payload using VALIDATION_PREVIEW mode. See more details here.

Hope this helps!

Thanks, Ritika Selling Partner API Team

limeng92 commented 3 months ago

Thank you very much for your reply, thank you

At 2024-07-27 05:22:13, "Ritika Chaudhary" @.***> wrote:

Thank you very much for your reply. I have another question, which is how to use JSON_LISTINGS_FEED to batch update the available inventory of sku and turn some sku into pre-sale products, filling in the pre-sale inventory + pre-sale arrival time? Here I give an example. If you have time, can you help me check whether the data format is correct? Thank you. I only need to update these data, and the others do not need to be updated Example: { "header": { "sellerId": "A1PP0FEH11Rxxxx", //shop ID "version": "2.0" }, "messages": [{ "messageId": 1, "sku": "ssnm002", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", : 10 //Available Stock }] }, { "messageId": 2, "sku": "ssnm003", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", "quantity": 10 //Pre-sale inventory "restockDate" 2024-08-01 //Pre-sale arrival time }] }] } At 2024-07-24 03:59:42, "Ritika Chaudhary" @.> wrote: Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [ { "fulfillment_channel_code": "AMAZON_EU", "marketplace_id": "A1F83G8C2ARO7P" }, { "fulfillment_channel_code": "DEFAULT", "quantity": 1, "marketplace_id": "A1F83G8C2ARO7P" } ] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products. At 2024-07-22 09:07:01, "Rugved Dighe" @.> wrote: Hi @limeng92, Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster. Best, Rugved Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Hi @limeng92, Fulfillment_channel_code represents the name of the fulfillment channel. The DEFAULT value for this attribute means it is an MFN inventoy, AMAZON_NA, AMAZON_EU, and AMAZON_JP are the region specific values for FBA inventory. Legacy XML Feed & Listings Items APIs and JSON_LISTINGS_FEEDs are used to update MFN inventory only. For managing FBA inventory, please use Fulfillment Inbound API. Migration guide tutorial will help you submit inventory using the Listings API, be sure to check it out. Thanks, Ritika Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Hi @limeng92

There are some required attributes that are missing from your payload, such as ASIN and condition type. We recommend that you get latest JSON Schema for required and conditional required attribute to creating an offer using Product Type Definitions API. Make a call to getDefinitionsProductType using the PRODUCT product type and LISTING_OFFER_ONLY as the value for the requirements parameter to get the required attributes.

Here's the sample payload for creating inventory with restock date for JSON_LISTINGS_FEED feed type:

{ "header": { "sellerId": "AXXXXXXXXXXXXX", "version": "2.0", "issueLocale": "en_US" }, "messages": [ { "messageId": 1, "sku": "ABC123", "operationType": "UPDATE", "productType": "PRODUCT", "requirements": "LISTING_OFFER_ONLY", "attributes": { "condition_type": [ { "value": "new_new", "marketplace_id": "ATVPDKIKX0DER" } ], "merchant_suggested_asin": [ { "value": "BXXXXXXXXX", "marketplace_id": "ATVPDKIKX0DER" } ], "fulfillment_availability": [ { "fulfillment_channel_code": "DEFAULT", "quantity": 5, "restock_date": "2024-07-31" } ], ... (more attributes, if applicable) } }, ... (more messages, if applicable) ] }

This sample payload will help you build your production payload. Before submitting the data through Feeds API, you can also test your Listings submission payload using VALIDATION_PREVIEW mode. See more details here.

Hope this helps!

Thanks, Ritika Selling Partner API Team

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

limeng92 commented 3 months ago

Hello, I have another requirement, which is to update the inventory information of Amazon vc in batches. Which API should I call? Can you give me an example, or I can give you a case, and you can help me see if it is feasible. Thank you.

Looking forward to your reply。

example：

marketplaceIds=ATVPDKIKX0xxxx

api:https://sellingpartnerapi-na.amazon.com/vendor/directFulfillment/inventory/v1/warehouses/{warehouseId}/items

{ "inventory": { "sellingParty": { "partyId": "096xx" }, "isFullUpdate": false, "items": [ { "vendorProductIdentifier": "ZLBVC-HLF1xxx", "availableQuantity": { "amount": 6, "unitOfMeasure": "Each" }, "isObsolete": false }, { "vendorProductIdentifier": "ZLBVC-HLF2xxx", "availableQuantity": { "amount": 79, "unitOfMeasure": "ullamco" }, "isObsolete": false }, { "vendorProductIdentifier": "ZLBVC-HLF3xxx", "availableQuantity": { "amount": 0, "unitOfMeasure": "Each" }, "isObsolete": false }, ] } }

At 2024-07-27 05:22:13, "Ritika Chaudhary" @.***> wrote:

Thank you very much for your reply. I have another question, which is how to use JSON_LISTINGS_FEED to batch update the available inventory of sku and turn some sku into pre-sale products, filling in the pre-sale inventory + pre-sale arrival time? Here I give an example. If you have time, can you help me check whether the data format is correct? Thank you. I only need to update these data, and the others do not need to be updated Example: { "header": { "sellerId": "A1PP0FEH11Rxxxx", //shop ID "version": "2.0" }, "messages": [{ "messageId": 1, "sku": "ssnm002", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", : 10 //Available Stock }] }, { "messageId": 2, "sku": "ssnm003", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", "quantity": 10 //Pre-sale inventory "restockDate" 2024-08-01 //Pre-sale arrival time }] }] } At 2024-07-24 03:59:42, "Ritika Chaudhary" @.> wrote: Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [ { "fulfillment_channel_code": "AMAZON_EU", "marketplace_id": "A1F83G8C2ARO7P" }, { "fulfillment_channel_code": "DEFAULT", "quantity": 1, "marketplace_id": "A1F83G8C2ARO7P" } ] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products. At 2024-07-22 09:07:01, "Rugved Dighe" @.> wrote: Hi @limeng92, Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster. Best, Rugved Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Hi @limeng92, Fulfillment_channel_code represents the name of the fulfillment channel. The DEFAULT value for this attribute means it is an MFN inventoy, AMAZON_NA, AMAZON_EU, and AMAZON_JP are the region specific values for FBA inventory. Legacy XML Feed & Listings Items APIs and JSON_LISTINGS_FEEDs are used to update MFN inventory only. For managing FBA inventory, please use Fulfillment Inbound API. Migration guide tutorial will help you submit inventory using the Listings API, be sure to check it out. Thanks, Ritika Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Hi @limeng92

There are some required attributes that are missing from your payload, such as ASIN and condition type. We recommend that you get latest JSON Schema for required and conditional required attribute to creating an offer using Product Type Definitions API. Make a call to getDefinitionsProductType using the PRODUCT product type and LISTING_OFFER_ONLY as the value for the requirements parameter to get the required attributes.

Here's the sample payload for creating inventory with restock date for JSON_LISTINGS_FEED feed type:

{ "header": { "sellerId": "AXXXXXXXXXXXXX", "version": "2.0", "issueLocale": "en_US" }, "messages": [ { "messageId": 1, "sku": "ABC123", "operationType": "UPDATE", "productType": "PRODUCT", "requirements": "LISTING_OFFER_ONLY", "attributes": { "condition_type": [ { "value": "new_new", "marketplace_id": "ATVPDKIKX0DER" } ], "merchant_suggested_asin": [ { "value": "BXXXXXXXXX", "marketplace_id": "ATVPDKIKX0DER" } ], "fulfillment_availability": [ { "fulfillment_channel_code": "DEFAULT", "quantity": 5, "restock_date": "2024-07-31" } ], ... (more attributes, if applicable) } }, ... (more messages, if applicable) ] }

This sample payload will help you build your production payload. Before submitting the data through Feeds API, you can also test your Listings submission payload using VALIDATION_PREVIEW mode. See more details here.

Hope this helps!

Thanks, Ritika Selling Partner API Team

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

ritikacd commented 3 months ago

Hello, I have another requirement, which is to update the inventory information of Amazon vc in batches. Which API should I call? Can you give me an example, or I can give you a case, and you can help me see if it is feasible. Thank you. Looking forward to your reply。 example： marketplaceIds=ATVPDKIKX0xxxx api:https://sellingpartnerapi-na.amazon.com/vendor/directFulfillment/inventory/v1/warehouses/{warehouseId}/items { "inventory": { "sellingParty": { "partyId": "096xx" }, "isFullUpdate": false, "items": [ { "vendorProductIdentifier": "ZLBVC-HLF1xxx", "availableQuantity": { "amount": 6, "unitOfMeasure": "Each" }, "isObsolete": false }, { "vendorProductIdentifier": "ZLBVC-HLF2xxx", "availableQuantity": { "amount": 79, "unitOfMeasure": "ullamco" }, "isObsolete": false }, { "vendorProductIdentifier": "ZLBVC-HLF3xxx", "availableQuantity": { "amount": 0, "unitOfMeasure": "Each" }, "isObsolete": false }, ] } } At 2024-07-27 05:22:13, "Ritika Chaudhary" @.> wrote: Thank you very much for your reply. I have another question, which is how to use JSON_LISTINGS_FEED to batch update the available inventory of sku and turn some sku into pre-sale products, filling in the pre-sale inventory + pre-sale arrival time? Here I give an example. If you have time, can you help me check whether the data format is correct? Thank you. I only need to update these data, and the others do not need to be updated Example: { "header": { "sellerId": "A1PP0FEH11Rxxxx", //shop ID "version": "2.0" }, "messages": [{ "messageId": 1, "sku": "ssnm002", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", : 10 //Available Stock }] }, { "messageId": 2, "sku": "ssnm003", "productType": "PRODUCT", "fulfillmentAvailability": [{ "fulfillmentChannelCode": "DEFAULT", "quantity": 10 //Pre-sale inventory "restockDate" 2024-08-01 //Pre-sale arrival time }] }] } At 2024-07-24 03:59:42, "Ritika Chaudhary" @.> wrote: Why can the sku in the fba mode be successfully modified by submitting the xml data of the feed, and the "fulfillment_availability" under attributes in the returned data is queried through the /listings/2021-08-01/items/Axxxx/skuxxxxx interface under sp-api: [ { "fulfillment_channel_code": "AMAZON_EU", "marketplace_id": "A1F83G8C2ARO7P" }, { "fulfillment_channel_code": "DEFAULT", "quantity": 1, "marketplace_id": "A1F83G8C2ARO7P" } ] What does this data structure mean? The quantity appears after the modification, but not before the modification. Does this mean that the inventory modification is successful? But doesn't it mean that the fba mode cannot modify the inventory? What does quantity mean? So if the inventory modification is successful, will it affect the delivery? Why can the fba inventory be modified successfully? Isn't it not allowed to be modified successfully? The reason why I use XML to modify inventory in batches is that there are too many fields in the JSON_LISTINGS_FEED type case without annotations, and I don't know what they mean, so I don't use this type of operation. If annotations and cases can be provided, it would be perfect. I need to modify inventory in batches or modify the products to pre-sale products + the arrival time of pre-sale products. At 2024-07-22 09:07:01, "Rugved Dighe" @.> wrote: Hi @limeng92, Are you looking to set a future date to release a product? You should be able to use "merchant_release_date" attribute from the JSON schema to set a future date when the item will go live on Amazon. This is the first date on which a merchant can deliver a pre-orderable product (one that has never been available prior to this date) to a customer. You can use this attribute in 1x1 API calls using the GET or PATCH Listings API call. Or you can use the JSON_LISTINGS_FEED to submit or update this attribute in bulk. We recommend that if you are updating more than 1500 items in 5 mins then use the JSON_LISTINGS_FEED. Anything less than that, 1x1 API call would be faster. Best, Rugved Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Hi @limeng92, Fulfillment_channel_code represents the name of the fulfillment channel. The DEFAULT value for this attribute means it is an MFN inventoy, AMAZON_NA, AMAZON_EU, and AMAZON_JP are the region specific values for FBA inventory. Legacy XML Feed & Listings Items APIs and JSON_LISTINGS_FEEDs are used to update MFN inventory only. For managing FBA inventory, please use Fulfillment Inbound API. Migration guide tutorial will help you submit inventory using the Listings API, be sure to check it out. Thanks, Ritika Solutions Architect, SP-API — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Hi @limeng92 There are some required attributes that are missing from your payload, such as ASIN and condition type. We recommend that you get latest JSON Schema for required and conditional required attribute to creating an offer using Product Type Definitions API. Make a call to getDefinitionsProductType using the PRODUCT product type and LISTING_OFFER_ONLY as the value for the requirements parameter to get the required attributes. Here's the sample payload for creating inventory with restock date for JSON_LISTINGS_FEED feed type: { "header": { "sellerId": "AXXXXXXXXXXXXX", "version": "2.0", "issueLocale": "en_US" }, "messages": [ { "messageId": 1, "sku": "ABC123", "operationType": "UPDATE", "productType": "PRODUCT", "requirements": "LISTING_OFFER_ONLY", "attributes": { "condition_type": [ { "value": "new_new", "marketplace_id": "ATVPDKIKX0DER" } ], "merchant_suggested_asin": [ { "value": "BXXXXXXXXX", "marketplace_id": "ATVPDKIKX0DER" } ], "fulfillment_availability": [ { "fulfillment_channel_code": "DEFAULT", "quantity": 5, "restock_date": "2024-07-31" } ], ... (more attributes, if applicable) } }, ... (more messages, if applicable) ] } This sample payload will help you build your production payload. Before submitting the data through Feeds API, you can also test your Listings submission payload using VALIDATION_PREVIEW mode. See more details here. Hope this helps! Thanks, Ritika Selling Partner API Team — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Hi @limeng92,

This issue has been closed, so it's cumbersome to track updates here. Could you please submit a new GitHub issue ticket?

Thank you, Ritika Selling Partner API Team

limeng92 commented 2 months ago

Hello, I have a feed that has been stuck in IN_PROGRESS state for several hours after submission. The update type is POST_INVENTORY_AVAILABILITY_DATA and the feedID is 441639019950.

rodrifed commented 2 months ago

Hi @limeng92,

In order to troubleshoot feed submission errors, we kindly ask you to contact developer support by using this link. Our support team will be able to help you with this.

Thank you, Federico Selling Partner Developer Services