PLATFORM ARCHITECTURE

One event backbone. Five operating systems. Zero data silos.

Understand how Trenvar's architecture connects warehouse execution, transport, billing, and commerce through a shared event layer — not fragile point-to-point integrations.

Book Architecture Review View Pricing

Event-Sourced

Data Model

Every action is an immutable event

Workspace-Isolated

Tenant Model

Sealed data boundaries per tenant

API + Webhooks

Integration Model

Workspace-scoped credentials and sync

Enterprise-Grade

Governance

Roles, audit trail, and approval flows

Design Principles

Three architectural decisions that change everything

These aren't implementation details — they're the reason Trenvar can connect warehouse floors to invoices without fragile middleware.

Event Backbone

Every operational action — a scan, a dispatch, a charge — is an immutable event. Downstream systems (billing, audit, reporting) consume these events, not copies of mutable state.

Workspace Isolation

Each workspace is a sealed boundary. Data, credentials, roles, and billing are scoped per tenant. No shared-tenancy data paths exist between workspaces.

Composable OS Layers

Each OS is a standalone execution layer. Stack them to create compound workflows — Warehouse + Transport, 3PL + Air Cargo — without re-platforming.

Data flows from warehouse floor to invoice through events — not copy-paste, not CSV, not middleware.

When a pallet is received, the event triggers putaway. When a shipment is packed, dispatch sees it. When storage accrues, billing captures it. One backbone connects everything.

Warehouse + Transport

Floor operations flow into delivery without a handoff gap

Warehouse OS captures inbound, manages inventory, and runs fulfillment. Transport OS picks up at dispatch — assigning drivers, tracking routes, and capturing POD. The connection is seamless because both layers consume the same event stream.

Receiving triggers putaway

Inbound events create inventory records and assign putaway tasks in the same transaction.

Fulfillment triggers dispatch

Packed shipments surface in dispatch queues automatically — no manual handoff between warehouse and transport teams.

POD closes the loop

Proof-of-delivery events link back to the originating warehouse order, creating an unbroken chain of custody.

3PL + Air Cargo

Multi-client operations with billing continuity across modes

3PL OS manages customer-owned inventory with per-client isolation. Air Cargo OS extends this with AWB lifecycle tracking and ground handling milestones. Both feed into the same event-backed billing engine.

Client-level data boundaries

Each client's inventory, charges, and operational records are isolated — visible only to authorized roles.

AWB milestone timeline

Ground handling events (intake, storage, handoff) are logged as immutable milestones on a per-AWB timeline.

Unified billing from events

Storage accrual, service charges, and cargo handling fees are all generated from the same event backbone — no manual reconciliation.

Commerce + CRM

Sales pipeline connects to buyer ordering without re-entry

Sales CRM tracks accounts and opportunities. Commerce OS activates buyer profiles, catalogs, and ordering portals. When a deal closes, the buyer is already connected to your operational core.