Everything a drayage carrier runs on, in one product

The records dispatch and the rate desk work from every day. Ports are keyed on UN/LOCODE, terminals carry what the gate cares about, and every quote and booking prices against a lane, so a port-to-door move cannot be mislabelled.

•  Ports and inland cities keyed on UN/LOCODE, enriched from the published list
•  Terminals with FIRMS code, gate hours, appointment system and chassis pool
•  Shipping lines by SCAC, linked to the terminals they call at
•  Lanes priced once and shared by every tariff; CY or SD is read from the lane, never typed
•  Quotes and price sheets with container lines and charges
•  Bookings converted from accepted quotes, with their charges carried along
•  A map of your network: ports, terminals, cities, zones and your service area over aerial imagery, with low bridges, hazmat routes, truck routes, weigh stations, rail crossings and truck parking as layers

Ledger, invoices, bills, pricing and settlement. Your customers, steamship lines and terminal operators are the same records dispatch picks from, so the company on the booking is the company on the invoice.

•  General ledger and a financial dashboard
•  Invoices and vendor bills
•  Customers and contacts shared with operations
•  Charge codes that drayage charges post against
•  Payment settlement

A document designer for the paperwork a drayage carrier prints and sends. Lay out an invoice, a rate confirmation, a delivery receipt or a bill of lading on the page, bind its fields to the record, and print it to any printer or save it as a PDF.

•  Design on letter, legal, A4 or a custom paper size, portrait or landscape, with guides and margins
•  Headers, footers, detail and group bands, so a multi-page invoice paginates itself
•  Barcodes, page numbers and the print date as elements you place
•  Bound to a record: one invoice, one booking, one delivery; or a global document any record can fill
•  Print to a named printer with a PDF fallback, or straight to PDF for email
•  Tractor-feed and text-mode printers supported for the warehouse

Drayage Cloud Driver runs on iPhone and Android. A driver sees today's trips and each stop in order, taps arrived, unloading and delivered, reports a problem at the gate, and sends photos and the signed receipt. Every update is saved on the phone first and sent when there is signal, stamped with the time and place of the tap.

•  Today's trips in order, with the container, move type, size and customer on each
•  Arrived, unloading started and delivered, one tap each
•  Problem at stop: gate closed, receiver not available, damaged container or seal, truck or chassis
•  Proof of delivery with photos and a scanned signed receipt
•  Truck route to the next stop, with low-bridge warnings and hazmat on the trip
•  Works without signal: updates queue on the phone and send later
•  Sign in from the dispatcher's invitation with an email code, no password to forget

Ask which quotes expire this week or which bookings still have unnumbered containers and get an answer from your own records. Anything that moves money asks you first.

•  Reads your drayage and accounting records, nothing else
•  Asks before any action that changes money
•  Only ever sees your company's data

Invoices and alerts are queued from the desktop and delivered by a service in the background. If a mailbox is down, the message waits in the queue; nothing is lost and nothing is sent twice.

•  Invoice delivery straight from Accounting
•  A queue every message passes through
•  Delivery over email, with a record of what went out

Every app reports its faults to one place. Administrators see them, filter them and get alerted when something needs a person.

•  Fault and log collection from every app
•  Alert rules with delivery through Communications

Pipelines bring data in and out on a schedule or on demand, with a record of every run. Reference data loads through it and reloads without touching what your team typed.

•  Load rates, customers and terminals from spreadsheets or your current system
•  EDI with your trading partners (X12), received through the gateway and kept
•  Scheduled, windowed and change-driven runs
•  Run monitoring and alerts

Create environments such as development, staging and production, each with its own database and credentials. Invite your team, issue keys and review who did what.

•  Environments with isolated databases and credentials
•  Teams, users and API keys
•  Security settings and an activity log
•  Sign-in with Microsoft Entra ID, so your work accounts and policies apply