Overview
The transmission of an EDI 204 (Motor Carrier Load Tender) can be different depends on whether the customer is configured with background workflows such as Contracts or Routing Guides.
Scenario 1: Customer Configured with Background Workflows
When a customer is set up with automated workflows (e.g., Contract or Routing Guide), the system automatically tenders shipments to a carrier upon scheduling.
Process Steps:
Create or Clone a Shipment
Schedule for Pickup
This process will automatically generate an EDI 204 and assign the carrier through the background workflow.
⚠️ Note:
If the user manually selects “Assign a Carrier” or “Tender to Carrier” after the workflow-generated tender, it can cause a duplicate 204 transmission with the same transaction code (00).
Scenario 2: Customer Without Background Workflows
If the customer is not configured with background automation (no contract or routing guide workflow), a 204 will not be generated automatically.
Process Steps:
Create or Clone a Shipment
Manually Tender to Carrier
In this case, the user must explicitly tender the shipment to a carrier for the system to generate the EDI 204 message.
Summary
Customer Configuration | How 204 is Generated | Risk of Duplicate 204 |
With background workflow (Contract/Routing Guide) | Automatically when shipment is created or scheduled | High (if carrier is manually assigned again) |
Without background workflow | Only when manually tendered to a carrier | None |