Integration between Ongoing WMS and Norce (previously Jetshop)
Table of contents
Introduction
Norce is a Swedish eCommerce platform provider.Features
The integration contains the following processes and features. The processes can be independently switched on or off.Article Registry
The article registry is automatically pulled from the shop to Ongoing WMS.
Field mapping
Ongoing WMS field name | Norce field name |
---|---|
ArticleDefinition ⇒ ArticleNumber | (product ⇒ ArticleNumber) or (variant ⇒ ArticleNumber) * |
ArticleDefinition ⇒ ArticleName | (product ⇒ Name) or (product ⇒ Name + " - " + variant ⇒ AttValue) * |
ArticleDefinition ⇒ ProductCode | (product ⇒ ProductId) or (variant ⇒ ProductId) * |
ArticleDefinition ⇒ ArticleDescription | product ⇒ ProductDescription |
ArticleDefinition ⇒ BarCode | product ⇒ EanCode |
ArticleDefinition ⇒ Weight | product ⇒ Weight |
ArticleDefinition ⇒ Volume | product ⇒ Volume |
ArticleDefinition ⇒ ArticleDescription | product ⇒ ProductDescription |
ArticleDefinition ⇒ CustomerPrice | product ⇒ Price |
ArticleDefinition ⇒ SupplierArticleNumber | product ⇒ ManufacturerArtnr |
Orders
Orders are automatically pulled from the shop to Ongoing WMS. When an order has been handled, it is reported back to the shop. This last step can also make Norce bill the end-customer.
Field mapping
Ongoing WMS field name | Norce field name |
---|---|
Customer ⇒ Name | OrderData ⇒ ShipToCompany + ", " + OrderData ⇒ ShipToFirstName + " " + OrderData ⇒ ShipToLastName * |
Customer ⇒ Address | OrderData ⇒ ShipToAddress |
Customer ⇒ Address2 | OrderData ⇒ ShipToCo |
Customer ⇒ PostCode | OrderData ⇒ ShipToZipCode |
Customer ⇒ City | OrderData ⇒ ShipToCity |
Customer ⇒ CountryCode | OrderData ⇒ ShipToCountryCode |
Customer ⇒ ExternalCustomerCode | OrderData ⇒ CustomerId |
Customer ⇒ IsVisible | true |
Customer ⇒ Email | OrderData ⇒ Email |
Customer ⇒ MobilePhone | OrderData ⇒ ShipToMobilePhone ** |
Customer ⇒ NotifyByEmail | true if ((Customer ⇒ Email) is not null or whitespace), else false |
Customer ⇒ NotifyBySMS | true if ((Customer ⇒ MobilePhone) is not null or whitespace), else false |
Customer ⇒ TelePhone | OrderData ⇒ OrderData ⇒ ShipToPhone *** |
Customer ⇒ NotifyByTelephone | true if ((Customer ⇒ TelePhone) is not null or whitespace) && ((Customer ⇒ NotifyBySMS) is false), else false |
OrderInfo ⇒ DeliveryDate | OrderData ⇒ OrderDate |
OrderInfo ⇒ GoodsOwnerOrderNumber | OrderData ⇒ OrderId |
OrderInfo ⇒ ReferenceNumber | OrderData ⇒ ReferenceNumber |
OrderInfo ⇒ OrderRemark | OrderData ⇒ PaymentTypeText |
OrderInfo ⇒ WayOfDeliveryType ⇒ Code | OrderData ⇒ freightMethodName |
OrderInfo ⇒ WayOfDeliveryType ⇒ Name | OrderData ⇒ freightMethodName |
* Only (OrderData ⇒ ShipToFirstName + " " + OrderData ⇒ ShipToLastName) if (OrderData ⇒ ShipToCompany) is null or empty.
** (OrderData ⇒ MobilePhone) if (OrderData ⇒ ShipToMobilePhone) is null or empty.
*** (OrderData ⇒ MobilePhone) if (OrderData ⇒ ShipToPhone) is null or empty.
Stock balance updates
Ongoing WMS manages the stock balances and continuously synchronizes these with Norce.
Default settings and considerations
The following needs to be considered before Ongoing WMS can activate the integration.
-
Synchronization interval.
Default: Every 15 minutes. It is usually a suitable balance between responsiveness and band-width usage. -
Stock balance updates. Should the available quantity be written to Norce from Ongoing WMS?
Default: Yes. - Does the article registry contain variants? This will require special handling by Ongoing WMS.
-
Which status should an order have for it to be pulled from Norce to Ongoing WMS?
Default: "Recieved". -
After an order has been handled by the warehouse, which status should it receive in Norce?
Default: "Delivered". - After an order has been handled by the warehouse, should Ongoing WMS cause Norce to bill the end-customer?
Getting started
For Ongoing to be able to activate the integration, the following needs to be done by Norce support:
- They need to activate the "SOAP Webservice" for the shop.
- They need to supply you with a URL, a password and a username for the webservice.