1. Home
  2. Docs
  3. Current
  4. Guides
  5. TIKI Theory
  6. Variant


Variant example:

      "sku": "sku1",
      "min_code": 14234,
      "quantity": 21,
      "option1": "Black",
      "option2": null,
      "price": 10000001,
      "inventory_type" : "cross_border",
      "supplier" : 239091,
      "image": "https://cdn.fptshop.com.vn/Uploads/Originals/2019/8/8/637008711602926121_SS-note-10-pl-den-1-1.png",
      "images": [
FieldTypeMandatoryOverride rule(*)Description
skuStringYNovariant ‘s sku from source side
min_codeLongNNoidentifier from manufactory
priceIntegerYNovariant ‘s sell price
market_priceIntegerNReplacevariant ‘s market price ( price before discount )
option1StringNNoattribute code of the first option attribute
option2StringNNoattribute code of the first second attribute
inventory_type(*)StringNNoinventory type of this variant
quantityIntegerYNonumber of products available for sell
supplier(*)IntegerYNosee detail below
nameStringNReplacename of this variant
descriptionStringNReplacedescription of this variant
attributesList<Attribute>NMergelist specific/addition attribute for this variant
imageStringNReplaceavatar url of this variant
imagesStringNReplacelist urls of variant product gallery


  • option1, option2 is required corresponding with the number of option attributes start from 1. The unused option value maybe null or empty or even don’t need to appear.That’s why it’s mandatory still equal “no”
  • Override rule describe how transform system will treat your request if any field is conflict between variant and parent product. By default child product will inherit all of member from its parent.
  • No : Field can’t not override
  • Replace : Field of variant will replace the parent one.
  • Merge : attributes will merged from both side.
Was this article helpful to you? Yes No

How can we help?

Leave a Reply

Your email address will not be published.