1. Advantages of variant merging - Reduce duplicate information and invalid clicks, and improve sales conversion rate. It can merge products of the same brand but different colors or sizes, giving buyers a clearer visual effect and increasing the possibility of purchase.
- Reduce the advertising costs of merchants. The merged product page only requires one advertising fee.
2. Rules for Creating Variants- They must belong to the same product and share some common attributes, such as you can create variations by color, size, and style for selling T-shirts, but not for shoes or accessories.
- Must have at least one common attribute, such as creating variations based on color, and each variation must have the same size and style.
- Each variation must have a unique SKU for tracking and management purposes.
- Must comply with Amazon regulations and standards, including product quality, labeling, safety, and compliance.
- You must use the correct variation attributes, which can be found in Seller Central. The rules for different product categories may be different.
3. Causes and solutions for failure to merge variants- Reason: The seller may have a misunderstanding. The categories displayed on the front end are consistent, but the actual parent and child categories are inconsistent.
- Solution: Contact customer service to help change it to be consistent.
- Reason: There was a problem with filling in the brand name when registering the store, which resulted in inconsistent brand names when adding variations after the listing was promoted.
- Solution: Obtain editing rights, and then open a case for modification by repairing the product page path in the background (providing packaging information of products with brand logos and UPCs), or first split the parent and child variants, use a template to change the child brand, and then merge them. You can also use a VC account to modify it (you can contact the service provider).
- The backend shows that the merge is successful, but the frontend does not show the variant
- Cause: The merge of inconsistent major categories was successful, or there was a system identification problem.
- Solution: Contact customer service directly to resolve the issue; if the system identifies the problem, you can change the parent body and put it back on the shelf, or find out the other parent bodies bound to the child body, delete them, and then merge them.
- The frontend shows that the merge was successful but the comments are not shared
- Solution: Change the parent.
- There is a problem with the vine variant
- Reason: Customer service usually asks you to file a complaint, but it may not be a problem with the link itself.
- Solution: Abandon the variation link and merge it with another link.
IV. Notes on variant merging- Do not hijack the parent variant and do not add unrelated child variants to the parent variant.
- Do not make a new generation a sub-variant of a previous generation.
- Do not reuse sub-variants to avoid complaints.
- Try to avoid using information that goes against common sense or is illegal as sub-variable information, do not use the same SKU information in multiple listings, do not use price promotion information as sub-variable information, and try to avoid using real names as sub-variable information.
V. Variant Violation Appeal Process- Check the warning information to identify the violating ASIN.
- Unbind/remove the offending variant.
- Write an effective Plan of Action (POA) that describes the violation, what happened, the actions taken, and future solutions.
|