Acenda helps fashion teams organize parent styles, child SKUs and their sellable offers. A style with eight sizes in three colors is twenty-four sellable SKUs that must roll up to one shoppable product — with distinct values on every variation axis and an offer behind each one.
Acenda models a parent style and its children with the variation axes stated outright rather than inferred from whatever happens to differ in a batch. Color is color. Size is size. Each child carries its own distinct values on those axes, its own identifier, and its own offer.
Two children resolving to the same color-and-size combination. Because department-store channels validate the family, the whole group can be held, and the item the feedback names may not be the one you would have guessed.
A variation value living in a descriptive field instead of the defining one, so the channel sees a grid that does not vary.
Children of one style mapped into two different categories, so requirements differ across children that should share one structure.
The style publishes, but sizes with no stock or no offer never become purchasable, and the listing reads as broken to a shopper.
Acenda structures the family before submission so these surface as fixable data issues rather than a held style with no obvious cause.
Children share colors and sizes; that is normal. What must be distinct within a family is the complete combination. Black / Small and Black / Medium are different variants; two Black / Small records require investigation. A subtlety worth knowing: when your marketing color names collapse into a smaller set of standardized values, two colorways that look distinct on your site can resolve to the same accepted value — and become a duplicate combination you never created. Acenda audits the combination after mapping, which is the only place that clash is visible.
Illustrative data only. These labels are not an official Macy’s code list. Confirm the category’s current variation fields and accepted values. A distinct combination alone does not establish listing approval or offer availability.
Fashion sellers rarely treat a colorway as a simple attribute — it carries its own imagery, often its own copy, sometimes its own identifier. Acenda supports colorway-level assets and content within the parent style, so the grid stays one shoppable product while each color shows its own photography.
Size runs change mid-season. A sold-out size should stop being purchasable without pulling the style down; a re-stocked size should come back without a re-launch. Acenda drives that from inventory and offer state per child SKU, continuously.
A letter size, a numeric size, a regional shoe size and a kids’ size are different systems. Avoid mapping by label alone. Confirm the category and applicable sizing context, then map the values Macy’s accepts. Follow channel guidance for extended sizes, widths or other supported axes; do not assume every attribute can define a variation.
Back to hub: Sell on Macy’s with Acenda
