--- title: "Fall '25 Receive LTL 3PL Rates through LTL Aggregators" slug: "fall-25-receive-ltl-3pl-rates-through-ltl-aggregators" tags: ["Admin", "Expanded Content", "LTL Carriers", "TMS Admin", "Training", "Fall '25"] updated: 2026-02-24T15:39:28Z published: 2026-03-03T14:14:34Z canonical: "documents.revenova.com/fall-25-receive-ltl-3pl-rates-through-ltl-aggregators" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Fall '25 Receive LTL 3PL Rates through LTL Aggregators ## **Overview** ## Receive LTL 3PL Rates through LTL Carrier Aggregators Follow these steps to receive rate data from LTL aggregators. Project44 is shown as an example. ### **Credentials** Valid credentials are required for the aggregator. 1. Navigate to **TMS Admin** and select **Credentials**. 2. Find the card for aggregator. In this case, Project44. 3. Click the link to open the record. 4. Add a value **User Id** and **Password 1**. Other aggregators may require additional credential information. 5. Note the **Record Id** at the bottom of the Credentials record. 6. Click **Save**. ### **Transportation Profile** Create a Transportation Profile for the LTL 3PL. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/BlueGrace%20logistics%20-%20SCAC.jpg?sv=2022-11-02&spr=https&st=2026-02-24T15%3A39%3A26Z&se=2026-02-24T15%3A54%3A26Z&sr=c&sp=r&sig=MJunW%2Boon%2BNw%2F28Ubo%2B6KCCvQlXoAAx%2FhwDSt8bFgyQ%3D) - The **SCAC** field on the Transportation Profile must match the SCAC code set for that 3PL on the aggregator's website. Confirm there is a Carrier Service for the LTL 3PL. Create a new Carrier Service if necessary. 1. Per the 3PL (shown in the screenshot below). 2. Quote, Tender, and Status Methods must all be ***API***. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/BG%20-%20Carrier%20Service.jpg?sv=2022-11-02&spr=https&st=2026-02-24T15%3A39%3A26Z&se=2026-02-24T15%3A54%3A26Z&sr=c&sp=r&sig=MJunW%2Boon%2BNw%2F28Ubo%2B6KCCvQlXoAAx%2FhwDSt8bFgyQ%3D) 3. The **Credentials** field on the Carrier Service record must match the Credentials **Record Id** found on the Project44 Credentials record. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/BG%20-%20Carrier%20Service%20-%20P44%20Credentials.jpg?sv=2022-11-02&spr=https&st=2026-02-24T15%3A39%3A26Z&se=2026-02-24T15%3A54%3A26Z&sr=c&sp=r&sig=MJunW%2Boon%2BNw%2F28Ubo%2B6KCCvQlXoAAx%2FhwDSt8bFgyQ%3D) Create a *Carrier* Rate Entry for the *Global* Transportation Profile with the BlueGrace Carrier Service created above. Set the **Base Rate Calculation** field to *API*. The LTL aggregator sends information to the TMS for the Carrier and 3PL SCACs. If the Carrier and 3PL SCAC fields are different, the 3PL Transportation Profile is added to the Carrier Quote as the Vendor. The Carrier Service is the Carrier responsible for moving the load. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Carrier%20Quote%20Example.jpg?sv=2022-11-02&spr=https&st=2026-02-24T15%3A39%3A26Z&se=2026-02-24T15%3A54%3A26Z&sr=c&sp=r&sig=MJunW%2Boon%2BNw%2F28Ubo%2B6KCCvQlXoAAx%2FhwDSt8bFgyQ%3D) > [!NOTE] > A flow must be created to update the **Carrier Bill To** field on the load to match the billing address for the LTL 3PL. > > - In this example, the **Carrier Bill To** for BlueGrace must be the BlueGrace billing address fields because BlueGrace negotiated the contract with the Carrier. > - If the wrong address is listed, the Carrier bills customers an incorrect rate, not the BlueGrace contractual rate. ### **Integration Examples** The Project44 integration sends the 3PL SCAC as the *capacityProviderAccountGroup*, **code** field. This field queries the Carrier Service and Vendor in the TMS and assigns the quote accordingly. See the screenshot below: ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Project44%20-%203rd%20Party%20SCAC(1).jpg?sv=2022-11-02&spr=https&st=2026-02-24T15%3A39%3A26Z&se=2026-02-24T15%3A54%3A26Z&sr=c&sp=r&sig=MJunW%2Boon%2BNw%2F28Ubo%2B6KCCvQlXoAAx%2FhwDSt8bFgyQ%3D) The Banyan integration sends the 3PL SCAC as the **ThirdPartySCAC** field. See the screenshot below: ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Banyan%20-%203rd%20Party%20SCAC(1).jpg?sv=2022-11-02&spr=https&st=2026-02-24T15%3A39%3A26Z&se=2026-02-24T15%3A54%3A26Z&sr=c&sp=r&sig=MJunW%2Boon%2BNw%2F28Ubo%2B6KCCvQlXoAAx%2FhwDSt8bFgyQ%3D)