Customer Portal
Case Study
Matrux.
Three apps, one platform. From UI mockups to a live freight system in under a year.
Follow a request
Pick a flow and watch it move through the system.
Steps
Carrier work- 1 The team enters a lane in New Quote. Admin
- 2 The platform checks the permission, never the role. Permission
- 3 The request leaves with a server-side key no browser ever sees. Server-side
- 4 The carrier engine prices the lane across carriers. Carrier
- 5 Rates stream back one carrier at a time. Stream
Matrux Admin
Platform API
Unified backend and shared database
Cloudflare AI
Smarty
Carrier Engine
Resend
Metabase
A simplified interactive map created for this case study to show how requests move through the system.
Matrux Freight is a US freight company that helps shippers move less‑than‑truckload (LTL) freight: rates across carriers, booking, and every shipment followed through to delivery.
In February 2026 the customer portal didn’t exist yet. There were only UI mockups. Today Matrux runs on three new applications: a customer portal where shippers quote, book and track; Matrux Admin, the back office where the team prices lanes and manages every shipment; and the platform API that unifies them over a shared database.
All three are live in production, designed and built end to end.
Resources
The challenge
A shipper wants three answers: what will it cost, when can it go, and where is it now.
Behind those answers sits an existing carrier engine that prices lanes and books with carriers. It does that well. Everything around it had grown page by page.
Four problems stood out:
- No portal for customers. Shippers had no self‑service place to quote, book and follow their freight, only a set of mockups describing one.
- A back office built page by page. Mixed building blocks, editing in pop‑ups on some screens and full pages on others, document downloads scattered across a single page, and search limited to a box and two dropdowns.
- No platform of its own. Clients, logins, permissions and pricing rules lived inside the carrier engine, so every change to the business depended on it.
- Access that was all or nothing. Permissions worked per menu, not per action, and accounts started with a password someone else had chosen.
Matrux needed a platform that kept the carrier engine for what only it can do, and took ownership of everything else.
The solution
A new architecture with one simple rule: reads come straight from the database, and anything a carrier has to act on goes through the carrier engine.
The platform API sits at the centre, with a new database structure designed for both the back office and the customer portal. It owns the people, the clients, their address books, the permissions and the pricing rules. Pricing, booking, cancelling, carrier documents and tracking are forwarded to the carrier engine with a server‑side key that never reaches a browser.
Lists never wait on a carrier. When the team prices a lane, rates stream back one carrier at a time, so the first options appear as soon as they arrive instead of after the slowest carrier answers.
The customer portal signs in through the same platform and shares its database. An address saved by a customer is the same record the team sees in the back office, in the same vocabulary.
The complete system
Three applications, each designed for a specific user, all working against the same platform.
Customer Portal - for shippers
Built from UI mockups into a full Next.js application. Shippers get LTL quotes, book shipments, track them, and manage their address book, quote history, billing and profile. Guests can get a quote and track a shipment without an account. The portal speaks English and Chinese, and stays carrier‑blind until a booking is confirmed. Freight can be typed in, or pasted straight from an email or a spreadsheet.
Matrux Admin - for the team
A complete rewrite from scratch, built on React Admin with a custom, polished interface in light and dark mode. The team prices a lane and picks Economy and Premium tiers from streamed carrier rates, books from a saved quote, and follows each shipment along a journey bar from booking to delivery. Documents live in one menu, and cancellations come with a refund estimate.
An Ops Workspace turns every shipment into a case: who owns it, what happens next, the last outside contact, and a timeline of every note, hand‑off and carrier update. Teams, tenants and per‑action permissions decide who sees what.
Platform API - the core
A new AdonisJS backend and a new database structure. Admins and customers share one account model and one sign‑in. Nobody is handed a password: invitations and resets go out by email, and people choose their own. Every action checks a permission, never a role, and an admin without full access only ever sees the clients assigned to them. Covered by its own automated test suite.
Integrations
- Smarty for address validation and ZIP lookup, returning every city a ZIP covers. Answers are cached, and queries run within monthly and daily budgets, so the service never costs more than planned.
- Cloudflare Workers AI through AI Gateway to recognise freight items from free text or a spreadsheet. Structured data is parsed first, AI handles the rest, and the form degrades gracefully to warnings if AI is unavailable.
- Resend for invitations, password resets and transactional email.
- Metabase for Lane Insights: dashboards opened right from a quote in the back office.
- The carrier engine for pricing, booking, cancelling, documents and tracking, reached only through the platform’s server‑side key.
Before and after
The real change isn’t the new stack. It’s how the team works every day.
- One place to run a shipment. Following a shipment after booking used to mean juggling the admin portal and a separate third‑party system. Now quoting, booking, tracking, documents and follow‑up all happen in one back office.
- Nothing slips between people. Every shipment has an owner, a person or a team, and a clear next step. Shipments are claimed and handed off with a note, and one that nobody owns stands out in the list instead of quietly falling through.
- The whole story in one timeline. What happened on a shipment used to live in chat threads and inboxes. Now the booking, every carrier update, every note and every hand‑off sit in one timeline, shared by customer service, truck management and operations. Anyone opening a shipment can see what happened, who is handling it, and what comes next, without asking in chat.
- Every customer request reaches the team. Booking requests, guest quotes, account requests and sales enquiries from the portal arrive by email the moment they’re sent, with the details the team needs to act.
- From quote to booked, faster. Carrier rates stream in as they arrive, so the team starts comparing before the slowest carrier answers. A saved quote turns into a booking without typing anything twice.
- The right access for everyone. Each person sees exactly what their work needs, down to individual actions, and new colleagues and clients join by invitation and choose their own password.
AI, with rules
AI brings the speed. Ownership keeps the shape.
In the product, AI does one job a person shouldn’t have to: reading freight out of an email or a spreadsheet and turning it into clean line items, with plain parsing first and AI only where it’s needed.
In the work, AI sped up both development and refactoring across all three codebases. Each repository carries written ground rules for it: stay native to the framework, use React Admin and AdonisJS as they were designed, add no dependency or custom layer without approval, and type‑check before anything is called done.
The result is speed without drift: three codebases that still read as if one person wrote them, because one person decided what each of them should be.
Built end to end
Three apps, one line of responsibility.
From the first mockup to production, every layer was designed and built end to end: the portal’s screens, the back office, the API and its database. The same decisions run through all three: one account model, one permission system, one vocabulary for addresses and freight, and one rule for where data is read and where carrier work is sent.
Less than a year in, the system is live, and still taking shape.