Importing product feed to catalogs

Custom import type ensures more freedom as you select an endpoint or more endpoints to which data are sent.

This article describes a use case of importing a product feed to a catalog and for that the custom import type is used.

Why Custom import instead of Product feed import type?

Product feed import type is used to import a XML file for the needs of AI recommendations. Whereas custom import type is used to create a catalog with products.

Requirements


Only for this use case:

  • Prepare a sample XML file. It must include a probe of products (few or many more) included in the product feed.
    Tip: Products in the product feed can have various groups of attributes. That is way it’s important to choose the full range of attributes in the sample file. Example: If you want to import <g:sale_price> attribute to a catalog and only part of the products is assigned to this attribute, then the sample file must contain at least one product with this attribute (<g:sale_price>). Otherwise it will be missed during the mapping.
  • Include in a sample file anitem_key column. In the case of product feeds, the item key is usually an ID of a product (g:id or g:item_group_id). Remember! The values in the item key column must be consistent with the product ID on the website (og:tags) and in transactions.
  • Create a catalog.

Procedure


  1. Go to Settings icon Settings > Import > New import.

  2. Select the Custom import type.

  3. If your feed is available under the link, select Pull - SFTP or API method (you can read more about this method here).

  4. Enter the name of your import (it’s visible only on the list of imports).

  5. In the Access section, choose the GET method and in the Endpoint URL field, enter the product feed URL.

  6. Confirm with the Apply button.

  7. In the Schedule section, define the frequency of importing the feed.

  8. Confirm with the Apply button.

  9. In the Sample file section, upload an XML sample file.

  10. Confirm with the Apply button.

  11. To proceed, click Next.
    Result: You are directed to the mapping view.

  12. On the left side of the screen, click Add endpoint.
    Result: A dropdown list shows.

  13. From the dropdown list select the Upload to catalog endpoint.

  14. To define columns that will show in the catalog, match the fields from the left side with the attributes. Use Auto mapping option.

    A file before mapping
    A file before mapping

    Result: All attributes are mapped and the columns in the catalog will have the same names as the attributes.

    A file after auto mapping
    A file after auto mapping
  15. You can still make some changes:

    • Delete a column from mapping (if you don’t want to include all attributes from the product feed).
    • Add a new column
      1. In the Add field field, enter the name of the column. It must contain value. prefix (example: value.new_column).
      2. Map the newly added field with any attribute by connecting the field and the attribute with a line.
    • Add a new attribute
  16. Define the item key of a catalog. It means defining a column that will be the key used to refer to a catalog. Map the Item Key from the Required list with the attribute.

    Note: In the case of product feeds, the item key is usually an ID of a product (g:id or g:item_group_id). Remember! The values in the item key column must be consistent with the product ID on the website (og:tags) and in transactions.

  17. Add a new column:

    1. Click Add input.
    2. In the Input name field, enter the name of the catalog.
    3. In the Plain text field, enter the ID of the catalog (it’s the numerical value at the end of the link to the catalog).
    4. Click Save.
  18. Map the newly added column (with the catalog) with the Bag Id (the Optional list > Additional Data).

  19. If the attributes are mapped, to proceed, click Next.
    Result: A preview of mapping is displayed.

  20. Check if the transformation of attributes is correct.

  21. To start imports, on the left side, click Run import.
    Results:

  • The attributes from a sample file are imported to the catalog.
  • Product feed will be imported periodically according to the settings in the Schedule section and data will be added to the catalog. If a product is removed from the feed, this product will stay in the catalog anyway.
  • You can check the status of imports in the Progress section.
😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.