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
    • DOMS - distributed order management system (routing)
    • External actions
    • Interfacility transfer
    • Notifications
    • Availability & promising
    • Returns
Powered by GitBook
On this page
  • Creating a Load Unit Type
  • Adding an Icon to a Load Unit Type
Edit on GitHub
  1. More Integration Guides
  2. Configurations for order fulfillment

Load units

Last updated 5 months ago

It is possible to use load units within the picking process. Load units can be any kind of custom items which complement the picked task, such as bags, boxes, vouchers, or any kind of goodies / information that the picker should get once the picking process is finished.

Creating a Load Unit Type

While the load unit entity captures the information for a particular pick job, the entity is the configuration object. So the typical task is to create the load unit types that you want to use in your picking process - here's an example:

curl -sSL -X POST 'https://your.api.fulfillmenttools.com/api/loadunittypes' \
  --header 'Authorization: Bearer <TOKEN>' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "nameLocalized": {
                "de_DE": "Papiertasche",
                "en_US": "Paperbag",
                "pl_PL": "Torba papierowa"
    },
    "priority": 1
  }'

To update/modify an existing load unit type, use the corresponding PATCH call:

curl -sSL -X PATCH 'https://your.api.fulfillmenttools.com/api/loadunittypes/:loadUnitTypeId' \
  --header 'Authorization: Bearer <TOKEN>' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "version": 3,
    "actions": [
        {
            "action": "ModifyLoadUnitType",
            "priority": 2
        }
    ]
  }'

All defined load unit types will be immediately be displayed for selection in the picking process. If there are no load unit types defined, this step is skipped in the app.

Once a load unit type has been defined, it cannot be deleted via the API (yet). Please contact us if you require assistance in this scenario.

Adding an Icon to a Load Unit Type

You can (and should) add an icon to the load unit type definition so that is displayed nicely in the Android app and the picker knows which bag, box, etc. to choose.

The image file needs to be base64 encoded in the HTTP request:

curl -sSL -X PUT 'https://your.api.fulfillmenttools.com/api/loadunittypes/:loadUnitTypeId/icon' \
  --header 'Authorization: Bearer ' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "name": "paperbag.png",
    "content": "==base64-encoded content=="
}'

See our for details.

See our for details.

load unit type
API specification
API specification