{"section":"known-issues","requestedLocale":"en","requestedSlug":"meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller","locale":"en","slug":"meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller","path":"docs/en/known-issues/Connections/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md","branch":"main","content":"## Summary\n\n\n\nWe currently have an issue which still needs more investigation and details, But there are some categories mapped inside the Mapper feature, and for some attributes which were not mapped but they are currently being sent to MELI.\n\nThis will result in some SKUs being exported and some won't as the first SKU includes and undesired attribute, and second SKU won't be exported as MELI have rules that requires all variantion inside the same product must have same attribute combinations.\n\n\n##\n\n## Simulation\n\n\n\nInside bridge product menu, you will see an error for some SKUs as seen below:\n**Variations with different attribute combinations are not allowed.**\n\nThis is due to first SKU exported with undesired attribute, and the rest of SKUs are not being sent to that attribute.\n\n\n##\n\n## Workaround\n\n\nIs there a workaround for this bug? If yes, describe it here. If not, write \"N/A\" or \"There is no workaround available.\". Do not remove this section if there is no workaround, please."}