FA©26

Case study — 2026

NDA · Automotive inventory client

Automated FTP Inventory Feed Handler

Role
Full-stack · Data pipelines
Status
Delivered to the client
In one line
Inventory files from FTP drops, mapped and sent on, on schedule.

An inventory-ingestion dashboard. Scheduled jobs pick up inventory files from FTP drop points, apply field-mapping rules and send the rows on through verified connectors. Every run is logged with its rows in, rows sent and duration.

client build · under NDA
Feed handler overview: cards for FTP accounts, rules, connectors and rows sent, above a table of recent scheduled ingestion runs, all successful. Account and file names are blurred.
The overview screen. Account and file names blurred.

01 — The problem

Inventory feeds arrive as CSV files on FTP servers, each in its own format. Someone has to pick them up, fix the columns and pass them on before the listings go stale, and nobody notices when a feed quietly stops.

Client work under NDA. The system is described in full; the names stay private.

02 — What I built

  • Ingestion health

    FTP accounts, rules, connectors and rows sent in the last 24 hours, at a glance.

  • Run history

    Every scheduled ingestion with status, rows in, rows sent and duration.

  • Accounts, connectors and rules

    Manage FTP accounts, connectors, field-mapping rules and users.

03 — How it runs

The flow — Scheduled FTP pickup, then Field-mapping rules, then Verified connectors, then Rows sent on, then Run logged.
  1. Scheduled FTP pickup
  2. Field-mapping rules
  3. Verified connectors
  4. Rows sent on
  5. Run logged

04 — Proof

  • Every run logged

05 — Stack

  • React + Vite
  • TypeScript
  • Tailwind CSS
  • shadcn/ui
  • Vercel rewrites to a VPS API

Next project

Skip-Trace Orchestration Service

A GHL contact event starts a tiered vendor waterfall, under a cost cap.