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
  • Introduction
  • Description
  • Inbound process overview
  • Inbound process status
  • Accepting goods with the inventory app
  • FAQs

Was this helpful?

  1. Clients
  2. Inventory app
  3. App sections

Inbound

PreviousApp sectionsNextStorage and relocation

Last updated 5 months ago

Was this helpful?

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

Introduction

The inbound section in our inventory app supports users in handling the receipt of goods. Items can be accepted, a brief quality inspection can be performed, and the items can be stowed on an inbound location. An admin view of all closed and pending inbound processes can be found in the Backoffice in the .

Description

Inbound process overview

Upon opening the inbound section, the user gets an overview of all expected deliveries based on information within purchase orders. In the app, only processes that are not closed or cancelled are displayed. For each entry in the overview, the supplier name is displayed in the headline while the subline shows the value configured in the field "tenantInboundProcessId". Users can search for specific processes by purchase order ID or supplier name. In addition, entries can be filtered by status and date.

Inbound process status

There are 3 functional status that cannot occur simultaneously:

  • Open: Delivery has not arrived or receipt of goods has not been completed yet.

  • Closed: Completeness of delivery was confirmed, items were checked and put on a storage location OR delivery was cancelled.

  • Partial Delivery: Delivery has arrived and items were checked and put on a storage location BUT some items are missing.

  • On hold: Every inbound process can be set on hold. If a process was set on hold, app users trying to accept the delivery will be displayed a modal asking if they are sure they want to start the process.

    • Exemplary Use Cases:

      • Some items were missing and the order should only be stowed once the complete delivery has arrived.

      • Items are damaged and a supervisor must check the order before items can be stowed or written off.

Accepting goods with the inventory app

General

A goods receipt can be started by either clicking on one of the entries or by scanning the delivery note. If you want to scan, click on the symbol in the right corner and scan the barcode on the delivery note with your MDE device.

Upon opening an entry in the inbound overview, the user receives an overview of all items that are expected to arrive.

By clicking on an entry, the inbound process can be started. For each product that has arrived, the user can indicate total quantity and quantity of rejected items.

In addition, it is possible to add a comment and photos, explaining, e.g., reasons for rejecting certain items. If at least one product has been confirmed, the user can continue to scan the storage location.

After that, a summary of all accepted items as well as the scanned storage location is shown and the user can complete the receipt of goods.

Partial Deliveries

It is still possible to complete the receipt of goods without accepting all items. In that case the entry gets the status "Partial Delivery". The process remains in that status until either the rest of the delivery was accepted or the rest of the delivery was cancelled.

If a subsequent delivery arrives that belongs to the same entry, the receipt of goods can be continued by clicking on the entry. In that case the user can edit quantity and condition of items that have not been accepted yet. Items that have already been accepted cannot be edited anymore. If all remaining items have arrived in the subsequent delivery, the status of the process is changed to "closed" and the entry is not visible any more in the overview.

Products with Stock Properties

In the detail page, values for stock properties such as expiry date or batch number can be added.

If there are different properties for the same product, several property sets (e.g., several expiry dates) can be added by scanning or selecting the product again and clicking on the plus button in the product detail page.

Adding attachments to receipts

More details on the delivery in general or on specific items can be added via comments and/or photos.

Comments concerning the whole delivery can be added on the overview page by clicking on the comment icon.

Comments concerning a specific product can be added by clicking on the "Add comment" section in the product detail view for products without properties, or at the end of the wizard for products with properties. Photos of delivered product can be added by clicking on the "Add photos" section in the product detail view.

FAQs

How do I add a storage location if scanning does not work?

Upon clicking on the plus icon in the location scan view, an overview of all existing storage locations is shown. It is possible to search for storage locations by storage location ID or storage location name. A location can be selected via click. After that, users are forwarded to the summary page.

Go for more details on the inbound process status.

can be entered during the receipt of goods. If stock properties are configured for a product in the listing, the user is directed to a different product detail page upon scanning or clicking on a product in the inbound overview.

After adding stock property information, the total and rejected quantity of received items can be entered as usual. Depending on whether tracking of the respective stock properties is , the process can (not) be completed without entering property information.

https://docs.fulfillmenttools.com/documentation
Inbound Admin View
here
Stock properties
configured as mandatory