fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
      • Facility discounts
    • 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
  • Instructions
  • Emergency hotline
  • Incident priorities
Edit on GitHub
  1. Core

Incident management

Last updated 5 months ago

Instructions

Please create a ticket in the to report an incident or ask for support.

  1. Select the right ticket type

  2. Summarize and describe the problem by filling-out the mandatory fields

  3. Select an incident priority & add attachments (e.g., screenshots) if available

  4. Issue the incident ticket by clicking on the send button

Please create your ticket here:

Emergency hotline

In case of emergencies, you can also use our hotline: +49 221 956 732 10.

Please only use this number for urgent incidents! The hotline is intended to use when our support portal is unavailable or you do not get any reaction by our agents.

In case we are already talking to a different customer, we might not be able to answer your call. Please always create a ticket via the service portal in these cases to make sure that your incident reaches us.

When reporting an incident, you are asked to identify the priority of your issue. This is how incidents are prioritized at fulfillmenttools.

Incident priorities

Incident Priority

Description

Priority 1

Customer is unable to use the SaaS services or essential applications are not executable or create data loss or corruption. This results in a complete loss of production.

Priority 2

The customer is able to use the SaaS services, but not all functions are usable. This results in a significant reduction in production.

Priority 3

Most of the functions of SaaS services are applicable with slight limitations

service portal
https://ocfulfillment.atlassian.net/servicedesk/customer/portals