Skip to content

Case study Enterprise UX Desktop

SCHENKERLogistics Platform

Simplifying a complex shipping workflow, designing a structured logistics interface for shipment creation, document handling, and operational efficiency.

Year
2023
My role
UI/UX Designer
Domain
Enterprise logistics
Platform
Desktop app
Where shipments usually go wrong, and the answer in the design
Addresses
Typos, a missing unit, the wrong party. Sender and receiver each get their own step.
Weight and size
Guessed figures mean surcharges. Packages and pallets have a step of their own.
Labels
An incomplete label can lose a parcel. Labels are generated in the app from the shipment itself.
Documents
Missing details on a waybill delay it. Packing lists and waybills share one table view to review.

Typical errors: NetSuite, How to prevent shipping errors. The client's own error figures were not measured in this project.

schenkerclient.cubsten.com
Schenker, Sendung

The story in four steps

  1. 00.1Hook

    What if enterprise logistics software could feel intuitive, not like a spreadsheet with buttons?

  2. 00.2Friction

    Schenker's internal tools drowned operators in form complexity, scattered workflows, and inconsistent UI patterns. The tool was slow to learn and easy to get wrong, and in shipping the usual slips are costly: a mistyped address or postcode, a wrong weight or size, an incomplete label or waybill.

  3. 00.3Pivot

    We unified shipment creation, label management, and settings into one coherent design language, progressive disclosure over cognitive overload.

  4. 00.4Proof

    Desktop-first enterprise platform. Streamlined multi-step forms. Contextual help system. One design system for the entire logistics workflow.

01Project overview

Designing clarityfor enterprise logistics

SCHENKER is a desktop shipping management platform built for operational logistics tasks. The system brings together shipment creation, sender and receiver data, package setup, labels and tracking, packing lists, waybills, settings, and technical tools inside one workflow.

The goal was to make this complexity feel clear, structured, and manageable in daily use, a product built for real operations, not just presentation.

Modules
7
Shipment, labels, packing lists, waybills, settings, help, developer
Shipment Steps
5
Multi-step flow
Document Types
3
Labels · Lists · Waybills
Platform
1
Desktop App

02Challenge & solution

The Challenge

Enterprise logistics systems become difficult to use because they combine many repetitive, detail-heavy tasks in one place.

  • Multi-step shipment setup complexity
  • Large amounts of form input
  • Document-heavy workflows
  • Need for operational speed
  • Technical setup & configuration

The Solution

A clear, modular interface with strong workflow thinking, structured form design, and consistency across complex modules.

  • Step-based shipment creation flow
  • Grouped & scannable form fields
  • Consistent table-based document views
  • Strong side navigation structure
  • Separated operational & technical areas

Friction → Flow

Four principles, applied to enterprise complexity

01

Step

Break long flows into stages

Cognitive load down ~60%

02

Group

Cluster fields by semantic intent

Scannable forms · fewer errors

03

Table

Document workflows in dense tables

Bulk operations enabled

04

Separate

Operational vs technical zones

Right user · right tools

Designed in this case: 9+ screens across the 7 modules, 47 form fields

03Product structure

Modulararchitecture

  1. 01SendungShipment creation
  2. 02LabelsLabels & Tracking
  3. 03LadelistePacking lists
  4. 04FrachtbriefWaybills
  5. 05EinstellungenSettings
  6. 06HelpDocumentation
  7. 07EntwicklerDeveloper tools

04Shipment flow

Step-basedshipment creation

Instead of placing everything on one screen, the flow is divided into clear steps that reduce cognitive load and make complex data entry easier to complete.

  1. Step 01: Sendungsdaten & Informationen

    The starting point: delivery options, notification toggles (SMS, email, driver notifications), and transport remarks.

    Fix Day Zustellung · Zustell-Avis · Fahreravis

    schenkerclient/sendung/informationen
    Sendungsdaten & Informationen
  2. Step 02: Versender & Empfanger

    Sender and receiver each have their own focused step, company, address, email, and phone fields separated for clarity and fewer mistakes.

    Firma · Address fields · Contact info

    schenkerclient/sendung/empfanger
    Versender & Empfanger
  3. Step 03: Pakete & Paletten

    Package details as a separate operational layer, dimensions, quantity, weight, volume, and packaging type without mixing with contact data.

    Dimensions · Gewicht/Volumen · Palette hinzufugen

    schenkerclient/sendung/pakete
    Pakete & Paletten

05Key screens

Every module,designed

From shipment data to technical settings, each screen follows the same design language with consistent spacing, layout, and interaction patterns.

schenkerclient/sendung-empfaenger
Sendung, Empfänger
01

Sendung, Empfänger

Receiver data entry with structured form fields for address, contact info, and shipment details

Form Design · Data Entry · Address Fields

schenkerclient/sendung-informationen
Sendung, Informationen
02

Sendung, Informationen

Shipment settings with delivery options, notification toggles, and transport notes

Delivery Options · Notifications · Transport

schenkerclient/sendung-pakete
Sendung, Pakete
03

Sendung, Pakete

Package management with dimensions, weight, volume, and pallet configuration

Dimensions · Weight · Pallet Config

schenkerclient/labels--tracking
Labels & Tracking
04

Labels & Tracking

Label generation and tracking URL management with tabular shipment list view

Label Generation · Tracking URLs · Shipment List

schenkerclient/einstellungen
Einstellungen
05

Einstellungen

Workstation settings with printer configuration, API setup, and license management

Printer Config · API Setup · License

schenkerclient/api-schluessel
API-Schlüssel
06

API-Schlüssel

API key management with webhook configuration for developer integration

API Keys · Webhooks · Integration

06Document workflows

Structuredtable views

Labels, packing lists, and waybills rely on structured table views that support quick review, editing, downloading, and deletion. Consistency across these modules helps the system feel more stable.

schenkerclient/labels
Labels und Tracking

Labels und Tracking

Shipment list with checkboxes, tracking URLs, label generation, and bulk export functionality.

schenkerclient/ladeliste
Ladeliste (Packing List)

Ladeliste (Packing List)

Document management table with name, sender, date, download status, edit and delete controls.

schenkerclient/frachtbrief
Frachtbrief (Waybill)

Frachtbrief (Waybill)

Waybill management with the same consistent table structure, quick review, download, and edit.

schenkerclient/einstellungen
Einstellungen (Settings)

Einstellungen (Settings)

Workstation and printer configuration, API key management, and license status display.

07Design approach

Clarity overdecoration

The interface is built around clarity and operational speed. Its strength comes from structure, not excess.

Navigation
Strong side navigation
Surfaces
Large structured areas
Progression
Tab-based flow steps
Actions
Clear primary & destructive

What makes this workstand out

  • Strong workflow thinking
  • Clear information architecture
  • Structured form design
  • Consistency across complex modules
  • Usability for repeated daily tasks
  • Operational & technical support in one product

08Outcome

A clearerenterprise interface

By breaking complex workflows into focused modules and step-based screens, the platform becomes easier to navigate, easier to complete, and more useful in real working conditions.

  • Enterprise workflows
  • Complex form systems
  • Document-heavy interfaces
  • Clarity under operational complexity
Salome
Mosiava
Currently
Freelancing between a few brave brands and one very full sketchbook ;)
Previously
ScopeUniLabCubisten