Zones (Contracts & RFPs)
Zones
The system now has the ability to create and store Zone information within the application. A Zone is a collection of locations that can be used to group multiple locations together for easier management within the TMS. For example, if a carrier provides a single rate per mile for all of the Midwest states, a Midwest zone can be created made up of all the states within the Zone.
To create a Zone, go to Manage, Company, Lane Management, Zones. Here you will see a list screen of all existing zones, as well as the options to manually create a new Zone, or import Zone data.
Clicking on a Zone or creating a new Zone takes you to the Zone Detail screen. The Reference value must be unique, and is used when including a Zone when importing a Contract, or used in conjunction with the RFP process.
From this screen locations can be added or removed from the Zone. Valid locations include:
Full location address
City
State / Province
Country
3 digit postal code
5 or 6 digit postal code
Supports all alpha numeric postal codes for countries such as Canada, Mexico, China (etc)
In this example, you can see that the Midwest Zone is made up of a collection of states.
The Zone importer allows you to easily create or update existing Zones in the system. Here you can see the multiple types of locations that can be included in Zone.
Once a Zone is created, it can be used in conjunction with the Contract Import and RFP Automation processes.
Contract Importer
The contract importer now includes an Origin Zone and Destination Zone column. If a valid Zone Reference ID is located in these columns, import process will reference the Zone and create a contract lane for each location within the Zone.
For example, if my carrier contract has a single rate of $2.35 per mile to all locations in the Midwest Zone, the contract will appear as depicted below, creating a lane for all the locations within the Zone. This process allows me to avoid creating contracts that contain many locations that are all served under the same rate.
RFP Process
Similar to the contract importer, the RFP Automation process can leverage pre-existing Zones to simplify the process. Origin and Destination Zone columns have been added to the RFP Importer, where again a valid Zone Reference ID can be added.
When imported via the RFP process, the Zone Name is displayed as an RFP lane. Hovering over the Zone Name will display all the locations within the Zone. In this example, when the carrier receives the RFP spreadsheet, they will be able to enter a rate for the Midwest zone and a rate for the Chicago zone.
When the carrier uploads the RFP response that includes their rates, the contract that is automatically created will break apart the zone data and create all of the associated lanes within the contract. This process mirrors the logic used when importing contracts that contain zones. In the example below, you can see the 2 Zones included in the RFP have created all the associated lanes within the contract.
PC Miler Version 39
Support has been added for the latest version on PC Miler, Version 39. To change your distance configurations, go to Manage, Customer, then select your customer account. In the Distance Service drop list, you can now select PC Miler Version 39.
Stop Out of Order Warning
Sometimes carriers look to complete stops out of order. On the Shipment Details page we have implemented a ‘Stop Out of Order Warning.' This warning is triggered when a user selects either ‘Mark Stop as Complete’ or tries to enter a dispatched, arrival, or departure for a stop prior to the stops before them have been completed it will trigger a warning. The carrier can still take action and select ‘Yes, Mark Stop as Complete’.
This functionality is active for all users with enhanced stop experience (shown above) present.
Shipment Templates
Shippers oftentimes repeat types of shipments that are generated frequently. Today Shipwell customers will use the ability to clone a previous shipment to easily transfer data from a prior shipment to be reused. We have a new option available in Shipwell web called Shipment Templates that allows you to create a pre-defined template for a shipment that can be reused.
Shipment Templates are easy to find and use. Any customer user with shipment create access can create shipment templates.
Create a Shipment Template
Open Create Shipment and switch to the New Shipment Creation experience (select “Try it Now” in the top-right if you don’t see it).
Set up the shipment details you want to reuse. You can start from scratch or by cloning an existing shipment first.
Click “Save as Template” in the top-right.
In the dialog:
To overwrite: select an existing template from the dropdown.
To create new: enter a clear, searchable Template Name.
Click “Create Template.” Your template is now saved for your organization.
Use a Shipment Template
In the New Shipment Creation experience, choose one of:
“Load from Template” and select the template you want, or
The clock icon to quickly pick from your most recently used templates.
The shipment form will auto-populate with the saved template details. Review and submit.
Update a Template
Load a template, make changes, click “Save as Template,” then select the same template in the dropdown to overwrite.
Delete a Template
Click ‘Save as Template’ and select an existing template and then select ‘Delete’.
Best Practices for Naming
Use descriptive, searchable names that help others understand the purpose (for example: “LTL_Dallas→Chicago_FreezeProtect,” “FTL_Weekly_DC→Store_53’_NoLum”).
Limitations and Notes
Not for Orders workflows yet. Templates currently support manual shipments only.
Available only in the New Shipment Creation experience (“Try it Now”).
We anticipate future support for order templates and welcome customer feedback.
Troubleshooting Tips
Don’t see templates? Ensure you’re in the New Shipment Creation experience and have shipment creation permissions. Refresh the page after creating new templates.
List of top-level objects or fields that can be used when Creating a Template. If looking to create and/or manage shipments templates via API you can learn more here.
Accessorials (accessorials)
Additional BOL Recipients (additional_bol_recipients)
Bill To Fields (bill_to_override)
BOL Number (bol_number)
Buy It Now Amount (buy_it_now_amount)
Buy It Now Amount Currency (buy_it_now_amount_currency)
Capacity Provider Customer Reference Number (capacity_provider_customer_reference_number)
Charge Line Items (charge_line_items)
Custom Data (custom_data)
Customer Reference Number (customer_reference_number)
Drayage Container Return Date (drayage_container_return_date)
Drayage Estimated Arrival Date (drayage_estimated_arrival_date)
Drayage Last Free Date (drayage_last_free_date)
Drayage Release Date (drayage_release_date)
Equipment Type (equipment_type)
Line Item Fields (line_items)
Max Buy Amount (max_buy_amount)
Max Buy Amount Currency (max_buy_amount_currency)
Mode (mode)
Notes for Carrier (notes_for_carrier)
Pickup Number (pickup_number)
PRO Number (pro_number)
Purchase Order Number (purchase_order_number)
Service Level (service_level)
Shipment Name (shipment_name)
Stop Fields (stops)
Tags (tags)
Target Rate Amount (target_rate_amount)
Target Rate Amount Currency (target_rate_amount_currency)
Temperature Lower Limit (temperature_lower_limit)
Temperature Upper Limit (temperature_upper_limit)
Template Name (template_name)
Total Declared Value (total_declared_value)
Total Declared Value Currency (total_declared_value_currency)
Total Weight Override (total_weight_override)
Total Weight Override Unit (total_weight_override_unit)
Customer (customer)
Vendor (vendor)
Data Science
No customer facing changes
API Changes
Overview
This release introduces broad enhancements to shipment, quoting, routing, and company APIs, including new optional properties for charge line items and contracts, a new endpoint for applicable routing policies, and an additional mileage type enum value.
Create and Manage of groups(Related to upcoming broader functionality being released)
Overview
This update introduces a new object, groups, that we will be building on to support organizations to leverage within other objects to classify parts of their organizations (e.g. division, distribution centers, companies, etc). The first generation of Groups will simply tie groups onto orders and shipments along with having the concept of a Group management. In this release we are simply providing ability to perform CRUD operations to manage Groups but nothing is in the Shipwell interface and nothing is tied to orders and shipments in this release.
Groups Endpoints
GET /groups
POST /groups
PUT /groups/{group_id}
PATCH /groups/{group_id}
Shipment & Quoting APIs: Enhanced Charge Line Item Fields
Endpoints impacted:
/shipments/, /shipments/{shipmentId}/, /purchase-orders/build-shipment/, /carrier-relationships/, /quoting/spotnegotiations/spot-negotiations/, and many more.
Changes:
New optional fields in both request and response schemas:
base_rate
rate_type
Present within: customer_charge_line_items, vendor_charge_line_items, and associated nested objects.
Routing Guide Policy APIs: Contract Support
Endpoints:
GET /routing-guide/policies/
Added optional response fields: contract, contract_details
POST /routing-guide/policies/
Added optional request property: contract
Added optional response fields: contract, contract_details
PUT /routing-guide/policies/{policyId}/
Added optional request property: contract
Added optional response fields: contract, contract_details
DELETE /routing-guide/policies/{policyId}/
Added optional response fields: contract, contract_details
GET /routing-guide/policies/{policyId}/
Added optional response fields: contract, contract_details
New endpoint:
GET /shipments/{shipmentId}/applicable-policies/
Allows retrieval of policies relevant to a specific shipment.
Usage Example:
{
"contract": "Carrier-Q3-Prime",
"contract_details": {
"type": "annual",
"effective_date": "2025-08-01"
}
}ENUM Expansion: New Mileage Type Value
Change:
Extended the mileage_type enum with support for a new value: PC_MILER_39.
Endpoints Affected by PC_MILER_39 Enum Value:
GET /auth/me/
POST /auth/token/
GET /companies/{companyId}/
PUT /companies/{companyId}/
GET /brokerages/{brokerageId}/shipper-relationships/
POST /brokerages/{brokerageId}/shipper-relationships/
GET /brokerages/{brokerageId}/shipper-relationships/{shipperRelationshipId}/
PUT /brokerages/{brokerageId}/shipper-relationships/{shipperRelationshipId}/
GET /brokerages/{brokerageId}/shipper-relationships/{shipperRelationshipId}/carriers/
PUT /brokerages/{brokerageId}/shipper-relationships/{shipperRelationshipId}/carriers/
GET /carrier-relationships/
POST /carrier-relationships/
GET /carrier-relationships/{carrierRelationshipId}/
PUT /carrier-relationships/{carrierRelationshipId}/
GET /carriers/
GET /carriers/integrations/automated-vendors/
GET /carriers/{carrierId}/power-units/{powerUnitId}/shipments/
POST /purchase-orders/build-shipment/
PUT /purchase-orders/update-built-shipment/
GET /shipments/
POST /shipments/
GET /shipments/{shipmentId}/
PUT /shipments/{shipmentId}/
PUT /shipments/{shipmentId}/add-orders/
PUT /shipments/{shipmentId}/remove-orders/{orderId}/
PUT /shipments/{shipmentId}/carrier-assignments/{carrierAssignmentId}/
POST /shipments/{shipmentId}/carrier-assignments/
GET /shipments/{shipmentId}/carrier-assignments/
GET /shipments/{shipmentId}/carrier-assignments/{carrierAssignmentId}/
POST /shipments/{shipmentId}/initiate-check-call/
POST /shipments/{shipmentId}/auto-book/
POST /shipments/{shipmentId}/award-quote/
POST /shipments/{shipmentId}/cancel/
GET /shipments/external/
GET /shipments/external/{shipmentId}/
GET /shipments/pickups/
POST /shipments/pickups/
GET /shipments/pickups/{shipmentPickupId}/
PUT /shipments/pickups/{shipmentPickupId}/
POST /shipments/pickups/{shipmentPickupId}/cancel/
GET /quoting/spotnegotiations/spot-negotiations/
GET /quoting/spotnegotiations/spot-negotiations/{spotNegotiationId}/
PUT /quoting/spotnegotiations/spot-negotiations/{spotNegotiationId}/
GET /quoting/loadboard/
GET /quoting/loadboard/{loadBoardShipmentId}/
GET /tenders/
POST /tenders/
GET /tenders/{tenderId}/
Summary Table
Area | Change | Details |
Shipments/Quoting | base_rate, rate_type (optional fields) | Charge line items on major shipment/quote APIs |
Routing Guide Policies | contract, contract_details (optional fields) | Policy management APIs endpoints |
Routing Guide Policies | Endpoint added | /shipments/{shipmentId}/applicable-policies/ |
Orders APIs | groups (optional property) | Orders, Purchase Orders, Sales Orders APIs |
Enum Fields | PC_MILER_39 value added to mileage_type enum | Present across company, carrier, shipment, etc. |
Actions for Developers
All API consumers:
No immediate migration is required. All new fields are optional.
Review your integrations to ensure new enum values (PC_MILER_39) do not cause failures.
Leverage new contract fields, groups properties, and endpoints as appropriate for your business logic.
Other Features Part of The Release
Description |
Update Swifty Error Messaging Email for Use Case Where Shipment Cannot Be Found in Uploading a Document |
Macropoint: Location Detail missing for breadcrumb table |
Tracking information missing on Air Shipment |
Samsara: Display real time location updates in Shipwell |
FE: Ensure new Samsara data is working in tracking |
Not receiving any approved invoices |
[ANDROID][5.3.8] Support non whole number quantities for line items |
[ANDROID][5.3.9] Mobile App - The ask is to relax the number of requests made to the user to turn on "Always Tracking" |
[ANDROID][5.3.8] App crashed in the create pod screen |
[ANDROID][5.3.8] App crashed when the user tried to open a shipment from a facility appointment |
[ANDROID][5.3.9] TrimbleMaps crash in android 35 |
[ANDROID][5.3.8] Image crop screen crashed when moving app to background |
[iOS][5.6.4] Mobile App - The ask is to relax the number of requests made to the user to turn on "Always Tracking" |
[iOS][5.6.4] Financials actions in mobile application not working |
[ANDROID][5.3.8] Welcome message didn't work for driver |
Support suppliers created Orders via the Supplier Portal |
Create shipment table edit for custom reference data single select list |
Update Shipment Financials Write Back of Information into Shipwell Shipment Record in SuiteApp |
Update dock scheduling to support 3PL or carrier clients that are customers to leverage dock scheduling |
Update SuiteApp configuration UI to only display in marketplace if flag active for customer |
Update SuiteApp configuration UI to show both business friendly and actual field name in search and selection for SuiteApp config |
BOL Displays Duplicated or Stale Line Items After Shipment Modifications |
New V3 Order Creation experience-Bug -Item numbers not showing on the order |
Create Shipment from Order - Order_simple not passing all the custom data to the shipment |
[ErpGateway] - Orders with releases are failing to update |
The Customer Invoice does not display the correct Bill To following Invoice creation. |
V3 Order importer single date/time entry issue resolution |
Add Warning Modal & System Log for Out-of-Order Stop Completion |
Duplicate Invoice Number - Inline Error and Warning Modal Workflow |
[NetSuite] - Fix geocode processing for addresses |
Unable to create Customer Invoice in the Production environment |
Can not create invoice when stop has invalid address |
Two handling units being incorrectly displayed |
Intercompany Transfer Order isn't being sent to Shipwell using SuiteApp |
RFP - Routing Guide dropdown shows mismatched options unrelated to shipment destination |
Routing Guides - Add contracts with any currency |
Support for PC Miler v39 |
Rate Per Mile Not Visible on Shipment Financials |
Bulk Tender screen displays $0.00 when contract is a fixed rate |
LTL Shipments - not updating with Pro's or moving status |
FRONTEND - Rate Per Mile Not Visible on Shipment Financials |