Skip to content

Categories

Categories group items and expense items for filters, reports, store browsing, and optional accounting. The same category list is shared across Revenues, Expenses, Inventory, and POS.

Navigation: left sidebar → Setup → Categories, or Revenues / Expenses / Inventory → Data Setup → Categories (/setup/categories).

Without categories, every item posts to the same default GL accounts from GL Account Mappings. Categories let you:

  • Organize products for lists, POS, and the online store
  • Report sales and inventory by product group
  • Optionally post different product groups to different GL accounts (for example Service revenue vs Merchandise revenue, or separate stock accounts)

Assign a category on each item. Accounting fields on the category apply to all items in that group when set.

Click + Create.

Field Description
Code Identifier (often auto-numbered)
Name / Local name Display names
Shipping policy Optional default for e-commerce (category-level policy)
Show in store When e-commerce or POS is enabled, whether the category appears in the store/POS
Separate item auto number When enabled, items in this category can use a dedicated number format

Save, then configure the Accounting tab if the Accounting (GL) module is enabled.

The Accounting tab appears when the GL module is enabled for your tenant. All four fields are optional overrides. Leave them empty to use the system defaults from GL Account Mappings.

Field Used when Why set it
Sales account Selling items in this category (invoice / credit note revenue) Post this group’s sales to a specific revenue account instead of the mapped Revenue / Revenue Service account
Inventory account Stock valuation (receive, sell COGS side, purchase of inventory items) Keep this category’s on-hand stock in its own asset account
Cost of goods account Cost of goods sold when inventory items are invoiced Separate COGS by product line for profit and loss analysis
Stock issue account Free goods / stock issues (non-sale stock out) Route issues separately from COGS; if empty, COGS (category or mapped) is used

How posting picks an account (simplified):

  1. Category override (this tab), if set for that role
  2. Else GL Account Mapping for that line role (Revenue, Inventory, COGS, …)

Expense purchases of non-inventory lines can also use a per-item Expense GL Account on the expense item — that overrides the mapped Expense account for that item only.

Placeholders on the selectors show the currently mapped default account so you can see what will be used when the override is empty.

Complete the Chart of Accounts and GL Account Mappings before relying on category overrides.

Access requires the Categories permission scope (category). Menu items appear based on your role and enabled modules.