Skip to content
Industry

From shop order to loading dock: 68 documented releases of a production and shipping system

A production and shipping application for large motorised fans that leave the factory disassembled, from the import of orders and bills of materials to barcode-driven loading and pallet labels. Sixty-eight releases so far, each documented.

Client
An industrial fan manufacturer
Sector
Industry

In numbers

releases, each documented in a changelog
68
version reached in June 2026
1.41
pallet labels printed from the shipping flow
A5

The context

Large industrial fans are built to order and shipped disassembled. A single fan leaves the factory as several handling units, each with its own weight, packaging and place on the truck. If one part is missing at the destination, the installation waits.

The client's shop-order system knew what had to be built, but not how it would be packed, weighed, planned and loaded. That knowledge lived in spreadsheets and in the experience of a few people.

A system that people on the shop floor and at the loading dock rely on every day also has to change carefully: each version must say what it changed.

What we built

We built the flow in stages, releasing each part as soon as it was useful. Scanning each unit as it is loaded checks the truck against the packing list, so a missing unit shows up at the dock, not at the customer's site.

The flow covers:

  • Orders and bills of materials, imported from the shop-order system.

  • Packing lists and handling units, with the weighing of each unit.

  • Weekly production planning, including the planning of laser production.

  • Loading plan for each shipment.

  • Barcode-driven shipping: each unit is scanned as it is loaded.

  • A5 pallet labels, and exports to Excel and PDF.

  • Safety module: the workflow for installation and operation manuals, and the related dossiers.

  • Machinery quotes.

How it connects

Orders and bills of materials come from the shop-order system, so nothing is typed twice. The safety module and the machinery quotes were added later on the same platform, as the system extended to new areas.

The application runs on Azure App Service with Azure SQL, keeps documents in Blob Storage and uses Azure Service Bus for background work. People sign in through Keycloak single sign-on.

The outcome

The system has reached 68 releases — version 1.41 in June 2026 — and each one is described in a changelog, so the client always knows what changed and why.

Packing, weighing, planning, loading and labelling happen in one application, from the order to the truck. The same platform also carries the safety documentation and the machinery quotes, so the client extends one system instead of adding another.

Technology

  • Angular 21
  • .NET 10
  • Azure App Service
  • Azure SQL
  • Azure Blob Storage
  • Azure Service Bus
  • Keycloak

Related services

  • 02

    Custom software

    Web platforms, portals and operational applications built for one company, documented, then run by us or handed over.

    • Enterprise platforms and portals
    • Production, logistics and back-office apps
    • Installable web apps for mobile
    • Documented, maintained, handed over
  • 04

    Architecture and operations

    Architecture design and review, security by design, cloud and on-premises operations, maintenance and continuous releases.

    • Architecture design and review
    • Single sign-on, roles and audit by design
    • Azure or on-premises, observable
    • Maintenance and documented releases

Your project

Does one of these look like your problem?

The details change from company to company; the method doesn't. Tell us about yours.

Request a private meeting