Q: Whether the name field of variation distinguishes language
A: Languages are not distinguished, and the number of characters does not exceed 15
Q: How to judge the hierarchical relationship of each variation
A: Look at the attribute name, there can be up to 4 variations, and the field name is variation1-variation4, with 1 being the top level, sorted down in order
Q: I see the hasImage field in the variation, what does this mean?
A: This indicates whether the current sales attribute can set the picture, only variation1 can this be true
Q: When using the updateProduct API to add a variation, can the existing SKU not update this variation?
For example, there is an existing size sales attribute, I want to add the color_fmaily attribute, but the existing product did not add the color_fmaily attribute when updating
A: No, an error will be reported. After the sales attribute is added, all SKUs under the product must be set to the corresponding value of the sales attribute
Q: When I call RemoveSku to delete a variation, can I not delete the SKU under the variation?
A: Yes, but there are conditions. For example, there are two variations under product A, variation1: color_fmaily and variation2: size, and there are two SKUs A and B. The attributes are as follows
A: color_fmaily=red
size=s
B: color_fmaily=blue
size=s
Simply, if you only delete color_fmaily, an error will be reported, because when only size is left, there is a problem of duplication of sales attributes, which is not allowed
Q: What should I do if I want to eliminate one of the options under variation?
A: Call "RemoveSku" to delete the corresponding SKU, or use "updateproduct" to replace the "variation" of this SKU with other options
Q: When creating a product for the first time, I can declare multiple variations and corresponding options, but only enter one SKU?
For example: I declared "color_fmaily": "red", "blue" and "size": "S", "M", "L", but only created one SKU and set "red" and "S", Will other options remain?
A: It will not be retained because only options and variations written to the SKU will be persisted, and other values that do not appear in the SKU will disappear
Q: Can I delete a variation directly?
A: In removesku, just fill in the name of the variation to be deleted
Q: If the red option has three SKUs, what operations are required for the corresponding SKUs when deleting red?
A: You need to fill in the corresponding SKU when deleting the red option
Q: Following the question, after the red option is deleted, I want to add the red option and the corresponding SKU again, do I need to declare red in vairation again?
A: Need
Q: Support multiple SKU deactivation under one item. Will some sku deactivate successfully and some unsuccessfully?
A: If multiple SKUs are deactivated under one item, they will either be deactivated successfully, or all of them will be unsuccessful, and will not be partially unsuccessful.
Q: How do we determine which categories support several variant attributes?
A: Currently all online categories are supported, but in the future, the allowed category information will be released in advance and placed in the get category interface
Q: The types of variants supported by different types of items are different. Some only support one, some two, and four. We want to know which categories support several
A: Currently available Variations, "CreateProdcut" has 2 and "UpdateProduct" has 4, that is, ordinary (current) new products should not be passed into Varition3, Varition4. Explain again in this regard, because the category is not configured with mandatory mandatory restrictions, but subsequent categories will have legal mandatory mandatory restrictions. At this time, you need to verify all mandatory mandatory attributes, and new ones may appear. When sending goods, you also need to pass in the parameters Variation3 and Variation4. For this type of category current information, it is planned to be forwarded to the category information acquisition interface, which has not been provided yet, but the category configuration data at the current stage is Does not affect the use of
Q: In the hasImage field of variation, the input parameter description writes that there can only be at most one attribute setting wall chart, but the verification rule says that only variation1 can set the wall chart. What is the rule?
A: In the latter case, only variation1 can set the flipchart
Q: According to the logic discussed today, the updateproduct interface supports adding variables. When a commodity is created, there are two variables and SKUs corresponding to the two variables. When updating, only one variable is added without updating the SKU. Will an error be reported?
A: An error may be reported. When adding a variation, that is, adding a sales attribute dimension (such as color family), all SKUs under this commodity must set the attribute value corresponding to the sales attribute, such as "red" and "black"
Q1: When calling the removesku interface, there will be a check that after deleting the sales attribute and SKU, there are duplicate sales attributes in the remaining SKUs. This means that if a commodity has two attributes: color and size, after deleting one attribute color, you need to delete all SKUs using the color attribute together, right?
A1: This error reporting is not the logic you described. The real logic is that, for example, there are two sales attribute colors and sizes under a commodity. There are two sales attribute values under the color: red and black, and there is only one size: S. if the color needs to be deleted in the parameters and all the SKUs to be deleted are not transmitted (for example, no SKUs to be deleted are transmitted), At this time, two SKUs are s and have no other sales attributes. At this time, this error code will be returned. The positive understanding of this logic is: if you need to delete the sales attributes, you need to delete the corresponding SKUs to ensure that the sales attributes among the remaining SKUs can be combined, but not in the example
Q2: According to this logic, assuming your example, on the other hand, delete the size and leave the color, is it supported?
A2: On the contrary, it is OK to satisfy that the sales attribute combination of SKU is right
Q: For example, the sales attribute and color of the goods have three options: red, black and white, size, s and L. if I want to delete a white option in the future, I must delete only white s and white l SKU? Then lazada will default that I delete the white option?
A: You don't have to delete white, you can also replace it with other colors. If you replace them, the white option is deleted
Q: If a product has 2 skus: Red/S, Green/S; Red/M, Green/M, but the user wants to edit into 3 SKUs: Red/S; Yellow/S; Green/S, correct What is the order of interface calling?
A: ① Delete Red/M, Green/M from removeSKU A: ① delete red / M and green / m in removesku ② add SKU: Yellow / s in update interface. Note: declare yellow / s in vairation
Q: How do I delete a color attribute directly—— In the example scenario, we have created 9 SKUs. After directly deleting the color attribute, how do you deal with these 9 SKUs? After I delete the color attribute directly, there are only three SKUs (s, m, l) left
A: If you delete variation, you need to put the corresponding deleted SKU into the transfer parameter. That is, after deleting the color, if the SKUs to be deleted are not transmitted, the S / M / l cannot form the remaining 9 SKUs, and the seller's intention cannot be recognized at the commodity background: which 3 to keep and which 6 to delete. After deleting the SKUs to be deleted, the attributes of the remaining SKUs do not need ISV update. During the deletion process, the program logic will automatically retain the remaining attribute values. The removesku interface is expected to solve all scenarios that need to delete sales attributes (variables), delete sales attribute values (options), and delete SKUs
Q: I use the removesku API to delete variation and SKU in a request and prompt me that the attribute is duplicate. Why?
A:
1. When deleting, please ensure that the variation combination of the deleted variant is not duplicate
2. Please confirm whether the XML format is wrong. For example, one layer less < sellersku > or < SKU > is written in the < SKUs > tag