Back to all work

Professional, 2026

Carrier manifest import and transformation

Automated daily import of carrier shipment manifests (fixed-width TXT and JSON) into a legacy TMS with rule-based code mapping and per-shipment error logging.

Role

Developer

Stack

C# / .NET / SQL Server

Problem

A parcel carrier delivers daily manifests in two formats. The legacy TMS expects single-character product and billing codes and a fixed schema that could not change.

What I did

  • Parallel import paths (TXT and JSON) into a staging table, run as batches and compared against each other.
  • Explicit lookup-table mapping of new carrier codes onto the legacy code scheme at the transformation layer; fallbacks in the rule engine for missing customs data.
  • Per-shipment, event-level error log exportable by operations.

Result

Manual re-keying removed; discrepancies between formats visible and traceable per shipment.