---
title: Connecting Your Store With Shopware Nexus | Shopware Community Hub
description: >-
  Learn what Shopware Nexus is, how it differs from Flow Builder, and when a
  visual low stock alert helps your warehouse team react faster.
canonical_url: >-
  https://hub.shopware.comhttps://hub.shopware.com/learn/unit/user-shopware-nexus
---

# Connecting Your Store With Shopware Nexus

<LearningObjectives>

- Explain **what Shopware Nexus is** in everyday store terms.
- Decide **when to use Nexus** and when **Flow Builder** is enough.
- Name the **building blocks** of a Nexus workflow: trigger, action, and condition.
- Recognize a **low stock alert** as a typical first Nexus use case.

</LearningObjectives>

# Automate Store Reactions With Shopware Nexus

At **Strum & Co.**, popular guitars sell out faster than the warehouse team notices. After busy days, someone still checks stock by hand — and restocking starts too late.

**Shopware Nexus** helps you automate that kind of follow-up. You build a visual workflow: when something happens in your shop (or at a set time), Nexus runs the next steps for you. You do not need to write code. Nexus can also connect Shopware to other tools later (for example Slack or an ERP). In this learning path, your first example stays inside Shopware: a **low stock alert** by email.

<Callout title="Not available in the learning environments" type="warning">

Unlike the other features in this course, **Nexus is not available in the interactive learning environments** and cannot be tried there. To practice the example, you need **your own Shopware shop** (6.7.1.0 or newer) and a **Shopware account** where that shop is registered.

</Callout>

<Callout title="Early Access" type="warning">

Nexus is in **Early Access**. Features may still change. Where possible, try things first in a test or staging shop.

</Callout>

<Callout title="What Nexus is and is not" type="info">

- **It is** a visual tool to react to shop events or schedules, and optionally to connect Shopware with other systems.
- **It is not** a replacement for the Shopware Administration or a tool for designing your storefront.

</Callout>

## Nexus vs Flow Builder

You already know **Flow Builder** from earlier in this path. It is the right place for many everyday automations *inside* Shopware — welcome emails, status updates, and similar tasks.

| You want to… | Prefer |
| --- | --- |
| Send emails or change order status with the usual Flow Builder options | **Flow Builder** |
| Build a visual multi-step flow (check stock, then decide, then notify) or connect another system | **Nexus** |
| Fix something once by hand | Do it manually |

Nexus is a **Shopware Service**. You create workflows in the Nexus Builder and link your shop in the Administration so Nexus can react to what happens in the store.

## The Building Blocks of a Workflow

Every Nexus workflow follows a simple idea: *when this happens, do that*.

- **Trigger** — the start. Example: a new order is placed, or a daily schedule runs.
- **Action** — the work. Example: look up stock in Shopware, send a Shopware email, or (later) send a Slack message.
- **Condition** — a yes/no check. Example: only continue if stock is below five units.

You arrange these steps as boxes (**nodes**) on a visual board (**canvas**) and connect them with arrows. In message fields you can type **@** to insert details from the order, such as the order number.

<Scenario title="Low stock alert for Strum & Co.">

A customer buys a guitar. Stock drops below the level your warehouse team needs for restocking. Today, they often notice too late.

With Nexus you set up: **when an order is placed → check stock → if it is low → email the warehouse team**.

That is enough for your first workflow. The product documentation also shows a version that uses Business Central and Slack; you can add those connections later when you need them.

</Scenario>

You can also check stock **once a day on a schedule** instead of right after each order — useful for a morning overview.

Before a workflow really runs, it goes through clear statuses:

1. **Draft** — you are still editing.
2. **Published** — the workflow is ready.
3. **Active** — it is turned on and processing events.

Important: **Publish** prepares the workflow; **Start** turns it on. Both steps are needed.

## When to Use Nexus

Use Nexus when the job **repeats**, starts from a **shop event or schedule**, and needs **several steps** (check → decide → notify) — or when you want to involve another system. A low stock alert is a good first example.

Stay with Flow Builder when it already offers the trigger and action you need. For deep custom shop behavior, involve your agency or a developer.

## Final Thoughts

Shopware Nexus gives Strum & Co. a visual way to react to store events — starting with a low stock email to the warehouse. Use Flow Builder for classic in-shop flows; use Nexus when you need a multi-step canvas or a connection to another system. Next, you link your shop and build that alert step by step.

Further reading: [Shopware Nexus documentation](https://docs.shopware.com/en/shopware-6-en/shopware-services/shopware-nexus)