Submit online product inventory update feeds

Submit online product inventory update feeds

Here is how you create a feed file using a spreadsheet program.
Important

Not everyone has this feature yet. If you don’t, don’t worry - it's coming soon!

For product attributes that you update frequently, like price, availability, sale price, and sale price effective date, you can easily make updates using online product inventory update feeds. While you will still need to submit your full product feed at least once every 30 days, you can use the update feed for the specific attributes that are already in your full product feed: price, availability, sale price, and sale price effective date.

Why should I use the online product inventory update feed?

  • Allows for faster processing for frequently changing attributes.
  • Keeps your product ads data up-to-date.
  • Allows the option to submit only offers that have changed.

When should I use the online product inventory update feed?

There are two different feed types you can use to upload your product data. The first is the main product feed file for your product data for Bing Merchant Center, which should be submitted at least every 30 days. Any time you upload a new product feed file, it overwrites the previous uploads.

On the other hand, you want to use the online product inventory update feed when you want to update only price, availability, sale price, and sale price effective date that’s already been submitted in your main product feed file. This means:

  • You can update the price, availability, sale price, and sale price effective date quickly and frequently.
  • You can make updates only to these attributes without having to update the entire feed file.
  • If there is an error with the update feed file, it won’t impact the main product feed file.

Submitting an online product inventory update feed

The online product inventory update feed can be uploaded manually through the update feed tab or via FTP. Once the feed has been processed, the report will be available in the update feed tab on the top banner.
When submitting via FTP:

  • The file name must be in the following format: inventoryfeed_{market}.txt (for example, inventoryfeed_enus.txt).
  • The supported market values are enus, enuk, dede, frfr, enau, enca, and enin.
  • The file name is case sensitive.
  • If you send the file with a zip file, both the zip file name and the file name must follow the naming format above.

The feed contains five attributes, as detailed below.

Attribute What it is Required in txt header row? Can value be blank?
'id' The ID of the product that will be updated. The ID must match the ID provided in the full product feed file. Yes No
'price' The price submitted here overrides the price from the last submission of the product feed file. If price is submitted, the value cannot be blank. No changes will be made if the value is blank and you’ll receive the following error message:
Offer cannot be updated as price cannot be blank. Please add a valid price value.
No No
'availability' The availability submitted here overrides the availability from the last submission of the product feed file. If availability is submitted, the value cannot be blank. No changes will be made if the value is blank and you’ll receive the following error message:
Offer cannot be updated as availability cannot be blank. Please add a valid availability value.
No No
'sale price' and 'sale price effective date' The sale price and sale price effective date submitted here overrides what was last submitted from the product feed file. If blank values are submitted, it will void the previous sale details submitted from the last product feed file. No Yes

Example submissions of the online product inventory update feed

Update priceexpando image
id price
Offer1 20
Update availabilityexpando image
id availability
Offer2 Out of stock
Update sale price and sale price effective dateexpando image
id sale_price sale_price_effective_date
Offer3 30 2017-01-01T00:00/2017-04-30T00:00
Void sale priceexpando image
id sale_price sale_price_effective_date
Offer4

File format requirements

  • File must be tab delimited plain text with extensions: .txt, .zip, .gz, .gzip, .tar.gz, .tgz.
    - .xml files are also accepted (if Google-formatted).
  • The file name must be in the following format: inventoryfeed_{market}.txt (for example, inventoryfeed_enus.txt).
  • If uploading via FTP, the file name of .txt or .xml files have to match the file name specified for a catalog’s settings.
    In the case of compressed text format, the compressed .txt file inside the archive (.zip, .gz, .gzip, .tar.gz, .tgz) must have the matching file name.
  • File must start with a single header row
  • Each product offer has to be on a separate line of the file
  • Do not include HTML in the text files
  • Do not include trailing tabs at the end of lines
  • Do not include tabs or line breaks in the middle of offer attributes
  • Special/Invalid characters will cause processing problems. Learn more about Accepted Symbols in Feed Files next

Accepted symbols in feed files

Here are the symbols/special characters and what attribute they are accepted in.

Symbols Where you can use
Period [.] Prices, URLs
Colon [:]
Question [?]
Forward-slash [/]
Equal [=]
URLs
Hyphen [-] Offer Identifiers where this is valid (eg: ISBN, MPN)
Pipe [|]
Comma [,]
Greater [>]
Multi-value fields (MerchantCategory, B_Category, Bingads_label)
Any Unicode symbol Brand, Title, Description

See more videos...