🌐 NL · Last reviewed: 27 May 2026
Purchase Groups and Group Vendors
A Purchase Group clusters items with similar supply-chain characteristics for planned replenishment. Each group can carry several vendors with their own delivery terms; one is flagged as Default for the group.
The model
-
Create one Purchase Group per product family (e.g. BEAMS-CARBON, COIL-STAINLESS).
-
Add multiple Purchase Group Vendors, each with its own Delivery Term and remark.
-
Mark one vendor as Default (DXSteel enforces uniqueness within the group).
-
Link items to the group via Purchase Group Code on the Item card.
Field reference — Purchase Group
|
Field |
Purpose |
|---|---|
|
Code |
Group identifier. Primary key. |
|
Reorder Point (days) |
Minimum stock duration before reorder signal. |
|
Reorder Quantity (days) |
Planned replenishment cycle. |
|
Safety Stock Quantity (days) |
Safety margin. |
|
Days Average Sales Calculation |
Lookback window for consumption average. |
|
Max Inventory (days) |
Upper threshold where ordering stops. |
Field reference — Purchase Group Vendor
|
Field |
Purpose |
|---|---|
|
Purchase Group Code + Vendor No. |
Composite primary key. |
|
Delivery Term |
Lead time (DateFormula). Drives Expected Receipt Date on requisition lines. |
|
Remark |
Vendor-specific note. |
|
Default |
Only one vendor per group can be default (auto-unique). |
Best practices
Fill Days Average Sales Calculation (e.g. 90) so that Calculate Reorder-Point Parameters can run.
Set Delivery Term realistically — DXSteel uses it to derive expected receipt dates in MRP suggestions.
Errors
|
Message |
Cause |
|---|---|
|
"Purchase group '%1' is used by item '%2'." |
Attempting to delete a group still referenced by items. |
[Screenshot: Purchase Group with multiple vendors and one default]