Mapping categories for Shopee-style feeds
Category trees, mandatory attributes, and keeping one catalog without drowning merchandisers in duplicate fields.
Regional marketplaces rarely accept your internal category tree as-is. A jacket that lives under “Outerwear / Unisex” in your PIM may need a gender split, a material attribute, and a size chart identifier before the feed validates.
We keep a mapping table owned by merchandising, not buried in connector code. Engineers implement the transform; merchants update the rows when the marketplace adds a required field. That separation prevents a late-night hotfix every time a category rule changes.
Variant explosions are another trap. If color and size already multiply SKUs in your storefront, the feed should reuse those identifiers rather than inventing marketplace-only SKUs that never sync back to inventory.
During engagement work we sample rejected listings from the last campaign week. Rejection reasons usually reveal missing attributes faster than reading the marketplace documentation cover to cover.