Settings: Products
Learn how the Products section lets your business create product records, manage attributes and SKUs, and track stock in a more structured way.
Thought Process
The Products section is more than just a place to add items. It is designed to give the CRM a structured product record first, and then allow the business to build out the rest of the product setup from there.
This is especially important where products may have different variations, multiple SKUs, or stock held across locations. Rather than forcing everything into one single step, the CRM separates the process into clear stages.
Why it matters
Products often need more structure than a simple name and price, especially where stock, variants, and different SKU records are involved.
Why the staged approach helps
Creating the product first and then managing attributes and SKUs afterwards makes the setup cleaner and easier to maintain.
What the Main Product Record Covers
Product name
The main product record starts with the product name and becomes the parent record for the rest of the setup.
Product type
Products can be created with a type so the CRM knows how that product should behave within the wider system.
Product group
Products can be assigned to a product group to help keep the catalogue more organised.
Brand and description
Brand and descriptive information can be stored on the main product record for clarity and presentation.
Base SKU prefix
A base SKU prefix can be stored to support later SKU creation where the business wants a structured SKU format.
Active or inactive status
Products can be enabled or disabled as needed so the list stays usable without having to remove old records completely.
Simple Products and Variant Products
The product setup supports two different ways of working.
Simple product
A simple product has no variations, so the first SKU and the first price can be added straight away as part of the product setup.
Variant product
A variant product should be saved as the parent product first, then attributes and SKUs are managed afterwards from the product row.
Managing Product Attributes
Once a parent product has been created, attributes can be managed from the product row for products that need variation or extra structured detail.
Attribute setup
Attributes help define the structure of a product where options or variations need to be handled properly.
Supports variant products
This is especially useful for products that are not just one single fixed item, but need variation underneath the parent record.
Managing SKUs
SKUs are managed separately once the parent product exists, giving more control over the actual sellable or stock-tracked units.
SKU code
Each SKU can hold its own SKU number or code as the main operational identifier.
Manufacturer part number
MPN values can be stored per SKU where manufacturer reference numbers are important.
Barcode
Barcode data can be stored at SKU level for scanning or stock purposes.
Unit of measure
Each SKU can store its own UOM so stock and pricing records stay consistent.
SKU status
Individual SKUs can be active or inactive without affecting the whole product record.
Price list and price
Simple setups can include an initial price and price list association straight away.
Stock by Location
Stock is handled at SKU level and can be viewed by location, which makes the setup much more useful where inventory is held across more than one place.
Stock by inventory location
The CRM can show stock quantities by location rather than only as one combined product total.
Stock movements
Stock changes are intended to be recorded through stock movement logic, helping preserve a clearer inventory history.
Inventory linked to SKUs
Stock is tied to SKU records, which makes the inventory setup more precise than tracking only at the parent product level.
Importing Products
Product import follows the same structured approach as the main product setup.
Simple product import
For simple products, the import can include the initial SKU and price on the same row.
Variant product import
For variant products, import the parent product first and then add attributes and SKUs afterwards.
Simple Walkthrough
- Go to Settings.
- Open the Products section.
- Create the parent product record first.
- If it is a simple product, add the initial SKU and pricing details.
- If it is a variant product, save it first and then use Manage Attributes and Manage SKUs.
- Open the SKU area to maintain SKU-specific details.
- Use the stock view to review quantity by location where needed.
Getting the Most From Products
Create the parent record first
This keeps the structure cleaner and makes later SKU or attribute work much easier to manage.
Do not force variants into simple products
If a product genuinely has variations, use the variant route rather than trying to keep everything in one flat record.
Keep SKU data tidy
Good SKU naming and consistent barcode or MPN entry makes stock and product handling easier later.
Think by location
If your business holds stock across more than one place, make sure the SKU and inventory setup reflects that from the start.
Import carefully
Keep simple and variant product imports separate in your thinking so the imported structure stays clean.
Review active status
Product and SKU activation controls are useful for housekeeping, but check what is in use before disabling anything.