New Feature: Multi-Day Planning Windows
Shippers can now plan pickups and deliveries across a range of days instead of a single date. This provides the flexibility needed for loads that don't have a strict time or can be serviced over a broader window. For example, you can set a pickup window from Monday at 08:00 to Wednesday at 17:00.
Multi-day windows are visible across the Shipwell platform, including the dashboard, shipment documents (BOL and rate confirmation), spot negotiation invitations, and the load board.
Key Benefits:
Increased Flexibility: Communicate a range of acceptable dates to carriers.
Platform-Wide Visibility: Multi-day windows are visible on the dashboard, shipment documents (BOL and Rate Confirmation), spot negotiations, and the load board.
How it Works with Appointments:
It is important to distinguish between a Planning Window (the range of time a stop can happen) and an Appointment (the specific time confirmed with a facility).
Independent Updates: Changing a planning window does not automatically change a confirmed appointment, and vice versa. Additionally, the appointment window does not have to fall within the planning window range.
Dock Scheduling: If a planning window moves so it no longer covers a scheduled dock appointment, that appointment is cancelled, unless someone from your company booked it.
Where you set it
The planning window fields replace the single date and time fields, each stop's planned date and time fields become a planned window start and a planned window end. Each takes a date and a time.
Create Shipment: Available on both the new and classic forms.
New form:
Classic form:
New Quote: The window carries through when you book. When booking with a connected carrier, a multi-day delivery window moves to the carrier's estimated delivery day.
Shipment Details and Edit.
Clone As A Shipment: The classic form copies windows as-is. The new shipment builder moves the itinerary so the first stop starts today, keeping each stop's day offset and times.
Orders: Shipments created from orders keep the order's window.
Workflow Impacts:
Dashboard: The Pickup and Delivery columns now display the full date range. Sorting by Pickup uses the opening day, while sorting by Delivery uses the closing day.
Tracking & Alerts:
When the carrier has given an ETA, on time is measured against that ETA. Otherwise, a stop is on time if the carrier arrives by the end of the planning window. For LTL, only the date is compared.
Detention: Detention tracking begins at the driver's arrival or the start of the planning window, whichever occurs later.
Integration & API Notes:
EDI: Outbound tenders (204) send the appointment when available (G62 77/78). Otherwise, they send the full planning window as earliest/latest dates (G62 37/38 for pickup, 53/54 for delivery). Inbound EDI doesn't support multi-day windows yet. Scheduled dates come in as a single-day plan, as today.
Shipwell API:
Existing Fields: Uses the existing
planning_windowfield (start/end) next to legacy fields.New Capability: Once enabled, you can write to
planning_windowviaPOSTandPUT.Legacy Sync: Single-date fields are filled from the planning window (first stop gets opening day; later stops get closing day).
Conflict Resolution: If both are sent and differ from stored values, the planning window wins.
Good to know:
A window that starts and ends on the same day works the same as a single date did before.
Parcel Shipments: These continue to use single-date scheduling.
Mobile App: The mobile app shows multi-day windows. On Android, you can edit the full window from a Late Pickup alert.
Products: A Redesigned Way to Manage Your Products
Overview
We've rebuilt the Products area in Shipwell to make your product catalog faster to build and easier to keep accurate. Adding, viewing and editing a product now happen in one organized form, with a live summary that shows exactly what you're saving. Product images are easier to add and look sharper, product categories stay tidy, and you can now see and sort by when each product was created and last updated.
Highlights
One organized product form with four clear sections: Basics, Size & Weight, Classification and Handling.
A live Summary panel that updates as you type.
Drag-and-drop product images with in-place cropping and higher-resolution uploads.
Smarter Product Category matching that helps prevent duplicate categories.
A Temperature Unit choice (°F or °C) for each temperature-controlled product.
New Created and Updated columns on the Products list, sortable in both directions.
What's New
One organized product form
Adding a new product, viewing an existing one and editing it all use the same form, so every field is in the same place every time. Fields are grouped into four sections:
Section | What it contains |
Basics | Reference, Description, Product Category, Piece Type, Value Per Piece, and any custom fields your company has set up for products |
Size & Weight | Package Type, Stackable, Length × Width × Height with Length Unit on a single line, Weight and Weight Unit |
Classification | Freight Class, NMFC Code, NMFC Sub Code and Country of Manufacture |
Handling | Hazmat details and emergency contact information; Temperature Controlled with Min Temp, Max Temp and Temperature Unit |
Fields sit side by side when there's room and stack neatly on smaller screens.
Live product summary
A Summary panel beside the form shows the product as you build it, so you can check your work before saving:
The product image and reference.
Requirement tags at a glance: Hazmat (with identification number and hazard class), the temperature range, and Stackable.
Key details: Package Type, Dimensions, Weight, Freight Class, NMFC and Value Per Piece.
For saved products, when the product was Created and last Updated.
Easier, sharper product images
Drag and drop: Drop a JPG or PNG anywhere on the product page to add it, or use Browse to choose a file.
Crop and zoom in place: Adjust the image right inside the Summary panel. No pop-up window.
Higher resolution: Images are now saved at up to 1200 pixels wide, up from 255 pixels, so they look crisp wherever they appear.
Safe by default: If you drop a file that isn't a JPG or PNG, Shipwell tells you and keeps the product's current image.
Smarter product categories
When you type a Product Category, Shipwell helps keep your category list clean:
Exact matches are reused. Typing an existing category, even with different capitalization, uses that category instead of creating a duplicate.
"Did you mean…?" If what you type is close to an existing category, Shipwell suggests it so you can use it with one click.
New categories when you need them. If nothing matches, you can create the category you typed.
Temperature-controlled products
Refrigeration Required is now called Temperature Controlled for consistency across the platform. The api field still keeps its original label.
Choose a Temperature Unit (°F or °C) for each product. It defaults to your unit preference.
The Summary panel shows the range at a glance, for example 34 to 40 °F.
Created and Updated dates
The Products list has two new columns: Created and Updated.
Click either column header to sort oldest first, and click again to sort newest first. This makes it easy to find recently added or recently changed products.
Dates appear in your date and time format, in your time zone.
The list still opens sorted by Reference, and your sort is kept as you page through results.
Sorting by Piece Type now works as expected as well.
Works better on smaller screens
The Products list header now wraps on narrow screens, so search, the page title and actions stay usable on phones and tablets. The product form adapts to the available width too.
Consistent Temperature Labels Across Shipwell
To match the new product form, temperature fields now read Min Temp, Max Temp and Temperature Controlled on shipments, shipment line items, orders, purchase orders, quotes and the load board summary. Only the labels changed. Your data and workflows are unaffected.
How to Get Started
Go to Manage › Products.
To add a product, click Add Product on the Products list, or choose + › Product.
To view or edit a product, click its Reference in the list.
Good to Know
No action needed. Your existing products, images and categories carry over unchanged.
Import is still available. Use Import on the Products list to add products in bulk.
Permissions are unchanged. Users without permission to edit products see product details as read-only, and deleting a product still requires delete permission.
Supported image formats: JPG and PNG.
Request Fuel Surcharge For Spot Bids
Shippers can request carriers to enter a fuel surcharge amount as well as a linehaul amount when sending out spot bid requests to carriers. From the Request Bid modal, the user can select the Require Fuel Surcharge amount in the bid option. Checking this box will allow carriers to enter a fuel surcharge amount when responding to the bid request.
When the carrier enters their bid amount in the Place a Bid modal, they will see the Linehaul Bid Amount as well as the Fuel Surcharge Amount fields. Both of these fields must be entered in order to submit the carrier bid.
Once the bid has been submitted, the shipper will see the total amount of the Linehaul and the Fuel Surcharge amount total on the shipment’s Bid tab.
Once the bid is accepted by the shipper, the shipment financials tab will break out the Linehaul charge and the Fuel Surcharge charge as separate financial line items.
API Changes
Overview
This release adds multi-day planning window context to stop responses, new fuel surcharge options for spot bidding, NetSuite bill details on bills, and several shipping dashboard and carrier relationship improvements. No endpoints or fields were removed.
Versions: Core API 2.7.731 → 2.7.742 · Orders API 0.8.29 (no changes) · Settlements API 0.3.49 (no changes) · Tempus (Dock Scheduling) API 0.4.47 (no changes) · Genesis (Carrier Connections) API 1.0.6 (no changes)
API Changes
Area | Change | Impact |
Stops | New read-only response fields | Action required |
Shipping dashboard |
| Action required |
Stop consolidation |
| Action required |
Stops | Multi-day | New capability |
Bills | New read-only | New capability |
Spot bidding | Fuel surcharge requirement on spot negotiations and load board shipments | New capability |
Shipping dashboard |
| New capability |
Carrier relationships |
| New capability |
Action Required
New fields on stop responses.
What changed: Stop, SlimStop and ShippingDashboardStop now return
appointment_window_type(AT,OPEN,BEFORE,AFTER),effective_window(start, end, type, display_text, source),effective_deadline(at, source, type) andrunning_late(statusSUCCESS/WARNING/ALERT, delay_hours).effective_window.sourceandeffective_deadline.sourceareAPPOINTMENT,PLANNING_WINDOWorPLANNED_DATE.What to check: Clients that validate responses strictly against the schema should accept these new properties.
running_lateisnullwhen the stop has no tracking ETA.driveradded tocolumnNames.What changed: The shipping dashboard column list accepts and returns a new
drivervalue.What to check: Clients with a closed enum for column names should add
driver.Stop consolidation plan request.
What changed:
order_idsis no longer required. Send exactly one oforder_ids(orders are fetched from the order service) ororders(used as sent). Eachordersitem needsid,ship_fromandship_to.What to check: Existing requests with
order_idscontinue to work. Generated clients that treatedorder_idsas always present should be updated.Endpoint:
POST /shipments/stop-consolidation-plan/
What's New
Multi-day planning windows
Item | Description |
| When the stop is planned to happen. The window can span several days. It replaces |
Enablement | Multi-day planning windows are enabled company by company and are disabled by default. While disabled, keep sending the legacy fields with every write, as they remain the source of truth for scheduling and rating. When enabled, the window and legacy fields are derived from each other (if both change, the window wins). |
| Read-only fields (see Action Required) that resolve the appointment window, planning window or planned date into one window and deadline, and report how far the tracking ETA runs past it. |
See the StopPlanningWindow schema description in the spec for full write, sync and validation rules.
Bills
Field | Description |
| The user who created the bill, or who approved or sent the freight invoice of an automated bill. Null when invoice matching created it or a company API key was used. |
| The bill's NetSuite bill, null until it has one. Includes |
Spot bidding fuel surcharge
Schema | Field | Description |
BulkCreateSpotNegotiationRequest |
| Require bids to carry both a line haul amount and a fuel surcharge amount greater than 0. Default false. Only allowed when the spot bid fuel surcharge feature is enabled for the request. |
LoadBoardShipment |
| Whether bids on this load take a separate fuel surcharge amount. Read-only. |
LoadBoardShipment |
| Whether bids must carry both amounts. False while the shipper's feature is disabled. Read-only. |
Shipping dashboard
Item | Description |
| Driver on the shipment's current equipment config. Sort with |
| Return shipments whose current driver is any of the given driver ids (repeat the parameter). |
| Sort by first pickup stop or last delivery stop, by city, then state/province, postal code and country. Rows with no location sort last. |
Carrier relationships
Endpoint | Change |
| New |
Other Minor Enhancements and Bug Fixes
Description |
Fixed an issue where freight invoices for shipments without a PRO number were occasionally failing to export to external accounting systems. These invoices will now export correctly with a blank PRO field, ensuring your financial records remain synchronized. |
Fixed an issue where carrier contact details (name, email, and phone number) were not automatically appearing on shipments after a carrier was assigned. The platform now correctly pulls this information from your saved carrier relationships, ensuring your team has immediate access to contact info for dispatch and tracking. |
Fixed an issue where "Ready At" and "Closes At" times were not updating correctly when selecting or changing a location from the Address Book. The shipment form now accurately reflects the operating hours configured for your saved facilities. |
Fixed a critical issue that prevented users from saving manual rates in the Customer Financials section. Shippers can now successfully enter negotiated rates and proceed with booking shipments as expected. |
Resolved a technical error that prevented new loads from being saved or dispatched when using the "New Load" form. Users can now select service levels and save drafts without interruption. |
Resolved: Reference Numbers Persist After Carrier Removal Fixed an issue where Pickup and PRO numbers were being cleared when a carrier was removed or a tender revoked. These reference numbers now remain on the shipment, ensuring you don't lose critical tracking or asset identifiers during the re-tendering process. |
Automated FMCSA Carrier Data Updates We have restored the automated synchronization of carrier safety and census data from the FMCSA. This ensures that carrier profiles, safety scores, and operating authorities are kept up-to-date automatically, reducing manual data entry and improving compliance monitoring. |
Accurate Delivery Reporting for Estes Drop-Trailers Fixed a tracking issue where administrative trailer-closure events from Estes were overwriting the actual physical delivery date. This ensures your on-time performance metrics and tracking history accurately reflect when the freight was actually delivered. |
Corrected Fuel Surcharge Calculations Resolved a calculation error that caused customer-side fuel surcharges to display incorrect, inflated values on certain contract shipments. Fuel surcharges now calculate accurately based on your negotiated contract rates and shipment mileage. |
Breakthrough Fuel Support for Default Carrier Rates You can now assign Breakthrough Fuel (BTF) surcharge tables as a default for carriers in their profile. When these carriers are assigned to a shipment, the platform will automatically retrieve and apply the correct BTF surcharge once the shipment is in transit. |
Improved SAIA Volume LTL Quoting Fixed an issue that prevented SAIA from returning Volume LTL rates when linear footage was not explicitly provided. The platform now better handles these requests to ensure you receive valid volume quotes during the quoting process. |
Restored Daylight Transport Tracking Resolved an authentication issue that prevented automated tracking updates for shipments moving with Daylight Transport. Tracking milestones and transit statuses will now flow into Shipwell automatically as expected. |
Resolved Booking Errors for Priority1/Mainfreight Fixed a "redispatch blocked" error that occurred when selecting certain rates from Priority1. The system now correctly validates carrier configurations before booking to ensure a smooth tendering process without duplicate booking errors. |
Automated Status Updates for XPO Direct Fixed an issue where shipments tendered to XPO Direct were not automatically transitioning to "In Transit" status upon pickup. These shipments will now update their status automatically based on carrier tracking events. |
C.H. Robinson Volume LTL Support We have enabled Volume LTL (VLTL) support for C.H. Robinson. Shippers can now receive volume quotes alongside standard LTL rates, view quote expiration dates, and ensure the carrier's Volume Quote ID (VQID) is automatically captured and printed on the BOL. |
Resolved Tracking and PRO# Issues for Ward Transport Fixed an issue where Ward Transport shipments were failing to return automated tracking updates and PRO numbers. Tracking is now fully operational, ensuring visibility into shipment milestones. |
Fixed Zone-Based Contract Matching Resolved an issue where contracts configured with specific geographic zones were not appearing as options during the tendering process. Zone-based contracts will now correctly match against shipment origins and destinations. |
Increased Precision for Fuel Surcharge Tables Updated Fuel Surcharge (FSC) tables to support higher levels of decimal precision (up to four places). This allows for more accurate rating when using specific incremental rate models required by certain shippers. |
Improved Contract Selection in Routing Guides Fixed a bug in the Routing Guide setup that prevented valid contracts from being suggested or selected. Shippers can now easily link their negotiated contracts to automated routing rules. |
Flatbed Support for Internal Fleet Contracts Fixed an issue where internal fleet contracts were not appearing as options for shipments set to Flatbed mode. These contracts are now correctly available for selection across all Flatbed tendering workflows. |
Accurate Financials on Rate Confirmations Resolved a timing issue where Rate Confirmation documents were occasionally generated without financial details when using the "Load from Contract" feature. Financial breakdowns will now consistently appear on the generated documents. |
Resolved Shipment Archiving Errors Fixed a technical error that prevented users from archiving shipments if the associated Fuel Surcharge table had been deleted. You can now archive historical shipments without interruption. |
Automated PRO# Capture for R&L and XPO Fixed an issue where PRO numbers assigned by drivers at the time of pickup were not being automatically pulled into Shipwell for R&L Carriers and XPO shipments. These numbers will now populate automatically from carrier tracking updates. |
Separate Linehaul and Fuel for Spot Bids Shippers can now require carriers to provide a separate breakout for Linehaul and Fuel Surcharge amounts when submitting spot bids. This provides better financial visibility and simplifies reporting by automatically creating separate line items upon bid acceptance. |
Improved FedEx Dispatch for Multiple Origins Resolved a dispatch issue where FedEx Freight pickups from different physical locations on the same day were being incorrectly merged into a single request. The system now ensures unique pickup confirmations for each distinct origin address. |
Resolved SAIA Dispatch Errors Fixed a dispatch error with SAIA where certain city/state combinations were not being recognized. This ensures successful electronic tendering for shipments to these locations. |
Fixed Hazmat Validation for SAIA eBOLs Resolved an issue where SAIA electronic Bills of Lading (eBOLs) were failing when Hazmat was selected but detailed info was missing. The system now provides clearer validation to ensure all required Hazmat data is included for a successful dispatch. |
Resolved: Shipment Sync Reliability We fixed a synchronization issue where certain automated shipment updates were not being sent to external integrated systems. |
Resolved: Swifty Email Tracking Accuracy We resolved an issue where Swifty incorrectly categorized shipment tracking requests sent via email. |
Improved: Automated LTL Invoice Recognition We improved the Swifty Document pipeline to better recognize invoice numbers on LTL freight bills. Previously, certain carrier layouts caused invoice numbers to appear blank in the Financials tab. |
Resolved: Accurate Credit Tracking in AI Studio We fixed a discrepancy where the AI Studio Analytics page was reporting incorrect credit usage for document processing. |
Resolved: Document AI Upload Stability We resolved a technical error that was preventing some documents from being successfully uploaded to Document AI. |
Improved: Consistent Credit Consumption for Document AI We updated the Document AI billing logic to ensure that all document uploads—whether via API, manual upload, or AI Worker—are consistently accounted for in your credit balance. |
New: Shipwell Certified Track & Trace Worker We introduced a new automated worker that monitors shipments from pickup through delivery. It proactively identifies missing tracking data, contacts carriers for updates, and escalates potential delays, ensuring full visibility without manual check calls. |
New: Default Configuration for Document AI Uploads Users can now set a default schema configuration for manual document uploads. This eliminates the need to select a configuration from a list every time you upload, streamlining the document ingestion process. |
New: Automatic Credit Top-Up via Invoice Customers can now choose to pay for automatic credit top-ups via invoice instead of a saved credit card. This provides more flexibility for organizations with traditional procurement and payment workflows. |
Accurate Handling Units on Multi-Pallet Orders: Each handling unit on an order keeps its own weight and dimensions, instead of copying the first pallet's values. |
Stop Dates Stay as Entered on Orders: Changing one stop's date on an order no longer moves the other stops' dates, so delivery dates change only when you change them. |
Accurate Stop Sequence Warnings: A bug was causing stop sequence warnings to fire when the stops were already in the right order. Stop numbers are now read as they are shown on the shipment, instead of an underlying stop identifier, so the warning appears only when stops really are out of order. |
Appointment Checkpoint Webhooks: In Dock Scheduling, an appointment's dock in, dock out, start loading and end loading each send their own webhook event, so your systems hear about each step as it happens. Check in and check out can now be subscribed to as well. |
Appointment Permissions Cleanup: A permissions gap was found, with no sign that anyone had used it, and has been closed. Only users of the facility's own company can record dock and loading times or check a truck in and out. |
NetSuite Shipment Financials Stay Current: NetSuite keeps only the current charges on each shipment, and shipment status now arrives as its own field. |
Expanded Webhooks for Multi-Stage Shipments: Shipment stage events can be added to webhook subscriptions, so integrations hear when stages are created, updated or removed. |
Reliable Purchase Order Updates: Purchase orders sync again when a shipment created from them was deleted. |
Faster Freight Invoice Search: Searching freight invoices in Settlements is faster and steadier for high-volume accounts. |
Self Schedule Appointments Search Improved: Self scheduling (aka non managed scheduling) users can search by Sales Order #, PO #, Order Name or a reference field you define, and see which field matched. The search matches the exact value, including upper and lower case. |
Self Schedule Time Requests Can Be Turned Off: A facility can stop self scheduling users from requesting their own times, so they book only the times the facility has opened. |















