CASE STUDY / LOGISTICS CONTROL API
CoreExpress API
Backend and database foundation for logistics operations, centralizing package movement from USA warehouse intake to Honduras delivery.
System flow
02
Project Snapshot
Responsibilities, stack and scope for a logistics API and relational data model.
- Designed relational structures for customers, users, roles and packages.
- Developed ASP.NET Core Web API endpoints and Swagger documentation.
- Modeled loads, shipment requests, statuses and authorization controls.
03
The challenge behind the project
The operation handled packages purchased in USA online stores, moving from warehouse intake to shipment, Honduras arrival and final customer delivery.
The business lacked a centralized platform to manage customers, users, roles, packages, loads, shipping requests, statuses and authorizations across the logistics flow.
- Package movement needed centralized operational information.
- Customers, packages and loads required consistent data modeling.
- Statuses and authorizations needed clearer backend control.
04
Centralizing logistics data into a backend foundation
A REST API and relational data model were implemented with ASP.NET Core, Entity Framework and PostgreSQL to centralize operational information.
System flow
05
Architecture & Technical Decisions
Layered ASP.NET Core backend prepared for modular growth without documenting fictitious service topology.
Frontend Scope
Frontend work was outside the documented scope; the case study centers on backend and data modeling.
ASP.NET Core API
C# .NET 8 Web API endpoints, DTOs, validation structures and Swagger docs.
PostgreSQL Model
Entity Framework schema for customers, packages, loads, requests and statuses.
DevOps & Docs
Docker, GitHub and client-owned server deployment context.
06
Key Challenges
No explicit challenge was documented; this section is limited to the documented database and API scope.
- 01 — Model customers, packages, loads, requests, statuses and authorizations.
07
My Contribution & Solution Highlights
Wilhen’s documented contribution covered schema development, REST API implementation and API documentation.
- Designed the relational database schema for logistics operations.
- Built REST API endpoints using C#, .NET 8 and ASP.NET Core Web API.
- Created entity models, DTOs, validation structures and Swagger documentation.
- Supported backend control for package statuses, requests and authorizations.
System flow
08
Business Impact
Documented impact is qualitative: logistics visibility, centralized information and cleaner operational control, with no verified numeric metric.
- Digitalized manual logistics workflows
- Centralized customer and package information
- Improved load and request control
- Reduced incomplete or duplicated records
09
Lessons learned
The project provided deeper understanding of international package logistics and domain modeling for operational software.
- USA reception, Honduras shipment and final delivery are connected operational stages.
- Data modeling directly affects logistics reliability.
- Centralized backend structures improve administrative visibility.
10
Next Evolution
Continue improving operational visibility and backend maintainability as logistics workflows evolve.
LET’S TALK