Catalog structure
Organize complex parts catalogs into navigable experiences.
PartGrid helps teams structure machines, assemblies, schematics, and parts into categories and curated collections for customer self-service, dealer portals, embedded parts lookup, and internal support workflows.
Source catalog
Parts, schematics, machines
One governed catalog foundation
Category tree
Curated collections
One catalog, multiple experiences
Customer website
Dealer portal
Regional catalog
Support tool
Flat catalogs do not scale
A flat list of diagrams is not a parts catalog strategy.
Large parts catalogs need structure. Customers, dealers, ecommerce teams, and support agents all need a clear path to the right machine, assembly, diagram, and part.
Customers do not know which diagram contains the part they need.
Dealers need views that match the product lines they sell and support.
Support teams need fast navigation by machine, model, assembly, or system.
Ecommerce and portal pages need relevant diagrams, not the whole schematic library.
Duplicating catalog data for every audience creates inconsistency.
Structure layers
Categories, collections, dealer collections, and part groups each have a role.
PartGrid separates catalog structure from operational segmentation so teams can create clear catalog experiences without duplicating source data.
Categories
Organize machines, models, product families, assemblies, systems, suppliers, brands, or regions so users can browse the catalog in a way that matches how they search.
Collections
Curate schematics and related catalog context for a product line, portal, customer website, support workflow, dealer experience, or embedded parts lookup.
Dealer collections
Connect source collections to dealer companies when dealer-specific access, sharing, and governance are needed.
Part groups
Segment parts for filtering, pricing, bulk operations, and internal workflows. They are different from public catalog navigation and curated publishing views.
Categories
Create a catalog structure users understand.
Categories help organize catalog navigation around how users search for parts. Different industries can model the hierarchy differently: the goal is to help users reach the right diagram faster.
Machine catalog
Browse by family, model, assembly
Collections
Package the right diagrams into the right experience.
Collections curate schematics and catalog context for a specific audience, product line, channel, or publishing context. The same source catalog can support multiple collections without becoming multiple disconnected catalogs.
Customer website
Show the diagrams and parts relevant to a product family or self-service experience.
Dealer portal
Package the right source collections for dealer-facing support and sales workflows.
Regional catalog
Create a focused market view without turning the source catalog into disconnected copies.
Support workflow
Give service teams a structured path from machine to assembly to diagram.
Publishing context
Create different views without copying the catalog.
Maintain one governed catalog foundation while publishing curated views for customers, dealers, regions, product lines, portals, and internal workflows.
Governed source catalog
Parts, schematics, categories, reviewed PDF-derived assets, and source catalog context stay controlled in one foundation.
Customer self-service
Curated from source data, published for a specific context.
Dealer support
Curated from source data, published for a specific context.
Product-line catalog
Curated from source data, published for a specific context.
Embedded ecommerce page
Curated from source data, published for a specific context.
Publish curated collections into websites and portals.
A curated collection can appear inside a website, customer portal, dealer portal, ecommerce page, documentation page, or internal tool so users see only the relevant diagrams and parts.
Explore embedsSupport dealer and market-specific catalog views.
Collections can help create targeted experiences for different channels and dealer workflows. Where dealer governance is needed, dealer workspaces own the access and sharing story.
Explore dealer workspacesDesign the structure here. Maintain it at scale with Bulk Tools.
Collections and categories define how the catalog is organized and published. Bulk Tools help teams move schematics, update categories, import parts, export data, and apply changes across many records.
Explore bulk catalog operationsRelated capabilities
Part of the broader PartGrid catalog workflow.
Collections and categories are the structure layer that helps the rest of the catalog experience work together.
What this is not
Structure and publishing, not just folder management.
Collections and categories shape how interactive parts catalog experiences are organized, navigated, embedded, and published. They do not replace every structure in ERP, PIM, ecommerce, or documentation systems.
Part groups are separate: they segment parts for operational workflows such as filtering, pricing, and bulk actions. Categories and collections shape catalog navigation and presentation.
FAQ
Collections and categories questions.
What is the difference between categories and collections?+
What is a dealer collection?+
What is the difference between a collection and a part group?+
Can one catalog support multiple collections?+
Can collections be embedded?+
Can categories represent machines or assemblies?+
How do Bulk Tools relate to collections and categories?+
Do collections duplicate the source catalog?+
Ready to structure your parts catalog into usable experiences?
Show us your machines, diagrams, manuals, or current catalog structure and see how PartGrid can organize them into categories, collections, embeds, and dealer-ready workflows.