Transolix Core Foundations Coming Together

Today was one of those days where a dozen small pieces finally clicked into a clean architecture. The Transolix TMS is starting to feel like a real product — not just screens and forms, but an actual logistics brain.

1. Shipment Creation Now Fully Structured

We finished the first serious version of the Shipment Create flow.
Address validation runs over YellowMap’s SmartMaps API, and the entire modal is now wide, scrollable, and usable even with big forms.

We also added:

• Inline customer creation

• Proper error/ok banners for clarity

• SmartMaps backend wired via services.smartmaps.key
  (after discovering the API actually uses key, not api_key 🙃)

And we introduced a proper data model for shipment items, so later the system can calculate:

• pallet space

• m³

• loading meters

• weight

• category → billing automation later
  This will be the backbone for accurate pricing, loading, and tour planning.

2. Documents Column in Shipments Table

The shipments overview now shows four icons:

• Auftrag

• Lieferschein

• POD

• Invoice

Icons appear for all shipments — but only activate if the document exists. Missing ones are greyed out.
This gives the dispatcher a perfect "document completeness" view at a glance.

Honestly looks beautiful already.

3. Admin Role Correction

We fixed the role logic:
Admins need zero permissions.
If you are admin → you own the entire system.

Everyone else uses permissions:
shipments.view, shipments.create, etc.

Warehouse is a role.
Drivers are a role.
Only users (your office team) receive permissions.

Clean and simple.

4. Fleet Module: The Big Vision

We started building the structure for the Fleet module — which will become one of the most powerful parts of Transolix.

The concept:

Vehicles (left side)

• Cards representing trucks, vans, trailers

• Drag & drop

• Add vehicle modal

• Each vehicle has max weight, pallets, volume, LDM

Drivers (right side)

• Cards representing drivers

• Drag & drop

• Add driver modal

• Assign one or multiple drivers to a vehicle

The shipment itself DOES NOT store driver info.
Drivers → Vehicles
Shipments → Only care about the assigned vehicle per leg.

This keeps the data clean and realistic.

5. Core Architecture File Saved

I generated a full transolix-architecture-core-2025-11-20.md that documents:

• Data models

• Role/permission system

• How shipments, items, vehicles, drivers relate

• Why we designed it this way

• What to continue tomorrow

Future-me will thank past-me for this.

---

Conclusion

Transolix is no longer a prototype.
It’s shaping into a real, scalable TMS architecture with:

• Clean RBAC

• Strong shipment model

• Document system

• Fleet module foundations

• Clear backend/frontend structure

Tomorrow, we continue building out the fleet UI and connect vehicles & drivers to the planner.