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
  • Description
  • Order status
  • Picking Status
  • Packing Status
  • Label Status
  • Handover Status
  • Filters
  • Perform operational actions
  • Fallback mechanism for setups without orders
  • Customer information in the order
  • FAQs

Was this helpful?

  1. Clients
  2. Backoffice
  3. Network view

Orders

PreviousHomeNextUnroutable orders

Last updated 5 months ago

Was this helpful?

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

Introduction

In the Network Overview users get an overview over all orders. Users with the role ADMIN are able to search for and to manipulate orders here.

The orders are sorted by the order date in a descending way.

The following actions are possible:

  1. Check the orders status

  2. Use filters

  3. Perform operational actions

Description

Order status

General

Depending on the processing state of an order there are different status. The status depends on how the order process is designed. The complete process includes a picking, packing, label creation and handover step. In the following, these steps are referred to as "operational process". The order's process status merges those different status (see below) and informs the user about the progress.

Order "locked"

An order can be created in the status locked (see ). This means the order is held back and operational processes are not started. Orders in locked status are marked with a yellow border and the -symbol.

Please note: The consolidated status on the top level is "open" since no operational processes have started yet.

Order "open"

An order is in status "open" if no operational processes have been startet yet. The icon is grey.

Order "in progress"

An order is in status "in progress" if at least one operational process has been started. The icon is yellow.

Order "finished"

An order is in status "finished" if all operational processes have been finished. Items were handed over to the consumer or to a shipping provider. The icon is green.

Order "cancelled"

Error-handling

An order gets an exclamation mark in its status and a red border if there occurred an error (operational or technical) along the way.

Picking Status

Picking has not started yet if all status icons are grey.

Picking is commenced if the picking status icon is orange.

Picking is finished if the picking status icon is green.

Picking is partially finished if the picking status icon shows a half filled green button.

If no items could be picked (zero pick), a red circled button with a check sign is shown.

Packing Status

Packing started if the packing status icon is orange.

Packing is finished if the the packing status icon is green.

Label Status

The label has been created successfully if the label button is green.

When there has been an issue with the label, a warning sign appears.

Handover Status

When the order has been picked up by a shipping provider or a customer, the handover status turns green.

Filters

The order overview must handle a high amount of entries. Therefore, a variety of filters is offered such as:

  • Timespan: filters by order date

  • Facilities: filters by facility in which fulfillment takes place

  • Facility Countries: filters by country in which fulfillment takes place

  • Delivery Countries: filters by country of the delivery address

  • Process Status: filters by the aggregated status of the process

  • Completion by: filters by time at which the pick job should be completed

  • Brands: filters by orders containing an item from a specific brand

Additionally, it is possible to directly search for an Order ID.

Perform operational actions

The following changes can be made to an order via the three-dot menu on the order overview:

  • Order history: The order history for individual orders can be called up from here. This overview contains detailed information about the course of the fulfillment process:

    -> Routing: When was what routed or even rerouted where and why?

    -> Picking/packing/shipping: When were which steps performed?

  • Change delivery address: Enables the user to handle situations where the shipment could not be delivered and a second attempt (with another address) should be performed.

  • Trigger a new DOMS decision: Checks for a routed order whether the current decision is still the best. If it is not, a new routing is performed – already created pick jobs are deleted. To perform this action the following conditions must apply: All pick jobs are open, no items were picked, and no labels were requested.

  • Cancel order: Cancels all corresponding entities of an order. To perform this action the following conditions must apply: All pick jobs are open, no items have been picked, and no labels were requested.

  • Reset task status: It is possible to reset the status of each step of each single task. This is helpful if a mistake has been made during the picking process in the store.

  • Unlock order: If the order is marked as locked, it is possible to unlock the order manually.

Fallback mechanism for setups without orders

Fulfillmenttools is a modular platform. Among others, this means that our platform can be used without order (entities). As we cannot assume that there is always an order entity, we implemented a fallback structure to make sure that the order overview always shows relevant information.

Explanation of default fallbacks for different information:

  • Order type - Fallback for the #1. Pickjob, #2: Shipments

  • Consumer name - Fallback #1 Pickjob, #2: Shipments

  • Consumer address: Fallback #1 Shipment, #2: Pickjob

  • Ordered Items - Fallback 1# Pickjob(s), 2#: Shipments - not yet available

  • Order timestamp - Fallback #1: Pickjob, 2#: Shipments - not yet available)

  • Order ID - Fallback #1: Shipments (here it is mandatory), #2: Pickjob (not mandatory)

  • If no information is present (no fallback available etc.) the column is empty

Customer information in the order

The consumer ID and the company name are displayed in the network order overview next to the consumer name.

The company name is an additional information where to ship the item in case the first and last name of the customer is not displayed on the bell plate.

The consumer ID enables the association of multiple orders from the same customer. For instance, a CRM system might assign a unique ID to a consumer within our order entity. This ID can be utilized in our network order overview to search for and identify the most recent orders placed by that consumer.

FAQs

Special case "consumer address"

We allow the situation where a click-and-collect order generates a ship-from-store pick job which will be shipped to the click-and-collect facility that the consumer selected. In order to show the correct address here (and not the facility address) we do not use a fallback and just look at the order information.

How to check the order history?
  1. Select “Network View”

  2. Click on “Orders” and you will arrive in the order overview

  3. Click on the three dot menu at the order you would like to check and click on "Order History"

  1. Now you can check the order movements

How to trigger a new DOMS decision?
  1. Select Network view

  2. Click on “Orders” and you will arrive in the order overview

  3. Expand the order you would would like to trigger a new routing decision for

  4. Click on the three dots and click on "Reroute task" (only possible if picking has not started)

  5. A new routing will be triggered for the selected pick job to find the ideal location of fulfillment

How to assign order to another facility?
  1. Select "Network View"

  2. Click on “Orders” and you will arrive in the order overview

  3. Click on the order that you would like to assign to a different facility (only possible if picking has not started)

  4. Select the facility

  5. The order will arrive as a new task in the selected facility

How to unlock an order which is marked as locked?
  1. Select "Network View"

  2. Click on “Orders” and you will arrive in the order overview

  3. Click on the locked order that you would like to unlock, and click on "Unlock"

How to cancel an order?
  1. Select “Network View”

  2. Click on “Orders” and you will arrive in the order overview

  3. Select the order you would like to cancel

  4. Click on the button “Cancel order”

  5. You will be asked if you really want to cancel the order. If yes, click on “Cancel order”. The order will be marked as canceled and will disappear in the picking app

How to change the delivery address?
  1. Select “Network View”

  2. Click on “Orders” and you will arrive in the order overview

  3. Select the order and select “Change delivery address”

How to check the order status?
  1. Select “Network View”

  2. Select “Network View”

  3. Click on “Orders” and you will arrive in the order overview

  4. Open up the order task and check status (orange= in prgress grey = not started, green = done)

How to reset the order status?
  1. Select “Network View”

  1. Click on “Orders” and you will arrive in the order overview

  1. Open the order and click on the lower three dot menu and click on reset status

How to add an order with an item from a specific brand?

The filter for brands appears if there is an order with an item whose description contains a brand.

A brand can be added to an orderline by adding an attribute with category "miscellaneous", key "BRAND" and with a value reflecting the brand (like in the following example):

// Some code```postman_json
 "orderLineItems": [
        {
            "article": {
                "tenantArticleId": "item4711",
                "title": "Name of the item",
                "imageUrl": "https://example.com/abcd.jpg?tx=w_600,h_600",
                "attributes": [
                    {
                        "category": "miscellaneous",
                        "key": "BRAND",
                        "value": "Adidas"
                    }
                ]
            },
            "quantity": 2,
            "scannableCodes": [
                "2020249"
            ]
        }
]

In some cases, it might not be possible to pick all ordered items. This is referred to as "" in our platform. If the short pick did not trigger a follow up action such as a re-route, the order can still go into the "finished" status.

An order is in status "cancelled" if it was cancelled manually or due to some configuration. The icon is a red . See how to cancel an order.

Type: filters by order type ( or )

Assign order: Assigns the order to a new facility and creates a new pick job in the selected facility. Already created pick jobs are deleted. The following conditions must apply to perform this action: All pick jobs are open, no items have been picked, and no labels were requested yet. The feature only works for . A cannot be assigned to another facility.

Force canceling an order: Cancels all corresponding entities of an order. This function differs from the previous one. Force cancelation is possible at any time and no operational status are checked. This means that processes might be revised operationally without system support. An example might be that picked items must be stowed back and the inventory must be adjusted manually. If items were not picked but reserved, the system releases the reservations. This feature must be for your tenant.

Reroute manually: It is possible to reroute tasks manually. This feature can be enabled in the settings. The difference between the the "Reroute order" and "Reroute task" functionality is that the reroute task action in which the order has already been. Furthermore this option will be also shown in the facility view, which means supervisors can reroute tasks as well.

It is possible to add further information to the customer of an order (see ).

Go for more information.

You have the possibility to set cancellation reasons. If you have set cancellation reasons via our API (see ) the user, after selecting "Cancel order", the user is asked to give a reason why the cancellation must be done. This reason is stored in our BigQuery and can be used for analytics purposes.

Change customer address and save

🔓
https://docs.fulfillmenttools.com/documentation
here
short pick
collect
shipment
ship-from-store orders
click & collect order
activated via API
blacklists the facility
here
here
ℹ️
here
❌
here