A Macy’s listing is not a feed row. It is a product page in a department store, and it is assembled from a category assignment, a required attribute set, a variant family, and an image set — each of which can hold the listing on its own. Acenda prepares all four before anything is submitted.
The category a style is assigned to determines which attributes are required, which values are accepted, and which variation axes are allowed. Choose it late and you inherit a required-field list your data was never built to answer. Acenda maps your product taxonomy to Macy’s categories once, then validates every style against the requirements of the category it actually landed in — and re-validates when a style moves, because a category change can leave a previously answered requirement unanswered.
The product record describes what the item is: its identity, category, attributes, variant relationships and imagery. The offer describes the commercial availability of a sellable SKU, including the applicable price and stock information. A submitted product record does not by itself establish that every size is available to buy.
Keep source identifiers stable and confirm the identifier requirements for the relevant category. Acenda connects catalog preparation with offer management so the team can investigate content issues and availability issues in the right place.
Every style is checked against the category’s required and conditionally required attributes, its variant structure, and its image slots. Gaps come back as a per-SKU, per-field worklist for a merchandiser. The alternative — submit and read rejections — costs a review cycle each time.
When Macy’s does return an error, Acenda holds it against the specific item and the specific attribute, so the fix is a value change rather than an investigation. Where a family is held because of one member, the member is identified.
Titles, bullets, descriptions and care copy can be composed per channel from your master record, so Macy’s gets the register it expects while your own storefront keeps your voice. Brand-name handling, prohibited claims and formatting rules are applied as mapping rules rather than manual edits per style.
Marketplace requirements move. Acenda re-imports the channel’s live category and attribute schema, so mapping rules are validated against what Macy’s requires now, and drift surfaces as a worklist rather than as a wave of rejections.
Back to hub: Sell on Macy’s with Acenda
