Stock-management settings let an automation calculate or normalize inventory before writing it into SureDone.
They are commonly used when a vendor feed provides multiple warehouse quantities, duplicate rows per SKU, or values that need to be transformed before they become the final stock number.
Summing Multiple Stock Fields
When a feed provides separate quantities for different warehouses, you can sum them into one final stock field.
"field_run": {
"warehouse_east": "EastQty",
"warehouse_west": "WestQty",
"warehouse_central": "CentralQty"
},
"stock_field": "stock",
"stock_sum_fields": ["warehouse_east", "warehouse_west", "warehouse_central"]
In this example, the values are added together and saved into stock.
Multiline Stock
Some feeds repeat the same SKU on multiple rows, one row per warehouse or location. In that case, stock_sum_multiline_field helps the engine understand how to group and total those rows into one final stock quantity.
Important Requirement: Set stock_field
Where Source Values Can Come From
The fields used in stock calculations are usually introduced through field_map or field_run. That means you can keep intermediate warehouse values available for math even if you do not want to save each one as a user-facing field in SureDone.
Common Patterns
- Sum several warehouse quantities into one stock field
- Choose a fallback warehouse when the preferred location is out of stock
- Preserve individual warehouse quantities in separate custom fields while also calculating a total
- Allow or block negative stock with stock_negative
Best Practice
Start by deciding what the final inventory field should be in SureDone, set that as stock_field, and then build the rest of the stock logic around it. That makes validation clearer and avoids ambiguous stock behavior later.