Skrym LogoOngoing

Ongoing

Learn how the Skrym-Ongoing integration works

Ongoing is one of the most popular Warehouse Management Systems (WMS) in Sweden for e-commerce retailers. It is very easy to utilize Skrym if you are already using Ongoing as a WMS provider, due to our many different integrations with them.

Setting up Skrym with Ongoing

Regardless of your needs, all of our integrations with Ongoing are handled through their developer.ongoingwarehouse.com faviconwebhook support.

Integration between Ongoing WMS and Skrym
sequenceDiagram autonumber participant S as Skrym participant O as Ongoing WMS activate O Note over O: Credentials provided to Skrym deactivate O O->>S: Ongoing Webhook (Depends on integration) activate S Note over S: Webhook received S->>O: GetOrder API Call activate O O->>S: Order Data Response deactivate O Note over S: Skrym processes data and performs calculations S->>O: Populate additional data deactivate S
Order data flow and processing

There are, of course, slight differences between the integrations, and depending on whether you're using one or many of our tools, the setup might differ. To see the basics of how our integrations are set up, have a look below:

Optimization

There are two common ways to integrate our optimization with Ongoing. One is by setting up the OrderCreated webhook event. This causes the webhook to be triggered whenever the order is created in Ongoing (this is usually when an ERP system sends it to the warehouse).

  • Basic recommendation: Skrym populates the OrderClass field in Ongoing with the package recommendation (using the package alias).
  • Recommendation with dimensions: Skrym populates the Parcel field in Ongoing with a parcel ID and the dimensions from the recommended package.

Error Handling Configuration

Skrym provides configurable error handling for optimization failures. You can set up automatic status changes and comments in Ongoing when optimization encounters issues:

Failed Optimization Handling: When Skrym's optimization process fails due to technical issues, you can configure:

  • Order Status: Automatically update the order status in Ongoing (e.g., to "Error" status 150)
  • Order Comment: Add a descriptive comment explaining the failure

Missing Products Handling: When optimization fails because products are missing from Skrym's database or have invalid dimensions, you can configure:

  • Order Status: Automatically update the order status in Ongoing to indicate manual review is needed
  • Order Comment: Add a comment explaining that products need to be reviewed or added to the system

These settings are configured in your Ongoing integration settings within Skrym's dashboard. The system supports both predefined status codes (like the standard Ongoing status codes: 150-Error, 200-Open, 300-Released, etc.) and custom status codes specific to your workflow.

Note that the comments will also include Skrym metadata about the errors for easier debugging.

Shipping

Shipping is an area that covers many of our tools; in particular, it relates to both Booking and Tracking. The integration for both of these options is quite similar since they rely on the same webhook, namely:

  • OrderStatusChanged: This particular webhook allows you to specify when it should be triggered depending on the status change of the order. The usual way to set this up is to always go from picked to sent.

Skrym will then fetch the required data from both Ongoing and our own checkout (if the checkout tool is being used) to create and print the labels using www.printnode.com faviconPrintnode.

The tracking integration will instead simply read from the tracking reference and order number to start a tracked shipment in Skrym.

Need more customization?

If the suggested implementations are not suitable for your current setup, you can always reach us with requests or questions at: dev@skrym.se