HalalChain

Supply Chain Compliance & Traceability Platform

Automated compliance monitoring, end-to-end traceability, QR verification, real-time alerts, operational intelligence, and scalable background job processing for modern halal supply chains across Southeast Asia.

English · Features · Architecture · Quick Start · API · Contributing · License

Demo

Overview

HalalChain is a compliance-driven automation platform that monitors, alerts, and scores supply chain health through four key capabilities:

Product Traceability

Public-facing traceability pages with QR code verification — consumers scan, no login required.

Compliance Monitoring

Automated certificate expiry detection (30-day window), expired certificate escalation with high-severity alerts, compliance issue tracking, and a transparent Compliance Score (0–100).

Automation Engine

Four automated rules run daily via cron:

Rule	Condition	Actions
Certificate Expiring	Expiry within 30 days	Notification + Alert + Email
Certificate Expired	Expiry date passed	HIGH severity notification + Compliance Issue + Email
Low Inventory	Stock ≤ reorder level	Notification + Replenishment suggestion
Shipment Delay	Past due + not delivered	Warning notification + Dashboard indicator

All rules include idempotent deduplication — no duplicate notifications per entity per day.

Real-time Alerts & Background Processing

In-app notifications via Server-Sent Events (SSE) with 25-second heartbeat
WebSocket (Socket.IO) for real-time shipment tracking and activity streaming
BullMQ queue system for reliable background job processing (emails, notifications, tracking events)
Redis (Upstash managed) for caching, pub/sub, and queue backend
Fire-and-forget email delivery via Resend or SMTP with exponential backoff retry (3 attempts)
Per-user notification preferences

Platform Features

Category	Capabilities
Traceability	Public traceability page, QR-based verification, product journey visualization
Compliance Monitoring	Certificate expiry detection, expired certificate alerts, compliance issue tracking, compliance scoring (0–100)
Operations Monitoring	Low inventory detection, shipment delay detection, dashboard alerts, automated notifications
Real-time	WebSocket (Socket.IO) for shipment tracking, SSE for notifications, BullMQ queues, Redis caching
Platform	RBAC (ADMIN/MANAGER/STAFF), audit logs (CREATE/UPDATE/DELETE/STATUS_CHANGE), email notifications (Resend/SMTP), real-time updates, dashboard analytics (6-month trends), Swagger API docs, 6-language i18n with RTL support

Architecture

┌──────────────────────────────────────────────────────────────┐
│  Next.js 15 (Frontend) — React 19, Tailwind CSS 4            │
│  /dashboard/*  /settings/*  /traceability/*                  │
└──────────────────────┬───────────────────────────────────────┘
                         │  rewrites: /api/* → backend
                         │            /uploads/* → backend
                         ▼
┌──────────────────────────────────────────────────────────────┐
│  Express 5 (Backend) — TypeScript, Zod validation            │
│  /api/docs (Swagger UI)  /api/health                         │
│  /ws (WebSocket / Socket.IO)                                 │
└──────────────────────┬───────────────────────────────────────┘
                         │
           ┌─────────────┼─────────────┐
           │             │             │
           ▼             ▼             ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│  Redis 7        │ │  BullMQ Queue   │ │  Socket.IO      │
│  (Upstash)      │ │  (3 queues)     │ │  WebSocket      │
│  - Cache        │ │  - shipments    │ │  - Rooms        │
│  - Pub/Sub      │ │  - notifications│ │  - Real-time    │
│  - Queue backend│ │  - emails       │ │    events       │
└─────────────────┘ └─────────────────┘ └─────────────────┘
                         │
                         ▼
┌──────────────────────────────────────────────────────────────┐
│  Automation Engine (Daily at 08:00)                          │
│  ┌──────────────────────────────────────────────────────┐    │
│  │  Rule Evaluation  →  Condition Check  →  Action       │    │
│  │  ┌────────────────────────────────────────────────┐   │    │
│  │  │ Certificate Expiring  │ Certificate Expired    │   │    │
│  │  │ Low Inventory         │ Shipment Delay         │   │    │
│  │  └────────────────────────────────────────────────┘   │    │
│  │         ↓          ↓           ↓                      │    │
│  │  Notification  +  Alert  +  Email (fire-and-forget)   │    │
│  └──────────────────────────────────────────────────────┘    │
└──────────────────────────┬───────────────────────────────────┘
                            ▼
┌──────────────────────────────────────────────────────────────┐
│  PostgreSQL 16 + Prisma ORM                                  │
│  node-cron — automation rules evaluated daily at 08:00       │
└──────────────────────────────────────────────────────────────┘

Monorepo managed with npm workspaces (backend/, frontend/).

Compliance Score

The Compliance Score (0–100) is computed on-the-fly from 5 transparent factors:

Factor	Weight	Description
Expired Certificates	30pt	Full penalty if any expired certificate exists
Expiring Certificates	15pt	Full penalty if any cert expires within 30 days
Delayed Shipments	up to 20pt	Proportional to delayed/total shipments
Low Inventory Items	up to 15pt	Proportional to low-stock/total items
Certificate Coverage	up to 20pt	Proportional to suppliers without active certs

The breakdown is returned with every score so users can see why each point was deducted.

User Roles & Account Management

Role	Access
ADMIN	Full platform access — all modules, user management, audit logs, destructive actions
MANAGER	Dashboard KPI/reports, analytics, suppliers, products, inventory, warehouses, POs, shipments, certificates
STAFF	Simplified dashboard, inventory operations (inbound/outbound/adjustment), warehouse read

Role-based navigation is enforced on both frontend (src/lib/navigation.ts) and backend (authorize middleware).

Account statuses: Users can be ACTIVE or SUSPENDED — suspended accounts are rejected at login with a clear message. Additional user properties: isVerified boolean, lastLoginAt timestamp, and tokenVersion for forced invalidation.

Invitation flow: ADMINs invite new users via email — the invitation includes a role selection (ADMIN/MANAGER/STAFF), an expiry date, and an accept-invite page flow.

Multilingual Support (i18n)

HalalChain is fully internationalised with 6 locale options:

Locale	Language	Direction	Flag
`en`	English	LTR	GB
`vi`	Tiếng Việt	LTR	VN
`ms`	Bahasa Melayu	LTR	MY
`id`	Bahasa Indonesia	LTR	ID
`ar`	العربية	RTL	SA
`th`	ไทย	LTR	TH

Language preference is persisted via cookie (halalchain_lang). Includes RTL layout support for Arabic. Every UI module (navigation, auth, dashboard, products, suppliers, inventory, warehouses, POs, shipments, certificates, reports, settings, notifications, traceability) has its own namespace for clean translation management.

Quick Start

Prerequisites

Node.js 20+
Docker (for PostgreSQL + Redis)
Cloudinary account (optional — required only for avatar and certificate file uploads)
Resend API key or SMTP credentials (optional — required only for email alerts)
Upstash Redis account (optional — production Redis is configured with Upstash; local Redis via Docker works for development)

Setup

# Clone the repository
git clone https://github.com/AbdolHamidDev/HalalChain.git
cd HalalChain

# Install dependencies
npm install

# Start infrastructure (PostgreSQL + Redis)
npm run db:up

# Configure environment variables
cp backend/.env.example backend/.env
cp frontend/.env.example frontend/.env

# Run database migrations and seed demo data
npm run db:migrate
npm run db:seed

# Start development servers
npm run dev

Service	URL
Frontend	http://localhost:3000
API	http://localhost:4000
Swagger docs	http://localhost:4000/api/docs
WebSocket	ws://localhost:4000/ws
Prisma Studio	`npm run db:studio`

Edit backend/.env — at minimum set JWT_SECRET. For avatar/certificate uploads, fill in the Cloudinary variables. For email alerts, set either RESEND_API_KEY or SMTP variables. For Redis, set REDIS_URL (local: redis://localhost:6379, or Upstash URL).

Demo Admin (No Account Required)

Try the admin panel instantly without creating an account:

Visit the landing page
Click "Try Demo Admin" button
Instantly access the full admin dashboard

Demo Credentials (pre-filled on demo login page):

Email: demo-admin@halalchain.local
Password: demo-admin-2024

Note: Demo mode is a temporary session. All changes are stored locally in your browser and are not saved to the database. When you try to add/edit/delete data, you'll see a friendly reminder that this is demo mode.

Seed Data Accounts

After running npm run db:seed, these accounts are created:

Email	Role	Purpose
admin@halalchain.com	ADMIN	Full platform access
manager@halalchain.com	MANAGER	Operations management
staff@halalchain.com	STAFF	Inventory operations
staff2@halalchain.com	STAFF	Warehouse staff

Default seed password: Set via SEED_PASSWORD environment variable in backend/.env (falls back to a secure default if not set).

Important: After seeding, immediately change the default password for all accounts in production environments.

Seed data creates all automation demo conditions:

3 expired certificates → Rule 2 fires → Compliance Score affected
1 certificate expiring in 14 days → Rule 1 fires
2 low-stock inventory items → Rule 3 fires
3 overdue shipments → Rule 4 fires
1 supplier without certificates → Coverage factor affected

Project Structure

HalalChain/
├── backend/
│   ├── prisma/              # Schema, migrations, seed
│   └── src/
│       ├── routes/          # 20 REST API route files
│       │   ├── settings/    # Notification preferences, etc.
│       │   └── websocket.ts # WebSocket info endpoint
│       ├── middleware/      # JWT auth + role authorization + WebSocket auth
│       ├── lib/
│       │   ├── automation/  # Automation Engine (Sprint 6)
│       │   │   ├── engine.ts             # Rule orchestrator
│       │   │   ├── types.ts              # Shared types
│       │   │   ├── complianceScore.ts    # 0–100 scoring
│       │   │   └── rules/                # 4 automation rules
│       │   ├── redis.ts      # Redis client (Upstash-ready)
│       │   ├── websocket.ts  # Socket.IO server
│       │   ├── queue.ts      # BullMQ queues (shipments, notifications, emails)
│       │   ├── shipmentTracking.ts # Real-time tracking events
│       │   ├── analyticsService.ts
│       │   ├── notificationService.ts
│       │   ├── notificationStream.ts  # SSE streaming
│       │   ├── emailService.ts        # Resend/SMTP
│       │   ├── scheduler.ts          # Daily cron
│       │   ├── certificateUtils.ts
│       │   ├── qrService.ts
│       │   ├── auditLog.ts
│       │   ├── activityStream.ts
│       │   └── ...
│       └── tests/       # Vitest unit & property-based tests
├── frontend/
│   └── src/
│       ├── app/         # Next.js App Router pages (auth, dashboard, settings, traceability)
│       ├── components/  # UI modules, layout, shadcn/ui, settings
│       ├── lib/         # API client, navigation, SSE hook, WebSocket hook, utils
│       ├── i18n/        # 6-language internationalisation (EN, VI, MS, ID, AR, TH)
│       └── types/       # TypeScript declarations
├── docs/                # Architecture docs, screenshots, demo
│   ├── ENHANCED_ERD.md
│   ├── REALTIME_ARCHITECTURE.md
│   ├── REALTIME_IMPLEMENTATION_SUMMARY.md
│   ├── REALTIME_SETUP_GUIDE.md
│   ├── UI_UX_IMPROVEMENTS.md
│   ├── UPSTASH_REDIS_SETUP.md
│   ├── screenshots/
│   └── demo/
├── markdown/            # Internal design & sprint docs
│   ├── DESIGN.md
│   ├── SPRINT6_PLAN.md
│   └── ADMIN_USER_MANAGEMENT.md
├── docker-compose.yml   # PostgreSQL 16 + Redis 7
└── README.md

API Overview

All protected routes require the halalchain_token cookie. Public endpoints live under /api/public/.

Prefix	Purpose
`/api/auth`	Register, login, logout, token refresh, `/me`
`/api/dashboard`	KPI stats + Compliance Score, charts, activity feed
`/api/analytics`	Date-range analytics (certificates, inventory, POs, shipments)
`/api/suppliers`	Supplier CRUD
`/api/supplier-contacts`	Supplier contact management
`/api/products`	Product CRUD + traceability + QR
`/api/certificates`	Halal certificate CRUD + file upload
`/api/inventory`	Stock levels + movements
`/api/warehouses`	Warehouse CRUD
`/api/warehouse-zones`	Warehouse zone management
`/api/batch-lots`	Batch/lot tracking
`/api/tags`	Tag management
`/api/purchase-orders`	PO workflow + line items
`/api/shipments`	Shipment tracking
`/api/reports`	Summary + CSV/XLSX/PDF export (6 modules: products, inventory, suppliers, certificates, purchase-orders, shipments) with date-range filtering
`/api/notifications`	User notifications (SSE stream + WebSocket)
`/api/audit-logs`	Audit trail (ADMIN)
`/api/admin/users`	User management (ADMIN)
`/api/invitations`	User invite flow (ADMIN)
`/api/profile`	Profile (name, email), avatar upload (256×256 WebP via Cloudinary), password change with validation
`/api/settings/notifications`	Per-user notification preferences (certificate alerts, inventory alerts, shipment alerts, invitation emails)
`/api/public`	Public traceability (no auth)
`/ws`	WebSocket endpoint (Socket.IO) — real-time shipment tracking, activity feed, notifications

Traceability Engine: The public traceability endpoint (/api/public/traceability/:sku) uses a dedicated engine (traceabilityEngine.ts) that builds a chronological timeline of events per product: supplier info → certificates → product details → purchase orders → shipments → inventory movements. All events are sorted ascending by date and returned as a structured JSON timeline.

Real-time Features:

WebSocket (Socket.IO): Room-based shipment tracking, live activity feed, instant notifications
SSE (Server-Sent Events): Notification stream with 25-second heartbeat
BullMQ Queues: 3 queues for reliable background processing (shipment-tracking, notifications, emails)
Redis: Caching, pub/sub, queue backend (Upstash managed in production)

Full OpenAPI 3 spec: backend/src/swagger.yaml — interactive docs at /api/docs.

Enums & Statuses

Model	Values
UserRole	`ADMIN`, `MANAGER`, `STAFF`
UserStatus	`ACTIVE`, `SUSPENDED`
SupplierStatus	`ACTIVE`, `INACTIVE`
PurchaseOrderStatus	`DRAFT`, `APPROVED`, `SHIPPING`, `RECEIVED`, `CANCELLED`, `PARTIAL`
ShipmentStatus	`PENDING`, `IN_TRANSIT`, `DELIVERED`, `DELAYED`
InventoryMovementType	`INBOUND`, `OUTBOUND`, `ADJUSTMENT`
AuditAction	`CREATE`, `UPDATE`, `DELETE`, `STATUS_CHANGE`
NotificationType	`LOW_STOCK`, `CERTIFICATE_EXPIRING`, `CERTIFICATE_EXPIRED`, `SHIPMENT_DELAYED`, `SYSTEM`, `COMPLIANCE_ISSUE`

Database Schema

User ──┬── InventoryMovement
       ├── Notification
       ├── AuditLog
       ├── RefreshToken
       ├── NotificationPreference
       └── UserInvitation (invitedBy)

Supplier ──┬── Product ──┬── Inventory ── Warehouse
           │             ├── InventoryMovement
           │             └── PurchaseOrderItem
           ├── HalalCertificate
           ├── PurchaseOrder ──┬── PurchaseOrderItem
           │                   └── Shipment
           ├── SupplierContact
           └── Tag

Warehouse ── WarehouseZone

BatchLot ─── (product tracking)

Technical Highlights

Layer	Technology
Frontend	Next.js 15, React 19, TypeScript, Tailwind CSS 4, shadcn/ui (Dialog, Select, DropdownMenu, Avatar, Checkbox, Tooltip, Collapsible, Label, Slot, Separator), TanStack React Query, Zustand (state), react-hook-form, Zod, Recharts, Framer Motion, Sonner (toast), next-themes (dark/light), Lucide icons, react-simple-maps, tw-animate-css
Backend	Express 5, TypeScript, Prisma, Zod, Helmet, JWT + Refresh Tokens, node-cron, Redis (ioredis + Upstash), BullMQ, Socket.IO
Automation	4-rule engine, idempotent deduplication, daily cron, SSE + WebSocket streaming
Database	PostgreSQL 16, Prisma ORM
Email	Resend (primary) / SMTP (fallback), exponential backoff retry, 3 attempts
File Storage	Cloudinary (avatars: 256×256 WebP resize, certificate files), multer for upload handling
Auth	JWT access token (HttpOnly cookie), Refresh Token rotation (bcrypt-hashed), token version invalidation, rate limiter (5 req/min on refresh), user suspension support
Real-time	Server-Sent Events (SSE) with 25-second heartbeat + WebSocket (Socket.IO) for bidirectional communication
Queue	BullMQ with Redis backend — 3 queues: shipment-tracking, notifications, emails
Deployment	Docker (multi-stage), Vercel (frontend), Render (backend), npm workspaces, GitHub Actions CI

Scripts

Command	Description
`npm run dev`	Start backend + frontend concurrently
`npm run dev:api`	Backend only
`npm run dev:web`	Frontend only
`npm run db:up`	Start PostgreSQL + Redis (Docker)
`npm run db:down`	Stop PostgreSQL + Redis
`npm run db:migrate`	Run Prisma migrations
`npm run db:seed`	Seed demo data
`npm run db:studio`	Open Prisma Studio
`npm run test -w backend`	Run backend tests

Testing

Backend tests use Vitest with unit tests and property-based tests (fast-check) for notification deduplication logic.

npm run test -w backend

Documentation

Document	Description
`docs/ENHANCED_ERD.md`	Enhanced Entity-Relationship Diagram
`docs/REALTIME_ARCHITECTURE.md`	Real-time architecture (Redis, WebSocket, BullMQ)
`docs/REALTIME_IMPLEMENTATION_SUMMARY.md`	Real-time features implementation summary
`docs/REALTIME_SETUP_GUIDE.md`	Step-by-step real-time setup guide
`docs/UI_UX_IMPROVEMENTS.md`	Dashboard & certificates UI/UX improvement proposals
`docs/UPSTASH_REDIS_SETUP.md`	Upstash Redis configuration & production setup
`markdown/SPRINT6_PLAN.md`	Sprint 6 — Compliance & Automation Engine plan
`markdown/DESIGN.md`	System design documentation
`markdown/ADMIN_USER_MANAGEMENT.md`	Admin user management guide

Deployment

Frontend (Vercel)

Deploy the Next.js frontend to Vercel:

Push your code to GitHub
Import the repository in Vercel
Set the Root Directory to frontend
Add environment variables:
- NEXT_PUBLIC_API_URL — your deployed backend URL (e.g. https://your-api.onrender.com)
- NEXT_PUBLIC_APP_URL — your frontend URL (e.g. https://your-app.vercel.app)
Deploy

Vercel automatically detects Next.js and handles the build. The frontend uses Next.js 15 with App Router and is optimized for Vercel deployment.

Backend (Render via Docker)

Deploy the Express backend to Render using the provided Dockerfile:

Push your code to GitHub
Create a new Web Service in Render
Connect your repository and set:
- Runtime: Docker
- Dockerfile Path: backend/Dockerfile
- Instance Type: Free or paid based on your needs
Add environment variables:
- DATABASE_URL — your PostgreSQL connection string (Render PostgreSQL or external)
- REDIS_URL — your Redis URL (Upstash recommended: https://...)
- JWT_SECRET — a strong random secret
- JWT_EXPIRES_IN — 15m
- NODE_ENV — production
- FRONTEND_URL — your Vercel frontend URL (e.g. https://your-app.vercel.app)
- PORT — 4000
- RESEND_API_KEY or SMTP variables — for email notifications (optional)
- CLOUDINARY_URL — for file uploads (optional)
Deploy

The backend Dockerfile uses a multi-stage build (deps → builder → runner) on node:20-alpine with a non-root user for security.

Infrastructure Options

Service	Options
Database	Render PostgreSQL, Supabase, Neon, or self-hosted
Redis	Upstash (managed), Render Redis, or self-hosted
Email	Resend (primary), SMTP fallback (Gmail, SendGrid, etc.)
File Storage	Cloudinary (avatars + certificates)

Production Environment Variables

Backend (Render):

DATABASE_URL=postgresql://user:pass@host:5432/halalchain
REDIS_URL=rediss://default:password@your-upstash-redis.upstash.io
JWT_SECRET=your-strong-secret-here
JWT_EXPIRES_IN=15m
NODE_ENV=production
FRONTEND_URL=https://your-app.vercel.app
PORT=4000
RESEND_API_KEY=re_xxx  # optional
CLOUDINARY_URL=cloudinary://api_key:api_secret@cloud_name  # optional

Frontend (Vercel):

NEXT_PUBLIC_API_URL=https://your-api.onrender.com
NEXT_PUBLIC_APP_URL=https://your-app.vercel.app

Local Docker Compose

For local development, use the included docker-compose.yml:

npm run db:up      # Start PostgreSQL + Redis
npm run db:down    # Stop containers
npm run db:migrate # Run Prisma migrations
npm run db:seed    # Seed demo data

The compose file includes:

PostgreSQL 16 (port 5432)
Redis 7 (port 6379)
Backend service (port 4000) with health checks
Named volumes for data persistence

Screenshots

Compliance Dashboard	Inventory Management

Compliance Score KPI, automation alerts, operational widgets	Stock levels, movements, and automated low-stock detection

Product Traceability	User Management

Public timeline — no login required	Role-based access with audit logs and invitation flow

Roadmap

Version 2.0 — Maintenance & Operations Upgrade

Status: ✅ Backend Complete | 🚀 Ready for Deployment

HalalChain v2.0 transforms the platform into a production-grade, self-maintaining system with comprehensive observability, automated maintenance, and operational control.

Key Features

Category	Capabilities
Observability	Structured JSON logging (Pino), health checks (PostgreSQL, Redis, BullMQ), system metrics, execution history
Automation	Automated daily backups (02:00), weekly data cleanup (Sunday 03:00), database-backed rule scheduling
Control	Runtime configuration management, feature flags with rollout %, maintenance mode, queue management
Resilience	Graceful shutdown (SIGTERM/SIGINT), dependency health monitoring, audit trail, error tracking

What's New

25+ new API endpoints for system administration
6 new database models (SystemConfig, FeatureFlag, AutomationRule, RuleExecution, SystemEvent, MaintenanceWindow)
4 scheduled cron jobs for automated maintenance
Automatic Docker migrations — no manual database setup needed
Production-ready deployment — Render + Vercel + Neon + Upstash

Documentation

📚 Complete v2.0 documentation available in docs/version2/:

Document	Description
Implementation Summary	Complete implementation details, statistics, and architecture
Testing Guide	Step-by-step testing instructions for all v2.0 features
Deployment Guide	Production deployment to Render (backend) + Vercel (frontend)
Maintenance Upgrade Proposal	Original proposal and design rationale

Quick Deploy

# Backend (Render) — auto-runs migrations & seeding
git push origin main

# Frontend (Vercel)
cd frontend && vercel --prod

No manual database setup required — Docker entrypoint automatically runs migrations and seeds v2.0 data on startup.

Contributing

HalalChain is open-source and welcomes contributions from the community.

We appreciate all contributions — whether it's a bug fix, feature implementation, documentation improvement, or design suggestion.

How to Contribute

Fork the repository
Clone your fork: git clone https://github.com/AbdolHamidDev/HalalChain.git
Create a feature branch: git checkout -b feature/amazing-feature
Commit your changes: git commit -m 'feat: add amazing feature'
Push to the branch: git push origin feature/amazing-feature
Open a Pull Request

Contribution Guidelines

Follow the existing code style and conventions
Write clear, descriptive commit messages
Update documentation for any new features
Add tests for new functionality
Ensure all tests pass before submitting PR

Code of Conduct

This project adheres to a Code of Conduct. By participating, you are expected to uphold this code.

Community

Discussions: GitHub Discussions — ask questions, share ideas, and connect with other contributors
Issues: GitHub Issues — report bugs or request features
Security: Please report security vulnerabilities to SECURITY.md

Recognition

Contributors will be acknowledged in our repository. We value every contribution, no matter how small.

Support

If you find this project helpful, please consider:

Starring the repository
Forking the repository
Sharing with others who might benefit
Joining discussions and helping others
Reporting bugs and suggesting features

Sponsorships

If you find this project valuable and would like to support its development, consider buying me a coffee:

Your sponsorship helps maintain and improve HalalChain for the community.

Acknowledgments

Built with Next.js, Express, Prisma, and many other amazing open-source projects
Icons by Lucide
UI components by shadcn/ui
Real-time infrastructure powered by Socket.IO, BullMQ, and Redis

License

MIT — see LICENSE for details. You are free to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software.

Built for the halal supply chain community

Website · Documentation · Demo · Report Bug · Request Feature

Name		Name	Last commit message	Last commit date
Latest commit History 79 Commits
.github		.github
.vscode		.vscode
backend		backend
docs		docs
frontend		frontend
markdown		markdown
.gitignore		.gitignore
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
SECURITY.md		SECURITY.md
cookies.txt		cookies.txt
docker-compose.yml		docker-compose.yml
package-lock.json		package-lock.json
package.json		package.json

Uh oh!

Folders and files

Latest commit

History

Repository files navigation

HalalChain

Demo

Overview

Product Traceability

Compliance Monitoring

Automation Engine

Real-time Alerts & Background Processing

Platform Features

Architecture

Compliance Score

User Roles & Account Management

Multilingual Support (i18n)

Quick Start

Prerequisites

Setup

Demo Admin (No Account Required)

Seed Data Accounts

Project Structure

API Overview

Enums & Statuses

Database Schema

Technical Highlights

Scripts

Testing

Documentation

Deployment

Frontend (Vercel)

Backend (Render via Docker)

Infrastructure Options

Production Environment Variables

Local Docker Compose

Screenshots

Roadmap

Version 2.0 — Maintenance & Operations Upgrade

Key Features

What's New

Documentation

Quick Deploy

Contributing

How to Contribute

Contribution Guidelines

Code of Conduct

Community

Recognition

Support

Sponsorships

Acknowledgments

License

About

Topics

Resources

License

Code of conduct

Contributing

Security policy

Uh oh!

Stars

Watchers

Forks

Releases 2

Sponsor this project

Uh oh!

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages