We're excited to announce several key improvements to our Tive integration, designed to streamline device management and improve tracking accuracy for shipments using Tive devices.

Benefit: Easier shipment identification and improved user experience when working across both platforms.

We've updated the shipment information sent to Tive to use Shipwell's shorter, user-friendly shipment ID instead of the full UUID. This creates a consistent experience between Shipwell and Tive, making it significantly easier to identify and reference shipments when accessing the Tive Dashboard.

Before: Long UUID format displayed in Tive

​After: Short, readable shipment ID matching what you see in Shipwell

Benefit: More accurate and reliable ETA information for Tive-tracked shipments.

Shipments tracked with Tive devices now prioritize ETA updates directly from Tive. Now, when a Tive device is attached, the platform uses Tive's real-time tracking data as the primary source for shipment and stop ETAs, ensuring you have the most accurate arrival predictions based on actual device location and movement. These ETAs will be visible on the shipment stop level.

Benefit: Quickly correct device attachment errors without support intervention.

You can now disconnect a Tive device from a shipment before the shipment has started transit. This enhancement allows you to correct mistakes if the wrong device was attached, providing greater flexibility and reducing delays in your shipping workflow.

How to disconnect a device:

Benefit: Maintain visibility across complex shipping scenarios without location restrictions.

Tive devices can now be attached to shipments regardless of the device's physical location relative to the shipment origin. This enhancement is particularly valuable for multi-pick and multi-drop shipments where devices may be registered at different facilities. You can now fully leverage your Tive investment without operational constraints, ensuring complete visibility across your entire shipping network.

How to attach a Tive device without location restrictions:

Note: While location restrictions have been removed for operational flexibility, we recommend following your organization's best practices for device attachment timing to ensure optimal tracking accuracy.

Questions? Contact your Customer Success Manager or reach out to our Support team for assistance with these new features.

We're introducing granular permission controls for the Product Book, giving administrators greater flexibility to manage user access and ensure proper data governance across your organization.

Benefit: Control exactly who can view, create, edit, and delete products in your Product Book, ensuring data integrity and organizational compliance.

Administrators can now assign specific Product Book permissions to users through the Company Users section. This new permission structure follows the same familiar pattern used for other Shipwell modules like the Address Book, making it intuitive to configure access levels across your team.

Available Permission Levels:

Prerequisites: You must have administrative privileges to manage user permissions.

Step-by-step instructions:

Benefit: Users see only the actions they're authorized to perform, reducing confusion and preventing errors.

The Product Book interface dynamically adjusts based on assigned permissions:

Products Listing Page:

Product Detail/Form Page:

This intelligent interface design ensures users can focus on their authorized tasks without encountering access errors or confusion.

Benefit: Never accidentally lock users out of critical Product Book data.

When configuring permissions, if all Product Book permission checkboxes are unchecked and you save the changes, the system automatically defaults to "View" permission. This safeguard ensures every user maintains at least baseline visibility to the Product Book, preventing accidental complete loss of access.

How it works:

This feature is designed for:

Questions? Contact your Customer Success Manager or reach out to our Support team for assistance with configuring Product Book permissions.

We're pleased to announce improvements to our tracking map functionality that deliver enhanced visibility and more accurate tracking source attribution for your shipments.

Benefit: Greater tracking visibility and more detailed location history without compromising system performance.

We've increased the frequency of location data points displayed on the tracking map by reducing the distance threshold from 5km to 3km between tracking pings. This enhancement provides you with more location dots along your shipment routes, offering improved visibility into shipment movement and progress. Despite the increased data density, platform performance remains unaffected, ensuring you get richer tracking detail without any system slowdown.

What this means for you:

Before: Location updates every 5km
​After: Location updates every 3km - 67% more tracking detail

Benefit: Accurate identification of tracking data sources for better data quality and troubleshooting.

We've resolved an issue where shipments were displaying an "Unknown" tracking source in the location breadcrumbs. All tracking location breadcrumbs now correctly display the source of the location detail, providing clear visibility into your tracking data origins.

What was fixed:

Why this matters: Accurate source attribution is essential for:

Questions? Contact your Customer Success Manager or reach out to our Support team for assistance with tracking map features.

We're enhancing our MacroPoint integration with improved carrier change handling and visual schedule status alerts, providing you with more reliable tracking and at-a-glance shipment performance visibility.

Benefit: Maintain continuous tracking visibility when carriers change, ensuring you never lose sight of your shipments.

Shipwell now intelligently manages MacroPoint tracking when carriers are changed on a shipment before dispatch. The platform now automatically handles these transitions, canceling tracking with the original carrier and initiating new tracking with the replacement carrier.

How it works: When you reassign a carrier on a shipment with MacroPoint tracking enabled, Shipwell automatically:

What this means for you:

Benefit: Instantly identify shipment performance status with color-coded ETA indicators and detailed alert descriptions, enabling proactive exception management without leaving Shipwell.

MacroPoint schedule status alerts are now displayed as intuitive, color-coded pills directly on the Shipment Details page. Each stop's ETA now includes both a visual color indicator and descriptive alert text from MacroPoint, giving you immediate insight into schedule performance at a glance.

Color-Coded Status Indicators:

What you'll see: Each ETA pill displays:

Real-time updates: Schedule status updates automatically when MacroPoint detects changes to shipment performance.

Stop-level visibility:

Intelligent display logic:

Shipment coverage: Schedule status alerts apply to FTL and LTL shipments with MacroPoint tracking enabled.

Faster Decision-Making: Identify at-risk shipments immediately without switching between platforms or analyzing detailed tracking data.

Proactive Exception Management: Spot potential delays early and take corrective action before they impact your customers.

Improved Customer Communication: Provide accurate, timely updates to customers based on carrier-sourced schedule predictions.

Reduced Platform Switching: Access MacroPoint's schedule intelligence directly in Shipwell, streamlining your workflow.

Enhanced Operational Control: Monitor shipment performance across your entire network from a single dashboard view.

These enhancements are available to Shipwell customers with MacroPoint integration, with particular value for:

Questions? Contact your Customer Success Manager or reach out to our Support team for assistance with MacroPoint integration features.

New ‘Access to All Customer Shipments’ carrier contact permission has been created so that when selected then the user will have access to all the shipments that this carrier has been linked. Note that at least one carrier contact must have this ‘Access to all Customer Shipments’ user permission.

Previously only a contact that had a shipment tendered to them will have been able to access the shipment but that created a hardship for other carrier user contacts that may be filling in for that person.

This update does NOT impact any permissions a user can perform as respects shipments generally but rather simply impacts which shipments a carrier user is able to view. In the future, we will be adding a new enhancement wherein the carrier user will be able to update the appointment times for shipments even if they are not dock scheduling-linked appointments.

Groups is a newly fully rolled-out feature in Shipwell that applies to orders, shipments, and settlements. It serves as a flexible organizational tool to help companies segment and manage their transportation operations more efficiently. Examples of Groups include subcompanies, divisions, or locations, or combinations thereof.

Create, Update, and View Groups

You can view and manage your Groups via ‘Manage’ → ‘Company’ → ‘Group Management’ which will bring you to your Groups dashboard.
​

Add Groups onto Orders and Shipments

Groups can simply be added to orders and/or shipments when the order or shipment is created or updated. Note the Groups only applies to v3 orders, not v2 orders.

When orders are created into shipments, then the respective shipment created or updated will have the same Groups as respects its associated orders attached. Further, when orders are added or removed from shipments, then the respective shipment updated will have the same Groups as respects the updated orders on the shipment.

Add Groups onto Freight Invoices

Groups are automatically managed as respects freight invoices. Groups are added to the freight invoice based upon the Groups on the shipment that the freight invoice is associated at the time the freight invoice is created. Note similar to other aspects of freight invoice, we do not update the freight invoice’s Groups later if its linked shipment’s Groups are modified. The freight invoice record is meant to be a record based on the data at the time it was created.

'Groups' Availability Summary

Shipwell’s Track and Trace AI Worker is an autonomously operating AI worker that provides maximum visibility of shipments throughout Shipwell by taking on the research and carrier and driver monitoring and outreach that your team would normally need to do to ensure shipment tracking is occurring. This article covers an overview of the Track and Trace AI Worker.

Track and trace is a constant burden on transportation teams that oftentimes gets dropped due to other pressing logistics functions. With that said, dropping track and trace actions can lead to more shipment delays and result in negatively impacting your supply chain. Track and trace is an activity that doesn’t stop in that you always need to be monitoring shipments and missing or delayed tracking. Further, actions needing to be taken take transportation coordinators out of the flow of other actions taken. Therefore, track and trace activities oftentimes get delayed or missed.

Develop Track and Trace AI Worker from a starting goal to behave in a similar frequency and method as your team would act. Shipwell’s Track and Trace AI Worker is highly configurable so that you can setup the AI worker just as you would exactly want your team to monitor and follow up with drivers and carriers. This means only communicating on an exception basis and never missing a shipment that is not tracking and/or delayed.

There are many different issues that arise that result in less than perfect tracking. Shipwell’s Track and Trace AI Worker aims to tackle the most common issues we have witnessed with our customers and in turn get better end-to-end tracking.

The AI worker has the ability to communicate with the following tools:

Other communication options coming:

Before activating the Track and Trace AI Worker, we strongly recommend completing the following steps to ensure high response rates and carrier cooperation:

Subject: Action Required: New Automated Tracking Process for [Company Name]

Body:

Hello [Carrier Name] Team,

To improve shipment visibility and streamline our communication, [Company Name] is now utilizing Shipwell’s Track and Trace AI Worker.

What to Expect: If a tracking update is not received for an active load, you will receive an automated email from the AI Worker. These requests will arrive with the subject line: "Tracking Update Requested."

How to Respond: When you receive these emails, you can provide an update in two ways:

Visual Reference: Below is an example of what these requests look like. Please ensure your team is aware that these are authorized requests from [Company Name].

Thank you for your cooperation in helping us maintain accurate tracking data.

Best regards,

[Your Name/Company Name]

Yes, the AI worker has the ability to modify data when incorrect data that is causing tracking gaps. This is a configuration though and you can have the AI worker: 1) make updates when it finds them, 2) reach out and verify with one of your users prior to making the change, or 3) not make the change but still notify your users that a change should be made.

See below for an example of an email a user will receive when the tracking worker is seeking to change a BOL #:

The most common communication is a request for a tracking update by the Track and Trace AI Worker when it is observes a missed pickup or missed tracking update. A sample email is below on what the broker, carrier, or driver would receive.
​

Note that when the broker, carrier, or driver responds to this email then Shipwell will be updated with the information provided whether it is related to a pickup being made or a location tracking update just like any other tracking update that has been received via EDI, ELD, etc.

Yes, the AI worker is able to work 24/7/365. However, it is configurable to identify which hours you want it doing outreach communications. This is one of the items setup within the AI Studio configurations.

Yes, there is a full audit log of any outreach or changes that the AI worker takes. This audit log is within AI Studio under ‘Activity Log'.

Select the eye icon under actions and detailed information about the action taken is populated.

Note the Activity Log does not display monitoring and observations it takes that do not result in performing actions that do not result in either an outreach communication happening or an observed discrepancy in data. Be assured that we do capture all this data if we need to research this detailed monitoring and observation information, but we do not populate in the Activity Log as for most customers it would overwhelm the Log with non-actionable information.

Contact your Shipwell Customer Success Manager. If you are an existing Shipwell customer, Track and Trace AI worker is an add-on product. Further, the Track and Trace AI worker is in the process of being able to be delivered as a standalone option outside of the Shipwell TMS.

The AI worker utilizes generative AI along with other machine learning in deciphering requests and information sent to it. However, we have several guardrails in place to ensure high quality behavior from our AI workers. While it is possible that the AI worker incorrectly understands a request, it should be quite rare.

Shipwell Track and Trace AI worker leverages best-in-class AI models from Anthropic, OpenAI, and Google currently. This is a configurable option that you can select which AI model underlying that you want leveraged. Shipwell has opted out of its data being used by the modeling companies for modeling purposes. Learn more about each of the model providers and their privacy policies here:

Shipwell cares deeply about protecting our customers’ data. We have strong information security policies and practices to keep our customer’s information safe. We use trusted third parties. Where appropriate we disclose third parties we use, like Anthropic’s Claude, to let you, as a customer, make an informed decision. In the future, Shipwell plans on offering additional Generative AI models that a company can switch between based upon preference. See Shipwell’s Privacy Policy here.

Shipwell is rolling out a multi-day planning and appointment window for shipments. Previously the planning and appointment window for shipments had two limitations: 1) they were both tracked in the same data fields so that the planned date / times and the appointment date / times needed to be the same data elements unless a customers had dock scheduling add-on; and 2) they could only span the duration of a single calendar day.

Supporting multi-day planning and appointment windows provides additional flexibility when customers have more flexible planning and/or appointment dates. Further, having the ability to have separate planning date / times from appointment date / times allows for better configuration.

The process of this rolling out multi-day planning and appointment shipment windows to Shipwell customers will be done over the next two to three weeks. Post rolling out this multi-day planning window to customers we will be updating aspects of EDI, reporting, and other areas to support this enhanced multi-day planning and appointment window functionality.

API Connected Customer Awareness:

Currently the existing planned date/time data fields (legacy planning date/time) of a shipment are:

Now there is a new ‘planning_window’ object and a new ‘appointment_window’ object on shipments as follows:

As part of this effort to create these new ‘stops.planning_window’ object was to be backward compatible with the existing planned date/time data fields. We do this by converting data from the ‘stops.planning_window’ object into the existing planned date/time fields. We plan to keep doing this and maintaining these existing planned date/time data fields for at least 18 months, but we are deprecating and treating as legacy these old fields and any new implementations or upgrades should leverage the new ‘stops.planning_window’ object.

The conversion between the new ‘stops.planning_window’ object to the legacy planning date/time data is as follows:

See the following single day and multi day scenarios and how the conversion between the prior ‘stops.planned…’ data fields are populated based on the new ‘stops.planning_window’ fields.

Custom Stop Data is now available in Shipwell customer’s Address Book. This allows for customers to manage additional stop data elements that they want captured within orders and shipments.

Access Custom Stop Data via ‘Manage’ → ‘Company’ → ‘Custom Data’ and in the ‘Stop Fields’ card identifies the Custom Stop Data for an account.

All Address Book entries will then display these Custom Stop Data fields as available fields to manage stop data.

Once a Custom Stop Data field within an Address Book entry has been saved then it will automatically be added to orders and shipments within the user interface (not available yet but targeted in 26.01 release). Further, if custom stop data within an API POST or PUT call is made referencing an Address Book entry then the saved Custom Stop Data fields will populate the order created or updated as long as the API call does not provide data that contradicts this Custom Stop Data field (not available yet but targeted in 26.01 release).

The new shipment creation experience page has three main updates in this release. We are nearing completion of the new shipment creation experience wherein we will deprecate the old shipment creation page sometime in Q1 2026. We will provide notice two weeks in advance, and then we will move all users to the new shipment creation experience. However, we encourage for those companies that are leveraging the old shipment creation experience today that start encouraging their users to leverage the new shipment creation experience.

The carrier’s user interface for processing an RFP allows the user to enter their bids directly into the system without having to download the lane data and then upload bids back into the system. Clicking the RFP menu option will bring the user to the RFP dashboard. Here you will see a list of all RFPs, with active RFPs displaying the remaining bid time, as well as the number of lanes within the RFP.

Clicking on an RFP will bring you to the RFP details page. Displayed at the top of the screen you will see the bid time remaining and any attachments or instruction files sent to you by the shipper. Any data being requested of you by the shipper will appear in an editable box within the bid table. If the shipper provided the expected rate type this will be show in the table, however, if this was not provided you will be required to select either a Per Mile or Flat Rate rate type for each lane.

As you enter bid data into the table, the system automatically saves your information. This allows you to enter bid data, close down the page, and return to it later to resume completing the RFP.

Some bid related data relates to the entire RFP contract, such as additional stop charges or specific accessorial rates. If the shipper included this type of information in the RFP, the Edit Contract Rates link will be active on the screen. Click this link to open up the Edit Contract Rates modal window to enter the rate amounts. Since these charges apply to all the lanes included in the RFP, you will only need to enter them once using this modal. You will be prompted to enter rates in this area if requested in order to complete the RFP Submit process.

The filter icon located on the left side of the screen allows you to choose which columns to display in the table, and also lets you choose the order in which the columns appear. To change the column display order, click and hold the mouse on the 6 dots to the left of the column names, and then drag the column up or down to rearrange the display order in the table.
​

Once you have completed entering all the bid data for the RFP, click the Submit button at the bottom of the screen. This will initiate the process of sending all the bid information back to the shipper. After submitting your bids, you are still able to come back to the RFP details and make updates to any of the bid information. If any changes are made to the RFP, the Submit button will become available and you can submit your updated bid information to the shipper. You can do this as many times as necessary until the bidding window expires.

If you do not wish to enter a bid for a particular lane, you can leave the Rate column blank for that lane. All other bid data that was entered will be sent back to the shipper.

This release introduces enhancements to shipment tracking, credit limit management, custom field capabilities, shipper relationship financial tracking, and query filtering. The update also includes streamlined schemas and is fully backward compatible.

Summary:

Added comprehensive next_stop metadata to shipment responses, providing enhanced visibility into upcoming stops and their details.

What's New:

Enhanced Endpoints (27 changes):

Shipments:

Shipment Pickups:

Quoting - Spot Negotiations:

Carriers:

Purchase Orders:

Benefits:

Added support for credit currency and outstanding balance tracking in shipper relationships, enabling better financial management and credit monitoring.

What's New:

Enhanced Endpoints (12 changes):

Benefits:

Added support for credit limit overrides on shipment relationships and carrier assignments, enabling per-shipment credit management that overrides default relationship limits.

What's New:

Enhanced Endpoints (77 changes):

Shipments:

Carrier Assignments:

Shipment Pickups:

Quoting - Spot Negotiations:

Carriers:

Purchase Orders:

Benefits:

Added support for additional field types in custom fields, enabling richer data capture and validation.

What's New:

Enhanced Endpoints (24 changes):

Benefits:

Expanded query parameter support for location-based filters to accept both single values and arrays, enabling more flexible and powerful search capabilities.

What's Enhanced: Query parameters now accept both string and array types for:

Enhanced Endpoints (16 changes):

Benefits:

Removed deprecated schemas that are no longer used:

Creating a shipper relationship with credit tracking:

POST /brokerages/{brokerageId}/shipper-relationships/ { "shipper_id": "shipper_123", "credit_currency": "USD", "outstanding_balance": 5000.00, "credit_limit": 50000.00 }

Response:

{ "id": "relationship_456", "shipper_id": "shipper_123", "credit_currency": "USD", "outstanding_balance": 5000.00, "credit_limit": 50000.00, "created_at": "2025-01-07T12:00:00Z" }

Shipment response with next stop information:

GET /shipments/{shipmentId}/ { "id": "shipment_789", "status": "in_transit", "metadata": { "next_stop": { "stop_id": "stop_123", "appointment_status": "confirmed", "location": "Chicago, IL", "scheduled_date": "2025-01-10" }, ... }, "stops": [...] }

Awarding a quote with credit limit override:

POST /shipments/{shipmentId}/award-quote/ { "quote_id": "quote_456", "credit_limit_override": 75000.00 }

Creating a carrier assignment with credit limit override:

POST /shipments/{shipmentId}/carrier-assignments/ { "carrier_id": "carrier_789", "credit_limit_override": 100000.00, "assignment_type": "primary" }

Response includes the override in relationship data:

{ "id": "assignment_123", "carrier_id": "carrier_789", "credit_limit_override": 100000.00, "shipment": { "id": "shipment_789", "relationship_to_vendor": { "credit_limit_override": 100000.00, ... } } }

Creating custom fields with new types:

POST /companies/{companyId}/custom-fields/ { "name": "Delivery Date", "field_type": "DATE", "entity_type": "shipment" }

POST /companies/{companyId}/custom-fields/ { "name": "Weight", "field_type": "FLOAT", "entity_type": "order" }

POST /companies/{companyId}/custom-fields/ { "name": "Package Count", "field_type": "INTEGER", "entity_type": "shipment" }

POST /companies/{companyId}/custom-fields/ { "name": "Pickup Time", "field_type": "TIME", "entity_type": "stop" }

Single value (existing functionality):

GET /shipments/?pickup_stops__contains=Chicago

Multiple values (new functionality):

GET /shipments/?pickup_stops__contains=Chicago&pickup_stops__contains=Detroit&pickup_stops__contains=Milwaukee

Or using array notation:

GET /shipments/?pickup_stops__contains[]=Chicago&pickup_stops__contains[]=Detroit

All changes in this release are backward compatible and optional to adopt.

If you manage credit terms and balances for shippers:

If you manage credit limits for shipments and carriers:

✅ Fully Backward Compatible: This release contains no breaking changes. All existing integrations will continue to work without modification.

New Optional Features:

Potential Client Impact:

Testing Recommendations: