The API exposes two distinct product catalogs. They solve different problems and live under different endpoints:
| Catalog | What it represents | Endpoint |
|---|---|---|
| Supplier products | The items a given supplier offers to you | /api/v1/supplier/products |
| Company products | Your own catalog of finished goods / SKUs you sell | /api/v1/company/products |
Supplier products
A supplier product is scoped to a single supplier (supplierId is required on creation) and captures the commercial terms that supplier offers you:
- Identification —
name,code,description. - Unit commerce —
unitOfMeasure,unitPrice,currency. - Availability —
active.
Use supplier products to keep track of what each supplier can sell you. When you later create a purchase, you can reference items from this catalog.
Company products
A company product belongs to your own company catalog — the SKUs you actually sell or consume. It only carries the essentials:
name,code,description.unitOfMeasure,active.
Company products are the entities you reference when building product traceability journeys.
When to use which
- If the item is something you buy →
supplier/products. - If the item is something you sell or finish →
company/products. - For textile-specific materials (fibers, yarns, fabrics) use the textile endpoints, which carry specialized attributes the generic product schema does not have.
- For chemical substances use the chemicals endpoint, which adds CAS number and ZDHC level.
Units of measure
Both catalogs share the same allowed units:
Shell
KG, G, T, L, ML, M3, M, CM, MM, M2, PCS, ROLL, BOX, PALLET