These features are available on your Test site and released to your Production site on the evening of June 18th.Dispatch Board user interface redesign is available in this release. Be sure to review the user interface and the user guide.
Transition to New Map Board Thursday June 19
We’re retiring the Legacy Map Board in favor of a faster, more powerful version as part of our ongoing improvements to the Dispatch Science platform. If you haven't yet created a Map Board, one will be created for you automatically when you open an Order in the Back Office using the Navigate to Dispatch Board from the Order list or the Order details.
The new Map Board, included in the Tabular Dispatch Boards, delivers improved performance, usability, and a modernized interface.
What’s New:
- Unified and intuitive user experience across both the Map Board and Grid Board
- Significant performance enhancements
- A redesigned layout to streamline dispatcher workflows
The transition to the updated Map Board is part of our commitment to provide smarter, more efficient tools for managing your operations. Stay tuned as we continue to roll out improvements across the Dispatch Board.
New Features in This Release
Route Checkpoints
Dispatch Board User Interface Improvements
Enhanced Filtering and Usability Tools Across the Platform
New Multi-Segment Order Profile Controls
Enhanced Controls for Pickup and Delivery of Partial Orders
TABLE OF CONTENTS
- Driver App Version 1.71
- Driver App Version 1.72
- Back Office
- Dispatch Board
- Light Search
- Administration
- Scripts
- ODATA
- Integration API
- Tenant API
Definitions
The release notes refer to different sections of the application:
Back Office: Where Customer Service Representatives (CSR) create and edit orders, create accounts, review drivers, etc.
Dispatch Board: Where Dispatchers assign orders to drivers, get notifications for invalid orders, etc.
Auto-Dispatch: This section refers to the automated order assignment setup and its process.
Administration: This section is in the Back Office but refers to sections only an administrator will use like Settings and Pricing.
Customer Portal: Where account users log in to create orders, view their order history, enter a credit card, etc.
Tracking site: Where customers enter a tracking number like the order ID or a reference number to view the status of their order.
OData: Data fields and variables saved in OData
Account API: API provided to your accounts to create, update and get orders. For documentation, please follow this link: https://api.dispatchscience.com/
Tenant API: API provided to you to create orders for your accounts, retrieve invoices and change invoice status. For documentation, please follow this link: https://api.dispatchscience.com/
Scripting: Custom script building abilities and functions within Dispatch Science
Driver App Version 1.71
Features
Push Notification Responsiveness Improvements
The stability and responsiveness of push notifications between Dispatch Science and the Driver App has been enhanced. With this update, the Driver App now receive push notifications instantly after an action is performed in Dispatch Science such as an order update, the dispatching of a new order, etc. These improvements ensure that you, as a driver, are promptly informed of any changes, enabling faster response times and improved operational efficiency.
This feature was introduced in Driver App v1.71. It is included in these release notes to ensure all users are aware of the improvement.With the release of Dispatch Science version 1.72, all drivers should upgrade to version 1.71 to ensures that all drivers benefit from the latest performance and stability enhancement.Driver App Version 1.72
This version will not be included in the initial 1.72 Production release. It is expected to become available in the weeks following the rollout of version 1.72.Features
Driver App Checkpoint Routes
This feature will be documented prior to the release of the Driver App.
Back Office
Clear All Filters
A new Clear All button has been added to make it easier to reset filters on various lists in Dispatch Science. This new button will save time and ensures you can quickly return to the original view without manually removing each filter.
This new button is available in the following lists:
- Orders menu
- Already available in Orders and Recurrences
- Order Templates
- Import
- Routes and Route Checkpoints
- Drivers menu
- Already available for Drivers
- Settlements
- Accounts menu
- Already available in Accounts and Transactions
- Master Accounts
- Content Templates
- Pricing menu
- Extra Fee Types
- Discounts/Surcharges
- Settings menu
- Checkpoints
- Manage Exception Codes
- Settings>Configurations>Orders menu
- Parcel Types
- Settings>Configurations>Account menu
- Tax Rules
- Settings>Configurations>Accounting menu
- Accounting Items
- Terms
- Settings>System menu
- Users
- Addresses
- Scripts
- Script Rules
- Application Logs
How it works
1) When a new filter is applied to a list, the Clear All Filters button will automatically appear.
2) Click on the button to instantly reset the list to its default unfiltered state.
Orders
Enhanced Filtering on Order List
The Order List now includes expanded filtering options, giving users more precision and flexibility when managing and reviewing orders with improved visibility into orders missing signatures or pricing thresholds. It simplifies exception management and supports faster troubleshooting.
- Signature (Pickup and Delivery):
You can now filter orders based on the presence or absence of a signature at both pickup and delivery.
- Total Price Filter:
Filter the Total Price column using the following numeric operators:- Is equal to
- Is not equal to
- Is greater than
- Is greater than or equal to
- Is less than
- Is less than or equal to
Distance Filter:
The Distance column now supports the same numeric filters as Total Price for more accurate range filtering.
Exceptions Filter:
Filter orders by specific exceptions using a checkbox list. Each exception is displayed alongside the number of matching orders in parentheses, helping you quickly identify and focus on the most frequent issues.
Improved Behavior for Automatic Barcodes Suffix Stability
In earlier versions, when item barcodes were generated automatically, the numeric suffix (indicating the item number) would be recalculated if one or more items were deleted from an order. This often led to changes in existing barcodes.
With this update, automatically generated barcodes now remain stable, even when items are removed from the order. The suffix will no longer be regenerated, preserving consistency and preventing potential scanning or tracking issues.
Benefit: Ensures barcode integrity throughout the order lifecycle, improving reliability for scanning.Route Checkpoints
Found under Orders>Routes
This feature will be available when Driver App version 1.72 becomes available.A Route Checkpoint is an enhanced Checkpoint that offers all the standard features of a regular Checkpoint—including integration settings, tracking page visibility options, and barcode format configurations. In addition to these capabilities, a Route Checkpoint introduces functionality specific to Route management.
When using a Route Checkpoint, drivers are required to select a specific route before proceeding. Once the checkpoint is completed, the system automatically performs several actions:
- Moves orders to the selected route
- Marks the orders as picked up, if setup
- Dispatches the route to the driver, if setup
This feature streamlines Route operations by consolidating key logistics actions into a single Checkpoint event, helping to ensure accuracy and efficiency in the field.
For more information on this new feature, please review the Route Checkpoints article.
Route Checkpoints enable:
- One-step routing and dispatch — As soon as a driver completes the checkpoint, orders are automatically moved onto the selected route, Marked as picked up (if configured), Dispatched directly to the driver (if configured). This consolidates multiple actions into a single event, reducing manual steps
- More autonomy and possession scan options for drivers — Drivers can select a route at the checkpoint, ensuring accurate assignment and preventing routing errors.
- Configurable selection logic — You can define which routes are shown based on start time windows, and locations allowing drivers to see only relevant upcoming or allocated routes .
Improved efficiency and accuracy — By bundling route assignment, pickup confirmation, and dispatching into one checkpoint, this feature streamlines operations, minimizes errors, and accelerates delivery workflows.
A new permission was added to the Roles to give access to the Route Checkpoints. The permission is turned on for all internal roles of type Admin Internal).Drivers
Driver List Filters
The Driver List has been improved with advanced column filtering capabilities, making it easier to quickly find and manage drivers based on flexible criteria giving you greater control when filtering a large driver list, faster access to specific driver data and improved accuracy when performing searches.
Text fields filters:
- Contains (default operator)
- Does not contain
- Is equal to
- Is not equal to
- Starts with
- Ends with
- Is empty
- Is not empty
Vehicle Type Filter:
Multi-select filter with checkboxes allows you to quickly narrow down the list of drivers by selecting one or more vehicle types.
Driver Status Information
A new Status column has been added to both the Driver List and the Driver Details views. This improves visibility when making modification to the Driver details.
Accounts
Enhanced Control for Partial Orders Pickup and Delivery
A new configuration option has been added under "Allow Partial Orders to be Picked Up" and Allow Partial Orders to be Delivered" to give you more control over Driver scanning requirements during order handling.
New Options: Allow Pickup Without Scan and Allow Delivery Without Scan
In previous versions, Drivers could pick up or deliver an order without scanning any items. With this update, you can now enforce at least one item scan before an order is marked as picked up or delivered.
When enabled (default setting): Drivers can continue to pick up or deliver orders without scanning, maintaining existing workflows.
When disabled: Drivers must scan at least one item before they can complete the pickup or delivery process.
This setting can be configured independently for both pickup and delivery steps to align with your operational needs.
This option is enabled by default to ensure backward compatibility with your current processes.Multi-Segment Order Profiles
Accounts>Multi-segment order profiles
A new default Multi-Segment Order Profile has been introduced to streamline status updates across segmented orders. It simplifies the management of multi-segment orders, helps maintain consistency across segments and reduces manual updates, making the order flow more efficient.
In this first version, only one default Multi-Segment Order Profile is available and has been created automatically and has been assigned to all accounts.
This profile includes one configurable option that enables automatic segment updates when the last segment’s status is modified.
By default, this option is unchecked to preserve current behavior unless explicitly enabled. The profiles applies to newly created orders only and will not affect existing ones.
When option is unchecked, behavior remains unchanged as in previous releases:
- Last segment picked up:
- If the multi-segment order was in Received status, it is updated to Picked Up.
- Other segments remain unchanged.
- Last segment delivered:
- If the multi-segment order was not yet delivered, it is updated to Delivered.
- Other segments remain unchanged.
- Last segment is cancelled:
- No status changes are made to the multi-segment or other segments.
When option is checked:
- Last segment picked up:
- All previous segments (not cancelled or already delivered) are updated to:
- Picked up and then Delivered using the last segment's pickup date/time.
- The multi-segment order is also marked as Picked Up using the last segment's pickup date/time.
- Signatures and Signed By fields remain empty.
- All previous segments (not cancelled or already delivered) are updated to:
- Last segment delivered:
- All previous segments and the multi-segment (not cancelled or delivered) are:
- Set to Picked Up (if not already), and then to Delivered using the last segment's delivery date/time.
- Only the multi-segment receives the signature and signed by information (if available).
- All previous segments and the multi-segment (not cancelled or delivered) are:
- Last segment cancelled:
- All previous segments and the multi-segment (that are not already delivered or cancelled) are updated to Cancelled.
Configure the Default Multi-Segment Order Profile
1) Open Accounts then click on Multi-Segment Order Profiles:
2) Check the Update segments status automatically on last segment status update checkbox to have the statuses update automatically then click on Save.
or
Uncheck the Update segments status automatically on last segment status update checkbox to return to the previous behavior.
Dispatch Board
Both Grid and Map Boards had their user interface made more user friendly and the same features work and look the same way.
For more information about using the Dispatch Board, please review the Dispatch Board article.
Disabling Cancelled Orders Move to Routes and Set at Checkpoint
Previously, cancelled orders could be manually moved to a route, which unintentionally:
- Reactivated the cancelled order without notice
- Allowed the order to be assigned to a checkpoint.
This behavior has been disabled to prevent errors and ensure data integrity. Cancelled orders can no longer be moved or reactivated through routing action. This reduces the risk of operational mistake and preserves the intended status of cancelled orders.
Route Performance Improvement
Significant performance enhancements have been made to order grouping on Routes. Previously, grouping more than 5,000 orders on a route could take over 20 seconds to process.
With this improvement, the grouping now completes in approximately 2 to 5 seconds, resulting in a much faster and smoother user experience for high-volume routing scenarios.
Light Search
To improve system resilience and ensure continued access during service degradation, a new Light Search mode has been introduced for the following lists:
- Order List
- Driver List
- Account List
- Transaction List
- Address List
Lightweight Search Mode:
If performance issues are detected, the system will automatically switch to Light Search mode to maintain uptime and usability. A yellow warning icon will display in the quick search bar to indicate that the light search has been activated.
Simplified Filters & Sorting:
While Light Search includes fewer filter and sort options compared to the full version, it still enables users to effectively search and access the information they need.
This feature ensures uninterrupted access to critical data, maintains core search functionality and improves the system reliability and user experience even during service degradation.
Order List Search Fields:
- OrderId
- Barcodeid
- Templateid
- Recurrenceid
- Account name
- Account Number
- Driver Number
- Status
- Created At
- Pickup from/to
- Delivery from/to
You will be able to search for orders from the past 2 weeks.
Driver List Search Fields:
- Driver number
- Driver first name
- Driver last name
Account List Search Fields:
- Account number
- Account name
Transactions List Search Fields:
- TransactionId
- OrderId
- Account number
- Account name
Address List Search Fields:
- Address line 1
- City
- ZIP/Postal Code
FIlters for Columns:
The filters that will be available are:
- Is equal to
- Is not equal to
- Is empty
- Is not empty
Administration
Improved Empty Miles Distance Calculation in Price List
This feature will not be available when version 1.72 becomes available in Production. It is expected to become available in the weeks following the 1.72 release.Pricing>Price List
The empty miles or "deadhead" travel distance calculation has been improved to offer greater flexibility. In addition to using the warehouse’s latitude and longitude, the system now offers the option to also calculate the order distance using the Account’s main address location. The change ensures greater flexibility in choosing either warehouse or account main address as the origin point for distance-based pricing.
This enhancement provides more accurate and context-specific distance data when calculating the order's mileage.
Set Distance Travelling Distance by Account Address
1) Click on Pricing.
2) In the Price List, either create a new price list or edit an existing price list.
There are now 2 options available:
- Include Warehouse Travelling Distance which will use the latitude and longitude entered in the price list.
- Include Account Travelling Distance which will use the main address's latitude and longitude associated to the Account which can be found when you open an Account from the Account list:
To modify or add an address to an account, open the Account: Accounts>click on Account name in the list>Account Details that is accessed from the upper right Edit button once an account is opened.
3) Select the option you wish to use. Unselect the option if it was selected by error and the radio button will uncheck.
or
4) Select the desired option:
- For the warehouse travelling distance, click in the Include warehouse travelling distance radio button then enter the latitude and longitude of your warehouse.
- For the account's main address, click in the Include Account Travelling Distance radio button.
You will notice the latitude and longitude boxes will be locked.
5) Check to Exclude distance on return orders and/or continuation orders if needed.
6) Enter the formula to use in the Distance Formula box.
Use LocationToPickup to add the distance between the Location (warehouse or account main address) to the order pickup address.
Use DeliveryToLocation to add the distance between the order delivery address to the Location (warehouse or account main address).
7) Click Save.
To support the new location-based distance calculation, the following changes have been made to the distance formula terminology: WarehouseToPickup becomes LocationToPickup DeliveryToWarehouse becomes DeliveryToLocation What this means to you: If you edit a price list that uses the old Warehouse terminlogy, you will need to update the formula to use the new Location wording. If you don't make changes to your existing price lists, no action is required. The system will continue to support the old workding through backward compatibility until the price list is modified.
Scripts
Order Properties
Order Ready At is available as a Date-Time Offset and is called ReadyAt. For more information please review https://github.com/dispatchscience/DispatchScience.Scripting/blob/main/Dispatch.Scripts.Abstractions/Interfaces/IOrderReader.cs
Order Update Scripts
Modify Pickup and Delivery Addresses for Standard and Multi-segment Orders
You can now update pickup and delivery addresses for both standard and multi-segment orders using the Order Update Script.
- For standard orders, the updated addresses are applied directly.
- For multi-segment orders:
- Updating the pickup address will automatically update the pickup address of the first segment.
- Updating the delivery address will automatically update the delivery address of the last segment.
These changes ensure that address modifications are accurately reflected across the order structure without requiring manual updates to individual segments.
Properties:
newPickupAddress
newDeliveryAddress
Task:
UpdateDeliveryAddress(Address newDeliveryAddress, Action<PricingUpdateOptions>? configureOptions = null);
UpdatePickupAddress(Address newPickupAddress, Action<PricingUpdateOptions>? configureOptions = null);
The configureOptions are:
public bool UpdateDeliveryCharge { get; set; } = true;
public bool UpdateWeightExtraFee { get; set; } = true;
public bool UpdateNumberOfPiecesExtraFee { get; set; } = true;
public bool UpdateMileageAffectedExtraFees { get; set; } = true;
public bool UpdateVehicleAffectedExtraFees { get; set; } = true;
public bool UpdateScriptedExtraFees { get; set; } = true;
For more information please review:
UpdateDeliveryCharge for the configureOptions in: https://github.com/dispatchscience/DispatchScience.Scripting/blob/main/Dispatch.Scripts.Abstractions/Interfaces/IOrderUpdater.cs
ODATA
Routes
New field DriverAllocatedAt was added to the table to show the date and time a driver was allocated to the route.
Integration API
POST /api/v1/orders/quote
Previous Behavior:
Users required edit access to "Addresses - Global" in order to create a quote, even though quotes do not result in an actual order.
Updated Behavior:
This requirement has been removed. Since creating a quote does not generate an order, users no longer need access to the Global address to create quotes.
Tenant API
Search
A new Search section has been added to the API, allowing developers to perform powerful searches on orders—similar to the search functionality available in the Back Office Order List. This new endpoint brings powerful search capabilities to API users while speeding up integration workflows requiring order lookups while reducing devlopment time by mirroring the Back Office order list user interface logic.
GET /api/v1/search/orders
This endpoint gives a summary of the values and operators that can be used in the POST /api/v1/search/orders.
SearchTermFields
This field functions as a quick search, allowing the entered value to be searched across a predefined set of fields:
- Order ID
- Account Name / Number
- Driver Name / Number
- Recurrence Name
- Template Name
- Reference Numbers 1, 2, 3
- Pickup/Delivery Address
- Pickup/Delivery Company
- Barcodes
FilterableFields
This section gives you the field names and their operators that can be used in the search Filters section.
FilterLogic
This field gives you the operand And/Or that is used in the CompositeFilter
Date field example:
Use 0 (and operand) to search for a date range.
Vehicle field example:
Use 1 (or operand) to search for car or truck.
You can also use a different field in the composite filter.
POST /api/v1/search/order
Request Body
{
"Page": 1,
"PageSize": 50,
"SearchTerm": "C10",
"Filters": [
{
"field": "Status",
"operator": 4,
"value": "Received",
"compositeFilter": {
"logic": 0, 0 is and, 1 is or
"field": "DriverId",
"operator": 11,
"value": null
}
}
]
}
Fields
Pagination
- Page: Specifies the page number to retrieve in the result set.
- PageSize: Defines the number of orders to return per page. Used in combination with Page to control pagination.
Quick Search
- SearchTerm: A general text input used to perform a quick search across the predefined set of searchable fields.
Filters:
- Each filter includes the following properties:
- Field: The name of the field to filter on, as defined in the GET /api/v1/search/order endpoint.
- Operator: The comparison operator to apply (is equal, contains, etc), valid per field as listed in the GET /api/v1/search/order endpoint for the field.
- Value: The search value to match against the selected field with the operator.
- Composite Filter
- This is optional. Use a composite filter to apply a second condition, either on the same field or a different field. Useful when combining conditions with custom logic.
- Logic: Defines how to combine the two filters
- 0 = AND
- 1 = OR
- Field: The name of the secondary field to filter. It can be the same as the one used in Filter.
- Operator: The operator to apply to the secondary field.
- Value: The value to compare agains the second field using the operator.
When applying multiple filters, the logic between different fields is always AND. This means that all filter conditions must be met for a record to be included in the results. If you need more complex filtering logic—such as combining multiple values for the same field or using OR logic—you can use the CompositeFilter however in a CompositeFilter, you can add one additional condition on: The same field (e.g., Total Price > 100 OR Total Price < 10) or A different field, if needed You can then define the logic (e.g., AND or OR) between these composite conditions to suit your specific filtering needs.
Quick Search Fields:
- OrderId
- AccountName
- AccountNumber
- DriverFullName
- DriverNumber
- RecurrenceName
- TemplateName
- ReferenceNumber 1, 2, 3
- PickupAddressLine1/DeliveryAddressLine1
- PickupPostalCode/DeliveryPostalCode
- PickupStateProvince/DeliveryStateProvince
- PickupCity/DeliveryCity
- PickupCompany/Delivery Company
- Barcodes
Valid values by field types
- Example of text fields: TemplateName, DeliveryCity, CreatedbyUserName
- Enter the value in quotes, "New York"
- Example of date fields: StatusPickupDate, ReadyAt
- Enter the date and time in quotes as YYYY-MM-DDThh:mm:ssz to enter as UTC or YYYY-MM-DDThh:mm:ss-04:00 to enter in a specific time zone , "2025-06-10T15:00:00-04:00"
- Examples of numeric fields: Volume, Distance
- Enter the number without quotes
- Examples of boolean fields: IsInvoiced, IsSettled, IsOnHold
- Enter True or False with or without quotes
- Order status field:
- You can enter the name of the status in quotes or its id without quotes:
- 0 = Received
- 2 = Picked Up
- 4 = Delivered
- 91 = Cancelled
- You can enter the name of the status in quotes or its id without quotes:
Set Order as Unbillable
A new API endpoint has been added to allow orders to be marked as unbillable, making it easier to separate test orders from production orders in your billing process.
Purpose:
Helps prevent test orders from being accidentally invoiced in a live environment.
Ensures that only legitimate, production-ready orders are included in invoicing runs.
Use Case:
Use this endpoint when testing in your production site to ensure cleaner, more accurate invoicing once you're ready to go live.
POST /api/v1/orders/mark-as-not-billable
Request Body
{
"orderIds": [
"string"
]
}
Enter one or move orders Ids in the array.
Additional Webhooks Events
Two new webhooks have been added to enhance real-time visibility into order activity:
- Item Scanned Webhook
Triggered when an item is scanned (e.g., during pickup, delivery, or at a checkpoint).
Enables live tracking and better operational monitoring. - Order Charges Webhook
Triggered when charges on an order are added, updated, or removed.
Helps ensure billing systems and external integrations stay up to date with charge changes in real time.
These webhooks improve automation, accuracy, and responsiveness by keeping your systems synchronized with critical order events.
The following information shows as order information followed by a section for the new webhook:
{
"OrderId": "orderid",
"Metadata":
"Status": 0,
"Timestamp": "YYYY-MM-DDThh:mm:dd:ss:ms+00:00",
"Language": "en",
"EventType": "charges_added",
"AccountId": "1",
"FulfillmentType": 0,
"RouteId": null,
Metadata: show if added on the order when created through api
Status: 0=received, 1=pickup,2=,
Language: en or fr or sp
FulfillmentType: 0 = standard, 1=
RouteId:show if order is on a route
Item Scanned Webhook
Event Name
tracked_order_items_added
Call-back Content
"Items":[
{
"ItemId": "abcd1234",
"Barcode" : "barcode",
"ScanTime" : "yyyy-mm-ddThh:mm:ss",
"ExceptionCodes" : ["Exception1"],
"IsMissing" : "True/False",
"IsDamaged" : "True/False",
"CheckpointId": "checkpointid",
"TrackingType": 0 // Checkpoint = 0, PickedUp = 1, Delivered = 2
}
],
"userId": "fe4bc3ab-ece3-4163-aced-13af016877fd"
}
ExceptionCodes will show all item exception codes
IsMissing: True if the item was not scanned, False if the item was scanned
IsDamaged: True if you indicate that the item is damaged or if the exception code is an exception of type damaged.
TrackingType: Checkpoint = 0, PickedUp = 1, Delivered = 2
Charges Added Webhook
Upon order creation, all charges, deliveries and extra fees, will be sent. If an invalid order is created, once the price is added, the charge will be sent. If extra fees are added to the order during its lifecylce, the charges will be sent.
Event Name
charges_added
Call-back Content
Delivery Charges:
"Charges": [
{
"chargeType": "Delivery",
"chargeId": "GUID",
"total": 100,
"fuelSurcharge": 15,
"totalWithFSC": 115
}
]
total: show the delivery price without fuel surcharge
fuelSurcharge: show the amount of fuel surcharge
totalWithFSC: show the total with fuel surcharge
Extra Fee charges:
"Charges": [
{
"chargeType": "Extra",
"chargeId": "GUID",
"extraFeeTypeId": "extra fee id",
"unitPrice": 1.4,
"quantity": 5,
"total": 5.6,
"fuelSurcharge": 0.06,
"totalWithFSC": 5.66
}
]
When an extra fee is added, the charges section includes the following :
extraFeeTypeId
unitPrice
quantity
Charges Updated Webhook
If a delivery charge or an existing extra fee are updated, they will be sent through the update.
Event Name
charges_updated
Call-back Content
Delivery:
"charges": [
{
"chargeType": "Delivery",
"chargeId": "GUID",
"total": 100,
"fuelSurcharge": 15,
"totalWithFSC": 115
}
]
Extra Fee:
"Charges": [
{
"chargeType": "Extra",
"chargeId": "GUID",
"extraFeeTypeId": "extra fee id",
"unitPrice": 1.4,
"quantity": 1,
"total": 1,
"fuelSurcharge": 0.01,
"totalWithFSC": 1.01
}
]
chargeType: Delivery or Reattempt or Extra
extraFeeTypeId: show if the charge is an extra fee id
unitPrice: show the per for extra fee
quantity: show the quantity of the extra fee
total: show the total without fuel surcharge
fuelSurcharge: show the amount of fuel surcharge
totalWithFSC: show the total with fuel surcharge
Charges Removed Webhook
Event Name
charges_removed
Call-back Content
"ChargeIds": ["GUID", "GUID"]
ChargeIds: show all charges that were removed as their GUID.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article