Channels organise products into their own category tree (their taxonomy). Category mapping connects each of your store categories to the matching category on the channel. Many channels won't accept products until this is done, and it often unlocks extra required attributes too.
Just ask
Which of my store categories aren't mapped yet for this feed? Suggest the best matching target category for each and map them once I confirm.
Other examples: "Map my 'Laptops' category to the right target category." · "Show me my current category mapping."
How it goes, step by step
Find the gaps. The assistant lists your store categories that don't have a mapping yet.
Find the target. For each gap it searches the channel's category tree and proposes a matching target.
You confirm, it maps. You approve the matches and the assistant saves them.
Category rules are shared. The mapping applies to every feed that uses the same channel taxonomy, so a change can affect more than one feed. The assistant will warn you and ask for confirmation when other feeds are affected - read that before you say yes.
Category mapping is saved but reaches the channel only after the feed is exported. Map categories, then ask the assistant to export.
Behind the scenes (for the curious)
Behind the scenes (for the curious)
The assistant inspects current rules with get_category_mapping, finds gaps with list_unmapped_categories (and the full list with list_store_categories), finds targets with search_target_categories (which returns a target hash), and writes rules with set_category_mapping (rules: [{ store_category_ids, target_hash }]). Because the rule set is shared per project + taxonomy, a first write that touches other feeds returns a "confirm required" response listing the affected feeds; the assistant re-sends with confirm: true after you agree.