Beta
Back to the blog
Product

Your categories, not your store's: mappings instead of guesswork

Every supplier has its own name for the same thing, and every store has its own tree. Why it pays to have your own categories, translate them to each destination through clear mappings and never let anyone — not even an AI — guess where a product goes when you publish.

3 min readNoobit team

One supplier says "Hair care > Shampoos". Another, "Hair". Your store has "Salon > Wash". And the day you open another channel, that one has its own tree. Categories are where you notice most that every system speaks its own language, and where a mistake shows right away: a product in the wrong category, or in "Uncategorized", is a product nobody finds.

The problem with guessing

The temptation is to solve it by similarity: if the supplier's category looks like one in the store, use that one. It works until it doesn't. "Tints" looks like "Lash tints", "Men" matches anything with that word in its name, and an AI can pick the wrong option with complete confidence. Every mistake is a misplaced product, and at scale they multiply without anyone having decided anything.

Your own tree and clear mappings

Noobit works with your category tree: your business's own, kept separate from any store. Each product is linked to a category in that tree, and each category is translated to each destination through a mapping: this category of mine is that one in this store. Mappings are decided once and work from then on.

When you publish, the rule is simple. If there's a mapping, it's used. If not, Noobit looks in the store for a category with the same name (or one of its synonyms). And if none turns up, nothing gets guessed: the product is published without that category and flagged for you to resolve.

The category console

Everything pending shows up in a console: your tree in rows, your destinations in columns and, at each intersection, the mapping or what's missing. From there:

  • You confirm a suggestion in one click.
  • You pick the store's category by hand when the suggestion isn't the right one.
  • You create the missing category in your WooCommerce store without leaving Noobit.
  • You ask the AI to suggest mappings: it suggests and you confirm; it never turns anything on by itself.
  • You merge two categories in your tree that were really the same one.

And when you confirm that your "Shampoos" is the store's "Wash", Noobit saves it as a synonym and recognizes it on its own next time.

Products that arrive without a category

When you import a CSV, before anything is created, Noobit shows you the supplier's new categories so you can decide whether each one goes into one of yours or gets created. And if a product arrives with no category at all, when it's written with the Noobit Engine (we turn it on with you when you get started), it's given the best fit from your tree, chosen among the categories that already exist: a new category is never invented. If none fits with confidence, it stays uncategorized and shows up in the console with everything else that's pending.

Start with your tree
It doesn't have to be perfect on day one. Start from your main store's categories, review the mappings Noobit finds on its own and resolve what's left. From then on, each new channel only needs its own mappings.

Put your catalog on autopilot

See Noobit working on your own catalog, with no strings attached.