Lanexa was built around freight that crosses between Canada and the United States. The crossing is planned from the load you already booked — booth waits, customs broker, control numbers, the paper the driver carries — instead of being retyped into another tool.
In a lot of small carriers the border lives somewhere else: a government portal, a broker's inbox, a spreadsheet of control numbers, a second piece of software with its own logins. The shipment is typed a second time to cross, and from that moment the two records can drift apart — a trailer swapped, a driver changed, a shipment added — with the difference found at the booth rather than in the office.
Live commercial booth waits at the crossings you use — US Customs and Border Protection southbound, the Canada Border Services Agency northbound — refreshed every 30 minutes. On their own page, as a dashboard chip, and as a badge on any cross-border load.
Every plan, including Solo
Border Desk gathers what a crossing needs from where it already lives — the driver, the truck and its plate, each load's commodity, weight and piece count, your carrier codes, the customs broker — and scores readiness on a checklist where every gap links to the screen that fixes it. Southbound and northbound rules differ, and so do the checks.
Fleet and up
Shipment and cargo control numbers are derived from your SCAC or CBSA carrier code plus the load's probill, never typed per shipment. Lanexa prints the lead sheet, PARS and PAPS labels and a driver packet with real barcodes — and refuses to print a barcode too dense to scan.
Fleet and up
Border Desk emails your customs broker their packet from your own sender, with the label record attached, and tracks each shipment's entry — pending, packet sent, acknowledged, entry on file — with an automatic chase. A banner counts active cross-border loads that have no broker at all.
Fleet and up
The manifest has to be in before the truck arrives — an hour ahead for most highway shipments. Every crossing shows a countdown against its ETA, and dispatch is alerted when arrival is close and the crossing is still not filed or accepted.
Fleet and up
Sales tax on the invoice is resolved from the province the freight was delivered to, and CAD/USD comes from the Bank of Canada rate. A load in another currency with no real exchange rate on file is refused rather than guessed.
Every plan, including Solo
A dispatcher books a load to Buffalo. Because origin and destination are in different countries, the booking sheet opens its customs block and fills the shipment control number from your SCAC and the probill. On Fleet, the trip becomes a crossing on Border Desk: the checklist shows the trailer plate is missing and links straight to the truck, the broker's packet goes out from your own address, the driver's packet prints with its barcodes, and the countdown runs against the ETA. The one step that happens outside Lanexa is the filing itself — keyed into the government portal from a list laid out in the portal's own field order.
Border Desk prepares the ACE or ACI data, the control numbers, the barcoded paper and the broker packet, ready to file, and the Filing Assistant lays every value out in the government portal's own field order.
Fleet and Enterprise. Live booth wait times, sales tax resolved from the destination province and the Bank of Canada CAD/USD rate are on every plan, including Solo.
Lanexa keeps a directory of brokers with a default per customer, and on Fleet Border Desk sends the broker their packet from your own address and tracks whether the entry is on file.
A load in another currency with no real exchange rate on file is refused rather than guessed, on every plan.