Serial numbers can be entered directly when creating a receipt — simply list them for the stock item in the vyrobniCislaPrijata element.
Example in XML
<winstrom version="1.0">
<skladovy-pohyb>
<typDokl>code:PŘÍJEMKA</typDokl>
<typPohybuK>typPohybu.prijem</typPohybuK>
<kod>TEST1234</kod>
<sklad>code:PLZEŇ</sklad>
<skladovePolozky>
<skladovy-pohyb-polozka>
<cenik>code:PP 86.910 CR</cenik>
<sklad>code:PLZEŇ</sklad>
<mnozMj>2</mnozMj>
<cenaMj>50</cenaMj>
<vyrobniCislaPrijata>
<vyrobni-cislo>
<kod>4156156</kod>
</vyrobni-cislo>
<vyrobni-cislo>
<kod>145144</kod>
</vyrobni-cislo>
</vyrobniCislaPrijata>
</skladovy-pohyb-polozka>
</skladovePolozky>
</skladovy-pohyb>
</winstrom>
🚨 Element names are case-sensitive. Writing <typpohybuk> in lowercase is silently ignored — the import goes through, but the value is not set. For a receipt, this may not be noticeable, since receipt is the default; for an issue, however, this will create a document of the opposite type. The correct form is <typPohybuK>.
Example in JSON
{
"winstrom": {
"@version": "1.0",
"skladovy-pohyb": [{
"kod": "TEST1234",
"typDokl": "code:PŘÍJEMKA",
"typPohybuK": "typPohybu.prijem",
"sklad": "code:PLZEŇ",
"skladovePolozky": [{
"cenik": "code:PP 86.910 CR",
"sklad": "code:PLZEŇ",
"mnozMj": "2.0",
"cenaMj": "50.0",
"vyrobniCislaPrijata": [
{ "kod": "4156156" },
{ "kod": "145144" }
]
}]
}]
}
}
ℹ️ Serial number tracking needs to be enabled for the price list item using the evidVyrCis field; the unikVyrCis field additionally enforces their uniqueness. The number of serial numbers must match the quantity on the item — otherwise the import will fail with an error described in the article Error: Insufficient number of serial numbers provided.