Skip to content
Silka

Logistics2026UA · EN

GLIDEX

Sea, air, road, rail and multimodal freight across 74 countries — with a route planner, a live quote and shipment tracking on the public site.

Visit the live site
  • Web App
  • Calculator
  • Tracking
  • i18n
GLIDEX logistics platform homepage
Industry
Logistics
Engagement
14 weeks
Team
1 designer · 2 engineers
Platforms
Public platform · Route planner · Pricing calculator · Tracking

01

Challenge

Freight forwarding sells on certainty, but the industry's websites sell on brochure copy: a form, a phone number, and a quote three days later.

The brief was to move the first three steps of the sales conversation — is this route possible, how long does it take, what does it cost — onto the site itself, in two languages, without oversimplifying a genuinely complex pricing model.

Coverage
74 countries · 42 terminals
Modes
Sea · air · road · rail · multimodal · warehousing
Locales
Ukrainian and English

02

Solution

An interactive corridor selector lets a visitor pick origin and destination and see the viable modes, transit times and constraints for that lane before any contact happens.

The pricing calculator produces a transparent breakdown rather than a single figure — freight, handling, customs, surcharges — because in this industry a number without its components is not trusted.

Tracking exposes shipment status with a real timeline, and compliance requirements surface before booking rather than after, which is where they usually derail a shipment.

Route planner
Corridor → modes → transit time
Quoting
Itemised breakdown, not a single number
Compliance
Surfaced before booking

03

Architecture

  1. L0
    Localised site/ua · /en
    Route plannerClient
    Rate calculatorClient
  2. L1
    API layerService
  3. L2
    Route serviceCorridors, transit
    Rate engineItemised pricing
    TrackingStatus timeline
  4. L3
    PostgreSQLData
  5. L4
    CRM / enquiriesExternal
    Carrier dataExternal
Connections (10)
  • Localised site API layer
  • Route planner API layer
  • Rate calculator API layer
  • API layer Route service
  • API layer Rate engine
  • API layer Tracking
  • Route service PostgreSQL
  • Rate engine PostgreSQL
  • Tracking Carrier data
  • API layer CRM / enquiries · qualified enquiry
Localised static shell with dynamic route, rate and tracking services behind a single API layer.

04

UX

The site is organised around the question a shipper actually starts with — a lane, not a service. Mode, terminal and vertical content all hang off the corridor they picked.

Language is a routed segment, not a client-side toggle, so every localised page is independently linkable, cacheable and indexable.

Primary axis
Route first, service second
i18n
Routed locales, not a client switch

05

UI

Operational rather than glossy: schedules, transit times and cost components are typeset as data, with tabular figures that align down a column.

Industry verticals — retail, e-commerce, automotive, pharma — each get their own constraints surfaced, because a pharma cold chain and a retail container are not the same sale.

06

Development

Route and rate data are modelled as versioned reference data, so a tariff change is a dated record rather than a deploy.

The calculator runs its arithmetic server-side and returns the breakdown, which keeps commercially sensitive pricing rules out of the browser bundle.

07

What it does

  • Corridor selector

    Interactive route planner across 74 countries with transit times.

  • Six transport modes

    Sea, air, road, rail, multimodal and warehousing, each with its own constraints.

  • Pricing calculator

    Itemised cost breakdown per shipment rather than a single opaque figure.

  • Shipment tracking

    Status timeline with detailed updates.

  • Compliance checks

    Documentation requirements surfaced before booking.

  • Industry verticals

    Retail, e-commerce, automotive and pharma with cold-chain handling.

  • Locations & terminals

    Office and terminal network with contact routing.

  • Bilingual

    Ukrainian and English as routed locales.

08

Integrations & stack

Integrations

  • Carrier data
  • CRM
  • Tracking feeds
  • Email notifications
  • Analytics

Frontend

  • Next.js
  • TypeScript
  • Tailwind CSS
  • Interactive maps

Backend

  • Node.js
  • PostgreSQL
  • Rate engine
  • REST API

Platform

  • i18n routing
  • ISR
  • CDN

09

Where it landed

Starts on the site
Sales conversation

Route, time and cost before contact

Itemised
Quotes

Freight, handling, customs, surcharges

UA + EN
Locales

Routed, indexable, cacheable

Server-side
Pricing rules

Never shipped to the browser

A forwarder's website that behaves like the operations platform behind it: a shipper can qualify their own lane before anyone picks up the phone.

GLIDEX route planner
Corridor selector
GLIDEX services and modes
Transport modes
GLIDEX tracking and pricing
Tracking and quoting
GLIDEX on mobile
Mobile

Every build is designed for the phone as its own experience, not as a narrowed desktop layout.

Got a product that should exist by now?Tell us about it.

Describe what has to change in your business. We will work out what that actually takes — including when it takes less than you think.