Types & Configuration
Several small lookup lists exist purely to classify the bigger records. They share the same shape — a name, a manual sort order, and an active flag — and the same rule: a value that's in use can't be deleted, only deactivated. Grouping them here keeps the master-data section focused on the records that matter most.
The lookup lists
| List | Classifies | Example values |
|---|---|---|
| Material types | Materials (required) | Raw, Packaging, Additive |
| SKU types | Products (required) | Finished good, Sub-assembly |
| Customer types | Customers (required) | Retail, Distributor, Direct |
| Customer segments | Customers (optional) | VIP, New, Strategic |
| Order channels | Sales orders (required) | Web, Phone, EDI |
| Acquisition sources | Sales receipts (required) | TikTok ad, Meta ad, Organic |
How they behave
- Name + sort order + active flag. Each value is just a name;
sortOrdercontrols where it appears in pick lists, andisActiveretires it without breaking history. - Required vs. optional. Material, SKU, customer, and order-channel classifications are mandatory on their parent records; customer segment is optional.
- In-use protection. You can't remove a type while records still point at it. Reassign or deactivate first. Order channels and acquisition sources additionally support being deactivated and later reactivated.
See also
Manage these lists through the REST API or the MCP server.