Integration between Ongoing WMS 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 Ongoing WMS.
Article Registry
Ongoing WMS pulls article registry updates from Viskan. Viskan contains the master data. Articles in Ongoing WMS are mapped to stock keeping units in Viskan since the Products in Viskan contains stock keeping units with different attributes, which is not supported in Ongoing WMS. Each stock keeping units in Viskan is therefore a seperate Article in Ongoing WMS. Thus, information from both the Products and their stock keeping units is used to create Articles, which can be seen in the field mapping.
| Ongoing WMS field name | Viskan field name |
|---|---|
| ArticleDefinition ⇒ ArticleNumber | Product ⇒ ProductNumber |
| ArticleDefinition ⇒ ArticleName | Product ⇒ ProductName + StockKeepingUnit ⇒ Attribute1Code + StockKeepingUnit ⇒ Attribute2Code + StockKeepingUnit ⇒ Attribute3Code |
| ArticleDefinition ⇒ ArticleDescription | Product ⇒ Translations ⇒ LongDescription |
| ArticleDefinition ⇒ Weight* | Product ⇒ StockKeepingUnit ⇒ Weight* |
| ArticleDefinition ⇒ Volume** | Product ⇒ StockKeepingUnit ⇒ Volume** |
| ArticleDefinition ⇒ CustomerPrice | Product ⇒ StockKeepingUnit ⇒ Prices ⇒ UnitPrice |
| ArticleDefinition ⇒ PurchaseCurrencyCode | Product ⇒ StockKeepingUnit ⇒ Prices ⇒ CurrencyCode |
| ArticleDefinition ⇒ BarCode | Product ⇒ StockKeepingUnit ⇒ EuropeanArticleNumber |
| ArticleDefinition ⇒ ProductCode | Product ⇒ 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 Ongoing WMS, this is reported back to Viskan.
| Ongoing WMS field name | Viskan field name |
|---|---|
| OrderInfo ⇒ GoodsOwnerOrderId | Order ⇒ DeliveryId |
| OrderInfo ⇒ GoodsOwnerOrderNumber | Order ⇒ DeliveryNumber |
| OrderInfo ⇒ DeliveryDate | Order ⇒ OrderDate |
| OrderInfo ⇒ WayOfDelivery | Order ⇒ DeliveryMethod ⇒ MethodName |
| OrderInfo ⇒ CustomerPrice | Order ⇒ Value ⇒ Total |
| Orderline ⇒ ExternalOrderLineCode | Order ⇒ Rows Item ⇒ RowId |
| Orderline ⇒ ArticleNumber | Order ⇒ Rows Item ⇒ StockKeepingUnitId |
| Orderline ⇒ NumberOfItems | Order ⇒ Rows Item ⇒ Quantity |
| Customer ⇒ Name | Order ⇒ Customer ⇒ FirstName + Order ⇒ Customer ⇒ LastName |
| Customer ⇒ Address | Order ⇒ Customer ⇒ DeliveryAddress ⇒ AddressLine1 |
| Customer ⇒ PostCode | Order ⇒ Customer ⇒ DeliveryAddress ⇒ Zipcode |
| Customer ⇒ City | Order ⇒ Customer ⇒ DeliveryAddress ⇒ City |
| Customer ⇒ CountryCode | Order ⇒ Customer ⇒ DeliveryAddress ⇒ CountryCode |
| Customer ⇒ Email | Order ⇒ Customer ⇒ EmailAddress |
| Customer ⇒ MobilePhone | Order ⇒ Customer ⇒ Cellphone |
| Customer ⇒ NotifyByEmail | Order ⇒ Customer ⇒ EmailAddress (If the feild has value) |
| Customer ⇒ NotifyBySMS | Order ⇒ 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.
| Ongoing WMS field name | Viskan field name |
|---|---|
| InOrderInfo ⇒ GoodsOwnerOrderNumber | PurchaseOrder ⇒ PurchaseOrderId |
| InOrderline ⇒ ExternalOrderLineCode | PurchaseOrder ⇒ Rows Item ⇒ RowId |
| InOrderline ⇒ ArticleNumber | PurchaseOrder ⇒ Rows Item ⇒ StockKeepingUnitId |
| InOrderline ⇒ NumberOfItems | PurchaseOrder ⇒ Rows Item ⇒ Quantity |
| InOrderSupplier ⇒ SupplierName | PurchaseOrder ⇒ Supplier ⇒ SupplierName |
| InOrderSupplier ⇒ SupplierNumber | PurchaseOrder ⇒ Supplier ⇒ SupplierId |
Returns
Ongoing WMS automatically reads returns from Viskan. The returns are handled as purchase orders in Ongoing 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 they are expanded in Ongoing WMS. When the returns have been delivered and stocked, they are reported back to Viskan.
| Ongoing WMS field name | Viskan field name |
|---|---|
| InOrderInfo ⇒ GoodsOwnerOrderNumber | Return ⇒ ReturnId |
| InOrderInfo ⇒ IsReturnType | true |
| InOrderline ⇒ ExternalOrderLineCode | Return ⇒ Rows Item ⇒ RowId |
| InOrderline ⇒ ArticleNumber | Return ⇒ Rows Item ⇒ StockKeepingUnitId |
| InOrderline ⇒ NumberOfItems | Return ⇒ Rows Item ⇒ Quantity |
Supplier Registry
All suppliers are synced automatically from Viskan to Ongoing WMS.
| Ongoing WMS field name | Viskan field name |
|---|---|
| Supplier ⇒ SupplierName | Supplier ⇒ SupplierName |
| Supplier ⇒ SupplierNumber | Supplier ⇒ SupplierId |
Stock balance
When the stock balance differs in Ongoing WMS and Viskan, the balance is updated in Viskan with the balance from Ongoing WMS.
Default settings and considerations
-
Synchronization interval.
Default: Every 15 minutes. It is usually a suitable balance between responsiveness and band-width usage. -
Do you have any variant of your articles without unique article numbers? For example, colors, sizes, packaging.
Default: No. -
Sync of stock balance back to Viskan.
Default: false
Preparations
To set up the integration between Viskan and Ongoing WMS the following information is needed:
- Goods owner token: A identifier for the specific goods owner in Ongoing WMS, called X-Instance-Id at Viskan. Contact Viskan to get the token.
Please see this guide on how to set up an integration between Viskan and your Ongoing WMS.