fulfillmenttools
API documentationIncident ManagementFeedback
Developer Docs
Developer Docs
  • Developer docs
  • Getting Started
    • Quickstart
    • Integration tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
    • Free trial
  • Technical Basics
    • Access to fulfillmenttools
    • Feature status
    • Available regions
    • Backup policies
  • Connecting to fulfillmenttools
    • Client SDKs
    • commercetools connect
    • OpenID connect
      • Configure Microsoft Entra ID / Azure Active Directory
      • Configure Keycloak
  • API
    • Core concepts
      • Authentication & authorization
      • API Versioning & lifecycle
      • Assign user to jobs
      • Localization
      • Resource timestamps
      • Custom attributes
      • Article attributes
      • Recordable attributes
      • Data update guarantees
      • Rate limits & scaling
      • Retries
      • Performance on test vs. production systems
      • Load testing
    • API calls
      • Postman
      • cURL
      • GraphQL Explorer
    • GraphQL API
    • RESTful API
      • Pagination interface
      • RapiDoc
      • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an event
      • Available events
        • Event flows
      • Eventing example
      • Event export
  • Integration Guides
    • Address formats for specific carriers
    • Basics
      • Article categories
      • Audits
      • Custom services & bundled line items
      • Facilities
      • Facility groups
      • GDPR configuration
      • Listings
      • Orders
        • Order types
        • Order status
      • Remote configuration
      • Receipts
      • Search
      • Subscribe to events
      • Sticker
      • Stocks
      • Storage locations
      • Tags
      • Users
    • Channel inventory
    • Facility discounts
    • Inbound process
    • Outbound stocks
    • Purchase order
    • Receipt
    • Routing strategy
    • Show sticker to clients
    • Stow jobs
  • More Integration Guides
    • Carrier management
      • Introduction to carrier configuration
      • Required data when operating carriers
      • Adding & connecting carriers to facilities
      • Custom carrier
    • Configurations for order fulfillment
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing and document configuration
      • Packing container types
      • Parcel tag configuration
      • Headless order fulfillment
      • Short-pick reasons
      • External documents in order fulfillment
      • Service jobs
      • Load units
      • Running sequence
    • External actions
    • Notifications
    • Returns
Powered by GitBook
On this page
  • Sticker to order
  • Tag to order
Edit on GitHub
  1. Integration Guides

Show sticker to clients

Last updated 5 months ago

To display in the backoffice network order overview or other fulfillmentools clients two possible ways are available.

Both options can be used together.

Sticker to order

The first option is to attach a sticker to an order at creation. If this order reaches fulfillmenttools it will, for example, be displayed in the backoffice application, and an additional filter will allow you to filter orders based on those stickers.

Such an order could look like this:

POST https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/orders
{
  "tenantOrderId": "4711",
  ...
  "stickers": [
    {
      "key": "customercategory",
      "priority": 100,
      "nameLocalized": {
        "de_DE": "A-Kunde",
        "en_US": "A-Customer",
      },
      "color": "#19b6b5"
    }
  ],
  ...
}

Tag to order

The second option is to attach a tag to an order and configure the sticker configuration so that the sticker is added to the order automatically upon entering the system. Furthermore, configurations for other entities can add a sticker for other entities.

In this example, we consider all the used tags to be present in the system, such as:

GET https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/tags
{
    "id": "Channel",
    "allowedValues": [
        "B2B",
        "B2C"
    ],
    "created": "2023-04-03T09:28:59.336Z",
    "lastModified": "2023-04-03T09:28:59.336Z",
    "version": 1
}

Now we need to create a configuration that adds stickers based on tags for orders. Consider the following configuration:

PUT https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/configurations/tags/order
{
    "stickerConfiguration": {
      "offeredStickersByTag": [
        {
          "tagRef": "Channel",
          "matchingValues": [
            "B2B"
          ],
          "stickers": [
            {
              "key": "CustomerType",
              "priority": 100,
              "nameLocalized": {
                "de_DE": "Firmenkunde",
                "en_US": "Business Customer",
              },
              "name": "Firmenkunde",
              "color": "#9919b6"
            }
          ]
        },
        ...
      ]
    }
  ...
}

Now new orders can be tagged with Channel and automatically get the CustomerType sticker attached:

POST https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/orders
{
    "tenantOrderId": "4711",
     ...
     "tags": [
        {
            "id": "Channel",
            "value": "B2B"
        }
    ]
    ...
}
sticker