ShipsyKnowledge Base

New Custom Status Mapping

Article iDnbbwjM · source

Custom mapping defines the particular status updates that need to be reflected in Shipsy with the 3PL. Its need becomes inevitable whenever a new carrier is added by the end user in the system, it becomes essential to define a status mapping as well. Shipsy provides a default mapping for all 3PL integrated in the system and the mapping is easy to define at the time of carrier setup.

This is required to ensure that statuses reported by 3PL, if not present within the client organisation, are mapped to relevant client statuses to ensure seamless status tracking

General Notes :

  1. Step Pricing will be present wherever applicable: Weight ( Both Dead + Volume) & No of Pieces
  2. Delivery and Installation differentiation will be handled via Service Type
  3. Zone Pricing will be done on City to City for all Permutations and Combinations

ZONE LEVEL RATE CONTRACTS

Construct :
The following rates have to be calculated on the basis of Origin and Destination City as per softdata of a consignment. Column headers to be as follows:

  • Customer Code
  • Origin City
  • Destination City
  • Price

PIECE LEVEL RATE CONTRACTS

Construct:
The following rates have to be calculated on the number of Pieces (Child Consignments). Column headers to be as follows:

  • Service Type
  • Customer Code
  • Number of pieces (Min & Max)
  • Price

VOLUMETRIC WEIGHT

Construct :
The following rates have to be calculated on the basis of volumetric weight captured/calculated during softdata upload. Column Headers to be as follows.

Note : Volumetric weight will be calculated for each piece individually, if piece details are mentioned and on consignment, if only consignment details are mentioned

  • Service Type
  • Customer Code
  • Volumetric Weight Min (Kg)
  • Volumetric Weight Max (Kg)
  • Price
    Volumetric weight Formula = LBH/4000

DEAD WEIGHT

Construct :

The rate would be calculated on the piece level and not on CN level.
The following rates are to be calculated on the basis of dead weight which will be captured during softdata upload. Column headers to be as follows :

  • Service Type
  • Customer Code
  • Weight Min (Kg)
  • Weight Max (Kg)
  • Per_piece_weight_limit (Kg)
  • Price

Step pricing (if empty, upper limit of the weight would be the threshold weight - Weight Max). Upper limit will be provided by FlowPL to split consignments.

Step weight pricing to be implemented where we would have fixed price for weight slab and the per Kg step pricing can be done.
FlowPL to confirm on the thresholds to be maintained on CN level and Piece level?

ITEM TYPE PRICING

Construct :

The following rates are to be calculated on the basis of item type captured during softdata upload. A content type validation will be present, post receiving from Flow. Column headers to be as follows :

  • Service Type
  • Customer Name
  • Price
  • Category - Big/Small
  • No of Pieces
    Open points.
  • Big - Volumetric Weight > 20kg

Small - Vol. Weight < 20kg

DECLARED VALUE PRICING

Construct :
The following rates are to be calculated on the basis of percentage of Declared Value as entered in softdata with a minimum of 150SR. Column Headers to be as follows :

  • Service Type
  • Customer Code
  • % of Selling Invoice ( % of Declared Value)

LINEAR METER PRICING

  • Client would be pushing the total length in meters and this would simply be calculated as per the below formula -

    Rate = Number of meters * Rate from Masters

    The following columns headers would be there in the masters -

  • Service Type

  • Customer Code

  • Charge per Meter
    FlowPL to pass the no. of meters under the Length field in the softdata

Was this article helpful?