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
  • Operations Android application
  • Operations web application
  • Backoffice web application
  • Returns applications
  • Hosts & Ports
  • Android applications

Was this helpful?

  1. Clients
  2. Technical requirements

Requirements for fft applications

This page is outdated. Please go to our new documentation under https://docs.fulfillmenttools.com/documentation.

Operations Android application

  • Android Smartphone or MDE scanning device

  • Software min. Android Version 8 (API Level 26)

  • Software max. Android Version 14 (API Level 34 - requires App version 1.22.0 or higher)

  • Our App is developed and tested on Google Pixel devices (4a or above).

  • We support a range of MDE devices like Honeywell (e.g. EDA-52) and Zebra (e.g. TC 21 & TC 26) devices, please contact us for a list of recommended devices or the approval of specific devices.

  • MDE may need additional software to be installed and activated so that hardware scanner is accessible by app.

  • In case you do not run a Device Management Tool your Devices must be able to access Google Play for downloads and updates of our Android App.

  • Alternatively, APK download is also possible via the REST API when using custom MDM solution (in this case do not download the App from Google Play but will download it through a channel provided by fulfillmenttools)

  • Required app permissions must be granted on device.

  • Ports/URLs must be accessible for Google Firebase Cloud Messaging to support Push-notifications. See FCM ports and your firewall for details.

  • Current Google Play Services must be installed (this is usually present when a Google account is configured on the device).

  • Ports/URLs must be accessible for Google Play Services - see appendix

  • Stable internet connection/ sufficient WiFi signal in the entire area in which the app is being used (e.g. 50 Mbit/s or LTE). Note that this is also depending on the number of active devices.

Operations web application

  • Current Browser (Google Chrome recommended)

  • Stable internet connection (50 Mbit/s)

  • Honeywell devices may need a separate license for the hardware scanner to be usable

Backoffice web application

  • Recommended to use one of the last 2 versions of the browser (Google Chrome recommended)

  • Recommended minimum screen resolution: 1024x768

  • Stable internet connection (50 Mbit/s)

Returns applications

  • Returns iOS Application

    • Apple iOS device with camera

    • Software min. iOS Version 14.1 (requires App version 1.2.1 or higher)

    • Our app is developed and tested on iPhone SE (iOS version 14.1 or above)

    • Devices must be able to access Apple App Store for downloads and updates of our Returns iOS app

    • Required app permissions must be granted on device

    • Stable internet connection/ sufficient WiFi signal in the entire area in which the app is being used (e.g. 50 Mbit/s or LTE). Note that this is also depending on the number of active devices.

  • Returns Android Application

    • Android Smartphone or MDE scanning device

    • Software min. Android Version 8 (API Level 26)

    • Software max. Android Version 14 (API Level 34 - requires App version 1.2.1 or higher)

    • Our App is developed and tested on Google Pixel devices (4a or above).

    • We support a range of MDE devices like Honeywell (e.g. EDA-52) and Zebra (e.g. TC 21 & TC 26) devices, please contact us for a list of recommended devices or the approval of specific devices.

    • MDE may need additional software to be installed and activated so that hardware scanner is accessible by app.

    • In case you do not run a Device Management Tool your Devices must be able to access Google Play for downloads and updates of our Android App. (Google play link is not available yet)

    • Alternatively, APK download is also possible via the REST API when using custom MDM solution (in this case do not download the App from Google Play but will download it through a channel provided by fulfillmenttools)

    • Required app permissions must be granted on device. (Camera permission on Android Smartphones)

    • Stable internet connection/ sufficient WiFi signal in the entire area in which the app is being used (e.g. 50 Mbit/s or LTE). Note that this is also depending on the number of active devices.

Hosts & Ports

The following Hosts and protocols must be accessible in your network in order to use our apps:

  • Must be able to access Google Identity Toolkit service

    • https://identitytoolkit.googleapis.com/

    • https://securetoken.googleapis.com/

  • Must be able to access Sentry.IO service

    • https://*.ingest.sentry.io/api/

  • Must be able to access https://pick-<tenant>-prd.web.app/ (In-Store-Fulfillment web application)

  • Must be able to access https://ocff-<tenant>-prd.web.app/ (Backoffice web application)

  • Must be able to access REST API: https://ocff-<tenant>-prd.api.fulfillmenttools.com/

  • Must be able to access GraphQL API: https://ocff-<tenant>-prd.graphql.fulfillmenttools.com/, wss://ocff-<tenant>-prd.graphql.fulfillmenttools.com/

  • Must be able to access Download API: https://ocff-<tenant>-prd.download.fulfillmenttools.com/

  • Must be able to access public config files: https://storage.googleapis.com/ocff-<tenant>-prd-config-public/

  • We use dedicated URLs per tenant

Android applications

The Android mobile application makes use of Google Play Services and therefore requires access to the following services:

  • Firebase Analytics requires access to the following URL:

    • app-measurement.com/a

  • Firebase App Distribution requires:

    • firebaseappdistribution.googleapis.com

    • appdistribution-uploads.crashlytics.com

  • Firebase Authentication requires:

    • www.googleapis.com

    • firebaseauth.googleapis.com

    • identitytoolkit.googleapis.com

    • securetoken.googleapis.com

  • Firebase Crashlytics requires:

    • *.crashlytics.com

    • *.fabric.io

    • crashlyticsreports-pa.googleapis.com

    • firebasecrashlyticssymbols.googleapis.com

  • Firebase Performance requires:

    • play.googleapis.com

    • www.googleapis.com

  • Play Services/Firebase Installations requires:

    • device-provisioning.googleapis.com

    • firebaseinstallations.googleapis.com

PreviousSupported barcodes for camera scanningNextZebra printer

Last updated 6 months ago

Was this helpful?