Build the load around orders, stops, and capacity.
Group sales orders, transfers, shipments, stops, pallets, lots, quantities, customers, delivery windows, equipment, temperature needs, and route requirements.
AJAX Logistics
Keep every load connected to the warehouse, carrier, and customer.
AJAX Logistics brings transportation execution into the same operational platform used by the warehouse. Plan and tender loads, assign carriers, coordinate appointments and docks, confirm staging and loading, capture shipment documents, record exceptions, and preserve delivery proof without rebuilding the story across calls, emails, and spreadsheets.
Transportation Execution
Connect tendering, carrier activity, dock operations, and delivery proof in one load record.
AJAX Logistics is designed to reduce status chasing when tenders, appointments, carrier communication, warehouse readiness, paperwork, freight cost, and delivery evidence are managed in separate systems.
Issue and track carrier tenders.
Record the carrier, rate, equipment, pickup, delivery, response status, timing, instructions, and communication history for each tender issued.
Keep the accepted carrier tied to the load.
Track approved status, operating authority, insurance, equipment, service history, contact details, acceptance, rejection, cancellation, and replacement assignment.
Schedule arrivals and departures with context.
Record carrier, customer, supplier, load, date, time, dock, shipment, purchase, transfer, and special-handling requirements.
Match doors, loads, and warehouse readiness.
Assign dock doors, show staging status, identify delays, confirm loading sequence, and preserve arrival, departure, and service timing.
Make the complete transportation cost visible.
Record base freight, fuel, detention, lumper, redelivery, storage, stop-off, temperature, brokerage, and other approved accessorial charges.
Keep the paperwork with the load.
Attach bills of lading, packing documents, inspections, certificates, carrier records, rate confirmations, images, and customer-required documents.
Preserve evidence at the final handoff.
Capture signatures, names, dates, times, locations, images, shortages, damage, refusals, temperature exceptions, and final proof of delivery.
Load Lifecycle
One controlled story from planning through delivery.
The same order, shipment, pallet, lot, customer, carrier, tender, route, dock, document, exception, and cost reference can follow the load through every operational step.
Build the load, stops, equipment, schedule, capacity, shipment contents, customer requirements, and expected cost.
Issue the load to a carrier, record the response, and preserve the communication and tender history.
Capture driver, vehicle, trailer, appointment, arrival, documents, safety steps, and dock assignment.
Confirm warehouse readiness, staged pallets, lots, quantities, loading sequence, temperatures, and exceptions.
Record departure, route status, milestones, carrier updates, delays, temperature evidence, and delivery timing.
Capture proof, shortages, damage, claims, accessorials, final status, and the reviewed result required by finance.
Tender and Carrier Control
Preserve the full tender history, including rejected, cancelled, and replacement tenders.
Tendering is an operational event. Each tender issued can be tracked independently so the business can see which carrier received the opportunity, how the carrier responded, why the load changed, and which tender ultimately produced the accepted assignment.
Confirm the carrier commitment.
Preserve the accepted rate, equipment, pickup, delivery, reference numbers, contact, and response timestamp.
Keep the reason visible.
Record rejection, cancellation, capacity failure, timing conflict, price issue, service restriction, or other reason.
Create a new controlled tender event.
When a load is re-issued to another carrier, preserve the original tender and create a new tender record rather than overwriting the history.
Rules by Transportation Context
Configure tender, carrier, and load controls around customer risk, product requirements, route, equipment, and service expectations.
| Context | Transportation-Control Options |
|---|---|
| Carrier | Track approved status, insurance, authority, equipment, service history, contacts, and response rules. |
| Customer | Require appointment, routing, document, signature, image, delivery, or temperature proof. |
| Product | Apply cold-chain, food-safety, lot, shelf-life, segregation, inspection, or equipment requirements. |
| Route | Control stop sequence, delivery windows, mileage, instructions, access restrictions, and route-specific proof. |
| Exception | Route detention, late arrival, damage, shortage, temperature deviation, rejection, or failed delivery into review. |
Dock and Delivery Proof
Capture evidence once and keep it with the shipment.
Arrival, loading, departure, temperature, route, and delivery evidence should remain connected to the same load instead of being distributed across paper forms, email attachments, text messages, and carrier portals.
Carrier and Appointment Readiness
Capture check-in and dock context.
Capture arrival, driver, vehicle, appointment, documents, safety acknowledgment, dock assignment, and warehouse readiness.
Cold-Chain and Delivery Proof
Preserve the evidence from departure through delivery.
Preserve temperature records, images, signatures, route timing, delivery acceptance, shortages, damage, and shipment exceptions.
Connected Operations
Logistics becomes more valuable when warehouse, quality, finance, and profitability share the same operational story.
AJAX OES applications are designed to reduce manual handoffs between warehouse, dispatch, quality, customer service, finance, and executive reporting.
Pick status, staged pallets, lots, quantities, dock assignment, holds, loading readiness, and shipment confirmation can flow into logistics execution.
View WMSInspection results, release status, temperatures, photos, holds, damage, claims, and shipment conditions can remain connected to the same load.
View QMSBase freight, fuel, accessorials, detention, redelivery, claims, route complexity, and service requirements can help explain customer and sales-order profitability.
View ProfitabilityLoad tenders, responses, shipment status, advance ship notices, acknowledgments, invoices, and supporting documents can be connected to the operating record.
View EDI
Business Central Connection
Keep Business Central as the financial system of record while AJAX OES manages transportation execution.
AJAX Logistics is designed to connect carrier and delivery activity to warehouse pallets, customer orders, shipment documents, quality evidence, freight cost, and Business Central transaction references already used by the operation.
Give every participant the same load context.
Dock staff, dispatchers, warehouse users, drivers, carriers, supervisors, and customer-service teams can work from the same load context while authorized users retain control over Business Central shipment, payable, and financial posting.
Connect transportation work to source records.
Sales orders, warehouse shipments, transfers, returns, posted shipments, purchase documents, customers, vendors, carriers, and locations remain connected.
Use the actual fulfillment status.
Pick status, staged pallets, SSCCs, lots, quantities, dock assignment, holds, and loading readiness remain visible.
Prepare reviewed carrier costs.
Reviewed carrier charges, accessorials, supporting documents, shipment references, and payable-ready results remain connected.
Preserve the final delivery evidence.
Bills of lading, images, signatures, delivery times, shortages, damage, claims, and proof of delivery remain available.
Executive Value
Reduce status chasing, detention, disputes, and hidden transportation cost.
Connected load data gives operations, finance, quality, and customer service a common record for reviewing service, evidence, cost, and exceptions.
Connect appointment, pick, staging, dock, documents, loading, and departure status so users spend less time calling, texting, and searching for answers.
Documents, images, signatures, temperatures, delivery times, shortages, damage, and exceptions remain connected.
Tender and assignment records help management review carrier responsiveness, service, rate history, and replacement frequency.
Detention, redelivery, lumper, storage, fuel, damage, shortage, and other charges can be reviewed against the load and supporting evidence.
Freight, route complexity, stop count, delivery requirements, exceptions, and accessorials can support cost-to-serve and sales-order profitability analysis.
Shared load records reduce repeated explanations, disconnected spreadsheets, and conflicting versions of shipment status.
Start with connected logistics execution.
Estimate AJAX OES pricing, create a tenant, and begin guided setup without waiting for a consultation.
Separate Tender Events
Each load tender issued is treated as a separate operational tender event. A rejected, cancelled, broken, or re-tendered load may create an additional tender transaction when a new tender is issued.
Capabilities shown on this page describe the intended AJAX Logistics application and may include planned features. Final availability and scope depend on enabled applications, customer workflows, carrier participation, external services, device permissions, Business Central configuration, integrations, and implementation requirements.