Purchase Orders And Inventory Control

If purchase orders are being used in Neto Advanced Inventory, then the connector searches for them using a filter on the purchase orders screen. This filter, only selects purchase orders with a Sent status.

The Neto Advanced Inventory connector accesses each individual purchase order and collects the following information:

• Purchase Order Number

• OrderID (Neto's internal number)

• For each line:

  • Line number

  • SKU

  • Quantity.

These will then be imported using the UpsertSimpleReceipt API endpoint.

The Neto Advanced Inventory connector checks for changes, approximately, every 15 minutes and will re-upsert purchase orders on every check. As such, modifications made in the purchase order will synchronise prior to closure.

For completion of purchase orders, an export must be set up that the Neto Advanced Inventory connector will call, in order to complete the orders.

Note: This is not the File Export launched from .wms, as the Neto Advanced Inventory connector must work off summaries not off individual purchase orders. This is due to the last of an independent API to complete.

The following information must be provided in the export using a Generic SQL:

• ShipmentNumber

• OrderID (will be in Additional01)

• ItemCode

• ReceivedQuantity.

To speed up the connection, set an interval on the purchase orders to be checked. Typically, this is 5 days.

Once the export is created, provide it as the Closed Receipts Export ID. This will be called by the connector. When called, the Neto Advanced Inventory connector searches for the particular purchase order using its Order ID and then being the receipt process. The Neto Advanced Inventory connector receives the appropriate quantity for each SKU as based on the export.

Once all values have been entered, the Neto Advanced Inventory connector selects Save And Complete on the purchase order. If any items are left to be received, Neto's default behaviour is to create the same purchase order again for the remaining items using a '-1' suffix. For example, PO1234 becomes PO1234-1.

There are 2 primary reasons a purchase order may not be able to be closed by the Neto Advanced Inventory connector:

• The purchase order has the same item on multiple lines. As the export does not associate with lines, it may struggle with any purchase order that has the same SKU on multiple lines.

• If someone has already received the purchase order, but has not completed it, the Neto Advanced Inventory connector will not be able to receive the purchase order and it will have to be done manually.

Similar to purchase orders, stock adjustments operate based on a file export, which will typically contain the past 5 to 6 hours of adjustments and create them using the associated UserID in Neto.

The SQL output required is as below from the ULDL table:

• CONCAT ('Adjustment', ULDID)

• AdditionalInfo as AdditionalRef

• AdditionalInfo as Type

• ItemCode

• ChangeByUnitQuantity

These stock adjustments are created in Neto by the connector using specified reason codes. The connector takes the first 3 digits of the reason code and matches that to a specified Neto reason in the drop-down menu. The generic reason codes:

• ST1 > New Stock

• ST2 > Damaged

• ST3 > Shrinkage

• ST4 > Promotion

• ST6 > Other

• ST7 > Cost revaluation

ST5 is a hidden reason code and does not exist in the list. It is only used by the stocktake section of Neto and cannot be accessed by this tool.