Categories place your product in the right part of the marketplace. The catalog is the shared library of product identities. Here’s how to work with both — and how to ask Fawran to fix catalog data.
The category hierarchy
Categories are a three-level, platform-owned tree: Category → Subcategory → (optional) third-level subcategory. You pick from them; you can’t invent your own. Choosing a category cascades the child dropdowns and decides where buyers find you.
Choosing a category does not add per-category attribute fields in the current flow. Use Other Specifications to capture product-specific attributes.
Candidate catalog
When no verified catalog match exists, you create a candidate identity (CANDIDATE) with title AR/EN, brand, category, optional barcode and images. It’s buyable immediately; Fawran verifies it later and may promote (VERIFIED), merge (MERGED) or reject (REJECTED) it.
Suggestion vs Request — which one?
| Tool | Use it to… | Effect |
|---|---|---|
| Catalog Suggestion | Improve a verified catalog product’s data — one of TITLE, IMAGES, BRAND, CATEGORY, ATTRIBUTES, BARCODE | Proposes a change; never overwrites the catalog directly |
| Catalog Request | Change the catalog structure/identity — PROMOTE a candidate, MERGE into another, BARCODE add/fix, or a general EDIT | A request Fawran reviews |
Request statuses
Both suggestions and requests go to Fawran and move through: PENDING → APPROVED / REJECTED / NEEDS_INFO. When a request comes back as NEEDS_INFO, open it and add the missing details.
See your products’ catalog link status under Catalog›My Products — filter by Linked, Unlinked, Candidate, Verified, and brand status.