Import JSON files - advanced settings

JSON (JavaScript Object Notation) is a human-readable format for exchanging data between systems. It consists of key-value pairs that can look similar to this: {"id": "1111"}. In this example, id is the attribute key, and 1111 is the attribute value. In a JSON file, every key is enclosed in double quotation marks. Every value can be a string, array, object, or number. If a value is a string, it is also enclosed in double quotation marks.

Here is an example of a typical JSON file that stores data for one product in one object:

{
    "id": "1111",
    "title": "Shirt",
    "size": "L",
    "price": "30 EUR",
    "stock": "5"
}

If a JSON file stores data for multiple products, the file contains an array that opens and closes with a square bracket. Inside the array, each product is an object that opens and closes with a curly bracket:

[
    {
        "id": "1111",
        "title": "Shirt",
        "size": "L",
        "price": "30 EUR",
        "stock": "5"
    },
    {
        "id": "2222",
        "title": "Pants",
        "size": "S",
        "price": "60 EUR",
        "stock": "3"
    }
]

You can import your raw JSON files into Productsup using the following data source options:

To read and interpret JSON files correctly, the platform parses them before uploading their contents to your site. To ensure that parsing goes smoothly, you can use various JSON settings while setting up your data source option.

Some JSON files have root nodes. A root node is a key that contains an array storing all your products. It serves as an entry point from which the platform should start importing products in your file.

The root node in the following example is products:

{ 
    "products": [
        {
            "id": "1111",
            "title": "Shirt",
            "size": "L",
            "price": "30 EUR",
            "stock": "5"
        },
        {
            "id": "2222",
            "title": "Pants",
            "size": "S",
            "price": "60 EUR",
            "stock": "3"
        }
    ]
}

To specify a root node for your JSON file:

If your products are available in multiple sizes or colors, your JSON file may store this data in variant keys in each product. In the following example, the variant key sizes-and-stock contains different sizes and the related stock data:

{
    "products": [
        {
            "id": "1111",
            "title": "Shirt",
            "price": "30 EUR",
            "sizes-and-stock": [
                {
                    "size": "L",
                    "stock": "5"
                },
                {
                    "size": "S",
                    "stock": "2"
                }
            ]
        },
        {
            "id": "2222",
            "title": "Pants",
            "price": "60 EUR",
            "sizes-and-stock": [
                {
                    "size": "L",
                    "stock": "3"
                },
                {
                    "size": "M",
                    "stock": "5"
                }
            ]
        }
    ]
}

When importing products with variant keys, the platform creates one row per product by default and adds new columns for all attributes and values stored within the variant key. This is why you get the following data in your site:

However, the platform can also import variant keys as separate product rows:

To let the platform import variant keys as separate product rows, use the Variant Node setting on the data source page:

A JSON file may have a key with an array that stores multiple values. For example, see the size key:

{
    "id": "1111",
    "title": "Shirt",
    "price": "30 EUR",
    "size": [
            "XS",
            "M",
            "L"
    ]

}

By default, the platform creates a new column for each value in the array and imports the data as follows:

However, you can bundle the repeating values into one column and let the platform import the data this way:

To bundle repeating values into one column:

You can let the platform exclude specific keys during import. For example, you may want the platform not to import the key updatedOn into your Productsup site:

{
  "id": "1111",
  "title": "Shirt",
  "size": "L",
  "updatedOn": "17.04.2023"
}

To let the platform skip an unneeded key:

Some export channels prefer uploading CSV files rather than JSON files. In these cases, you may want to transform your JSON file into a CSV file before Productsup imports it: