Integration between Ongoing WMS and the ERP Nemo made by Eseco
Ongoing has developed an integration with the ERP system Nemo made by Eseco. This integration makes it possible for businesses which use Nemo to easily outsource their warehouse needs to a 3PL company which uses Ongoing WMS. The integration can also be used by businesses who run Nemo and who want to run their own warehouse using Ongoing WMS.
With Ongoing WMS, you'll be able to utilize features such as scanning (compatible with any device) to reduce picking errors, efficient picking routes, batch-picking, streamlined return processing, automatic label printing, warehouse maps, support for multiple warehouses, and comprehensive traceability. Moreover, Ongoing WMS is entirely web-based, allowing you to access your warehouse operations from any device, anywhere.
Get started with a free trial today!
Table of contents
Scheduled functions
Some functions in the integration run on a schedule. The article registry, orders and purchase orders are synced automatically from Nemo to Ongoing WMS.Article registry
The article registry is read automatically from Nemo to Ongoing WMS. If a change is made in Nemo, it will be reflected automatically in Ongoing WMS.
Field mapping
Ongoing WMS field name | Nemo field name |
---|---|
Article ⇒ Article number | Article ⇒ Item number |
Article ⇒ Article name | Article ⇒ Item name |
Article ⇒ Purchase price | Article ⇒ Purchase price |
Article ⇒ Structure article info | Article ⇒ Items in composite |
Article ⇒ Alternative article names | Article ⇒ Texts |
Filters
By default, all published products that have been updated in Nemo will be synced to Ongoing WMS. Deleted products will not be synced.
Orders
Invoices are read automatically from Nemo to Ongoing WMS, resulting in orders being created in Ongoing WMS corresponding to the invoices in Nemo. If the invoice contains a PDF-file, the file will be copied to Ongoing WMS.
Note: For the invoice sync to work you will need to specify one or more country codes to sync invoices from.
Field mapping
Ongoing WMS field name | Nemo field name |
---|---|
Order info ⇒ Order number | Invoice ⇒ Invoice number |
Order info ⇒ Reference | Invoice ⇒ Order number |
Order info ⇒ Prepared transport document ID | Invoice ⇒ Shipments[0] ⇒ Shipment ID |
Customer ⇒ Customer number | Invoice ⇒ Customer number |
Customer ⇒ Name | Invoice ⇒ Customer name |
Order line ⇒ Article number | Order line ⇒ Article number |
Order line ⇒ External order line code | Order line ⇒ Invoice row number |
Order line ⇒ Number of items | Order line ⇒ Count |
Order line ⇒ Customs total value | Order line ⇒ Price |
Filters
By default, all invoices matching the following filter in Nemo are synced to Ongoing WMS. Note that if the order exists in Ongoing WMS, it will only be updated if the status of the order in Ongoing WMS allows it to be updated!
Nemo field name | Default filter |
---|---|
Order ⇒ Last change time | Later than the last time the integration synced |
Country code | SE |
Status | Open |
Purchase orders
Purchase orders in Nemo are mapped to purchase orders in Ongoing WMS. This allows the warehouse to report received goods to Nemo.
Field mapping
Ongoing WMS field name | Nemo field name |
---|---|
Purchase order ⇒ Order number | Purchase order ⇒ ID |
Purchase order ⇒ Reference | Purchase order ⇒ Our reference |
Purchase order ⇒ In date | Purchase order ⇒ Date of delivery |
Purchase order ⇒ Order date | Purchase order ⇒ Order date |
Purchase order ⇒ Order remark | Purchase order ⇒ Comment |
Purchase order supplier ⇒ Supplier name | Supplier ⇒ Name |
Purchase order supplier ⇒ Supplier number | Supplier ⇒ Number |
Purchase order line ⇒ Article number | Purchase order line ⇒ Item number |
Purchase order line ⇒ Article name | Purchase order line ⇒ Item name |
Purchase order line ⇒ Count | Purchase order line ⇒ Ordered amount |
Purchase order line ⇒ Row number | Purchase order line ⇒ Row number |
Purchase order line ⇒ Currency code | Purchase order ⇒ Currency |
Purchase order line ⇒ Row price | Purchase order line ⇒ Purchase price |
Filter
By default, only purchase orders in Nemo that has not yet been completed will be synced to Ongoing WMS. For a purchase order to be synced it also needs to have been created/updated in Nemo since the last time the integration ran.
Functions based on user actions
Inbound deliveries
When a delivery is made to the warehouse, this will be recorded on a purchase order. This triggers an update of the purchase order in Nemo, where the received amount for each purchase order line will be updated. It is possible that the received quantities differ from the advised quantities.
Outbound deliveries
When an order has been set to status Sent or Collected in Ongoing WMS, the corresponding invoice in Nemo will be marked as invoiced and dispatched.
Inventory adjustments
It is possible to sync the stock changes to Nemo. By default, this is done every 15 minutes for the inventory changes that has occurred in Ongoing WMS. If this module is activated the integration will also perform a full stock sync once a night.
Getting Started
To configure this integration, you must provide an API key and URL for the API of Nemo.