When to Use Custom Mappings

Custom mappings may be typically used in the following scenarios:

Soft Data Transformation: 

1. When users receive input data from clients or partners that is not in a format directly compatible with their chosen 3PL providers, custom mappings allow them to transform this soft data into a structured and accepted format for seamless integration.

2. For example, if the customer passes data for destination city as “Delhi”, but the 3PL only accepts this data as “DL”, then a custom mapping may be set up to ensure that soft data is transformed to ensure seamless transfer of consignment date

Specific Account Requirements

1. Custom mappings can be used when different 3PL accounts have unique data requirements. Users can create mappings tailored to specific accounts, ensuring that the data sent to each account meets their specific needs.

Wildcard and Default Values

1. Using custom mappings, users can assign wildcard values like "Default" or "Empty" for situations where input data is missing or incomplete. This ensures that no critical information field is omitted for the 3PL to process relevant data.

2. For example, in the case of prepaid orders, many customers may pass a null value under cod amount. However, the 3PL may operate in such a way that they require some data to be passed in the cod amount field to process the consignment. In this scenario, users may create a custom mapping to ensure that when no cod amount data is available a default value such as “1” is passed over to the 3PL instead. 

Therefore, custom mappings play a crucial role in optimising the integration of organisation systems with 3PL providers. They ensure that the data sent to carriers is accurate, compliant, and in the right format, reducing errors and improving the overall efficiency of the logistics operations.