SalePack
The SalePack resource allows to add products to packing in sale task. This is how you call it:
The full range of URIs and HTTP Verbs supported are:
Operation | HTTP Action |
Create or modify new Packing | POST /SalePack |
Available Fields for SalePack:
Property | Type | Length | Required | Notes |
TaskID | Guid |
| Yes | Sale task identifier |
Lines | Array of Line | 1 | Yes | At least one line is required. See description below |
Available Fields for Line:
Property | Type | Length | Required | Notes |
SKU | String | 50 | Yes | Product SKU |
Location | String | 256 | Yes | Location where product was picked from. Should match Sale Pick. Bins are referenced by the following format: “Location: Bin” |
Quantity | Decimal with up to 4 decimal places |
| Yes | Quantity of product to pack |
Box | String | 256 | Yes | Box number |
Operation description
To create new or add lines to existing Packing you need to send POST request to SalePack endpoint with SalePack structure (see above) as payload.
Sample of payload
POST /SalePack
{
"TaskID": "E6E8163F-6911-40e9-B740-90E5A0A3A996",
"Lines": [{
"SKU": "SKU-1",
"Location": "Main Warehouse",
"Quantity": 1,
"Box": "Box 1"
}]
}
Note
Status of Packing will be automatically changed to “AUTHORISED” after all lines from picking would be packed.
Return value
In case if no errors occurred you will receive response with list of packed lines for specified Sale Task, otherwise you will receive response with error list, like this:
[{
“ErrorCode”:400,
“Exception”:”Error explanation will be here”
},
{
“ErrorCode”:400,
“Exception”:”You try to pack more than picked”
}]
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB