Skip to main content

Product Details

Updated this week

The Product Details screen is where you manage the high-level information and structure of a product in Brahmin Solutions.

A Product is the parent record that groups one or more variants (SKUs). Products help organize your catalog, reporting, and pricing, while inventory is always tracked at the variant level.


What is the Product Details Screen Used For?

Use the Product Details screen to:

  • Maintain product-level descriptions and identifiers

  • Assign brand, category, and tags

  • View all variants under the product

  • Add new variants or kit variants

  • Keep your catalog organized and searchable

Products do not hold inventory directly β€” variants do.


How to Access Product Details

To open a product:

  1. Go to Inventory β†’ Products

  2. Search or browse for the product you want

  3. Click the product name to open the Product Details page


Product Header Overview

At the top of the page, you will see:

  • Product Name

  • Status (Active / Inactive)

  • Type: Product

This confirms you are viewing the product-level record, not an individual SKU.

Product Details Section

This section contains internal identifiers and descriptions for the product.

Product SKU (Required)

The SKU field at the product level is used as the main internal identifier for the product grouping.

Best practices:

  • Keep it broad and reusable

  • Do not include size, color, or packaging details

  • Use variants for SKU-level differences

Short Description

The short description is a brief summary of the product.

Common uses:

  • Internal catalog reference

  • Quick identification in product lists

Example:

Core item used in multiple configurations.

Long Description

The long description supports more detailed internal documentation.

Use this field for:

  • Product specifications

  • Handling notes

  • Internal operational context

  • Additional details shown to users (if enabled)

This field supports rich text formatting.

Product Organization Section

This section controls how products are grouped for navigation, reporting, and pricing.

Brand

Assigning a brand helps with:

  • Catalog consistency

  • Filtering and reporting

  • Pricing organization

Example:

Brand A

Category

Categories help group products across inventory and reporting.

Example:

Finished Goods
Raw Materials
Packaging

Tags

Tags are flexible labels used for search and segmentation.

Examples:

  • Seasonal

  • Export

  • Restricted

  • High Priority

Tags are especially useful when creating saved views and filters.\

Variants Section

Every product contains at least one variant (SKU).

The Variants table shows all SKUs under the product, including operational inventory metrics such as:

  • SKU Code

  • Available

  • Can Pick

  • On Hand

  • Allocated

  • Expected

  • Committed

  • MAC (Moving Average Cost)

This provides a quick snapshot of inventory performance across the product family.


Adding Variants

From the Product Details screen, you can create additional SKUs at any time.

Add Variant

Click + Add Variant when you want to create another SKU under this product.

Common examples:

  • Different sizes

  • Different packaging formats

  • Different configurations

Add Kit

Click + Add Kit when you want to create a kit or bundle variant.

Kit variants are used when:

  • The item is composed of multiple component SKUs

  • Inventory is consumed from underlying components

  • The bundle is sold as a single unit

Example:

Bundle = Component A + Component B


When Should You Edit the Product vs the Variant?

A simple rule:

Edit the Product when managing:

  • Product name and descriptions

  • Brand, category, and tags

  • Variant grouping and organization

Edit the Variant when managing:

  • Inventory quantities

  • Vendor assignments

  • Pricing

  • Reordering rules

  • Lot and expiration tracking


Best Practices

  • Keep product names broad and consistent

  • Use variants for operational SKU differences

  • Always assign brands and categories for reporting

  • Use tags for advanced filtering

  • Add kits only when components must be tracked separately


Related Articles

Did this answer your question?