MyCarrierPortal

MyCarrierPortal helps automate carrier onboarding, packet collection, compliance monitoring, and document sync.

Setup checklist

1. Confirm your MyCarrierPortal account access.
2. Open Settings, then Integrations.
3. Select MyCarrierPortal.
4. Enter required credentials.
5. Turn on Enable MyCarrierPortal onboarding.
6. Save settings.
7. Contact support for initial bulk import from monitored carriers if needed.

Test workflow

1. Search for one carrier.
2. Preview carrier details when available.
3. Send one carrier invite or sync one completed carrier packet.
4. Review documents, payment details, and compliance status.
5. Approve or keep the carrier inactive according to your policy.

Normal usage

Use MyCarrierPortal during carrier onboarding and compliance review. Review packet completion, documents, insurance, authority, and payment details before approving a carrier for use.

Manual sync is for carriers already onboarded in MyCarrierPortal. If the carrier is not onboarded there yet, invite the carrier first. When an invite finds an existing MyCarrierPortal carrier, ARK TMS syncs the latest packet instead of sending a duplicate invite.

Only one carrier onboarding provider can be active at a time. Turning on MyCarrierPortal onboarding disables RMIS and Highway onboarding actions.

Initial monitored carrier import

If you already monitor carriers in MyCarrierPortal, contact support. Support can help import monitored carrier data directly from the provider instead of relying on CSV import.

Troubleshooting

• Carrier not found: confirm the legal name, MC number, DOT number, or provider record.
• Identifier rejected: use a real DOT or MC/MX/FF docket value; all-zero or malformed values cannot be sent to the provider.
• Sync asks for an invite: the carrier is not onboarded in MyCarrierPortal yet.
• Duplicate carrier conflict: resolve or archive non-deleted local carrier records that share the same DOT or MC/MX/FF identity before retrying sync.
• Invite denied by Assure Advantage: review the provider risk result in MyCarrierPortal before retrying or approving the carrier.
• Packet incomplete: ask the carrier to finish the missing steps in MyCarrierPortal.
• Documents missing: confirm the documents are present in MyCarrierPortal and sync again.
• Compliance status differs: compare the provider portal and ARK TMS before approving the carrier.
• Provider timeout: transient MyCarrierPortal failures are retried automatically. Wait for the retry before re-running manual sync, then contact support if the carrier still fails.
• Bulk import needed: contact support before starting manual CSV cleanup.