fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
  • Introduction
  • Implication on routing decisions
  • Facility data
Edit on GitHub
  1. Core
  2. Facilities

Supplier facilities

PreviousManaged facilitiesNextFacility groups

Last updated 1 month ago

Introduction

In contrast to managed facilities, the operational responsibility at supplier locations lies entirely outside the network’s control. A supplier may operate multiple physical locations, but these individual sites are typically not known to the fulfillment network. Consequently, supplier facilities do not have registered addresses within the platform. Additionally, information such as working hours, capacity limits, or specific shipping carrier integrations are not maintained for supplier facilities.

Implication on routing decisions

This lack of visibility has important implications for certain standard . Since key data points about supplier facilities are unavailable, some rules can only consider the supplier part of the supply chain to a limited extent when dealing with supplier facilities. For example:

  • The geo distance rating does not factor in transport routes originating from suppliers, as their exact locations are unknown.

  • The country fence rule does not take into account the geographical location of supplier facilities.

These constraints should be considered when configuring routing strategies, especially when suppliers play a significant role in the overall fulfillment flow.

Facility data

Supplier facility data is limited to a few key attributes due to the reasons mentioned above. These attributes are interpreted analogously to those of managed facilities:

  • facility name

  • facility status

  • tenant facility ID

In addition, supplier facilities can be enriched with and to provide further categorization or metadata.

Important information

  • Supplier facilities can also have assigned to them.

  • and are not applicable for supplier facilities.

routing rules
tags
listings
Facility carrier connections
facility custom service connections
custom attributes