FlowChain API

Internal operations management system for multi-unit restaurant chains.

FlowChain replaces manual WhatsApp and Excel-based workflows with a structured, traceable, and role-based REST API — covering weekly supply orders, warehouse stock control, distribution planning, daily chicken stock tracking, urgent inter-unit transfers, and supplier payment registration.

---

🚀 Tech Stack

Technology	Version	Purpose
Java	21 (LTS)	Programming language
Spring Boot	3.5.13	Main framework
Spring Security + JWT (jjwt)	0.12.6	Authentication & authorization
Spring Data JPA + Hibernate	3.x	Database ORM
PostgreSQL	16	Relational database
Docker + Docker Compose	Latest	Containerization
Maven	3.x	Build & dependency management
JUnit 5 + Mockito	Latest	Unit & integration testing
Swagger / OpenAPI	2.8.8	API documentation
Lombok	Latest	Boilerplate reduction

---

🏗️ Architecture

The system follows a Layered Architecture with clear separation of concerns:

Client (Mobile App / Browser)
        ↓ HTTP Request + JWT
JwtAuthenticationFilter   ← Validates the token, sets the security context
        ↓ Authenticated
Spring Security rules     ← Decides whether the request is allowed through
        ↓ Authorized
Controller Layer          ← Receives HTTP requests, validates DTOs
        ↓
Service Layer             ← Business logic, validations, aggregations
        ↓
Repository Layer          ← Spring Data JPA, database communication
        ↓
PostgreSQL Database

Authentication is stateless: no sessions are created. Every request carries its own proof (the JWT), and the user's identity and role are read from the token itself — no database lookup is needed to identify the caller.

---

👥 System Roles

Role	Description
ADMIN	Full access — consolidated lists, all units, user management
WAREHOUSE	Stock management, distributions, delivery confirmation
UNIT	Weekly orders, daily chicken stock, payment registration
COURIER	Urgent transfers between units

---

🏪 Operational Units

The system manages 7 operational units:

Unit	Type	Special Role
Alpha	Restaurant	Portioning center — bacalhau & entrecosto
Beta	Restaurant + Take Away	Operations hub — soups, rice, prepared dishes + courier base
Gamma	Restaurant + Take Away	—
Delta	Restaurant + Take Away	—
Epsilon	Take Away	—
Zeta	Take Away	—
Eta	Take Away	—

---

📅 Weekly Operational Calendar

Day	Operation	Responsible
Monday	Charcoal distribution	Warehouse
Tuesday	Warehouse products distribution	Warehouse
Thursday	External supplier purchases + distribution	Admin + Warehouse
Friday	Meats & prepared dishes distribution	Warehouse
Daily	Chicken stock control	Each Unit
Any time	Urgent transfers between units	Courier

---

🗺️ Project Roadmap

✅ Phase 1 — Setup & Foundations (Completed)

• Requirements analysis
• Data model design (12 entities)
• System architecture diagram
• Spring Boot 3.x project setup
• GitHub repository initialization
• Docker Compose — PostgreSQL + pgAdmin
• Project folder structure
• Unit entity with JPA mappings
• UnitRepository, UnitService, UnitController
• First REST endpoint — GET /api/units
• Swagger UI integration
• Global exception handling with @RestControllerAdvice

🔄 Phase 2 — Authentication (Almost complete)

• User entity + Role enum (ADMIN, WAREHOUSE, UNIT, COURIER)
• UserRepository with email lookup
• BCrypt password hashing
• Spring Security enabled — stateless SecurityFilterChain
• Admin user seeding on startup (CommandLineRunner)
• JWT token generation with jjwt (JwtService)
• Login endpoint — POST /api/auth/login
• JWT authentication filter — token validated on every request
• End-to-end authentication working (protected endpoints accessible with a valid token)
• Role-based access control on endpoints

⏳ Phase 3 — Order Management

• Weekly order submission per unit (Supplier, Warehouse, Beira Sumos)
• Prepared dishes order (soup, rice, bacalhau, etc.)
• Automatic consolidated order list per supplier
• Order status tracking (PENDING → CONFIRMED → DELIVERED)

⏳ Phase 4 — Warehouse & Stock Management

• Warehouse stock entries and exits
• Weekly distribution planning per unit
• Portioning registration (Alpha & Beta units)
• Delivery confirmation per unit

⏳ Phase 5 — Daily Operations

• Daily chicken stock control (per unit)
• Urgent product transfers between units
• Supplier payment registration with invoice photo
• Operations history and audit trail

⏳ Phase 6 — Testing & Documentation

• Unit tests with JUnit 5 + Mockito
• Integration tests
• Full Swagger / OpenAPI documentation
• API usage examples

⏳ Phase 7 — Security & Quality

• Input validation on all endpoints
• System logging
• Externalize secrets (environment variables)
• Security review

---

📁 Project Structure

flowchain-api/
├── docs/                          # Project documentation (PDF)
│   ├── FlowChain_Analise_Requisitos.pdf
│   ├── FlowChain_Modelo_Dados.pdf
│   ├── FlowChain_Arquitetura.pdf
│   └── FlowChain_UseCases.html
├── src/
│   ├── main/
│   │   ├── java/com/flowchain/api/
│   │   │   ├── config/            # Startup configuration (DataSeeder)
│   │   │   ├── controller/        # REST Controllers (Unit, Auth)
│   │   │   ├── service/           # Business logic (Unit, Auth)
│   │   │   ├── repository/        # Spring Data JPA repositories
│   │   │   ├── entity/            # JPA entities (Unit, UnitType, User, Role)
│   │   │   ├── dto/               # Data Transfer Objects
│   │   │   ├── security/          # SecurityConfig, JwtService,
│   │   │   │                      #   JwtAuthenticationFilter
│   │   │   └── exception/         # GlobalExceptionHandler
│   │   └── resources/
│   │       └── application.yaml   # App configuration
│   └── test/                      # Unit & integration tests
├── docker-compose.yml             # PostgreSQL + pgAdmin containers
├── pom.xml                        # Maven dependencies
└── README.md

---

🐳 Running Locally

Prerequisites

• Java 21
• Docker + Docker Compose
• Maven 3.x

Steps

1. Clone the repository

git clone https://github.com/CLopes86/flowchain-api.git
cd flowchain-api

2. Start the database

docker compose up -d

3. Run the application

./mvnw spring-boot:run

4. Access Swagger UI

http://localhost:8080/swagger-ui/index.html

---

🔑 Authentication

All endpoints are protected by default. Only /api/auth/** and the Swagger paths are public.

On first startup, a default ADMIN user is automatically seeded:

Field	Value
Email	admin@flowchain.com
Password	admin123
Role	ADMIN

1. Get a token

curl -X POST http://localhost:8080/api/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"admin@flowchain.com","password":"admin123"}'

Response:

{
  "token": "eyJhbGciOiJIUzM4NCJ9...",
  "type": "Bearer",
  "email": "admin@flowchain.com",
  "name": "Patroa",
  "role": "ADMIN"
}

2. Call a protected endpoint

curl -X GET http://localhost:8080/api/units \
  -H "Authorization: Bearer <token>"

Without the header, the same request is rejected before it ever reaches the controller.

How it works

• The token is signed with an HMAC-SHA key and is valid for 24 hours
• Its payload carries sub (email), role, iat and exp
• JwtAuthenticationFilter validates the signature on every request and places the authenticated user in the Spring Security context
• Passwords are never stored — only their BCrypt hash, with a unique salt per user

⚠️ Development credentials only. Change them, and move the JWT secret to an environment variable, before any real deployment.

---

📋 Main API Endpoints

Method	Endpoint	Role	Description	Status
POST	/api/auth/login	Public	User login — returns JWT	✅
GET	/api/units	Authenticated	List all units	✅
GET	/api/units/{id}	Authenticated	Get unit by ID	✅
POST	/api/units	ADMIN	Create new unit	✅
DELETE	/api/units/{id}	ADMIN	Delete unit	✅
POST	/api/orders	UNIT	Submit weekly order	⏳
GET	/api/orders/consolidated	ADMIN, WAREHOUSE	Consolidated order list	⏳
POST	/api/warehouse/stock	WAREHOUSE	Register stock movement	⏳
POST	/api/distributions	WAREHOUSE	Create distribution	⏳
PUT	/api/distributions/{id}/confirm	WAREHOUSE	Confirm delivery	⏳
POST	/api/chicken-stock	UNIT	Daily chicken stock	⏳
POST	/api/transfers	COURIER	Register urgent transfer	⏳
POST	/api/payments	UNIT	Register supplier payment	⏳

Implemented endpoints currently require a valid token. The per-role restrictions listed above are the intended design — enforcing them is the remaining Phase 2 task.

---

📄 Documentation

Full project documentation is available in the /docs folder:

• 📋 Requirements Analysis
• 🗄️ Data Model
• 🏗️ Architecture Diagram
• 📊 Use Case Diagram

---

👨‍💻 Author

Cesaltino Lopes Computer Science Student @ IPCB — Castelo Branco, Portugal

---

This project is under active development. New features are added progressively following the roadmap above.