Purchasing lists
Overview
A purchasing list collects suggestions across several runs before ordering. That is the difference from converting directly: ordering individually every day means paying shipping and losing volume advantages.
The calculation is traceable rather than mysterious: each line shows the calculation — daily consumption rate, coverage, demand and the shortfall — plus the coverage in days. Anyone who does not believe the suggested quantity can recalculate it instead of overwriting it.
Core tasks
Run the calculation. The run produces suggestion lines with item, suggested quantity, coverage, calculation and sourcing route.
Use parameter sets. The calculation parameters can be saved as a set and reused; share with everyone makes a set usable by all — only its creator may still change it. Calculating without a set is equally possible.
Take lines over. Suitable lines move into a chosen purchasing list through take over.
Convert into purchase orders. Convert into purchase orders creates one draft order per supplier.
One restriction is stated explicitly: lines sourced from another warehouse are rejected. This tool is not meant for transfers between warehouses.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Purchasing list
A list collects demand before it turns into orders. The point is bundling: ten individual demands become one order per supplier instead of ten small ones.
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 120 characters | What the list is called, say "week 37" or "spring trade fair". |
Items items | no | articles with quantity and supplier | The collected demand. An article may appear several times; conversion consolidates them. |
Note note | no | text | A note on the list. |
Brand brandId | no | one of your brands | Which brand is buying. |
On conversion one order per supplier is created. Items without a supplier stay in the list rather than quietly disappearing.
Settings & permissions
- Module
module.purchasing. - Permission
purchasing.suggestion.manage. - The sourcing route per line distinguishes order from a supplier from *from another
warehouse*.
- The list does not order. It collects; it becomes binding only in the
FAQ & troubleshooting
The suggested quantity looks wrong. Read the line's calculation — daily rate, coverage, demand and shortfall are all there. Usually the figure is explained by an unusual consumption period.
Lines are missing after converting. Lines with the sourcing route from another warehouse are rejected — documented behaviour, not a fault.
I cannot change a shared set. Correct — shared sets may be used by everyone, changed only by the person who created them.
List or direct suggestion? For steady demand the list, for individual shortages the direct route via suggestions.