As tabs at the top of the Products page in the User Site.

As sections in the field app's product picker, in the order you set them.

As groupings on output documents (proposals, takeoff summaries, reports).

Create a new Category — give it a name and it becomes available as a destination for new Products and Bundles.

Rename a Category — the name update flows through to the field app and output documents. Existing Products and Bundles keep their assignment.

Reorder Categories — drag and drop to change the order. Put the Categories your team uses most at the top. The order set here is the order users will see in the field app.

Delete a Category — only available for empty Categories. Move or delete the Products and Bundles inside before deleting the Category itself.

Match your team's vocabulary. If your sales team calls them "fence sections," that's the Category name — not "Linear Bundles."

Order by frequency, not alphabet. The most-used Categories at the top saves taps in the field.

Don't over-segment. If a Category contains fewer than 3 items, ask whether it really needs to be its own Category.

Categories aren't sub-folders. ArcSite supports one level of Categories — there are no nested sub-categories. If you need finer organization within a Category, use Product Groups or naming conventions instead.

Build Your Product Catalog in the User Site — how Products, Groups, and Bundles fit together inside Categories.

Types of Products — built-in Product Types you can place into a Category.