Skip to main content
Charge Codes
S
Written by Shipwell TMS Support
Updated over 4 months ago

Charge Codes and Standardized Reference Data

We're excited to announce a significant update to Shipwell's charge codes and reference data, designed to empower you with greater efficiency, consistency, and flexibility in managing your transportation costs across new modes like ocean, drayage, and air freight but enhance existing modes such as Intermodal, Rail, LTL, FTL, and Parcel.

Introducing a Robust Charge Code Standard

Shipwell is now introducing a comprehensive version of the charge code standard which will be updated quarterly. The current version of the standard is v3 and it was created in 2024Q1. This enhanced standard offers several key benefits:

  • Standardized API Integrations: Seamless integration with carrier and third-party integrations ensures effortless data exchange and simplifies your workflows.

  • Expanded Reference Data: The new standard provides a wider range of pre-defined charge codes, encompassing commonly encountered fees like stop-off charges (SOC), cleaning charges (CLN), and vehicle ordered but not used (VOR, with alias TONU for "Truck Ordered, Not Used"). This eliminates the need for manual code creation and ensures consistency across your shipments.

  • Flexibility for Future Growth: The standard is designed to be adaptable, allowing us to incorporate new charge codes as the transportation landscape evolves. This ensures you'll always have the tools you need to accurately reflect your shipping costs and match to third parties in integrations, invoicing, and analytics.

Accessing the New Charge Code Standard

The charge code standard is available at {{baseUrl}}/reference-data/charge-codes/. This easy-to-access location empowers you to explore the available codes, understand their meanings, and incorporate them into your shipping processes. The endpoint has standard searching, filtering, pagination and performance consistent with Shipwell's v3 API standard. The response below shows an example response

{
"data": [
{
"id": "STOPOFFS_FOR_PRIVATELY_OWNED_VEHICLE_SHIPMENT_CHARGE",
"name": "Stop-offs for Privately Owned Vehicle Shipment Charge",
"code": "PVS",
"category": "Accessorials",
"aliases": []
},
{
"id": "STOPCHARGE",
"name": "Stopcharge",
"code": "SAM",
"category": "Accessorials",
"aliases": []
},
{
"id": "STOPOFF_CHARGE",
"name": "Stop-off Charge",
"code": "SOC",
"category": "Accessorials",
"aliases": []
}
],
"count": 3,
"total_count": 9,
"links": {
"next": "https://dev-api.shipwell.com/reference-data/charge-codes/?limit=3&page=2&q=stop",
"prev": null,
"first": "https://dev-api.shipwell.com/reference-data/charge-codes/?limit=3&q=stop",
"last": "https://dev-api.shipwell.com/reference-data/charge-codes/?limit=3&page=3&q=stop"
}
}

Mapping to/from EDI/API Connected Carriers

Shipwell's charge code standard will be used to map charge line items from carriers connected via EDI, API, and via Shipwell's portal. Additionally, any new carrier EDI or API connection will use this standard. The following diagram provides an example of an accessorial received by an API-connected carrier that maps to Shipwell's standard and provides consistent invoicing and settlement. You can see an accessorial called Airport Delivery flow from rating, to financials, and finally through the settlement process.

Analytics Changes

Analytics reports such as accessorials, costing, and additional chargeline item derived reporting will have expanded granularity and filtering.

New Financials Experience

If the new charge code capability is enabled you will now see the following capabilities enabled. First the financial interface for carrier, customer, and invoice allows you to select from the charge codes that are defined in the charge code standard which is versioned by date. Any API, EDI or carrier portal access will automatically be mapped to this standard. We’ve now added a “CHARGE ITEM” column which has the format Charge Code - Charge Code Description (Charge Code Category). The description field will automatically default to the Charge Code Description but you can overwrite or change this field.

In the edit modal, you will see the ability to add a new line item. When a new line item is first added, you have the ability to see the various categories and the associated charge code under each category:

Simply clicking the item will add that line item to the shipment. In this instance I am searching for all the codes that contain the string or code “det”. You will see a box that shows the search results

In this case I am adding DTB or Detention associated with labor. You can search by code, description, or category.

You will see this line item added to the modal.

Aliases

Many times businesses use the same charge code from the standard but might name or describe it as something different. For example, a common charge is a Truck Order But Not Used (TONU). You can search for TONU but this code will be aliased to the actual standard code which is (VOR) or Vehicle Ordered But Not Used. The description will be set to “Truck Order But Not Used” but the charge code will be set to “VOR.” When a carrier sends an invoice or edi for a TONU. This will also be normalized to VOR allowing for proper first pass match. We can add multiple aliases to a specific code which will allows additional flexibility.

Simplifying Your Shipping Management

By leveraging Shipwell's enhanced charge codes and standardized reference data, you can expect to:

  • Reduce Time Spent on Manual Coding: With a wider selection of pre-defined codes, you'll spend less time creating custom entries, streamlining your workflows.

  • Improve Cost Accuracy: Consistent and standardized charge codes ensure your shipping costs are accurately reflected, leading to better budgeting and financial control. Carriers will be instructed that these charge codes are part of the Shipwell standard and EDI, API, and carrier integrations will map to these standard codes.

  • Enhance Communication and Collaboration: Standardized codes facilitate clear communication with carriers, partners, and internal teams regarding transportation charges.

Did this answer your question?