How Kroconnect works

Last modified:

Kroconnect is an integration platform that connects your WooCommerce store with the other systems you run your business in — ERP and accounting systems (such as Specter, Visma/Spiris and Fortnox), order and invoicing tools (such as Contrl), and shipping solutions (such as Fraktjakt and nShift).

Instead of each system talking directly to every other system, they all connect through Kroconnect. Kroconnect moves the right data between them — orders, products, stock levels, order statuses — in the direction and at the moment you need it.

This page explains the core concepts that the rest of the documentation builds on.

Connections

A Connection is a configured link to one specific system or account — for example your WooCommerce store, your Specter account, or your Fraktjakt account.

A Connection holds the credentials and the system-specific settings for that system. For example:

  • On your WooCommerce Connection: the Create missing products setting (whether products that don’t yet exist should be created).
  • On your Specter Connection: which warehouse to use for stock level sync.

You typically have one Connection per system you integrate with.

Workflows

A Workflow defines a single flow of data between two connected systems, in one direction and for one purpose. Examples:

  • WooCommerce → Specter (order) — send new orders to Specter.
  • Specter → WooCommerce (stock level) — send stock changes back to WooCommerce.
  • WooCommerce → Fortnox (order) — create orders and invoices in Fortnox.

Each Workflow has a unique workflow ID. When a workflow runs, it is called at:

https://api.kroconnect.com/kroconnect/{your-workflow-id}

When triggered, a workflow reads data from the source system, applies its mapping, and writes the result to the target system. Because each workflow is one-directional and purpose-specific, a typical setup has several workflows working together — for example one to create an order and another to create the matching invoice.

Mapping (config)

Within a workflow, the mapping (or config) controls how fields from the source system are matched to fields in the target system.

Every workflow comes with a standard mapping. For example, the standard product mapping sends Title (Benämning in Specter), Weight, Price and Sale price. The mapping can be customized — you can map additional WooCommerce fields to fields in the target system, or modify or remove parts of the standard mapping. Contact us if you need a customized mapping.

Triggers

A trigger is what makes a workflow run. The most common triggers are:

  • Plugin setting — the Kroconnect WooCommerce Connector plugin can run a workflow automatically on certain events, such as Order sync action (e.g. on payment complete) or Product sync action (on create/update).
  • WooCommerce webhook — a WooCommerce webhook (for example the Order paid event) calls the workflow URL.
  • Manual action — buttons in the WooCommerce admin, such as Send order to Kroconnect or Sync product.
  • Custom code — for specific scenarios or events.

Some syncs are triggered from the other system instead. For example, when a stock level changes in Specter, Specter sends a signal to Kroconnect, which then updates WooCommerce.

Who sets this up

Kroconnect is moving towards being a fully self-serve app. Today the setup is a mix:

  • Fraktjakt and Specter have self-serve onboarding steps you can follow yourself.
  • Other Connections and Workflows are currently set up and activated together with Kroconnect staff.

If you want to add a new integration or workflow, contact us and we’ll help you get started.

Glossary

TermMeaning
ConnectionA configured link to one system or account (e.g. your WooCommerce store or Specter account), holding its credentials and settings.
WorkflowA one-directional flow of data between two connected systems for a specific purpose, identified by a unique workflow ID.
Workflow IDThe unique identifier of a workflow, used in the workflow URL and in the plugin’s sync settings.
Mapping/ConfigThe rules that determine how fields are matched between the source and target systems in a workflow.
TriggerThe event that causes a workflow to run (plugin setting, webhook, manual action, custom code, or a signal from the other system).
ERP order numberThe order number returned by the ERP (e.g. Specter or Fortnox) and saved on the WooCommerce order.
The Kroconnect appapp.kroconnect.com — where Connections and Workflows are managed and where workflow IDs are found.
Kroconnect WooCommerce ConnectorThe WordPress/WooCommerce plugin that connects your store to Kroconnect.