Categories
The difference between a vendor's categories and your own tree — and why they are kept apart.
Monokaido keeps two independent category trees, and that is deliberate rather than complicated.
| Tree | Where it comes from | Who changes it |
|---|---|---|
| Vendor categories | Arrives in the feed. Every vendor has its own structure and its own names. | Nobody. The import rewrites them on every run. |
| Your categories | The tree you build. The shop looks the way it does. | You. |
If there were only one tree, every new vendor would rearrange your shop. Keeping them apart means a feed can send anything and your shop does not move — until you say where it belongs. Saying that is called mapping.
How a product reaches a category
The import assigns the vendor's category
Automatically, from the feed. Root nodes shaped like
_root_<vendor>appear.A mapping assigns yours
Either you confirm the AI's proposal or you make it by hand. It applies to a whole category at once, not to individual products.
Manual placement handles the rest
Products the feed placed nowhere, and the exceptions a mapping does not cover.
The chapters in this section
| Chapter | Answers the question | Note |
|---|---|---|
| The category tree | How do I build my own structure? | Creating, moving, inheritance. |
| By vendor | What did each feed bring me? | |
| Category mappings | How do I match a vendor's categories to my tree? | The section's most important chapter. |
| Manual categories | How do I place specific products by hand? | |
| Storefront preview | What will a customer see? |