We're rapidly making improvements and the platform may or may not look the same as shown in the video, but the concepts remain the same.
Objective
The video provides a step-by-step guide to creating and configuring raid cards for managing logistics pricing. It explains setting up basic details like aliases, carrier information, discounts, and volumetric calculations. Guidelines are established with parameters such as weight rounding, calculation type (total or item weight), and size/weight limits for shipments. Weight breaks (e.g., 0-1 kg, 1-3 kg) are defined, and pricing is linked to specific zones (e.g., Sydney to Melbourne), either by total shipment weight or individual item weight.
The tutorial also covers kilo-based pricing and emphasises understanding the logic of weight and item-based structures, with more detailed follow-ups promised in future videos.
Creating a new rate card
You can create a rate card here. A rate card can be weight based or quantity based.
Fields that are mandatory are marked as * in the end.
Field Name | Description |
Rate Card Name* | The name of the Rate Card |
Rate Card Alias* | These are service code(s) that define the rate selection in reconciliation and simulations. Can be comma separated. |
Carrier Alias* | This is the carrier alias used in incoming invoices for reconciliations or simulations. |
Maximum discount allowed | Maximum discount available for a sales person to provide while signing up a new customer. |
Minimum margin needed | Minimum Margin needed on this rate card when it is shared as a rate contract with a customer. |
Volumetric Multiplier / Divisor* | Volumetric Multiplier / Divisor for this rate card. This is usually weight per volume or vice versa. |
Select Service name* | Select the service for which this rate card is built. |
Select zone group* | Select the zone group applicable for this rate card. |
Select Surcharge Rule Group* | Select the surcharge group applicable for this rate card. |
Include GST/VAT/Service Tax | If you want to include GST,VAT/Service Tax in the rate card, then select this option. |
Select breakdown type | Define whether the rates are based on number of items or weight of items. |
Select weight break type | If the breakdown is weight based then select the weight break type:
|
Calculation Type | If the breakdown is weight based then select the calculation type:
|
Round off weights | If yes, Dyspach will round off the value based on the Calculation Type. i.e If calculation type is per item, then we will round off the item weight. If calculation type is total shipment, then we will round off the total weight. |
Activate this rate card after creation | The option if the user does not want to activate the rate card, the check box can be un-checked. |
Add Guidelines
Fields that are mandatory are marked as * in the end.
Field Name | Description |
Guideline Name* | The name of the guideline |
Applies to* | Choose the item types to which the guideline is applicable:
|
Min-Max Item Length* | Input the minimum and maximum length of the item type acceptable in this rate card. |
Min-Max Item Width* | Input the minimum and maximum width of the item type acceptable in this rate card. |
Min-Max Item Height* | Input the minimum and maximum height of the item type acceptable in this rate card. |
Min-Max Item Weight* | Input the minimum and maximum weight of the item type acceptable in this rate card. |
Min-Max Item Volume* | Input the minimum and maximum volume of the item type acceptable in this rate card. |
Add Break
Fields that are mandatory are marked as * in the end.
Using bulk Add functionality we can add multiple breaks at once by entering data in the format: Name, Min, Max, with each entry on a new line.
Field Name | Description |
Weight break name/Quantity break name* | The name of the break (weight or quantity based) |
Min-Max Total Weight/ Quantity* | Input the minimum and maximum weight/quantity |
Carrier Alias | This is the carrier alias used in incoming invoices for reconciliations or simulations. |
If the above doesn't help, give us a holler and our support team would love to help out.