Skip to content
English
  • There are no suggestions because the search field is empty.

How do I setup Carrier Suppression in SmartTMS?

Carrier Suppression allows SmartTMS to exclude specific carriers from rate shop results based on defined business rules. These rules are configured via the CARRIER_SUPPRESSION system setting in the SmartTMS Admin Portal.                                            ⚠️ Important: Always confirm suppression requirements with the Client Relationship Manager (CRM) before making updates.

When to Use Carrier Suppression

Use carrier suppression when a client needs to:

    • Exclude specific carriers from rate results
    • Restrict carriers by lane, location, or shipment type
    • Apply routing guidelines or compliance rules

Access Requirements

    • SmartTMS Admin Portal access
    • Internal Admin permissions

Only Internal Admin Users can create, edit, or remove suppression rules.

Rule Format Overview

Carrier Suppression rules are entered as tilde (~) separated values in the system setting.

Supported Formats

1. Legacy (ZIP-Based – 7 Fields)

[CarrierSCAC]~[ClientLocation]~[MovementType]~[FromZip]~[ToZip]~[ShipToNamedLocation]~[ServiceType]

2. Extended (State + ZIP – 9 Fields)

[CarrierSCAC]~[ClientLocation]~[MovementType]~[FromZip]~[ToZip]~[FromState]~[ToState]~[ShipToNamedLocation]~[ServiceType]

✅ Both formats are supported
✅ Each rule must be on a new line

Field Definitions

CarrierSCAC

    • Carrier identifier (SCAC code)
    • Example:
    • SEFL~*~*~*~*~*~*

ClientLocation

    • Matches Company Name on SmartTMS user profile
    • Options:
      • Exact value (e.g., BAKER EL PASO 416)
      • Wildcard * = all locations
      • Multiple locations separated by |

    MovementType

      • Shipment type:
        • I = Inbound
        • O = Outbound
        • T = Third Party
        • * = All

      FromZip / ToZip

        • Origin and destination ZIP codes
        • Can be:
          • Specific ZIP (e.g., 90210)
          • Wildcard *

        FromState / ToState (Optional)

          • 2-letter state code (e.g., TX, CA)
          • Used for broader lane suppression
          • Wildcard * allowed

        ✅ ZIP-level rules override state-level rules

        ShipToNamedLocation (Optional)

          • Matches Vendor Address Book entry
          • Must match Company Name exactly
          • Wildcard * applies to all destinations

        ServiceType

          • Reserved field (typically * unless otherwise specified)

        Example Rules

        Suppress Carrier for All Shipments

        SEFL~*~*~*~*~*~*

        Suppress for Specific Client Location

        SAIA~BAKER EL PASO 416~*~*~*~*~*

        Suppress for Outbound Only

        SEFL~*~O~*~*~*~*

        State-to-State Suppression

        EXLA~*~O~*~*~TX~CA~*~*

        Setup Instructions

        Step 1: Access Admin Portal

          • Log into SmartTMS Admin Portal
          • Navigate to System Settings

        Step 2: Locate Setting

          • Go to Client Employee Account Settings
          • Filter by:
          • CARRIER_SUPPRESSION

        Step 3: Create or Copy Rule

          • Copy an existing entry (recommended)
          • Update:
            • Type
            • Account
            • User
            • Value (rule)

          Step 4: Add Rules

            • Enter rules in the Value field
            • Ensure:
              • Correct format (7 or 9 fields)
              • Each rule on a new line

            Step 5: Save

              • Click Copy to save the new configuration

            Validation & Testing

            After setup:

              • Run a rate shop using:
                • Shipment Wizard OR
                • My Quote
              • Confirm:
                • Suppressed carriers do not appear
              • Validate across applicable lanes and scenarios

                Rule Behavior & Prioritization

                Matching Priority Order

                  • Ship To Named Location
                  • ZIP-level (FromZip / ToZip)
                  • State-level (FromState / ToState)
                  • Wildcards *

                Conflict Handling

                If multiple rules conflict:

                  • Carrier will NOT be suppressed
                  • Internal alert is triggered (Slack/email)
                  • No user-facing error is shown

                Invalid Rules

                If formatting or logic errors occur:

                  • Notifications sent to Support
                  • Rule may not apply

                Best Practices

                  • ✅ Always confirm requirements with CRM
                  • ✅ Use specific rules before wildcards
                  • ✅ Test every rule after implementation
                  • ✅ Document rule intent in internal notes
                  • ❌ Avoid overlapping/conflicting rules

                Quick Reference

                Scenario

                Recommended Approach

                All shipments

                Use * wildcards

                Specific lanes

                Use ZIP or State fields

                Specific customers

                Use ClientLocation

                Precise targeting

                Use ShipToNamedLocation

                Need Help?

                If suppression is not working as expected:

                  • Verify rule format and spacing
                  • Clear the client’s cache on their dashboard
                  • Check for conflicting rules
                  • Confirm exact field match values
                  • Contact Support if alerts were triggered

                📎Related Articles:  How to Configure Carrier Suppression by Product?
                                                     How do I edit carrier suppression in Smart Audit?