Bulk RFP Rate Uploads for Carriers
Carriers can now manage large RFP bids more efficiently by exporting lane data into a CSV file, adding the rate data in the spreadsheet, and then uploading the rates back into the carrier’s RFP. Instead of only allowing manual entry for every lane in the Shipwell UI, you can now:
Download Lane Data: Export all RFP lanes to a spreadsheet with a single click. Any rates already entered in the UI will be included in the file.
Bulk Edit: Enter or update rates in your preferred spreadsheet tool.
Smart Validation: Upload the completed file back to Shipwell. The system now automatically validates data—including support for ZIP codes with leading zeros—and provides clear error messages if formatting needs correction.
Final Review: Review and edit your uploaded rates in the UI before final submission to the shipper.
To download, simply click on the Download Lane Data link, and the contents of the RFP will be contained in the CSV file. If they have already started entering some rate data, whatever has been entered so far will appear in the downloaded file.
The user can enter the rate data for the lanes as highlighted below. If they choose not to enter a rate on a particular lane, that is ok and the lane will appear without a rate once the file is uploaded. If the carrier does not wish to bid on a lane, they can submit the RFP back to the shipper leaving some lanes without a rate.
If the user has entered any invalid rate data, such as “ABC” in the rate column, the system will validate the data during the upload process and display an error message showing exactly where the bad data is in the file. This will allow the carrier to quickly correct any errors and make the download / upload process as efficient as possible. If errors occur, this stops the upload process and no data is changed in the carrier’s RFP. Only a successful upload will update the RFP data.
Once the file is successfully uploaded, the RFP screen will reflect the contents contained within the upload file. The user has the ability to make edits to the uploaded data prior to hitting the Submit button to transmit the rates back to the shipper.
Roadside Integration
Summary
Shipwell now integrates directly with Roadside (RoMa), so shipments moved on Roadside-tracked vehicles get live, automatic location tracking.
Once a company connects its Roadside account, its fleet vehicles flow into Shipwell automatically as power units. Assign one to a shipment and tracking starts on its own: location breadcrumbs appear
on the map and pickup/delivery stops and shipment status advance automatically as the truck moves.
Please contact your Customer Success Manager to enable this integration for your account.
Key Capabilities
Native, self-service connection, Roadside connection. Connect a Roadside account to Shipwell using your Roadside CUserid and Service Key, with connect/disconnect managed from the Integration Marketplace.
Automatic vehicle sync. Roadside fleet vehicles are imported as power units and kept in sync, an immediate sync on connect plus a nightly refresh, matched on Roadside VehicleID with no
duplicates. Each unit carries its name, VIN, odometer, and last-report time, and shows Active/Inactive based on recent data.Hands-off shipment tracking. Assigning a Roadside power unit to a shipment starts tracking automatically, polling location every 5 minutes and dropping breadcrumbs on the shipment map.
Geofence-driven status updates. When a Roadside truck enters or exits a stop's geofence (800m radius), Shipwell auto-completes the arrival/departure and advances shipment status using the same geofencing logic as other telematics providers.
How It Works
Any user can connect the company's Roadside account from the Integration Marketplace using the CUserid and Service Key.
Shipwell immediately pulls in the Roadside fleet as power units and keeps them current with a nightly sync.
Shipwell users can assign a Roadside power unit to a shipment in the equipment section, and tracking begins automatically.
Shipwell polls Roadside every 5 minutes, plots each location on the shipment map, and applies its existing geofence logic to auto-complete stops and advance shipment status as the vehicle arrives at and departs each location.
Note: The image above shows the following elements:
Blue line: this is the suggested route between stops. This may or may not be followed by the driver.
Small Yellow dots: These are the location pings received from Roadside and placed on the map to show where the vehicle has been
Black lines (between dots): These are the connecting lines between the location pings so that you can trace the route the driver actually took. This is a sample shipment, hence the deviation from the prescribed route (blue line).
Benefits
Less manual work. Vehicles appear automatically and shipments track themselves once a truck is assigned no manual equipment entry, location updates, or status changes.
Accurate, consistent visibility. Every Roadside shipment gets the same reliable, map-based location trail and automatic status progression as other shipments that use electronic logging devices.
Faster, cleaner status. Geofence-driven arrival/departure keeps stop and shipment status current without dispatcher intervention.
One less tool to watch. Roadside location lives inside Shipwell alongside the rest of the shipment.
Known Limitations
Location tracking only. The Roadside connection provides vehicle location for shipment tracking. It does not bring in driver Hours of Service or compliance logs.
Accurate tracking depends on stop addresses. Because arrival/departure is detected by geofence, stops need correct addresses/coordinates for status to update automatically.
Accessorial and Charge Code Updates
Summary
Shipwell has significantly expanded the built-in accessorial catalog so that charge codes which previously had no matching accessorial can now be selected directly on shipments. Before this release,
Accessorials vs. Charge Codes: What's the Difference?
These two terms are related but not the same, and understanding the distinction explains what changed in this release.
Charge codes are Shipwell's standardized library of billing codes — each has a short code, a standard name, and a category (for example, line haul, fuel surcharge, or accessorial). Charge codes are what appear on financials, invoices, contracts, and rate tables so that every charge is recorded consistently.
Accessorials are the accessorial-category charge codes that you can select as an add-on line item when adding charges to a shipment, template, or contract (for example, a liftgate fee, detention, or a redelivery charge).
In short: every accessorial is a charge code, but not every charge code was previously available to select as an accessorial. That gap is what this release addresses.
Where You Can Use It
The expanded accessorials are available anywhere you add accessorial charges:
Shipments — when adding or editing financial line items
Templates — so recurring charges are set up correctly by default
Contracts — for agreed-upon accessorial rates
Key Capabilities
Broader accessorial coverage. Accessorials were added for the charge codes that previously had none spanning operational services (detention, layover, limited-access pickup/delivery,
customs/border, trailer spotting, and more) as well as billing items (taxes, fuel, duty, and fees).New charge codes added. Several charge codes that didn't exist in the catalog were created so their accessorials could be added, closing gaps that previously forced a generic catch-all charge.
Correct dispatch behavior per charge. Operational accessorials can be dispatched/tendered to carriers, while billing-only items (taxes, fuel, fees) are flagged as non-dispatchable so they stay
on the financial record and aren't sent to carriers.Available everywhere accessorials are. The new accessorials are selectable in the same places as existing ones, the shipment Financials tab, stops, templates, and contract charge setup.
How It Works
The new accessorials are part of Shipwell's standard catalog, so there's nothing to enable. A user adds one the same way as any other accessorial; for example, on the shipment Financials tab via Add Line Item, choosing the Accessorials category and picking the specific charge and it flows through the platform to billing, and to carrier tendering when the charge is an operational (dispatchable) one.
Benefits
More accurate billing. Charges map to a specific, correctly-named accessorial instead of a generic "miscellaneous" line, reducing cleanup and reconciliation.
Less manual workaround. Teams no longer have to substitute an unrelated code when the exact charge wasn't in the catalog.
Right charges reach carriers. Operational accessorials tender correctly, while purely financial items stay off carrier documents.
Consistent, platform-wide. The coverage is part of the standard catalog, so every customer benefits with no setup.
Appointment Overrides
You can now allow specific users to override dock scheduling restrictions when booking or rescheduling an appointment. Two new user permissions control what can be overridden:
Override Dock & Load Type Rules: schedule an appointment on a dock even when the load does not match that dock's rules (for example a different product, mode, or equipment type than the dock normally accepts).
Override Facility Time & Capacity Constraints: schedule an appointment outside the facility's operating hours, inside the lead-time cutoff, or beyond the facility's capacity limits.
How It Works
A company administrator turns on either or both permissions for a user under Manage > Company > Users (highlighted below). When that user schedules an appointment the facility's rules would normally block, Shipwell shows a warning explaining the conflict, and the user can choose to proceed. Users without these permissions are blocked, exactly as before. Overrides apply to both new appointments and reschedules.
Benefits
Your facility rules keep running the calendar by default, and the exceptions you approve (a late truck, an emergency load, a one-off after-hours delivery) get handled by your own trusted users in seconds instead of waiting on support, manually adjusting facility hours, or being creative with dock rules.
API Changes
No Changes in This Release
Settlements API — version 0.3.47, no spec changes (PR #3014)
Orders API (corrogo) — version 0.8.28, no spec changes (PR #3430)
Dock Scheduling API (tempus) — version 0.4.30 in this release. Note:
point_of_contactsandcompany_namefields onGET /facilities/{facility_id}, plus Corrogo order schemas (CorrogoOrderItem,CorrogoOrderStop, etc.) are already live in prod (0.4.32) and will reach sandbox in the next release.
Analytics Model Updates
New fields in Report Builder Model:
SHIPMENT DETAILS
SHAREABLE EXTERNAL TRACKING LINK
LOGISTICS PROVIDER
USDOT
MC Number
SCAC
EXCLUDE FROM AUTOMATED CARRIER STATUS
FULL MAILING ADDRESS
Other Minor Enhancements and Bug Fixes
Description |
Resolved: Fuel Surcharge Calculation Error for Vortex LTL We fixed a calculation error where fuel surcharges for Vortex LTL shipments were being applied incorrectly. Surcharges will now calculate accurately based on the intended percentage of the line haul, ensuring correct financial records and invoicing. |
Improved: Batch Tendering Error Messaging We improved the error messaging when tendering multiple shipments at once. Previously, if a selected contract didn't apply to every shipment in a batch (e.g., due to weight limits), the system would show a generic failure. The system now provides clearer feedback so you can identify which shipments require contract adjustments. |
Resolved: ZIP Code Formatting in RFP Uploads We fixed an issue where RFP file uploads would fail if they contained ZIP codes starting with a zero. The system now correctly recognizes and retains leading zeros during the upload process, eliminating the need for manual file formatting. |
Resolved: Negative Totals on LTL Financial Records We resolved a bug where some booked LTL shipments were displaying negative totals in the Financials tab. This was caused by a missing markup line item during the booking process. Financial records will now accurately reflect the total rate approved during quoting. |
New: Lane ID Naming for Routing Guides You now have the option to name your routing guides based on Lane IDs during the RFP process. This enhancement allows for better organization and easier identification of specific lanes within your routing strategy. |
Improved: Rate Table Support for Pallet Spacing We have enhanced our rate table contract structure to account for pallet spacing and stackability. This allows for more precise LTL rating by considering how freight physically occupies space on a trailer. |
New: LTL Tender Control for Multiple Contracts We added a new control in the tender modal that allows the system to automatically return the highest rate contract when multiple valid contracts (such as CWT and Pallet-based) exist for the same carrier. |
Resolved: LTL Re-booking Blocks After Timeouts We fixed an issue that prevented users from re-booking LTL shipments if an initial dispatch attempt timed out. You can now successfully remove a carrier and re-dispatch the shipment without encountering persistent errors. |
Improved: Oak Harbor Transit Visibility We updated the Oak Harbor integration to ensure transit days are correctly included in rate results. This provides better visibility into estimated delivery timelines during the quoting process. |
New: Oak Harbor Guaranteed Service Quotes You can now view and book Guaranteed Standard and Guaranteed Hour-Specific service levels for Oak Harbor. These will appear as distinct quote options alongside standard rates when applicable. |
Resolved: Cloudtrucks Tracking Delays We fixed a synchronization issue where some shipments using Cloudtrucks were not updating to "Delivered" status automatically. Tracking updates will now flow through correctly to keep your shipment dashboard current. |
Resolved: Missing FedEx Proof of Delivery (POD) Documents We resolved a systematic issue that prevented FedEx Freight PODs from being automatically attached to delivered shipments. Digital PODs will now be correctly ingested and available in the shipment's document folder upon delivery. |
Resolved: R+L Carriers Tracking Status Updates We fixed an issue where R+L shipments booked via specific providers were not automatically transitioning to "In Transit." Status updates will now trigger automatically as the carrier moves the freight. |
Resolved: Estes Shipment Status Reverting from "Delivered" We fixed an issue where Estes shipments would occasionally revert from "Delivered" back to "At Delivery" due to out-of-order tracking updates. Shipments will now correctly maintain their final delivered status, ensuring accurate visibility and timely billing. |
Resolved: Delivery Status Sync for Road Runner and Forward Air We fixed an issue where shipments booked with Road Runner and Forward Air were not automatically updating to "Delivered" status. These shipments will now correctly advance to delivered upon completion by the carrier. |
Resolved: Missing Dayton Freight Documents We resolved an issue where POD and Invoice documents were not being automatically retrieved for Dayton Freight shipments. The system now correctly identifies these shipments to ensure all delivery documentation is attached automatically. |
Resolved: Cancellation Sync with Cloudtrucks We fixed a bug where cancelling a shipment in Shipwell would not always notify the integrated Cloudtrucks system. Cancellations now sync reliably across both platforms to prevent inadvertent dispatches. |
Resolved: Missing Purolator and Manitoulin Rates We fixed an issue where rates for Purolator and Manitoulin were missing from the UI for certain shipments. These carriers will now correctly display as selectable options during the quoting process. |
Resolved: Duplicate PRO Number Assignment We addressed a tracking issue where duplicate PRO numbers were causing invoices to attach to the wrong shipments. Status and document mapping have been improved to ensure billing accuracy for R+L Carriers. |
Resolved: Rating Errors for Canada Shipments We fixed a data mapping error that caused LTL rating to fail for shipments destined for Canada. The system now correctly identifies the destination country, ensuring accurate rate retrieval. |
Resolved: R+L Carriers Delivery Status Sync We fixed a tracking gap that prevented R+L Carriers shipments from automatically updating to "Delivered." This fix ensures that delivery events trigger the automated settlement and invoicing process as expected. |
Improved: Contract Stop Data Management You can now edit contract stop data even when a rate table exists for that contract. This provides greater flexibility in managing complex LTL contracts without needing to recreate the entire rate structure. |
Resolved: AAA Cooper Interline Visibility We fixed an issue where AAA Cooper rates were being incorrectly marked as "Direct" when they were actually "Interline" services. This ensures you have accurate visibility into the service type to better manage ETAs and potential delays. |
Resolved: ODFL Tracking Status Mismatch We resolved an issue where ODFL shipments would remain "In Transit" after delivery was completed. Status updates will now accurately reflect the final delivery, unblocking the invoicing process. |
Resolved: Prosoco Tracking Status Regressions We implemented a fix to prevent shipment statuses from "rolling back" to an earlier state if tracking updates are received out of order. This ensures that once a shipment is marked as delivered, it stays delivered. |
New: Estes Grocery Consolidation Accessorial We have added support for the "Grocery Consolidation Delivery" accessorial for Estes. This charge can now be correctly mapped and applied to your LTL shipments. |
Improved: Estes Service Level Descriptions We updated the Estes integration to display specific service level names (e.g., "Estes Retail Guarantee") instead of the generic "Service Level Adjustment." This provides better clarity on the exact service being booked. |
Resolved: Averitt Express Tracking Initialization We fixed an issue where Averitt shipments would not update to "In Transit" if the PRO number was added after the initial dispatch. The system now correctly triggers tracking as soon as the PRO number is populated. |
Resolved: Estes Direct Tracking Sync We resolved a tracking issue for Estes shipments tendered via direct connection. Shipments will now automatically transition to "Delivered" upon completion, eliminating the need for manual status overrides. |
Resolved: ABF Third-Party Billing Errors We fixed a dispatch error that occurred when booking ABF Freight shipments with third-party billing. The system now correctly transmits the required billing address details to the carrier, allowing for successful dispatch. |
Improved: Estes Pickup Request Details We updated the Estes integration to include shipment reference numbers (such as BOL and PO numbers) in the pickup request. This ensures the carrier has all necessary references at the time of pickup. |
Resolved: Numark Rating Errors for Long Company Names We fixed a rating failure with Numark that occurred when company names exceeded the carrier's character limit. The system now automatically handles long names to ensure successful rate retrieval. |
Swifty Legacy Appointment flow does not return confirmations in email |
Swifty Legacy Email Alias integration is not receiving inbound emails |
Implement New Roadside Integration |
Resolved: Carrier Visibility for All Customer Shipments. We fixed an issue where the "Access to All Customer Shipments" permission was not correctly displaying all relevant loads to carrier users. Carriers with this permission enabled can now reliably view and manage their full book of business for a customer. |
Improved: Shipment Date and Time Consistency. |
Improved Tracking Event Transparency. |
Reliability Improvements for Air Freight Tracking. |
Expanded Accessorial and Charge Code Catalog: We have added 88 new standard accessorials to the Shipwell platform, including specialized codes for international shipping, location-specific services (such as schools, farms, and malls), and various tax and fee types. These new codes are available globally for use in shipments, templates, and contracts, allowing for more precise billing and carrier instructions. |
Shipwell Mobile for iOS (v5.7.10) |
Improved: NetSuite invoice transmission reliability. |
Fixed: Facility creation now supports existing Address Book entries. |
Fixed a bug that prevented creating a dock scheduling facility from an address that already exists in the address book. This bug was due a removed requirement to the new facility override and overnight scheduling capability that conflicted with the address book to facility creation experience. |
Shipwell’s NetSuite integration is officially verified by NetSuite and ready for the NetSuite 2026.2 release & NetSuite Next |