Get in touch
CH · Logistics & MobilityFeatured engagementPartner since 2023
Galliker Logistics Software Development Scaling GPMS for Modern Operations
HQSwitzerland
IndustryLogistics & Mobility
EngagementFull dedicated team, long-term

Galliker Logistics Software Development Scaling GPMS for Modern Operations

Galliker, a Swiss logistics and transport group based in Altishofen, partnered with Axon Active for long-term logistics software development, leveraging a dedicated development team to build and evolve GPMS (Galliker Process Management System), supporting the full transportation lifecycle from customer contracts to invoicing.

Dedicated software development team delivering logistics software development solutions for transportation lifecycle management with GPMS
About the client

Who Galliker is

Galliker is a Swiss logistics group providing freight, cold-chain, and supply chain services across Europe. To unify fragmented operations, the company developed GPMS — a central platform that connects customer engagement, contract management, order execution, transport planning, and invoicing within a single workflow.

The system replaces legacy solutions with a consistent data model and API-driven architecture, delivering custom logistics software development that Galliker can continue evolving for years rather than relying on an off-the-shelf product. The platform covers key modules such as contract management, order processing, tour planning, and telematics integration. Axon Active’s Vietnam-based team supports ongoing development, with Swiss leadership ensuring alignment and governance.

How we work together

Structured Agile delivery across distributed teams

A dedicated development team follows a structured Scrum–Kanban approach with two-week sprints, including daily standups and regular reviews with Galliker stakeholders in Switzerland. A consistent morning overlap between Vietnam and Switzerland is used for synchronous collaboration, while tools such as Jira, Confluence, and Webex support asynchronous progress throughout the day.

Each sprint concludes with a working demo, providing ongoing visibility into delivery. Planning is carried out jointly, with scope aligned to team capacity, and retrospectives used to refine processes incrementally. The team structure supports continuity, with engineers remaining on the engagement over time and maintaining familiarity with the platform. A Swiss-based account lead coordinates governance, risk handling, and alignment for this Swiss logistics software partnership.

What the team works on

Logistics software development for Galliker GPMS

The team maintains and enhances the full GPMS stack—the transport management software at the core of Galliker—through long-term logistics software development. Development spans the entire lifecycle, from initial order intake through vehicle dispatch, tour execution, and final invoicing.

All nine functional modules are actively supported. Contact Management ensures accurate client data; Gateway handles EDI and partner integration; Order & VTO manage real-time validation and tracking; Resource & Tour Management translates plans into assignments; the tour planning software handles routing and loading; and Vecos telematics integration adds real-time vehicle data to operational workflows.

Engineers contribute across the full feature lifecycle—from specification and development to testing and deployment—supporting consistent quality and alignment with business needs.

Full-stack development with clear architectural boundaries

The frontend (React, TypeScript, Tailwind) and backend (.NET, SQL Server, MongoDB) are developed concurrently by the same engineers. This full-stack approach reduces handoffs, shortens feedback cycles, and promotes architectural consistency. The codebase is structured around clear service boundaries: domain models are defined in shared libraries, APIs use REST and gRPC, and frontend components interact through a central data layer. This architecture supports independent testing, versioning, and scalability.

Full-stack software development architecture using React, TypeScript, .NET, SQL Server, and MongoDB for scalable applications

Reliable data architecture for mixed workloads

MongoDB is used to manage event-driven and semi-structured data, while SQL Server handles core relational business data. The team balances performance, consistency, and maintainability through thoughtful indexing, schema evolution, and caching strategies. Data integrity is maintained at both the application and infrastructure levels, with transaction logging, idempotency controls, and audit trails embedded in critical workflows.

MongoDB and SQL Server data architecture managing event-driven, relational, and semi-structured data with secure integrity controls
The teams leverage GitHub Copilot as part of our AI-augmented software development
AI-Augmented Development

AI-assisted development

The teams leverage GitHub Copilot as part of our AI-augmented software development approach to gain a clearer understanding of project structure and system architecture, review and analyze existing codebases, and perform refactoring based on well-defined implementation guidelines. It is also used to generate initial test case drafts, evaluate potential optimizations, and provide actionable suggestions aligned with evolving requirements.

Team composition

Who sits on the engagement

Orca
Green
Navy
Tech stack

What the team works in

Tech stack
.NET 10EF CoreMS SQL ServerMongoDBAS400RabbitMQApache KafkaMSTestPTV FrameworkQuartzEloFile SystemMS Entra IDReact 18Ant DesignTailwind CSSZustandTanStackReact Hook FormAxiosTypeScriptshadcn/uiMSAL
By the numbers

Scaling success together

3 Years

Year of collaboration

Nearly three years of continuous partnership focused on scalable development and long-term platform evolution

1 → 5 Teams

Team expansion

The engagement started with a single team in December 2023 and has since grown to five dedicated teams, significantly increasing delivery capacity, technical coverage, and cross-functional expertise

Common questions

How this engagement works

How does logistics software development manage a large, multi-module system like GPMS?

The system is divided into clearly defined modules, each with specific responsibilities such as contact management, or tour planning. The team works across these modules while maintaining shared standards for architecture and data models. Coordination happens through sprint planning and regular reviews to ensure dependencies are handled properly.

How do you ensure consistency between frontend and backend development?

The same engineers work across both frontend and backend components, which helps reduce misalignment. Shared design discussions and clear API contracts keep both layers in sync. Changes are typically implemented and reviewed together rather than in isolation.

How is data integrity maintained across multiple systems and workflows?

Data is handled through a combination of relational (SQL Server) and non-relational (MongoDB) databases, each used for appropriate workloads. The team applies validation rules, transaction logging, and audit trails within workflows to ensure consistency, especially when data moves across multiple modules.

How does the team handle scaling and system evolution over time?

The platform evolves incrementally, with improvements made alongside feature development. Architectural boundaries, service-based design, and modular structure make it easier to adapt specific parts without impacting the entire system. Performance and technical debt are reviewed regularly as part of ongoing work.

How is collaboration managed across Vietnam and Switzerland?

A daily overlap window supports meetings, reviews, and key decisions. Outside of that, communication continues asynchronously via tools like Jira, Confluence, and Teams. This setup allows work to progress continuously while still maintaining regular touchpoints.