Planned
MyCarrierPackets integration: planned, not built
MyCarrierPackets, now called MyCarrierPortal, onboards and monitors carriers for brokers. A FreightVero integration is planned so its results update the carrier record. Here’s where it stands.
Short answer
MyCarrierPackets is a carrier onboarding service for brokers, rebranded as MyCarrierPortal in 2023 and acquired by Descartes in 2024. Brokers use it to onboard carriers, verify carrier identity, confirm insurance and monitor for fraud and double brokering risk. A FreightVero integration is planned and not built.
How it fits the load workflow
MyCarrierPortal describes its job as helping brokers verify and monitor carriers, with onboarding that plugs into a TMS workflow and automated insurance monitoring. The company started as MyCarrierPackets in 2012, and the login still runs at mycarrierpackets.com.
In the FreightVero TMS, carrier compliance is part of the first checkpoint. A load can’t move to Alerted until the carrier record shows an approved compliance status. Today your team sets that status on the carrier record, and the database enforces it.
The planned integration is meant to write MyCarrierPortal results onto that record, so an insurance lapse or a failed identity check shows up before the next load is booked. Until then, keep onboarding in your current tool and keep each status current. The carrier onboarding guide walks through the process, and double brokering explains the risk it’s meant to catch.
FreightVero has no partnership with Descartes or MyCarrierPortal.
What the integration is planned to cover
Packet results on the record Planned
Completed onboarding results written to the FreightVero carrier record.
Insurance monitoring flags Planned
Insurance changes flagged on the carrier before the next load.
Risk flags before booking Planned
Identity and fraud warnings visible to the rep when a carrier is booked.
Checkpoint reads the result Planned
The Alerted checkpoint using the onboarding status instead of a manual entry.
Request the MyCarrierPackets integration
Tell us whether you onboard with MyCarrierPortal, RMIS or something else. Requests help set the order we build in.
Frequently asked questions
Is MyCarrierPackets the same as MyCarrierPortal?
Yes. MyCarrierPackets rebranded as MyCarrierPortal in 2023, and Descartes acquired the company in September 2024. The old name is still widely used, and the login still runs at mycarrierpackets.com. Both names refer to the same product.
Does FreightVero integrate with MyCarrierPortal today?
No. The integration is planned and not built. Your team sets compliance status on the carrier record in FreightVero, and the first checkpoint enforces it. No carrier data flows in from MyCarrierPortal yet.
Why does onboarding data belong in the TMS?
Because the booking decision happens in the TMS. If an insurance lapse sits in a separate onboarding tool, the rep booking the load may never see it. With the result on the carrier record, the checkpoint that gates the load would read the same status the onboarding tool reported.
Which will FreightVero support first, RMIS or MyCarrierPortal?
We haven't set an order. Both are planned. Tell us which one your brokerage uses through the request form, since requests shape what gets built first. See the RMIS integration page for that plan.
What is a carrier packet?
A carrier packet is the set of documents a broker collects before working with a carrier, such as operating authority details, insurance certificates, a W-9 and a signed broker-carrier agreement. See our carrier packet definition.