Liftgate & Pallet Jack Accessorial Rating: Dynamic TMS Architecture

The Revenue Leakage Problem in Final-Mile Operations

Industry data consistently shows that 12-18% of final-mile shipments require liftgate, pallet jack, or additional labor that is either never captured or incorrectly rated. When these charges are omitted from the customer invoice, the carrier absorbs the cost. When they are added manually after the fact, disputes rise and days-sales-outstanding increase.

A properly architected TMS dynamic rating engine eliminates both problems by evaluating equipment requirements at the earliest possible point in the order-to-cash cycle and maintaining a single source of truth across quoting, dispatch, proof-of-delivery, and invoicing.

Core Architecture Components

The solution is built on five tightly integrated layers:

1. Consignee Attribute Repository - Normalized location intelligence stored independently of orders
2. Carrier Tariff Matrix - Version-controlled, rule-based accessorial tables for each carrier and lane
3. Dynamic Rating Engine - Real-time solver that combines shipment data, consignee flags, and carrier rules
4. Event-Driven Validation Layer - Dispatch and POD events that confirm or override system-generated accessorials
5. Audit & Revenue Assurance Dashboard - Exception reporting and carrier compliance scoring

High-Level System Diagram (Text Representation)

Order Entry ---> Consignee Lookup Service ---> Attribute Resolver
                          |
                          v
                Dynamic Rating Solver
                 /         |         \
Carrier Rate API  Tariff Matrix  Equipment Rule Engine
                 \         |         /
                          v
                Rated Line Items + Accessorials
                          |
                          v
                TMS Dispatch & Billing Integration

Data Model for Consignee Location Intelligence

Accurate accessorial rating begins with structured consignee attributes. The recommended schema includes the following core fields:

These attributes are maintained through a combination of customer master imports, driver feedback loops at POD, and periodic address validation against commercial databases.

Dynamic Multi-Carrier Rate Matrix Design

The heart of the system is a rule-based matrix that supports carrier-specific logic without hard-coding. Each carrier record contains a JSON-defined matrix with the following structure:

{
  "carrier_id": "C123",
  "effective_date": "2024-01-01",
  "expiration_date": "2025-12-31",
  "rules": [
    {
      "condition": "delivery_type == 'RESIDENTIAL' || !dock_available",
      "accessorials": [
        { "code": "LIFTGATE", "charge": 125.00, "per": "shipment" },
        { "code": "RES_DELIVERY", "charge": 45.00, "per": "shipment" }
      ]
    },
    {
      "condition": "pallet_jack_required == true",
      "accessorials": [
        { "code": "PALLET_JACK", "charge": 85.00, "per": "shipment" }
      ]
    },
    {
      "condition": "floor_level > 2 && !elevator_available",
      "accessorials": [
        { "code": "STAIR_CHARGE", "charge": 35.00, "per": "floor", "min": 70.00 }
      ]
    }
  ],
  "priority": 100
}

The solver iterates through applicable matrices in priority order, evaluates each condition using a safe expression engine, and aggregates the resulting accessorial line items. Normalization ensures that identical accessorial codes from different carriers are mapped to the customer's preferred billing code.

Real-Time Solver Implementation Patterns

Strong Tower Consulting recommends a microservice-based solver with the following characteristics:

• Stateless REST endpoint accepting shipment payload and returning rated accessorials in < 150ms
• Rule caching with Redis to avoid repeated database hits
• Versioned tariff matrices with effective and expiration dates
• Support for both deterministic rules and probabilistic models based on historical POD data
• Extensibility hooks for carrier-specific APIs (e.g., FedEx, UPS, regional LTL final-mile partners)

The solver is invoked at three critical workflow points:

1. Order Entry / Quoting - Preliminary rating using available consignee data
2. Dispatch Planning - Final pre-load rating with confirmed equipment requirements
3. Invoice Generation - Authoritative rating locked by POD evidence

Integration Workflows with TMS Platforms

The architecture has been successfully implemented with multiple enterprise TMS platforms. Integration patterns include:

Strong Tower Consulting and Exspeedite LLC are separately organized sister companies under common ownership (separate EINs; liability firewall). Neither is the parent or secondary of the other. Exspeedite is a Strong Tower company that frequently serves as the deployment platform for these dynamic rating architectures.

Implementation Roadmap

A typical engagement follows this phased approach:

1. Discovery & Gap Analysis (3-4 weeks) - Map current accessorial leakage, audit 90-day shipment sample, document carrier tariff variances.
2. Data Foundation (4-6 weeks) - Build and populate consignee attribute repository, cleanse address data, implement driver feedback workflow.
3. Rule Engine Build (6-8 weeks) - Develop dynamic solver microservice, import and normalize carrier matrices, create administrative UI for tariff maintenance.
4. TMS Integration & Testing (5-7 weeks) - Connect to order entry, dispatch, and billing modules. Parallel test against historical invoices.
5. Go-Live & Optimization (Ongoing) - Monitor exception dashboard, refine rules based on actual vs. system-generated charges, expand to additional final-mile partners.

Expected Business Outcomes

Organizations that complete this implementation typically realize:

• Reduction in unbilled accessorials of 85%+
• Decrease in accessorial disputes by 60-75%
• Improved carrier compliance scoring and faster payable processing
• More accurate customer quoting that reflects true cost-to-serve
• Audit-ready documentation for every accessorial charge

Technical Best Practices & Governance

To maintain long-term integrity of the dynamic rating system, enforce these governance rules:

• All tariff matrices must be versioned with immutable history
• Changes to consignee attributes require dual approval (operations + revenue management)
• Every solver decision must be logged with the full evaluation trace for audit
• Monthly reconciliation between system-rated and actual billed accessorials must remain below 3% variance
• Carrier tariff updates must be reviewed by pricing analysts before matrix import