TMS Logo

TMS Documentation

Integrations

Integrations connect ARK TMS to accounting, tracking, carrier onboarding, compliance monitoring, and visibility tools.

Available integration areas

  • QuickBooks Online: accounting sync for invoices, payments, and accounting review.
  • ARK Tracking: driver tracking requests and load visibility from ARK TMS.
  • MacroPoint: shipment tracking through MacroPoint visibility services.
  • TruckerTools: driver tracking and reefer-related tracking settings.
  • MyCarrierPortal: carrier onboarding, packet collection, monitoring, and documents.
  • RMIS: carrier onboarding, compliance monitoring, auto-sync, and documents.
  • Highway: carrier onboarding, monitoring, alerts, webhooks, and documents.
  • project44: shipment milestone and visibility updates.
  • Load-board posting providers: posting, updating, refreshing, and removing available loads when enabled.

Setup checklist

  1. Assign an internal owner for the integration.
  2. Confirm account access with the provider.
  3. Gather credentials, customer mappings, and carrier monitoring requirements before configuration.
  4. Open Settings, then Integrations.
  5. Configure and save the integration.
  6. Run one test workflow before using it broadly.
  7. Confirm the team knows which system remains the source of record for each workflow.

For Sylectus load-board posting, save the numeric Bill To default in Integration Settings. Blank or invalid values use 1. Stop searches use freight location suggestions across the United States, Canada, and Mexico. Select a suggestion when possible so the city, state or province, country, and postal code when available are saved together for Sylectus validation.

For Truckstop load-board posting, connect the organization account first. Each user who posts loads must then connect their own Truckstop account with user OAuth; organization credentials and legacy post-as mappings do not authorize posting for that user. Loads and spot quote loads can be posted, updated, refreshed, or removed when Truckstop is enabled. Truckstop postings are public by default unless the posting is marked private.

Truckstop refresh availability follows the provider's next-refresh time when available. If Truckstop does not return one, ARK TMS uses a six-hour refresh cadence.

For load-board posting providers, scheduled cutoff timing blocks new posts only. If a DAT, Sylectus, or Truckstop post already exists, update or remove the provider post from ARK TMS even when the local pickup timing is now in the past.

Test workflow

Use one normal business case first: one invoice, one tracked load, or one carrier profile. Confirm the record starts correctly, updates as expected, and produces the expected result in ARK TMS and the connected provider.

Avoid using unusual exceptions for the first test. Test access, required fields, and normal status updates before testing edge cases.

Normal usage

Review integration results as part of the existing workflow. Accounting users should review sync status before closing billing work. Dispatch users should review tracking status from the load. Carrier teams should review onboarding, documents, and monitoring results before approving carrier use.

Troubleshooting

  • Missing credentials: confirm provider access and reconnect the integration.
  • Record did not sync: confirm required fields, status, mapping, and provider account access.
  • Duplicate or mismatched record: review customer, carrier, or account mapping before retrying.
  • Tracking did not start: confirm the load is dispatched and contact details are complete.
  • Load-board posting is blocked: confirm required stop city, state or province, arrival start times, provider credentials, Sylectus Bill To default, the posting user's Truckstop connection, and scheduled cutoff timing. For existing provider posts, update or remove the post instead of creating a new one.
  • Carrier data looks incomplete: compare the carrier profile in the provider portal and contact support if the provider record is correct.

When to contact support

Contact support for credential issues, provider sync setup, initial bulk carrier import, accounting sync questions, or integration behavior that does not match the expected workflow after the basic troubleshooting checks.