Skip to content

[Post-Multi-Variation-Support] Handle Attribute/Option Sync by Using IDs Instead of Names #254

@faisal-alvi

Description

@faisal-alvi
  1. If a merchant changes the slug or name of an attribute in WooCommerce or renames a dynamic option in Square, a new option/attribute is created instead of updating the existing one in the next sync.
  2. If a merchant creates custom attributes with names identical to existing taxonomy attributes, it results in issues during import/sync. Products using the same-named custom attribute are updated (replaced) incorrectly with the taxonomy attributes.

Explore a way to track options/attributes by their ID instead of their name. A team discussion would be required to evaluate the importance and feasibility of this enhancement. Implement this improvement only if the need is established and prioritized during a healthy discussion.

It’s not mandatory to use IDs instead of names. Names are functional and easier to manage. Even WordPress core uses names for retrieving taxonomy details, so handling syncs using names is still a valid approach. However, I felt it was worth creating the ticket for potential future enhancements.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions