Wics file definitions

Export: Products

Products-StoreNr{0}-Batch{1}.xml

If StoreNr{0} is used as the store number and Batch{1} is used as an incremented sequence number for each export.

In each export run, the products that have been modified since the previous export are exported. It does not consider whether underlying data (such as barcodes or purchase information) has been modified.

If the setting is active to use the external code as the product number, and there is no external code for a modified product, then this product will be skipped.

Export: SaleOrders

In each run, sales orders that have been modified since the previous export are exported. Only sales orders with at least 1 order line are exported. Sales orders from relationships without an address are skipped.

Export: PreAlert (Packing slip messages)

All product receipts that have been modified since the previous export will be sent to Wics.

Update 17/9/2018: This message is not about the packing slip messages, but about the purchase orders. Wics wants to be informed about the existing open purchase orders, so that they can refer to the correct purchase order number when returning the receipt message (ExportStoreConfirmation.xml).

Import: ExportStockCorrection*.xml (Stock corrections)

This file contains stock corrections from Wics. The provided corrections will be applied as stock corrections per system date and time in RetailVista.

Import: StockReport*.xml (Stock report)

This file contains stock levels (end levels) from Wics. The provided stock levels are compared with the stock in RetailVista and the difference is recorded as a stock correction per system date and time in RetailVista.

Import: SaleOrderFreeze*.xml (Securing sales orders against mutations)

This file contains sales order numbers of orders that Wics has started to deliver. A sales order is blocked in RetailVista so that it cannot be mutated. If the sales order cannot be found (anymore), the line is ignored. If the sales order is already blocked against changes, the line is also ignored.

Import: ExportShippingConfirmation*.xml (Delivery message)

This file contains information about delivered products to customers. With this file, reservations are created in RetailVista. If the sales order number does not exist, the orderStatus line is ignored.

If the correct criteria are met, the reservation is automatically converted into a delivery on account. The criteria for this are one of the following:

1 - The relationship of the sales order is also a debtor. In that case, the delivery on account is created for this debtor.

2 - If a fallback debtor is indicated for the sales order in the webshop. In that case, the total value of the reservation must be less than or equal to the total amount already paid on the sales order.

Import: ExportStoreConfirmation*.xml (Inbound message)

Nothing is currently done with this type of message in RetailVista.

Update 9/17/2018: This message is important as it is used to register receipts in ERP from the inbound process and link these receipts to the correct purchase order. This reduces the size of open purchase order lines.