Connect a transport management system

Provider availability

• MachShip setup
• TransVirtual setup
• CargoWise requirements
• MyTrucking requirements

Company access and credentials

Owners manage credentials. Owners and admins review shipments and transfer authorized jobs; team managers are restricted to their assigned teams. Member drivers use the existing driver flows. Credentials are encrypted on the server, excluded from dashboard responses and audit records, and never displayed again. Requests use the existing company session and origin protection.

1. Sign in with a company staff account and select your shipper or carrier organization. No driver account is needed for dispatch staff.
2. The owner selects a provider, enters the account identifier and API credential, and confirms the provider environment. Select a team first for a connection restricted to that team.
3. Test read access before synchronizing. Replace credentials to rotate them; replacement pauses the connection until tested again.

• Open company TMS connections

Import and review shipper loads

Repeated imports preserve the existing draft. Linked shipments and HaulMatch export references are blocked from import to prevent loops. Dangerous goods and international shipments cannot be published through these adapters. Automatic allocation, provider cancellation and bulk discovery are outside this version.

1. Select an enabled connection and enter a specific pending shipment ID or consignment number. Confirm the record is unallocated and authorized for publication.
2. Import creates a review draft. Check source addresses, items, warnings, units, freight type, availability and instructions. Nothing is published by importing alone.
3. Save corrections or reject the draft. Confirm review to queue publication. Synchronization history shows the resulting operation.

Transfer an awarded job

MachShip receives a pending consignment. TransVirtual receives a consignment with PickupRequest disabled. Vendor account rules may still trigger their own automation. Export does not fetch rates, manifest a carrier booking, generate labels or perform financial actions.

1. Select an active awarded job and check its provider account. Complete pickup and delivery names, street addresses, suburbs, states and postcodes.
2. Enter item quantities, total weight per row in kilograms, and dimensions of one item in metres. The adapter converts these to the vendor units.
3. Confirm the shipment to queue an export. Review the resulting record inside the provider system before its dispatch workflow proceeds.

Linked tracking

Active linked jobs are polled every five minutes. Shipper connections show provider observations. Only the awarded fleet’s exported job can drive a HaulMatch delivery status, and existing team, driver, held-payment and lifecycle checks still apply. Unknown vendor statuses are recorded for review. Tracking cannot release money or confirm payments. MachShip tracking starts when the pending record has been converted into a consignment.

Recovery and disconnect

If reconciliation finds no record or multiple matches, the export stays paused. Check the provider before further action. A pending MachShip record already converted or removed may require vendor assistance to recover. Pausing prevents new work; disconnect also erases the saved credential. An in-flight request may still complete. Disabling the rollout flags preserves records and stops workers.