Routing Logic Directives (RLD) built into EPISHIP control shipments through the rate and label manifest processes of the supply chain.
The purpose of this article is to detail the Afferent Reference Rule, a specific RLD Rule type, that targets the transformation and control of reference field information before a rate or label request is processed.
Overview
A rate or label request utilizes reference fields to pass critical information—such as Purchase Order (PO) numbers, invoice numbers, internal billing codes, or custom customer messages—so that they are printed directly on the shipping label or returned in the carrier’s billing files. Sometimes, the default reference data submitted from an upstream system (like an ERP or WMS) is missing, improperly formatted, or placed in the wrong field for a specific carrier’s requirements. This is where the Afferent Reference Rule comes in. Unlike Efferent rules that post-process carrier responses, the Afferent Reference Rule pre-processes the request to explicitly modify the reference details (e.g., dynamically injecting a department code, truncating a long PO number, or mapping data between reference fields) before the request is ever submitted to the carrier network. The Afferent Reference Rule is one rule type within an RLD Template.
Afferent Reference Rule Components
Any number of Afferent Reference Rules can be built within an RLD Template to match business objectives. Each Afferent Reference Rule includes the following components.
Match conditions
Match conditions of criteria operators include the following types: All (AND), Any (OR), None (Not).
Match criteria
1. Sender
Sender fields available for match criteria include the follow properties:
- Sender Name
- Sender Company
- Sender Address 1
- Sender City
- Sender State
- Sender Postal Code
- Sender Country
- Sender Residential
2. Receiver
Receiver fields available for match criteria include the follow properties:
- Receiver Name
- Receiver Company
- Receiver Address 1
- Receiver City
- Receiver State
- Receiver Postal Code
- Receiver Country
- Receiver Residential
3. Package
Package fields available for match criteria include the follow properties:
- Package Type
- Package Quantity
- Declared Value
- Actual Weight
- Package Length
- Package Width
- Package Height
4. Line Items
Line Items fields available for match criteria include the follow properties:
- Line Item SKU
- Line Item HS Code
- Country of Origin
5. Options
Options fields available for match criteria include the follow properties:
- Saturday Delivery
- Cash on Delivery
- Cash on Delivery Amount
- Dropoff Type
6. References
References fields available for match criteria include the follow properties:
- Reference 1
- Reference 2
- Reference 3
7. Rate
Rate fields available for match criteria include the follow properties:
- Carrier
- Service Name
- Total Cost
- Zone
- Estimated Delivery Days
8. Time
Time fields available for match criteria include the follow properties:
- Day of Week
- Time of Day
The match criteria types listed above are used within individual rules or can be combined into a single rule to target specific conditions that include several match criteria.
Transformation
Modification of the information included within the payload of the shipment sent to the carrier targets any one of the following types. An is, the contents of the rate request or shipping label creation request includes the information set by the transformation rule.Â
1. Carrier Filter
Set fields avilable within Carrier Filter transformation is as follows:Â
- Allowed Carriers
2. Sender
Set fields available within Sender transformation is as follows:Â
- Sender Residential
3. Receiver
Set fields avilable within Receiver transformation is as follows:Â
- Receiver Residential
4. Package
Set fields available within Package transformation is as follows:
- Package Type
- Declared Value
- Actual Weight
- Package Quantity
- Package Length
- Package Width
- Package Height
5. Options
Set fields available within Options transformation is as follows:Â
- Cash on Delivery
- Cash on Delivery Amount
- Dropoff Type
6. References
Set fields available within References transformation is as follows:Â
- Reference 1
- Reference 2
- Reference 3
7. Account Holder
Set fields available within Account Holder transformation is as follows:Â
- Include or Exclude shipping accounts assigned to shipper
Reference Data Override
This configuration dictates exactly how the reference properties are altered in the outgoing request payload. Once the match criteria are met, the request is transformed to override, inject, or clear specific reference fields—such as Reference 1, Reference 2, or Reference 3—with explicitly defined replacement values before the carrier generates the label.
Afferent Reference Rule Use Cases
Usual use cases for Afferent Reference Rules within an RLD Template are numerous. Some common use cases include the following:
-
Automatically inject a specific internal department billing code into Reference 2 whenever a particular sender origin is used, ensuring accurate carrier invoice reconciliation.
-
Map a specific Line Item SKU or the Receiver Company Name into Reference 1 so that it visibly prints on the shipping label to aid warehouse receiving for B2B customers.
-
Append a standardized message (e.g., “Do Not Leave on Porch” or “Happy Holidays!”) to Reference 3 during specific times of the year or when high-value items are detected in the cart.