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

Remote Configuration

PreviousGDPRNextExpiry

Last updated 5 months ago

Was this helpful?

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

The remote configuration is used to store configurations affecting our clients such as the Backoffice and our applications. However, the fulfillmenttools backend is not using these remote configurations.

The remote configuration is a simple configuration key-value store. Based on a key, different values and value types can be saved. Furthermore, every entry can contain a specific scope, meaning that configurations can be made available only to certain user groups or clients.

Create / Update

Add Scope

Read All

Read Single

Delete Remote Config

Delete Scope

Example JSON

{
    "id": "REMOTE-CONFIG-ID-001",
    "key": "SHOW_RETURN_SECTION",
    "value": false,
    "valueType": "BOOLEAN",
    "groups": [
        "FULFILLMENT",
        "BACKOFFICE"
    ],
    "scopes": [
        {
            "id": "SCOPE-ID-0001",
            "facilityRefs": [
                "FACILITY-ID-001"
            ],
            "userRefs": [
                "USER-ID-001",
                "USER-ID-003"
            ]
        }
    ],
    "created": "2023-01-10T09:32:00.000+00:00",
    "lastModified": "2023-01-10T10:54:00.000+00:00",
    "version": 7
}

JSON Field Descriptions

key

The unique key that identifies the Remote Config entry, this can be freely chosen at entry creation.

value & valueType

The value of the key-value pair. With the valueType, the clients can identify the technical type of the value field for parsing.

groups

At creation every entry can (but it doesn't have to) have one or multiple groups. This are only simple strings that can defined free. If a client call later the API, this group-strings can be uses as filter. This way, every client gets only the configurations that are important to them.

scopes

Defines a specific scope where the configuration is available. It is possible to add different facilities and/or users. The facility and user declarations AND-linked.

Example:

"scopes": [{
    "id": "SCOPE-1234",
    "facilityRefs": [
        "FACILITY-4711",
        "FACILITY-4712"
    ],
    "userRefs": [
        "USER-40",
        "USER-43"
    ]
}]

In the example above the configuration will be only returned for user USER-40 or USER-43 that are working in facility FACILITY-4711 or FACILITY-4712. All other user and facility combinations will not get this Remote Configuration entry.

{
  "groups": [
    "BACKOFFICE"
  ],
  "key": "INBOUND_VIEW_ENABLED",
  "value": true,
  "valueType": "BOOLEAN"
}

Available Remote Configurations

Client

Value

Effect

Backoffice

  • groups: "BACKOFFICE"

  • key: "INBOUND_VIEW_ENABLED"

  • value: true

  • valueType: BOOLEAN

The inbound view is visible in the facility view.

Backoffice

  • groups: "BACKOFFICE"

  • key: "SENTRY_ENABLED"

  • value: true

  • valueType: BOOLEAN

If this config exists and is set to false we stop tracking errors on preand prdtenants.

By default we track all error and analytics data on all tenants.

Backoffice

  • groups: "BACKOFFICE"

  • key: "RETURN_VIEW_ENABLED"

  • value: true

  • valueType: BOOLEAN

The return view is visible in the network view.

Backoffice, Operations Web App

  • groups: "BACKOFFICE", "OPERATIONS_WEB_APP"

  • key: "RETURN_VIEW_ENABLED"

  • value: true

  • valueType: BOOLEAN

The service tab in the task overview is visible.

The feature custom-service must also be active in order to activate the service tab.

Backoffice

  • groups: "BACKOFFICE"

  • key: "CHANNEL_ALLOCATION_VIEW_ENABLED"

  • value: true

  • valueType: BOOLEAN

The channel inventory tab is visible in the stock overview.

Backoffice

  • groups: "BACKOFFICE"

  • key: "STORAGE_LOCATION_VIEW_ENABLED"

  • value: true

  • valueType: BOOLEAN

The storage location view is visible in the facility view.

Operations Webapp

  • groups: "BACKOFFICE"

  • key: "NEW_PRINTPREP_ENABLED"

  • value: true

  • valueType: BOOLEAN

The new print-preparation process to order labels is enabled. Including future customs.

Backoffice, Operations Web App

  • groups:"OPERATIONS_WEB_APP", "BACKOFFICE"

  • key: "SERVICE_JOBS_ENABLED"

  • value: true

  • valueType: BOOLEAN

The service tab is visible.

The feature custom-service must also be active in order to activate the service tab.

Operations Web App

  • groups:"OPERATIONS_WEB_APP"

  • key: "NEW_PRINT_OVERVIEW_ENABLED"

  • value: true

  • valueType: BOOLEAN

The new print overview is used.

Operations Web App

  • groups:"OPERATIONS_WEB_APP"

  • key: "NEW_PACKING_ENABLED"

  • value: true

  • valueType: BOOLEAN

The new packing process is used.

Operations Android App

  • groups:"OPERATIONS_ANDROID"

  • key: "android_native_printing_enabled"

  • value: true

  • valueType: BOOLEAN

Allows the user to select the native Android printing interface when printing documents.

Operations Android App

  • groups:"OPERATIONS_ANDROID

  • key: "android_zebra_printing_enabled"

  • value: true

  • valueType: BOOLEAN

Allows the user to directly select Zebra printers in the network when printing documents.

Operations Android App

  • groups:"OPERATIONS_ANDROID

  • key: "android_use_new_load_units"

  • value: true

  • valueType: BOOLEAN

Enables the new load units selection during the picking process.

Operations Android App

  • groups:"OPERATIONS_ANDROID

  • key: "android_calc_ean_check_digit"

  • value: true

  • valueType: BOOLEAN

Enables the app to automatically calculate the check digit for EAN-8 and EAN-13 barcodes, if the scanning device doesn’t send the whole code to the app. This happens for example on some Honeywell devices. For the camera scan or devices that already send the whole code, this setting has no effect.

Operations Android App

  • groups:"OPERATIONS_ANDROID

  • key: "android_use_picking_focus"

  • value: true

  • valueType: BOOLEAN

When this setting is active (true), the user is only able to scan the item that is currently in focus during the picking process. If disabled (false), the user is able to scan any item in the list during picking.

When no value exists, the default fallback value is true.

This setting only works if android_use_new_picking is enabled.

This setting has no effect for pick jobs that require a storage locations to be scanned, or pick jobs where barcode validation is disabled.

Operations KMP App

{ "groups": [ "OPERATIONS_KMP" ], "key": "return_trigger_review_enabled", "value": true, "valueType": "BOOLEAN" }

When this setting is active (true), the user is able to tick a checkbox for every Article in an ItemReturn to indicate that this item needs further review before finishing the ItemReturn.

If disabled (false), the checkbox will not be shown.

This setting is only supported with App version 1.3.0 or newer.

https://docs.fulfillmenttools.com/documentation

Get all remote configurations

get
Query parameters
startAfterIdstringOptional

all entities after given Id

sizeintegerOptional

number of entities to show

Default: 25
facilityIdstringOptional

facility to filter to

groupsstring[]Optional

groups to filter to

userIdstringOptional

userId to filter to

Responses
200
Central RemoteConfiguration
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 endpoint
application/json
404
Entity not found
application/json
get
GET /api/remoteconfigs HTTP/1.1
Host: 
Accept: */*
{
  "remoteConfigurations": [
    {
      "created": "2020-02-03T08:45:51.525Z",
      "lastModified": "2020-02-03T09:45:51.525Z",
      "version": 42
    }
  ],
  "total": 42
}
  • Create / Update
  • POSTCreate a new remote configuration
  • Add Scope
  • Read All
  • GETGet all remote configurations
  • Read Single
  • Delete Remote Config
  • Delete Scope
  • Example JSON
  • JSON Field Descriptions
  • Available Remote Configurations

Create a new remote configuration

post
Body
keystringRequired

unique business key of this entity

Example: PICKING_SHOW_NEW_SCAN_VIEW
valueTypestring · enumRequiredPossible values:
valueone ofRequired
stringOptional
or
integerOptional
or
numberOptional
or
booleanOptional
or
objectOptional
groupsstring[] · min: 1RequiredExample: INVENTORY
Responses
200
Created entity in the body.
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 endpoint
application/json
post
POST /api/remoteconfigs HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 217

{
  "key": "PICKING_SHOW_NEW_SCAN_VIEW",
  "scopes": [
    {
      "facilityRefs": [
        "928f3730-bc48-4d85-b83f-3fd86b776178"
      ],
      "userRefs": [
        "928f3730-bc48-4d85-b83f-3fd86b776178"
      ]
    }
  ],
  "valueType": "BOOLEAN",
  "value": "text",
  "groups": [
    "INVENTORY"
  ]
}
{
  "id": "LGMl2DuvPnfPoSHhYFOm",
  "key": "PICKING_SHOW_NEW_SCAN_VIEW",
  "scopes": [
    {
      "facilityRefs": [
        "928f3730-bc48-4d85-b83f-3fd86b776178"
      ],
      "userRefs": [
        "928f3730-bc48-4d85-b83f-3fd86b776178"
      ]
    }
  ],
  "valueType": "BOOLEAN",
  "value": "text",
  "groups": [
    "INVENTORY"
  ],
  "flattenScopeIds": [
    [
      "INVENTORY",
      "67151fc3-3ce1-400e-8b23-23c29e0cde90"
    ]
  ],
  "created": "2020-02-03T08:45:51.525Z",
  "lastModified": "2020-02-03T09:45:51.525Z",
  "version": 42
}