Now Available:
The SyncOnlineSale and SyncOnlineSales calls now include the AutoRemoveInfo parameter. When set to "true" this parameter will pick against sales with the status of "Completed". If set to false, no picks will occur unless your account has AutoRemove enabled.

You now have the ability to pull the retrieve the cost of an item for a specific sale. You can find the documentation for this call here. For any questions / concerns about this call, feel free to use our developers portal.

We have updated the response format to our GetSalesByDate call! Now, transactions related to a sale, such as a pick, pass, or fail will display in the results.

A new call has been released, PickItemBulk, that enables users to pick products in bulk. You must first use getTokens to acquire user and tenant tokens (which are unique). Then you can use those tokens to pick products by SKU, warehouse ID, and location code within the warehouse. With ExpressPick, if your product is in one location in your warehouse, you can set ExpressPick to true and will not need the location. Sale ID also has its field if you want to trace a pick back to a sale. Use getWarehouses if you are unsure of the ID('s) for your warehouse(s).

A new call has been released, getHandlingTime, that enables users to retrieve their product and kit SKU's handling time by warehouse per Amazon channel account in SkuVault. You must first use getTokens to acquire user and tenant tokens (which are unique). Then you can use those tokens to retrieve a product and kit's handling time by SKU and by warehouse ID. Use getWarehouses if you are unsure of the ID('s) for your warehouse(s).

We have now have an /updatePOs call that will allow you to update your existing Purchase Orders. For more information, visit this link "https://dev.skuvault.com/reference#updatePos"

Now available through the GetKits call, statuses can be retrieved for both Kits and AP's. For more information please reference /getKits.

Using /getLocations, you can now retrieve locations with current quantity.

We've added an optional parameter to the /getSalesByDate call that can be used to pull sales by their last modified date rather than always using the order date.

We've released an update to the getTransactions call today which modifies the response for pick transactions. If a pick was made against a specific sale, that sale's ID will also be included in the response.