The category structure of your procurement catalogue determines how users find items, how spend is reported, how approval rules are applied, and how effectively the catalogue scales over time. A well-designed hierarchy makes the catalogue intuitive and useful. A poorly designed one buries items in illogical locations, produces misleading spend reports, and frustrates users into bypassing the system.
This guide covers the principles and practical steps for setting up item categories and hierarchies in your Oracle Fusion Cloud procurement catalogue.
Why Category Structure Matters
Category structure is the backbone of your catalogue. It affects virtually every aspect of procurement operations.
User navigation. When users browse the catalogue rather than search (and many do, particularly when they are exploring what is available), the category hierarchy is their map. If the hierarchy is logical and intuitive, users find items quickly. If it is convoluted or uses unfamiliar terminology, they get lost.
Spend reporting. Spend analysis relies on accurate categorisation. The category hierarchy defines how spend is aggregated, compared, and reported. If items are inconsistently categorised or the hierarchy does not align with how the organisation thinks about spend, reporting becomes unreliable.
Approval routing. Many organisations use category-based rules for approval workflows. IT purchases above a certain value might require IT director approval. Construction materials might require project manager sign-off. These rules depend on accurate categorisation.
Sourcing strategy. Category management — the practice of developing and executing sourcing strategies by spend category — depends on a well-defined category structure that aligns with how the procurement team manages supplier markets.
Scalability. A good category hierarchy accommodates growth. It can absorb new item types, new suppliers, and new spend categories without requiring a fundamental restructure.
Choosing Your Category Framework
Most organisations base their category hierarchy on an established taxonomy standard, customised to fit their specific needs. The most common options include:
UNSPSC (United Nations Standard Products and Services Code)
UNSPSC is the most widely used procurement taxonomy globally. It provides a four-level hierarchy (Segment, Family, Class, Commodity) covering virtually all products and services. Oracle Fusion Cloud supports UNSPSC natively.
Advantages: Comprehensive coverage, widely recognised, supports benchmarking against industry peers, regularly updated.
Disadvantages: Can be overly granular for some organisations, terminology is sometimes technical or unfamiliar to end users.
Organisation-Specific Taxonomy
Some organisations develop their own category hierarchy, either from scratch or by significantly customising a standard taxonomy. This approach allows the hierarchy to precisely reflect how the organisation thinks about and manages its spend.
Advantages: Tailored to organisational needs, uses familiar terminology, aligns with internal reporting structures.
Disadvantages: No external benchmarking, higher maintenance burden, risk of structural issues if not designed by experienced practitioners.
Hybrid Approach
The most practical approach for many organisations is a hybrid: use UNSPSC or another standard as the foundation for backend categorisation and spend analysis, while creating a user-friendly browsing hierarchy on the front end that maps to the standard categories behind the scenes.
This gives you the best of both worlds — intuitive navigation for users and standardised data for reporting.
Designing Your Hierarchy: Principles
Design for the User First
The primary purpose of the browsing hierarchy is to help users find items. Design it from the user's perspective, not from procurement's analytical perspective.
Ask yourself: if a project manager needs to order safety equipment, where would they look? "Health and Safety" or "Personal Protective Equipment" is more intuitive than "UNSPSC Segment 46 — Defence, Security, and Safety Equipment."
Keep It Shallow
Deep hierarchies with many levels require more clicks to navigate and are harder for users to learn. Aim for three to four levels of depth at most. If you find yourself creating a fifth or sixth level, consider whether the lower levels could be handled through item attributes or filters rather than additional hierarchy levels.
Balance Breadth and Depth
Each level of the hierarchy should have a manageable number of options — ideally 5 to 15. Fewer than 5 suggests the level is not adding value and could be collapsed. More than 15 becomes difficult for users to scan and choose from.
Use Clear, Consistent Naming
Category names should be descriptive, unambiguous, and consistent in style. Decide on a naming convention (for example, noun phrases like "Office Furniture" rather than verbs or adjectives) and apply it throughout.
Avoid acronyms, jargon, and abbreviations that non-procurement users might not understand. "PPE" may be clear to safety professionals but confusing to someone in marketing.
Plan for the Future
Consider categories you may need in the future, even if you are not populating them immediately. It is much easier to add items to an existing category than to restructure the hierarchy later. Leave logical places in the structure for anticipated growth.
Implementing in Oracle Fusion Cloud
Oracle Fusion Cloud supports catalogue category hierarchies through its browsing categories and purchasing categories functionality.
Purchasing categories are the formal classification used for spend analysis, approval routing, and integration with sourcing and contracts. These should align with your chosen taxonomy standard.
Browsing categories are the user-facing navigation structure that appears in the shopping experience. These can be customised independently of purchasing categories, allowing you to create an intuitive shopping hierarchy while maintaining standardised data classification.
Configuration Steps
Define purchasing categories. Set up your purchasing category hierarchy in Oracle Fusion, mapping to UNSPSC or your chosen taxonomy. Assign category codes, descriptions, and attributes.
Create browsing categories. Build the user-facing browsing hierarchy, organised for intuitive navigation. Map browsing categories to the corresponding purchasing categories.
Assign catalogue items. When loading catalogue content, assign each item to both its purchasing category and its browsing category location. The Catalogue solution from Sharpe Project Consulting provides tools to streamline this mapping process.
Configure category-based rules. Set up approval workflows, spending limits, and access controls based on purchasing categories. Test these rules to ensure they trigger correctly.
Validate the structure. Before go-live, have representative users navigate the browsing hierarchy and search for items in their typical purchasing categories. Gather feedback and refine.
Common Mistakes to Avoid
Creating too many categories. Excessive granularity creates maintenance overhead and confuses users. If a category contains only a handful of items, consider merging it with a related category.
Mixing classification levels. Within a single hierarchy level, categories should be at the same level of abstraction. Having "IT Equipment" alongside "Laptop Chargers" at the same level is inconsistent — chargers should be nested under IT Equipment.
Neglecting services. Many hierarchies focus exclusively on physical goods and inadequately represent services — consulting, maintenance, training, temporary staffing. Services often represent a large share of spend and deserve proper categorisation.
Building and forgetting. Category structures need periodic review and maintenance. New spend types emerge, organisational structures change, and user needs evolve. Schedule annual reviews of your category hierarchy.
Ignoring the connection to contracts. Categories should align with how contracts are structured. If your contracts are organised by category, the catalogue hierarchy should make it easy to find items under each contract's scope.
Integrating with the Broader Procurement Framework
The category hierarchy connects to many other procurement processes within Oracle Fusion Cloud. Ensure alignment with:
- Sourcing events: Category definitions used in sourcing should match catalogue categories
- Contract management: Contract scopes should align with catalogue categories for effective compliance tracking; explore how contracts work alongside catalogues
- Spend analytics: The category hierarchy drives spend cubing and reporting dimensions
- Supplier management: Suppliers are often qualified and managed by category
Sharpe Project Consulting helps organisations design and implement category hierarchies that work across the full Oracle Fusion Cloud Procurement suite. Our services team brings experience from numerous implementations, helping you avoid common pitfalls and build a structure that supports your organisation's needs today and into the future.
If you are setting up a new catalogue or restructuring an existing one, getting the category hierarchy right is one of the most important decisions you will make. Get in touch with SPC3 to discuss how we can help you build a category structure that drives adoption, compliance, and insight.