Important: the systems below have documented integrations with Ongoing WMS. That does not automatically mean every function is part of every Karlholm setup. Field mapping, responsibilities and actual functionality are verified during onboarding.
What usually needs to be synchronised
| Data | Purpose |
|---|---|
| Item data | Correct SKU, description, barcode and stock information. |
| Orders | New orders sent to the warehouse without manual entry. |
| Stock levels | Keeping the sales channel or ERP up to date with physical stock. |
| Status and tracking | Reporting picked and shipped orders and delivery information back. |
A typical integration project: decide which system is master for item data; define when an order is sent to the WMS; decide how stock levels are synchronised; define the status and tracking flow; test cancellations, backorders, returns and partial deliveries; approve go-live and monitoring.
Webshop platforms
| Platform | Typical flow with Ongoing WMS | Documentation |
|---|---|---|
| Shopify | Orders and product data to the WMS; stock levels, order status and tracking back to Shopify. Relevant for growing B2C ecommerce. | Ongoing: Shopify |
| WooCommerce | Orders and product data to the WMS; stock levels, order status and tracking back to WooCommerce. Relevant for WordPress-based ecommerce. | Ongoing: WooCommerce |
| Centra | Product register, orders, stock levels and events through the documented integration and webhooks. | Ongoing: Centra |
| Adobe Commerce / Magento | Item register, orders and stock levels between Adobe Commerce and the WMS. | Ongoing: Adobe Commerce / Magento |
| Askås | Order and stock flows through Askås' documented integration with Ongoing WMS. | Ongoing: Askås |
ERP and finance systems
| System | Typical flow with Ongoing WMS | Documentation |
|---|---|---|
| Fortnox | Items, suppliers, orders, stock levels and – depending on setup – purchase orders. Common among Swedish companies. | Ongoing: Fortnox |
| Microsoft Dynamics 365 Business Central | Items, customer orders, purchase orders and warehouse-related statuses via the chosen integration route. | Ongoing: Business Central |
| Visma.net | Items, suppliers, orders, purchase orders and stock levels. | Ongoing: Visma.net |
Shipping
| System | Typical flow with Ongoing WMS | Documentation |
|---|---|---|
| nShift | Transport booking, labels and – depending on the nShift product – tracking and transport status between the WMS and the shipping platform. | Ongoing: nShift |
Not on the list? Ongoing's full integration catalogue covers more webshops, ERPs, marketplaces and carriers, and custom connections can be built through the API.
Keeping stock levels in sync
Stock levels need to be consistent between the physical warehouse, the WMS, your webshop and your ERP. Clear master responsibility and good synchronisation reduce the risk of overselling and manual corrections.
- Master for stock – decide which system is the authoritative source for physical availability.
- Sync frequency – how often stock is updated should match the order pace and the channel's requirements.
- Reserved stock – blocked, reserved or unsellable goods must not accidentally show as available.
Steps: define stock types, choose the master, map warehouse statuses, test purchases close to zero stock, test returns to stock and monitor deviations.
Order status and tracking
An order is not finished from the customer's point of view just because the warehouse has packed it. Status and tracking need to flow back to the right system so customer service and recipients see what is actually happening.
- Order status – picked, packed, shipped or blocked must be defined consistently.
- Tracking – tracking numbers and links should reach the right channel without manual copying.
- Deviations – cancellations, backorders or transport problems must not show as a normal delivery status.
Steps: define a status model, map warehouse statuses to your systems, decide when tracking is created, test carrier flows, test deviations and follow up incorrect statuses.
Technical integration details change over time – always check the current documentation from Ongoing.
Frequently asked questions
Does a documented Ongoing integration mean it is included in our setup?
No. A documented integration in Ongoing's catalogue shows that a connection exists. Field mapping, responsibilities and which functions are actually used are verified for your setup during onboarding.
What if our system is not in the catalogue?
Then an API integration may be the route. See API and EDI integration.
Which system should be master for stock?
That is decided per setup. Usually the WMS is the authoritative source for physical availability, while the ERP or webshop is master for item data – but it must be defined explicitly.