This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Overview

Welcome to the SkuDB Knowledgebase

What is SkuDB?

SkuDB is a a modeling and design environment for creating product taxonomy, attributes and other data structures intended for ERP, PIM and eCommerce applications. The application is widely used by distributors, manufacturers and retailers to build product taxonomies and other data structures.

Core Functionalities

  • Hierarchy Design
  • Hierarchy Metadata Design
  • Item Classification
  • Attribute Design
  • Attribute Inheritance Design
  • Attribute Metadata Design
  • Attribute Data Fill
  • Data Reporting & Visualization

1 - Projects

Select a project, update user settings, and view activity

The Projects page can be reached via the pyramid icon in the Top Left or the Person Icon in the bottom left. The “Log out” selection allows for quick log out of the SkuDB instance. The “Account” selection brings a user to the Projects page where they can perform the following functions:

  • Open an existing Project
  • Create a New Project
  • Logout

Administrative users have the additional ability to create new users and to view the system activity dashboard.

A page with a blue top half and grey bottom half is displayed with a triangular logo at the top, and buttons for Projects, Users, and Activity. On the rightmost side, a circle with the letters CP sits, with a margin to the right. Below is the word Projects anchored to the left margin. Beneath that word is a box which says All Projects, Select a project to get started. And a button on the right says Create New Project. There is a single row table below with the words ACME Project in blue, and grey text beneath which says March 1, 2026. An arrow pointing to the right sits at the right edge of the row. ACME Project is a link.

2 - Navigation

Learn how to get around SkuDB

To navigate between the views in SkuDB, open a new tab or pane. Navigate between the following views:

After opening a new tab, select a view

Dashboard

A high-level summary of the hierarchies in the project.

Tree

Open a tree view containing all hierarchies and categories in the project

Search item IDs across the project.

Chatbot

An ai-powered chat that brings project data into the context of the conversation. The chat can run read-only SQL queries to view any requested vertical(s). Requires configuration in “Settings” view.

Master Attributes:

A list of all unique attributes in the project, with summary statistics.

Fields

Fields view is where fields can be added to categories, attributes, items, issue log, QA, etc.

Issues

The issue log is the central repository for all issues across the project. New issue fields can be added from the Fields view.

Imports

The imports view is where attribute values and field values can be uploaded. Includes various options for controlling import behavior and includes preview and reporting.

Exports

The Exports view lists all current user-generated exports.

QA

The QA module contains a term dictionary and style guidelines. Add new QA fields from Fields view.

Settings

Project-wide settings, including project name, item tiers and names, chatbot configuration, and preview mode configuration.

3 - Tree view

The primary method of viewing and altering the hierarchy within a project
An image displaying a hierarchical structure made up of differengt categories. The categories are mainly abrasives-related, including adapters, disc holders, pads, drums, mandrels, assortments, belts, brushes, discs, sheets and roolls, shop setups, wheels, hand pads, rolls and sponges, and specialty abrasives.

Within the project, hierarchies are displayed as a branching tree.

Each hierarchy level can be toggled to display child categories down to the terminal level.

Hierarchy Menu

A right-click menu displaying several options to the user. These options are actions that can be performed on the target category, including open, create child category, resequence children, rename, move, copy, delete, granularize, expand branch, copy category path to clipboard, and copy ID to clipboard.

Right clicking anywhere in the hierarchy tree prompts a dropdown menu containing the following options:

Open

Opens the selected category. Categories will open to the default view in the last active pane.

Rename

Rename the selected category

Move

Move the selected category to a new location in the hierarchy

Delete

Delete the selected category or hierarchy branch.

Copy

Copy the selected category or hierarchy branch.

Create Child Category

Create a child category under the currently selected category.

Create Issue

Create a new issue on the category

Expand Branch

Open all child nodes under a selected branch.

Sequencing

Set the sequence of the child categories

Granularize

Granularize the hierarchy based on the values of a selected attribute.

An image displaying a hierarchical structure with the word Sets typed into the search bot at the top right. The categories displayed are now only those which contain the word Sets, such as Leg Sets & Stands, Carbide Burs & Sets, Bur Sets, Drill Bit Sets, Annular cutter Sets, Hole Cutter & Hole Saw Sets, Tap & Die Sets, and Tap Sets.

The search box can be used to enter all or part of a category name to search across all hierarchies and categories in a project.

4 - Category Views

Standardized views across all categories of SkuDB

Each category has the following standard view, which can be accessed by opening a category:

4.1 - Dashboard

Contains basic statistics about a category or branch. Can be customized to include any project summary information.

In its default state, the dashboard displays basic statistics about a category or branch.

It can be customized to include data quality rules, before and after summaries, and other project-specific summary information.

The SkuDB dashboard can be customized with any set of analyses, tailored to a given project. The image above shows an example set of customized metrics, with many slices of the data available at a glance. All aspects can be customized upon request, including both style and content.

4.2 - Metadata

Contains category field values, as defined in the Fields view.
The category metadata view, showing metadata fields including name, category table break, category table columns, long name, ready status, short name, table category, total revenue, create date, and category id.

The category metadata view allows you to update the metadata attached to a given category, without leaving the category tab. An unlimited number of metadata can be tracked here. For more information on adding new metadata fields, see Fields.

4.3 - Descendants

A table-view summary of child categories.

The Descendants tab contains a spreadsheet view of all the child categories of the selected category, with columns for standard or user defined fields including category name, category path, description, child counts, category level, variant type, category ID, and a creation timestamp.

A dropdown menu provides the following functionality:

  • Move Selected Categories
  • Delete Selected Categories
  • View all descendants, or view terminal categories only
  • Control the Number of Categories Displayed
  • Control the Columns Displayed
  • Control the Levels of Categories Displayed  
A screenshot showing the Descentants view in SkuDB. Five categories are displayed: ACME Master Taxonomy, Abrasives, Abrasive Accessories, Abrasive Adapters, and Backup Pads & Disc Holders. Some of the categories' metadata is displayed as well, including the Table Category, Total Revenue, Short Name, Child Count, Descendant Count, and Product Count

The Descendants view contains the same fields as displayed in the Metadata view, as well as standard columns like Child Count and Item Count to provide the most commonly used metrics out of the box.

4.4 - Master Attributes

A consolidated list of unique attributes in the project, including summary statistics.

The Master Attributes view contains a searchable list of unique attributes throughout the project, and metadata about said attributes. Any fields on the attributes will also be displayed here.

Multiple Values for a Single Field

Note that when viewing Master Attributes from a non-terminal category, all values held by that attribute for a given field will be displayed in that field, separated by a pipe | delimiter. You can double-click on the field value to see all category paths containing the attribute, as well as each value held by the field within a given category path.

Example - ANSI Cut Resistance Order

Attributes with differing values in different classifications will show all values within a cell, separated by a pipe | character.

When an attribute has multiple values in different categories, you can double-click the field to trace their origins.

4.5 - Attributes

A list of all attributes related to the category, including global attributes, inherited attributes, and category-specific attributes. Also includes any attribute fields set up via the Fields view.

The Attributes tab contains a spreadsheet view of all the attributes in the category, with columns for standard or user defined metadata fields including attribute name, attribute ID, breadcrumb, units of measure, allowed values, data type, display type, rank, required, sample values, and a creation timestamp.

A dropdown menu provides the following functionality:

  • Create New Attributes
  • Copy Attributes
  • Merge Attributes
  • Promote Attribute to a higher Hierarchy Level
  • Delete Attributes
  • Recalculate Attribute Fill Rates
  • Export Attributes
  • Control the Number of Attributes Displayed
  • Control the Columns Displayed
  • Control the Levels of Attributes Displayed

Single Value vs. Multivalue

An attribute can be single-valued or multivalued. Multivalued attributes can have multiple pipe-delimited values assigned to a single attribute. By default, SkuDB will order these values alphanumerically.


4.6 - Values

An editable list of category-specific attribute values. Contains each unique value for each attribute.

The Values tab contains a spreadsheet view of all unique values in the category, with columns for standard or user defined metadata fields including attribute name, value, ID, breadcrumb, units of measure, and a creation timestamp.

A dropdown menu provides the following functionality:

  • Create New Value
  • Delete Selected Value
  • Export Values
  • Control the Number of Values Displayed
  • Control the Columns Displayed
  • Control the Levels of Attributes Displayed

4.7 - Products

The primary “grid view” of items and attributes. Includes a toggle between product-level and item-level entities.

The Items tab contains a spreadsheet view of all the items and/or products in the category, with columns for standard or user defined metadata fields including Item ID, and a creation timestamp. The default item tier names can be updated in the project’s Item Tiers Settings.

a menu listing a set of acctions that can be taken on all items or the currently selected item. The list includes Create new item, Create issue for Selected Item, View Related Products, Filter by List of Item IDs, Filter on Selected Items, Copy Selected Item IDs to Clipboard, Map Selected Items, Move Selected Items, Granularize this Category, Parent Product Actions (which features a right arrow indicating more options appear onhover), Export View, and Delete Selected Item Classifications

The Items tab features icons at the far left for “card view” and “image view” and can be customized to contain quick links to other content as needed (e.g., source url, data sheet)

A dropdown menu provides the following functionality:

  • Create New Items
  • Create new Attribute
  • Delete Item Classification
  • Create Issue
  • Move Selected Items
  • Fill Attribute Values & Field Values
  • Transfer Values
  • Export
  • Parent Product Actions
  • Filter on Selected Items

4.8 - Product Mappings

A summary of item mappings across hierarchies. Product Mappings are only relevant when items are classified to mlutiple hierarchies.

4.9 - Category Issues

The category-specific issue log

The Issues tab contains a spreadsheet view of all the issues opened in the selected category, with columns for standard and user-defined metadata fields (e.g., issue name, status, author, description, priority).

By selecting “Edit Issue View,” the icon in the second column of the issue log’s spreadsheet view, you can bring up a popup view of all fields related to the issue. This can be helpful in issue review or editing.

There are also dropdown menus for creating and deleting issues, controlling pagination, toggling on/off columns & other configuration options.

4.10 - Exports

Displays all available standard and custom exports, grouped by type.

The Exports tab offers data export originating in the selected category. If exports are required from the entire hierarchy, open Exports from the Root category. Exports display a progress metric and have a cancel button.

SkuDB’s standard exports include:

  • Category Export
  • Attribution Export
  • Item Export
  • Issue Export
  • Value Export
  • Stacked Value Export

4.11 - Reports

Summary reports pertaining to the hierarchy, items, and attributes.

Reports provide a way of visualizing statistical information about the data contained in the SkuDB instance. Reports give information on categories and items through a variety of metrics that are useful for QA, descriptive summaries and as design aids.

Reports are typically filterable to include terminal categories, or categories only on certain levels.

Reports can often be toggled between a graphical display and a table of information. Additionally, the scale can typically be adjusted between linear and logarithmic. Standard reports include:

  • Children per Category
  • Category Name Length
  • Attributes per Category
  • Attribute Name Length
  • Items per Category
  • Items Concentration
  • Items Burial  

4.12 - Radial Tree

A radial tree view of the hierarchy, with the selected category as the center point. If root is selected, allows for a radial view of the entire hierarchy.
An image of a radial tree view, displaying each category under the [Abrasives] L1 as a dot orbiting a central point, representing the parent category. Categories with higher product counts are displayed in red, while lower counts display green. Categories between the min and max threshold appear more green, yellow, or red depending on product count.

The Radial Tree view provides a radial graph of the hierarchy structure from the selected category and down. This is an adjustable graphical representation of the hierarchy that is useful for QA, descriptive summaries, and as a design aid. The radial graph is adjustable on the following parameters: Label Size, Orbit Radius, Category Radius, Extent, and Rotation. There are also buttons to Reset Controls and Toggle Fullscreen.

4.13 - Preview

An alternate view of items/products in the category that can be customized to reflect the expected display view.

The Preview mode simulates a web navigation experience based on the current state of the selected category and its children. Categories appear as if laid out on a webpage, with a search bar across the top, followed by category tiles, and with a listing of items and a navigation filter below. Preview is a useful mockup of the hierarchy design. It can also be valuable as a classification aid.

While SkuDB comes equipped with a default Preview Mode UI mirroring the typical features of a modern ecommerce experience, it can also be customized to mirror the expected display of category and product landing pages.

5 - Fields

A method to store non-Attribute metadata on categories and items

The Fields view allows a user to define any custom string or select fields on categories, attributes, values, items, units & issues. When creating a new field, a user may define a string field as WYSIWYG, meaning it will be larger with some basic formatting features like bold, italics, bullets, or numbered lists.

The Fields view lists all user-created fields that are stored on the SkuDB instance. The Fields view displays the Field’s location, name, description, and type.

Fields are editable. To edit an already existing field, click on the field “Name”, and edit the available metadata. When done editing click “Save” to implement your changes. To delete a field, use the edit function, and then click “Delete” in the bottom left-hand corner of the page.

To create a new Field, click the “New Field” button in the top right corner of the page. Then fill out the required metadata on the field creation page and click the “Create” button to create the field.

6 - Settings

Configurable parameters to customize your project

The Project Settings view allows a user to configure certain aspects of the project setup. There are four main tabs under the project settings: Summary, Item Tiers, Freeze and Preview.

Summary

The summary tab allows the user to define and edit the project name.

Item Tiers

A screenshot of the Item Tiers settings in skudb. It says Manage ordered item levels. Lower-numbered tiers are parents of higher-numbered tiers. Below the text is a table, with two rows, numbered 1 and 2. Under the name column, the rows are called Products and Items. A column called Primary is on the rightmost side. Products holds a value of No for Primary, while Items holds a value of Yes. A button at the top right offers the option to Append New Item Tier.

The Items Tiers tab allows a user to set and establish item tiers in a multi-tiered data model. For example, in the image below there are three tiers, each a subset of the others. The interface defines which tier is the primary tier and allows a user to rename or delete the tiers.

Preview Settings

The Preview settings allow a user to define which attribute is used for navigation in the Preview view.

7 - Exports

View exports made from anywhere in SkuDB
A list of filenames that have been exported from SkuDB. Names have information sequenced within them to make them unique, such as ACME Project.terms_view.2026-06-12_203646.xlsx. Each row has a status (Complete), a Progress of 100% or 0%, and a Date Created, with mm/dd/YYYY H:mm:ss AM/PM format.

The Recent Project Exports tab lists all the export requests across the project, as well as their timestamp. Clicking on an export file will allow a user to redownload an export, rather than regenerating the export.

8 - Imports

Import Attribute and Field values into SkuDB

The Imports table allows you to load/import attribute values and field values using a standardized import template.

an image of a dialog box with a dropdown displaying several different types of imports. The lists shows that Class Items, Master Items, Categories, Style Guides, and Terms can all be imported. Ther is also a scrollbar to the right showing that more imports exist below what is currently displayed.

Help text related to imports is included in app. One key feature of the import functionality is the “Upload & Assess” feature. This allows you to load an import file and validate outcomes BEFORE approving the import job. Imports also allow you to control how blank values are handled and how missing attributes are handled.

a dialog displaying the word Import at the top, and four subsections within the dialog: Import Type, showing the import type is an Item Value Grid. Empty Cell Handling, a dropdown currently displaying Leave Existing Value Where Cell Is Empty. Missing Attribute Handling, a dropdown currently displaying Report an Error When an Attribute Is Missing in a Category. and Import File, with a button displaying Choose File, and greyed out text to its right which says No File Selected. a button is also at the bottom right on the dialog, displaying the words Upload & Assess. It is also greyed out.

After an import is completed successfully, an import result summary is generated and stored for reference.

An import results summary is displayed, showing the Import Type, Import File, Status, and Date Created. In the table are three rows, of type Item Valuye Grid, Master Item Creation, and Item Value Grid. The first two have no import file listed, and a status of new, with create dates of June 23rd and June 12th. The third, Item Value Grid, shows an Import File called ACME Taxonomy.Trailer Cable.item-value-grid.2026-04-12_061012.xlsx, with a status of Finished, and a Date Created of April 12th, 2026.

Import a Category or Set of Categories

9 - Issues

A centralized location to track all issues across the hierarchy

The Issues page provides a centralized place to track all issues across the hierarchy.

The Issues page contains a spreadsheet view of all the issues opened in the selected category, with columns for standard or user defined metadata fields including issue name, “closed?”, issue author, description, and a creation timestamp.

The Issues page contains the “Edit Issue View” feature, which allows a user to select the icon in the second column and see a popup view of all fields related to the issue. This can be helpful in issue review or editing.

There is also a drop-down menu to create and delete issues, control how many issues are displayed, toggle on/off columns and other configuration options.

When creating an issue in the global issues view, a user may select “+ Create new issue” from the “Actions” drop down. This will open the issue creation form with the type-ahead field for selecting the issue location.

10 - QA

Style Guide and Term rules help teams normalize and maintain data effectively

The QA section includes a configurable term dictionary and style guideline module. These views are customizable via the Fields view.

Terms

The Term Dictionary is typically used to document preferred and non-preferred terms, and to track additional metadata at the term level (definition, term type, open issues).

A screenshot of the Terms table showing a list of terminology entries with columns for Term, Non-Preferred Terms, Accepted Acronym, and Case Sensitive status. The table includes rows such as #1 Phillips, #2 Phillips, #3 Phillips, 3M, ARO, Accufit, Accuturn, and Acry-Max, with corresponding alternate spellings or synonyms listed in the Non-Preferred Terms column and most entries marked as case sensitive.

Style Guides

The Style Guidelines module is typically used to maintain rules related to formatting of categories, attributes, item names, etc. This view is also configurable using the Fields view.

Screenshot of a Style Guides table in a web-based interface with a Terms tab visible beside it. The table shows columns for Guideline Name, Approval Status, Bad Example, and Good Example. Several rows list formatting rules such as / in Category Labels, Brand in Table Names, Number vs No., x in Dimension Values, Thread Size vs Diameter, ARP Dash Numbers, AWG Ranges in Item Names, and Abbreviation for Ounces. Most entries are marked Approved, with one marked Denied. Example columns show formatting corrections like No. of Pieces vs # of Pieces, dimension formatting like 12 x 7-7/8 corrected to 540 mm x 210 mm, dash normalization such as -210 to 210, and abbreviation normalization such as 120Z to 12 oz.