2. Product Create

• You need to send "storeFrontCode" as Header Parameter.
• The maximum number of items that can be sent in each request is 1000.
• The product can be created without any stock, so that the stock will be 0 when product first created.
• You can only update stock through the stock update service.
• After product approval, color information can not be updated
• The attributes which slicer or varianter are true, cannot be updated after product approval
• "listPrice" cannot be lower than "salePrice"
• "stockCode" in product data, equals to "merchantSku" in order data. It can be checked in getShipmentPackages service.
• "shipmentAddressId" and "returningAddressId" are only eligible for the storeFrontCode "SA" and "AE".
• Following a successful product create request, product approval process starts. Products that are under approval or rejected will not go live. In this case you need to check product status through the productFilter service.

❗️

While createProducts, updateProducts, updatePriceAndInventory methods are processed by the queue in Trendyol System, a batchRequestId information is returned in each successful request result. By checking the "status" field in the return of the batchRequest service, you can check whether the batch has been completed. If an item in the batch results has an error, the failureReasons field can be checked to see error reason

HTTP method: POST

Service Parameters and Rules

You can use the brand & category below not to affected by missing definitions on stage environment

Sample Service Request

{
  "items": [
    {
      "barcode": "string",
      "stockCode": "string",
      "title": "string",
      "productMainId": "string",
      "brandId": 0,
      "categoryId": 0,
      "quantity": 0,
      "description": "string",
      "salePrice": 0,
      "listPrice": 0,
      "vatRate": 0,
      "shipmentAddressId": 0,
      "returningAddressId": 0,
      "deliveryOption": {
        "deliveryDuration": 1,
      }
      "images": [
        {
          "url": "string"
        }
      ],
      "attributes": [
        {
          "attributeId": 47,
          "customAttributeValue": "Red"
        },
        {
          "attributeId": 3,
          "attributeValueId": 998
        }
      ]
    }
  ]
}

Sample Service Response

{
  "batchRequestId": "8d30c8d3-0800-11ed-8fdd-cac59bbd2b08-1658317798"
}

Product Variant Creation

The product variantation process is based on the 'productMainId' value. The 'slicer' and 'varianter' values should be checked through the relevant category attribute service.

• To be able to variant a product, all values except the barcode and the property to be variant, must be kept the same for the relevant product.

Product Variant Creation by Slicer Value (Product color value, product memory value, etc.)

The product is opened in different contents, and the most commonly used value as a Slicer in the system is color. However, in electronic categories, for the product to be opened in different contents (such as internal memory), it can be used as a Slicer value. (The category attribute service should return slicer=true.)

• In a category, there can be multiple slicer values.
• Since the slicer value opens the product in different contents, it can be used as a variant.

Product Variant Creation by Varianter Value (Product size value, etc.)

These are different sizes of the same product listed within the same content. It does not open the product in different contents. Only one variant can be selected for each category.

• Multiple selections are not allowed.