Open infrastructure for
the movement of goods.

Transportation operations span spreadsheets, inboxes, PDFs, phones, dispatch systems, telematics, WMS, ERP and accounting. A warehouse can know what is staged while a dispatcher is still chasing coverage. A delivery can be complete while its proof remains buried in an inbox.

Without shared freight context, teams repeatedly reconcile references, recover missing PODs and investigate delayed invoices or operational blind spots. Kaporeal's direction is a coherent transportation record connecting those handoffs—not an unsupported promise of instant efficiency or a replacement for every specialist system.

A warehouse management system controls the work inside a facility: inventory locations, picking, packing, staging and receiving. A transportation management system coordinates the movement between facilities: carrier assignment, stop windows, freight milestones and delivery evidence. An ERP supplies commercial and financial context. The three systems need shared references, not overlapping ownership of every rule.

For outbound freight, a warehouse's ready-to-ship signal can provide shipment references, handling units and dock requirements. A future Kaporeal exchange would connect that context to a load and carrier, keeping readiness distinct from an appointment, arrival, loading or departure. Pallet and case identifiers should survive the handoff without asking the TMS to manage warehouse stock locations.

Inbound receiving needs more than a vehicle position. Teams need the expected shipment, a meaningful arrival estimate, observed milestones and a way to report shortages or damage against the same references. A received quantity remains a warehouse fact; the transportation record preserves the movement and its proof. Cross-docking later adds transfer relationships between inbound and outbound freight that cannot be captured by one generic delivered status.

Appointment scheduling, ASN / receiving context, handling-unit linkage and exception exchanges are planned. No WMS adapter or standards implementation is verified today. The purpose of the warehouse direction is to make these boundaries explicit before promising interoperability, so facility supervisors and integration engineers can challenge the model with actual handoff requirements.

Modular design and API-first contracts should let organizations adapt the transportation layer without surrendering their data or replacing every existing system. A proposed relational core and explicit extension boundaries favor a coherent operational model over premature distributed complexity.

Self-hostable by design is the intended deployment posture. It is not a current installer, a tested production release or a hosted subscription. Public source, licensing, migration guidance, backups and restore procedures must accompany credible deployment instructions.

Brokers, dispatchers, fleet operators, warehouse supervisors, 3PL software teams and industrial shipping departments see different edges of the same freight story. Open-source engineers can translate that operational knowledge into durable models and contracts. Kordspace founded Kaporeal to bring those perspectives into an adaptable transportation foundation.

No customer logos, community counts or installed deployments are invented here. Useful early collaboration begins with a workflow, an exception or a handoff that needs to be explained more clearly.