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
  • Summary
  • Making reservations
  • Redistributing reservations
  • Over-reservations

Was this helpful?

  1. Products
  2. Inventory Management
  3. Global Inventory

Reservations

PreviousInbound ProcessNextSafety Stock

Last updated 5 months ago

Was this helpful?

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

Summary

A reservation is made after an order has been assigned to a facility. The reservation reserves an existing or future stock for a customer. In case there is no stock available, the reservation is saved and assigned to a suitable stock as soon as any becomes available.

Making reservations

A reservation is made after an or a has been made to a customer. There are multiple reservation criteria that need to be met for a stock to be considered for a reservation:

  • The stock must be pickable & accessible. This means the stock must be placed on a pickable location which is not locked. Stocks have both traits pickable & accessible by default. Go for more information on setting traits.

  • The available until date must not be exceeded. If a is configured in the listing, the corresponding stock has an available until date. The available until date on the stock will default to the expiry date in the if nothing else is specified. The date has to be larger than now or larger than the delivery date specified in the order.

  • The arrival date of the stock must be before the . If a stock has not arrived in the facility yet, the requestedDate which is specified in the corresponding must be smaller than the latest point in time when the picking can be started.

  • The stock must not be part of a delayed delivery. Only from with a requestedDategreater than now are considered. If the requestedDate is in the past, we classify the delivery as delayed and consider it too risky to place (further) reservations on its stock.

Redistributing reservations

After a reservation has been assigned to an (expected) stock, our systems constantly ensure that the reservations can still be fulfilled. If reservations cannot be fulfilled anymore our systems will try to redistribute the reservations on stocks meeting the . This covers the following cases, among others:

  • Stock is deleted

  • Stock becomes non-pickable: This could mean that the stock was relocated within the facility and put on a location without the "pickable" trait.

  • Stock becomes non-accessible: This could mean that the stock was relocated within the facility and put on a location without the "accessible" trait.

  • Expected stock's arrival date changes: If users are notified about changes of the arrival date of a delivery, we recommend to adjust the requestedDate in the purchaseOrder. This will lead to a check, ensuring that all reservations can still be fulfilled.

  • Expected stock's quantity changes: If users are notified about changes of the requested items in a delivery, we recommend to adjust the requestedItems in the purchaseOrder. This will lead to a check, ensuring that all reservations can still be fulfilled.

  • Purchase order is cancelled

Reservations on expected stock whose delivery is delayed are not reassigned automatically. Users are expected to update the requestedDate or cancel the purchase order if reservations should be re-distributed.

If a stock expires and/or reaches its available until date, reservations are not automatically re-assigned. Users are expected to mark expired stock as non-pickable, non-accessible or delete it completely.

From a technical perspective, this means that reservations are always verified and re-distributed (if necessary) if there occurred updates on an (expected) stock. Only time-triggered changes are currently not considered when re-distributing reservations.

Over-reservations

In case there is currently no stock available, reservations are saved and assigned to suitable stock as soon as a stock meeting the reservation criteria becomes available.

Over reservations are displayed in the in the Backoffice together with "normal" reservations. If there are over reservations in a facility, the user is notified via a info icon and tooltip.

stock overview
https://docs.fulfillmenttools.com/documentation
order has been placed
delivery promise
here
stock properties
latest point in time when the order picking can be started
purchaseOrder
expected stock
purchase orders
reservation criteria
stockAvailableUntil