System Sequence
Inbound Payload Enrichment & Rule Execution Pipeline
When an order arrives from an ERP or e-commerce channel, profile-based rules apply transformation schemas in four distinct evaluation stages.
01
Customer Key Extraction & Profile Lookup
Middleware captures the customer identifier or account number from the incoming order header and queries the profile store to retrieve associated shipping presets.
Data Payload Requirement:
{ "customer_id": "CUST-9842", "order_type": "B2B_STANDARD", "delivery_terms": "DDP" }
02
Dynamic Attribute Evaluation & Parameter Merging
Retrieved profile defaults are matched against active line items, parcel thresholds, and destination flags to produce resolved service attributes.
Mapping Condition:
MATCH IF (profile.default_carrier == "UPS" AND package.weight > 70 LBS) THEN SET accessorial = "HEAVY_PACKAGE"
03
Policy Validation & Exception Trapping
The rule engine checks for policy conflicts, such as signature required mismatch, unsupported Saturday delivery zones, or PO Box restrictions.
Validation Trigger:
EVALUATE (recipient.address_type == "PO_BOX" AND profile.service_code != "SUREPOST") -> TRIGGER EXCEPTION_04
04
Final Manifest Payload Compilation
Enriched data records with applied account defaults, accessorial codes, and billing configurations are compiled into the final shipping database format.