The border desk is inside the load.
Cross-border is not an add-on module bought later. It is how the product was built, which for a carrier running into the United States is the difference between one system and three.
The usual arrangement.
In most arrangements the border lives somewhere else: a customs portal, a broker's inbox, a second piece of software with its own logins and its own deadlines. The shipment gets typed a second time to cross, and the two records drift apart from that moment on.
What is actually there.
Both directions, in-app
United States-bound and Canada-bound filings are prepared, validated and packaged from the load record you already have, rather than rebuilt in a separate tool.
Barcodes generated for you
Auto-numbered, linked to the shipment, and printed onto the paperwork instead of hand-written onto it.
Including the two nobody builds for
The filing lifecycle mirrors the authorities' own process, including rejection and amendment after acceptance. Real crossings have those days; most software pretends they do not.
Wait times where you are crossing
Canada Border Services Agency and US Customs and Border Protection wait times, read directly, inside the load rather than in another browser tab.
What it means on a Tuesday.
A dispatcher builds the load once. The filing is assembled from it, the barcodes come off the same record, the broker packet is generated rather than re-keyed, and if the filing is rejected the load knows about it. Nobody opens a second system, and nothing is typed twice to get a truck across.
Where this claim stops.
Lanexa prepares, validates, barcodes and packages the filing end to end. The electronic transmission link is built and readiness-checked, but it is not switched on yet, so today the finished filing travels through your customs broker or portal exactly as it does now. We will say the day that changes. Better you read it here than discover it on a call.