Viskan logo

Integration between Ongoing Warehouse and Viskan

Table of contents

Introduction

Viskan is an omnichannel e-commerce platform. Viskan has a REST-API which the integration is built against.

Features

The integration pulls articles, orders, purchase orders, returns and suppliers from Viskan and reports back orders, purchase orders and returns if the status of the these are updated. Default is to not report back the stock balance. At first sync the whole article registry at Viskan is synced to Ongiong WMS.

Article Registry

Ongoing WMS pulls article registry updates from Viskan. Viskan contains the master data. Articles in Ongiong WMS are mapped to StockKeepingUnits in Viskan since the Products in Viskan contains StockKeepingUnits with different attributes, which is not supported in Ongiong WMS. Each StockKeepingUnit in Viskan is therefore a seperate Article in Ongiong WMS. Thus, information from both the Products and their StockKeepingUnits is used to create Articles, which can be seen in the field mapping.

Show field mapping

Ongoing WMS field name Viskan field name
ArticleDefinition ⇒ ArticleNumberProduct ⇒ ProductNumber
ArticleDefinition ⇒ ArticleNameProduct ⇒ ProductName + StockKeepingUnit ⇒ Attribute1Code + StockKeepingUnit ⇒ Attribute2Code + StockKeepingUnit ⇒ Attribute3Code
ArticleDefinition ⇒ ArticleDescriptionProduct ⇒ Translations ⇒ LongDescription
ArticleDefinition ⇒ Weight*Product ⇒ StockKeepingUnit ⇒ Weight*
ArticleDefinition ⇒ Volume**Product ⇒ StockKeepingUnit ⇒ Volume**
ArticleDefinition ⇒ CustomerPriceProduct ⇒ StockKeepingUnit ⇒ Prices ⇒ UnitPrice
ArticleDefinition ⇒ PurchaseCurrencyCodeProduct ⇒ StockKeepingUnit ⇒ Prices ⇒ CurrencyCode
ArticleDefinition ⇒ BarCodeProduct ⇒ StockKeepingUnit ⇒ EuropeanArticleNumber
ArticleDefinition ⇒ ProductCodeProduct ⇒ StockKeepingUnit ⇒ StockKeepingUnitId

* Conversion from g to kg

** Conversion from mm^3 to m^3


Orders

Ongoing WMS automatically reads orders from Viskan. When an order is fulfilled in Ongiong WMS, this is reported back to Viskan.

Show field mapping

Ongoing WMS field name Viskan field name
OrderInfo ⇒ GoodsOwnerOrderIdOrder ⇒ DeliveryId
OrderInfo ⇒ GoodsOwnerOrderNumberOrder ⇒ DeliveryNumber
OrderInfo ⇒ DeliveryDateOrder ⇒ OrderDate
OrderInfo ⇒ WayOfDeliveryOrder ⇒ DeliveryMethod ⇒ MethodName
OrderInfo ⇒ CustomerPriceOrder ⇒ Value ⇒ Total
Orderline ⇒ ExternalOrderLineCodeOrder ⇒ Rows Item ⇒ RowId
Orderline ⇒ ArticleNumberOrder ⇒ Rows Item ⇒ StockKeepingUnitId
Orderline ⇒ NumberOfItemsOrder ⇒ Rows Item ⇒ Quantity
Customer ⇒ NameOrder ⇒ Customer ⇒ FirstName + Order ⇒ Customer ⇒ LastName
Customer ⇒ AddressOrder ⇒ Customer ⇒ DeliveryAddress ⇒ AddressLine1
Customer ⇒ PostCodeOrder ⇒ Customer ⇒ DeliveryAddress ⇒ Zipcode
Customer ⇒ CityOrder ⇒ Customer ⇒ DeliveryAddress ⇒ City
Customer ⇒ CountryCodeOrder ⇒ Customer ⇒ DeliveryAddress ⇒ CountryCode
Customer ⇒ EmailOrder ⇒ Customer ⇒ EmailAddress
Customer ⇒ MobilePhoneOrder ⇒ Customer ⇒ Cellphone
Customer ⇒ NotifyByEmailOrder ⇒ Customer ⇒ EmailAddress (If the feild has value)
Customer ⇒ NotifyBySMSOrder ⇒ Customer ⇒ Cellphone (If the feild has value)

Purchase Orders

Ongoing WMS automatically reads purchase orders from Viskan. When the purchase order is delivered to the warehouse and stocked, it is reported back to Viskan.

Show field mapping

Ongoing WMS field name Viskan field name
InOrderInfo ⇒ GoodsOwnerOrderNumberPurchaseOrder ⇒ PurchaseOrderId
InOrderline ⇒ ExternalOrderLineCodePurchaseOrder ⇒ Rows Item ⇒ RowId
InOrderline ⇒ ArticleNumberPurchaseOrder ⇒ Rows Item ⇒ StockKeepingUnitId
InOrderline ⇒ NumberOfItemsPurchaseOrder ⇒ Rows Item ⇒ Quantity
InOrderSupplier ⇒ SupplierNamePurchaseOrder ⇒ Supplier ⇒ SupplierName
InOrderSupplier ⇒ SupplierNumberPurchaseOrder ⇒ Supplier ⇒ SupplierId

Returns

Ongoing WMS automatically reads returns from Viskan. The returns are handled as purchase orders in Ongiong WMS and thus turns up in the same list as all the purchase orders. The difference is that the purchase orders that originate from return orders in Viskan are tagged as returns, which can be seen if the are expanded in Ongiong WMS. When the returns have been delivered and stocked they are reported back to Viskan.

Show field mapping

Ongoing WMS field name Viskan field name
InOrderInfo ⇒ GoodsOwnerOrderNumberReturn ⇒ ReturnId
InOrderInfo ⇒ IsReturnTypetrue
InOrderline ⇒ ExternalOrderLineCodeReturn ⇒ Rows Item ⇒ RowId
InOrderline ⇒ ArticleNumberReturn ⇒ Rows Item ⇒ StockKeepingUnitId
InOrderline ⇒ NumberOfItemsReturn ⇒ Rows Item ⇒ Quantity

Supplier Registry

All suppliers are synced automatically from Viskan to Ongiong WMS.

Show field mapping

Ongoing WMS field name Viskan field name
Supplier ⇒ SupplierNameSupplier ⇒ SupplierName
Supplier ⇒ SupplierNumberSupplier ⇒ SupplierId

Stock balance

When the stock balance differs in Ongiong WMS and Viskan, the balance is updated in Viskan with the balance from Ongiong WMS.

Default settings and considerations

  1. Synchronization interval.
    Default: Every 15 minutes. It is usually a suitable balance between responsiveness and band-width usage.
  2. Do you have any variant of your articles without unique article numbers? For example, colors, sizes, packaging.
    Default: No.
  3. Sync of stock balance back to Viskan.
    Default: false

Preparations

In order to set up the integration between Viskan and Ongoing WMS the following information is needed: