Tags

Introduction

In fulfillmenttools there is the possibility to map individual processes and to customize entities according to special needs. One way to impose a certain customization on your processes is through tags.

Before using a tag, it must be created via API: Tag REST API documentation. If the tag does not exist, the request to use it will be rejected.

Tags can be attached to several entities at fulfillmenttools, such as orders, order lines, pick jobs, pack jobs, or handover jobs. The usage of tags is indicated by the field tags. Usually, tags are added to entities by services that supply data to the platform (external services, middleware, or connectors).

Tag inheritance

Tags are inherited from one entity to another. Multiple tags with the same ID are merged into one tag. This applies to tags on the root level of the entity and the tags on the line item itself. This covers:

• Order inherits tags to pick jobs, pack job, and handover job.

• Listings inherit tags to pick job line items, pack job line items and handover job line items.

Use cases for tags

• Create routing rules with the DOMS Toolkit

• Define a picking method

• Define which external documents are offered for printing during picking and packing

• Configure the scanner behavior during Picking

• Add sticker to entities