fulfillmenttools
  • Welcome to the fulfillmenttools Platform Documentation
  • Getting Started
    • Setup your access to fulfillmenttools
    • Make your first API Calls
      • Add your first facility
      • Add your first listing
      • Place your first order
    • Core concepts & terminology
      • Order Flow
    • Postman Collection
    • Client SDKs
    • FAQ
  • Clients
    • Backoffice
      • First steps - Registration
      • Network view
        • Home
        • Orders
          • Unroutable orders
          • Pre-orders & Backorders
          • Order History
        • Inventory Management
          • Stock Overview
          • Channel Inventory
        • Facilities
        • Users
        • Returns
        • DOMS configuration
        • Settings
        • Analytics
          • DOMS Pages
          • Fulfillment Operations Pages
          • Inventory Pages
          • Downloads Page
      • Facility view
        • Home
        • Inbound
        • Tasks
        • Listings
        • Storage Locations
        • Facility
        • Users
    • Inventory app
      • Registration Inventory App
      • App sections
        • Inbound
        • Storage and relocation
    • Operations app
      • Android
        • Manual Registration
        • Android Enterprise Registration
        • Sections
          • Picking
            • Load Units (legacy)
            • Substitute items
            • Weighed or measured products
            • Scanning configuration
            • Picking Methods
              • Batch Picking
              • Multi Order Picking
          • Packing
          • Handover
          • Returns (legacy)
        • Printing
        • Notifications
      • Webapp
        • Packing
      • Overview features Android & Webapp
    • Technical requirements
      • Zebra Hardware Scanner Configuration
      • Honeywell Hardware Scanner Configuration
      • Supported barcodes for camera scanning
      • Requirements for fft applications
      • Zebra printer
    • Returns app
      • Handle unannounced returns
      • Handle announced returns
  • Products
    • Core Functionality
      • Process
        • External actions
      • Add and manage facilities
      • Notification Center
      • Checking on features
      • Tags and Stickers Concept
      • GDPR
      • Remote Configuration
      • Expiry
      • Target time
      • Time calculation for queries of future availabilities (LPS-calculation)
      • Interfacility Transfer
    • Carrier Management
      • Overview
        • Available Carriers
      • Concepts
        • Carrier Country Service Mapping (CCSM)
        • Non-delivery-days
        • Custom Carrier & Headless operation of Carriers
      • Providing needed data
    • Fulfillment Options
      • Fulfillability Check
      • Checkout Options
        • Available fulfillment options based on basket
        • Earliest possible delivery date
        • Available delivery dates within time-period
        • Availability for delivery date
      • Delivery Promise
    • Inventory Management
      • Configurations
      • Entities
        • Listing
        • Stock
          • Stock Properties
        • Storage Location
        • Zone
      • Global Inventory
        • Stock availability
        • Channel Inventory
        • Expected stock
        • Inbound Process
        • Reservations
        • Safety Stock
      • Inventory Control
        • Inventory Traits
        • Measurement Units
        • Outbound Inventory Tracking
        • Storage Location Recommendations
    • Order Fulfillment
      • Headless Order Fulfillment
      • Pick Jobs
      • Zone picking
      • Load Units
      • Custom Service
      • Handover Jobs
      • Add External Documents
      • Configurations
        • Picking Configuration
          • Picking methods
          • Short Pick Reasons
        • Packing Configuration
          • Packing Container Types
        • Print / Document Configuration
        • Tag Configurations
          • Parcel Tag Configuration
        • Handover Configuration
        • Operative Container Types
    • Order Routing
      • Entities
        • Ship-from-Store Orders
        • Click-and-Collect Orders
        • Locked Orders
        • Custom Services Orders
          • Simple Custom Service Order
          • Complex Custom Service Order
      • Fences
      • Ratings
      • Order Split
        • Order split - initial routing
        • Order split after shortpick
        • Item bundles
      • Reroute
      • Shape the routing with the DOMS Toolkit
      • Decision logs
    • Returns Management
      • Returns legacy
        • Available status
      • Returns 2.0
        • Return Reasons
        • Item Conditions
        • Integrating Returns with Events
    • Use Cases
      • Demand-Driven Replenishment
      • Expected stock in availability
      • Multi Order Picking
      • Interfacility transfer
      • Assigned Users
  • Connecting to fulfillmenttools
    • General Topics
      • Use external identity providers to authenticate to fulfillmenttools
        • Microsoft Entra ID / Azure Active Directory (AD)
      • Public Event Export
      • Available Regions
      • Backup Policies
    • GraphQL API
    • RESTful API
      • General Topics
        • API Release Life Cycle
        • Versioning
        • Authorization
        • Customization via Attributes
        • Update Guarantees
        • Rate Limits
        • Resource Timestamps
        • Pagination Interface
        • Localization
        • Custom Attributes
      • OpenAPI Specification
        • Swagger UI
        • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an Event
      • Available Events
      • Tutorial
    • commercetools Connect
    • Integration Tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout Options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
  • Incident Reporting
    • How to report incidents in fulfillmenttools
    • How to define incident priorities
  • Release Notes
    • Release Summary – May 2024
    • Release Summary – June 2024
    • Release Summary – July 2024
    • Release Summary – August 2024
    • Release Summary – September 2024
    • Release Summary – October 2024
Powered by GitBook
On this page

Was this helpful?

  1. Products
  2. Core Functionality

Notification Center

PreviousAdd and manage facilitiesNextChecking on features

Last updated 5 months ago

Was this helpful?

This page is outdated. Please go to our new documentation under .

Introduction

Our Notification Center keeps you informed about relevant events within our platform. The feature allows you to configure email notifications for specific events generated by our software:

  • Incoming orders: Get emails for incoming orders. Choose the facility you are interested in or receive emails for all incoming orders.

  • Unroutable orders: Get notified if an order could not be assigned to a facility.

Quotas may be imposed on this in the future

fulfillmenttools reserves the right to impose a quota per customer to this feature in the future.

Configuration

To set up notifications, you need to put a corresponding configuration in place. The notification configuration has the following attributes:

  • channels: A channel defines the source and the target of notifications. We recommend to define different channels for different receiver groups and/or facilities. See below for a detailed description.

  • enabled: Defines the state of the channel. Set to true if notifications should be sent and to false if notifications should be paused.

A channel is a JSON Object which contains the following attributes:

  • type: The type of the notification you will receive. Currently, only EMAIL is supported.

  • events: The events upon which the notification is triggered. Currently we support:

    • PICK_JOB_CREATED: An order was assigned to a facility and is ready to be picked.

    • ROUTING_PLAN_NOT_ROUTABLE: An order could not be assigned to a facility and is in "unroutable" state.

    • ROUTING_PLAN_WAITING: A routing plan is waiting

  • receiver: Who will receive the notification. This is an array of objects. The attributes of the objects change based on the TYPE:

    • Type EMAIL:

      • email: The email address of the recipient

      • language: The language of the email. Currently, this is either de_DE or en_US. It is possible to define a different language for each receiver email address.

You can define, whether you want to receive notifications on network level or only for specific facilities.

Configuration on network level

Create a new configuration

Create a configuration on network level if you want to receive notifications globally, i.e. for all events no matter which facility they apply to. To create a new configuration on network level, use the below endpoint to create one or several channel(s). If you want to send the same events to the same user group, it is sufficient to create one channel. Please speficy type, event(s), and receiver(s) as specified above and set enabled to true.

Add a new channel or update an existing channel

Get configuration information

Delete a channel

Configurations on facility level

Create a new configuration

Create a configuration on facility level if you want to receive notifications only for specific facilities, e.g., only for orders that are routed to a specific facility. To create a new configuration on facility level, use the below endpoint to create one or several channel(s). If you want to send the same events to the same user group in the same facility, it is sufficient to create one channel. Please speficy facilityRef, type, event(s), and receiver(s) as specified above and set enabled to true.

Add a new channel or update an existing channel

Get configuration information

Delete a channel

https://docs.fulfillmenttools.com/documentation

Returns the notification center configuration.

get

Responses
200
The notification center configuration was successfully returned.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
404
The requested entity was not found
application/json
get
GET /api/configurations/notifications HTTP/1.1
Host: 
Accept: */*
{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "id": "text",
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "created": "2025-05-12T08:59:55.102Z",
  "lastModified": "2025-05-12T08:59:55.102Z",
  "version": 1
}

Executes an action to manipulate the notification center configuration.

post

Body
one ofOptional
or
Responses
200
Notification center configuration action was successfully executed.
application/json
400
Invalid input. See response for details.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
409
A version conflict occurred.
application/json
post
POST /api/configurations/notifications/actions HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 164

{
  "channel": {
    "enabled": true,
    "events": [
      "PICK_JOB_CREATED"
    ],
    "receiver": [
      {
        "email": "name@gmail.com",
        "language": "de_DE"
      }
    ],
    "type": "text"
  },
  "name": "ADD_CHANNEL",
  "version": 1
}
{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "id": "text",
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "created": "2025-05-12T08:59:55.102Z",
  "lastModified": "2025-05-12T08:59:55.102Z",
  "version": 1
}

Creates or updates an existing notification center facility configuration.

put

Path parameters
facilityRefstringRequired
Body
one ofOptional
or
all ofOptional
Responses
200
Notification center facility configuration was successfully updated.
application/json
201
Notification center facility configuration was successfully created.
application/json
400
Invalid input. See response for details.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
404
The requested entity was not found
application/json
409
A version conflict occurred.
application/json
put
PUT /api/facilities/{facilityRef}/configurations/notifications HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 146

{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "version": 1
}
{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "id": "text",
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "created": "2025-05-12T08:59:55.102Z",
  "lastModified": "2025-05-12T08:59:55.102Z",
  "version": 1
}

Executes an action to manipulate the notification center facility configuration.

post

Path parameters
facilityRefstringRequired
Body
one ofOptional
or
Responses
200
Notification center facility configuration action was successfully executed.
application/json
400
Invalid input. See response for details.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
404
The requested entity was not found
application/json
409
A version conflict occurred.
application/json
post
POST /api/facilities/{facilityRef}/configurations/notifications/actions HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 164

{
  "channel": {
    "enabled": true,
    "events": [
      "PICK_JOB_CREATED"
    ],
    "receiver": [
      {
        "email": "name@gmail.com",
        "language": "de_DE"
      }
    ],
    "type": "text"
  },
  "name": "ADD_CHANNEL",
  "version": 1
}
{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "id": "text",
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "created": "2025-05-12T08:59:55.102Z",
  "lastModified": "2025-05-12T08:59:55.102Z",
  "version": 1
}

Deletes a notification center config channel.

delete

Path parameters
channelIdstringRequired
Query parameters
versionnumberRequired
Responses
200
Notification center config channel was successfully deleted.
400
Invalid input. See response for details.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
404
The requested entity was not found
application/json
409
A version conflict occurred.
application/json
delete
DELETE /api/configurations/notifications/channels/{channelId}?version=1 HTTP/1.1
Host: 
Accept: */*

No content

Returns the notification center facility configuration.

get

Path parameters
facilityRefstringRequired
Responses
200
The notification center facility configuration was successfully returned.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
404
The requested entity was not found
application/json
get
GET /api/facilities/{facilityRef}/configurations/notifications HTTP/1.1
Host: 
Accept: */*
{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "id": "text",
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "created": "2025-05-12T08:59:55.102Z",
  "lastModified": "2025-05-12T08:59:55.102Z",
  "version": 1
}

Deletes a notification center facility config channel.

delete

Path parameters
facilityRefstringRequired
channelIdstringRequired
Query parameters
versionnumberRequired
Responses
200
Notification center facility config channel was successfully deleted.
400
Invalid input. See response for details.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
404
The requested entity was not found
application/json
409
A version conflict occurred.
application/json
delete
DELETE /api/facilities/{facilityRef}/configurations/notifications/channels/{channelId}?version=1 HTTP/1.1
Host: 
Accept: */*

No content

  • Introduction
  • Configuration
  • Configuration on network level
  • PUTCreates or updates an existing notification center configuration.
  • POSTExecutes an action to manipulate the notification center configuration.
  • GETReturns the notification center configuration.
  • DELETEDeletes a notification center config channel.
  • Configurations on facility level
  • PUTCreates or updates an existing notification center facility configuration.
  • POSTExecutes an action to manipulate the notification center facility configuration.
  • GETReturns the notification center facility configuration.
  • DELETEDeletes a notification center facility config channel.

Creates or updates an existing notification center configuration.

put

Body
one ofOptional
or
all ofOptional
Responses
200
Notification center configuration was successfully updated.
application/json
201
Notification center configuration was successfully created.
application/json
400
Invalid input. See response for details.
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this
application/json
409
A version conflict occurred.
application/json
put
PUT /api/configurations/notifications HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 146

{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "version": 1
}
{
  "channels": [
    {
      "enabled": true,
      "events": [
        "PICK_JOB_CREATED"
      ],
      "id": "text",
      "receiver": [
        {
          "email": "name@gmail.com",
          "language": "de_DE"
        }
      ],
      "type": "text"
    }
  ],
  "created": "2025-05-12T08:59:55.102Z",
  "lastModified": "2025-05-12T08:59:55.102Z",
  "version": 1
}