How the Catalog connects to other modules
The Catalog is the shared list that the other modules pick from. A mistake here shows up everywhere, which is why it pays to set it up carefully.
| Module | What it uses from the Catalog | Example |
|---|---|---|
| Inventory | Product and variant: stock is kept per variant, per location | 100 × Cotton T-shirt Blue / Large on shelf A-01-01 |
| Sales | Products and variants on order lines | Order SO-1188: 10 × Ceramic Mug, Standard |
| Purchasing | Products and variants on purchase and receipt lines | 200 × Ceramic Mug from the supplier |
Rules of thumb
| Do | Because |
|---|---|
| Create the product before adding stock or orders | Other modules can only pick existing variants. |
| Give every variant a clear name and SKU | Staff choose variants by name in Inventory, Sales and Purchasing. |
| Use Discontinued instead of deleting | Deleting doesn't check stock or orders, and leaves them pointing at nothing. |
| Change product codes rarely | Documents and reports refer to them. |
| Keep colour and size on the variant, not in categories | Categories group products; variants are the versions you stock. |
Status isn't enforced elsewhere
Product and variant status is information for people. Other modules don't currently hide Inactive or Discontinued items, so tell your team when something is withdrawn.