Item Data

.wms has the ability to synchronise item data from Neto using NETO-APIACTION GetItem. Using this connection, item data can be automatically sourced based on one of the following rules:

• the item has been changed

• the item is new.

It is not a required component and we would not recommend usage in cases where the item profile is more complex than what Neto can store. For example, in cases where an item has multiple trade units, multiple dimensions, multiple barcodes, etc.

Data that is synchronised is mapped as:

Neto field	.wms field	Required	Notes
SKU	ItemCode	Yes
Name	ItemName	Yes
ShippingWeight	ItemWeight	Yes
ShippingLength x Shipping Width x ShippingHeight	ItemCubic	Yes
UPC	UnitGTIN	No	Will replace SKU if not present. Must be unique.
ShippingLength	TradeItemDepth	Yes
ShippingWidth	TradeItemWidth	Yes
ShippingHeight	TradeItemHeight	Yes

An alert email is sent on any item failure. By default, this will only update the unit level trade item in .wms and leave any inter, outers or additional trade units as they currently are.

In cases where .wms is not managing the internal bins, the Neto Pick Bin can be sourced to update the item's location during picking.

The Neto field used for this is the Pick Zone field.

In cases where .wms is not managing the internal stock levels, the Stock On Hand can be pulled from Neto in order to allow for waving rules to apply. This can be used to ensure that orders that do not have stock can either be rejected outright from the system or can be used in an Available To Promise check in wave builder.

In cases where .wms is managing the internal stock levels, .wms has the ability to update the Stock On Hand in Neto. This uses the Neto import template to upload and overwrite the existing Neto Stock On Hand data on an hourly basis. This is typically done using a SOH method, but can use an ATP method if the situation requires it.