Freight enquiries arrive through several channels with incomplete cargo details. Operators needed to qualify them, request quotes from several carriers, keep a clear record of every message and approval, and track shipments without losing context between steps.
Solution
What LATYNEX Digital built
One system that follows a request from first contact to delivered shipment: lead intake, readiness checks, RFQs and quote comparison, an approval queue for outbound messages, and milestone tracking, all backed by an audit trail.
What it demonstrates
What this shows we can build
A single system that follows a request from first contact to delivered shipment: lead intake, readiness checks, RFQs with side-by-side quote comparison, an approval queue for outbound messages and milestone tracking.
Operational safeguards: an approval state machine with idempotent sending, rule-based inbound classification with conservative confidence, and operations, lead and connector audit logs.
How the same capability could serve another business
A business that handles requests, quotes and handoffs through inboxes and spreadsheets could get one system with owners, next steps, approvals and a full history.
RFQ readiness checklist and customer-question handling
Supplier RFQs with side-by-side quote comparison and client offers
Needs-attention queue and approval drafts with autonomy tiers
Booking operations with planned versus actual milestones
Activity timeline built from audit logs
Standalone mail worker for inbound and outbound mail
Read-only connector for an AI assistant
Capabilities in the code
Rule-based inbound classification with conservative confidence
Approval state machine with idempotent sending and full audit
Service-token access scoped to an explicit route allowlist
Operations, lead and connector audit logs
Document handling per shipment
Deployment gate that runs type checks, tests, lint and build
Product showcase
The product, screen by screen
From enquiry to deliveryRFQ readiness on a leadActivity timeline and approval draftLeads list with owner and next step
Screens come from a demo environment with synthetic data. Interface text was translated to English for presentation, so these are localised composites, not untouched screenshots.
How it works
From input to outcome
01
An enquiry arrives
From the website, from a mail worker that reads shared mailboxes, or entered manually.
02
The lead is qualified
Each lead has an owner, a next step and an RFQ readiness checklist.
03
Quotes are compared
Supplier RFQs and quotes sit side by side, and client offers are created from selected quotes.
04
Outbound messages are approved
Messages pass an approval queue with autonomy tiers; every action is written to audit logs that feed an activity timeline, and bookings track planned and actual milestones.
Technical approach
How it is engineered
A Next.js 16 and React 19 application written in TypeScript with a PostgreSQL database evolved through about seventy SQL migrations. A separate Node worker handles mailbox synchronisation over IMAP and SMTP. Authentication, CSRF protection and bearer tokens guard the routes; a Vitest suite and a scripted deploy gate protect releases.
Next.js 16
React 19
TypeScript
PostgreSQL
IMAP / SMTP
Node.js
Vitest
Model Context Protocol (read-only)
Status and limits
What this page does and does not claim
A private internal system used inside LATYNEX; it is not publicly accessible and is not a client project.
All companies, contacts and quotes shown are synthetic. No real clients, carriers, prices or margins appear.
No volume, revenue or time-saving figures are claimed.
A multi-module operations platform that gives one owner a single focus queue, decisions, tasks, portfolio and lead inbox across several business directions.
Focus queue, decisions and unified tasks
Portfolio and lead inbox across modules
Operation registry for people and AI-agent actors
In-house product — not external client workView case study →
Need something like Logistics OPS?
Tell us what is not working today. You get a straight answer on what it would take, and whether we are the right team to do it.
