Skip to content
PERINGER Data Solutions, back to home

Back

Enterprise

Logistics and supply chain

Logistics data arrives from everywhere and never in the same format: a carrier file, a customs portal, a scanned docket, an email. The useful work starts by making them converge.

The sector’s needs

Delivered across Switzerland, remote-first, with on-site days by arrangement.

Scope boundary

Exchange monitoring checks arrival, format, volume, reconciliation and retry. It isn’t security detection: partner identities, secrets, endpoints, the network and incident response get scoped separately.

Examples of what gets built

  • Volume forecasting

    Forecasting by site and by week, with seasonality and campaign effects, so staffing is planned rather than endured.

    Predictive analysis →
  • Transport documents

    Reading dockets, freight invoices and declarations, with consistency checks before anything is written.

    Document automation →
  • Partner integration

    One connector per exchange format, tested and monitored, rather than one unmaintained script per partner.

    Business agents →
  • Deviation alerts

    Delays, unexpected quantities or unusual routings reported while there’s still time to act.

    Predictive analysis →
  • Answering tracking enquiries

    Sorting incoming enquiries and preparing the reply with the case status already assembled.

    Assisted customer care →
  • Cost of end-to-end visibility

    Flow tracking and transport history costed by use, with test environments switched off outside the periods they serve.

    Cloud cost optimisation →
  • Planning taken out of the spreadsheet

    The workbook that allocates the rounds becomes a multi-user application, with the entry rules and the history in the tool.

    The business tool built for you →
  • Freight invoicing

    QR-bill at the version in force, payment files on the current schema and reconciliation by reference, at volumes beyond manual checking.

    The Swiss invoicing chain →
  • Tracking portal for shippers

    Shipment status, delivery notes and invoices readable by the partner directly, read from the system rather than from a copy.

    Customer and supplier portal →
  • One tenant per group, not one per site

    The sites share one Microsoft 365 or Google Workspace environment with separated admin roles, reviewed external sharing and licences reconciled to people before every renewal date.

    Mail and collaboration tenant →
  • Watching the partner exchanges

    One check per expected feed: the file arrived, it’s readable, it’s complete. The alert goes to a named person with its procedure.

    Monitoring you can act on →
  • Partner and site access under one directory

    Carriers, sites and temporary staff receive accounts tied to a person and a role, with an end of assignment that closes the access on the planned day, portal included.

    Identity, directory and access →
  • Flow tracking restored before the next wave

    Shipment tracking, partner exchanges and invoicing each carry an accepted downtime. The timed restore says whether the warehouse reopens in the morning.

    Backup and recovery →

Relevant experience

Assignments I delivered, described without naming anyone. No logos and no testimonials: what I did, and with what.

  • Data-pipeline architecture on Google Cloud for an international index and financial-data provider

    Airflow · dbt · BigQuery · Terraform

  • An AI-agent environment for software development (scope review, testing, code memory), built and in daily use

    Copilot · Claude Code · MCP

  • Data-workflow automation for an internationally renowned classical-music festival

    Power BI · Python

Why me

  • Habit of feeds that arrive out of order, late, or twice
  • Connectors treated as software: tested, monitored, with an alert when the source changes
  • Right-sizing meant seriously: a fifty-gigabyte problem does not justify an architecture built for fifty terabytes
  • One person from the connector to the dashboard, with no handoff in between

Test the fit: Logistics and supply chain

Describe the context, constraints and decision you need to make. The first conversation qualifies scope, boundaries and the next useful step.

Describe the situation