Purpose of the document

This article describes the technical requirements for the JSON feed (file) used to transfer your product catalog to Pricer24.
General principles for working with feeds, supported data formats, and transfer methods are described in this article.

General Requirements

You provide the feed URL, and Pricer24 regularly downloads the file with your product catalog from this link.

• Compression: not required. If needed, use gzip.
• Size limit: none.

The feed (file) must contain the complete and up-to-date product catalog. After the file is downloaded, Pricer24 automatically compares it with the current catalog and updates only what is needed.
Only the products that are present in the feed (file) at the time it is downloaded are considered up to date.

JSON feed example:

This is an example of what a feed may look like. The detailed structure and requirements for the feed fields are described below.

{
  "categories": [
    { "id": "1000", "parent_id": null, "name": "Groceries" },
    { "id": "1001", "parent_id": "1000", "name": "Confectionery" },
    { "id": "1002", "parent_id": "1001", "name": "Chocolate" }
  ],
  "price_types": [
    { "id": "1", "name": "Warsaw Store 1" },
    { "id": "2", "name": "Warsaw Store 2" },
    { "id": "3", "name": "Krakow Store 1" },
    { "id": "4", "name": "Online" }
  ],
  "properties": [
    { "id": "weight", "name": "Weight (kg)", "type": "decimal" },
    { "id": "stock", "name": "Stock quantity", "type": "int" },
    { "id": "follow_rrp", "name": "Follow RRP", "type": "bool"},
    { "id": "category_manager", "name": "Category manager", "type": "string" }
  ],
  "products": [
    {
      "id": "153",
      "category_id": "1002",
      "name": "Baltic Cocoa Dark Chocolate 70% 100g",
      "vendor": "Baltic Cocoa",
      "vendor_code": "BC-DC70-100",       
      "barcode": "0000000000001",
      "link": "https://example.com/products/baltic-cocoa-dark-chocolate-70-100g",
      "image_link": "https://example.com/products/baltic-cocoa-dark-chocolate-70-100g.jpg",
      "availability": "+",
      "prices": [
        		{ "price_type_id": "1", "price": 9.99, "currency": "PLN" },
        		{ "price_type_id": "2", "price": 9.49, "currency": "PLN" }
      ],
      "properties": {"weight": 0.100, "stock": 20, "follow_rrp": true, "category_manager": "John Smith"}
     },
    {
      "id": "154",
      "category_id": "1002",
      "name": "Vistula Milk Chocolate with Hazelnuts 100g",
      "vendor": "Vistula Sweets",
      "vendor_code": "VS-MH-100",
      "barcode": "0000000000002",
      "link": "https://example.com/products/vistula-milk-chocolate-hazelnuts-100g",
      "image_link": "https://example.com/products/vistula-milk-chocolate-hazelnuts-100g.jpg",
      "availability": "-",
      "prices": [
        		{ "price_type_id": "3", "price": 8.00, "currency": "PLN" },
        		{ "price_type_id": "4", "price": 8, "currency": "PLN" }
      ],
      "properties": {"weight": 0.100, "stock": 0, "follow_rrp": false, "category_manager": "John Smith"}
    }
  ]
}

Feed structure

At the top level, the JSON feed consists of four arrays: categories, price types, properties, and products.

• categories: product category structure
• price_types: dictionary of price types referenced by product prices
• properties: additional custom fields not covered by the base contract
• products: detailed product catalog

{
"categories": [ ... ],
"price_types": [ ... ],
"properties": [ ... ],
"products": [ ... ]
}

The categories[ ] array:

The categories[ ] array is used to transfer all product categories in the same hierarchy as they exist in your catalog, for example: Pet food → Cat food → Dry cat food → …
The nesting depth should match your own catalog.
The relationship between categories at different levels is set through parent_id.

Data format of the categories[ ] array:

Example of the categories[ ] array:

"categories": 
[
  { "id": "1000", "parent_id": null, "name": "Groceries" },
  { "id": "1001", "parent_id": "1000", "name": "Confectionery" },
  { "id": "1002", "parent_id": "1001", "name": "Chocolate" },
    ...
    ...
  { "id": "100Х", "parent_id": "100(Х-1)", "name": "Dark Chocolate"},
  { "id": "100(Х+1)", "parent_id": "100Х", "name": "Dark Chocolate 100g" }
]

The price_types[ ] array:

In the price_types[ ], you define the price types you want to synchronize with our system.
These can be standard price types or prices at specific retail locations or sales channels.
For example:

• retail price
• recommended retail price
• promotional price
• wholesale price
• purchase price
• price of a specific sales channel

Data format of the price_types[ ] array:

Examples of the price_types[ ] array:

[ { "id": "1", "name": "My price" } ]

[ { "id": "1", "name": "Retail price" }, 
  { "id": "2", "name": "Promotional price" }, 
  { "id": "3", "name": "RRP" } ]

[ { "id": "XXXX", "name": "Krakow Store" }, 
  { "id": "YYYY", "name": "Online" } ]

The properties[ ] array:

In the properties[ ] array, you define additional fields, their names, and types, used to synchronize supplementary data. This can include: product stock quantities, the ID or name of the department responsible for the product, the ID or name of the category manager, and so on — any additional information needed for the project.

Data format of the properties[ ] array:

Any property with a different type will be ignored by the system.

Examples of the properties[ ] array:

[ { "id": "weight", "name": "Weight (kg)", "type": "decimal" } ]

[ { "id": "stock", "name": "Stock quantity", "type": "int" } ]

[ { "id": "follow_rrp", "name": "Follow RRP", "type": "bool"}, 
  { "id": "category_manager", "name": "Category manager", "type": "string" } ]

The actual property values are set for each product in the products[ ] array.

The products[ ] array:

The products[ ] array is the main part of the feed: this is where all your products, their characteristics, availability, and prices are transferred.

Data format of the products[ ] array:

It is by the id that Pricer24 determines whether an existing record should be updated or a new one should be created.
The product name can be refined, translated, or expanded, but the id should not be changed if the product remains the same.

In this case, the setup will have to be done again, which will lead to avoidable financial costs.

The prices[ ] array inside the product object:

The product.prices[ ] array contains all prices you transfer for one specific product.
Each price must reference one of the price types described in the root price_types[ ] array.
First, you describe all price types in the root price_types[ ] array, and then, for each product (in product.prices[ ] ), you transfer prices with a reference to the corresponding id from the price_types[ ] dictionary..

product.prices.price_type_id ← price_types.id

Data format of the product.prices[ ] array:

The properties object inside the product object:

The product.properties {} object contains the values of all properties (additional fields) for a specific product. First, you describe all the properties you need in the root properties[ ] array, and then, for each product (in product.properties), you transfer the corresponding values.

Examples of the properties object:

{
  ... ,
  "properties": [ ... ],
  "products": [
    {
      ... ,
      "properties": {
      	"weight": 0.100,
      	"stock": 20,
      	"follow_rrp": true,
      	"category_manager": "John Smith"
      }
    },
    {
      ...,
      "properties": {
      	"weight": 0.100,
      	"stock": 0,
      	"follow_rrp": false,
      	"category_manager": "John Smith"
      }
    }
  ]
}

The availability field - transfer rules

The availability field shows whether the product is in stock. The value can be transferred in the format already used in your catalog.

Examples:

Updated on: 07/08/2026