From 20 Hours to 4: How We Automated Our Parts Ordering Pipeline

Our appliance repair business processes 50+ parts orders weekly across multiple suppliers. I was spending around 4 hours daily just placing orders and tracking shipments—navigating supplier portals, checking FedEx, trying to consolidate shipments. With everything else I'm building for the business, that time wasn't sustainable.

So I built an automation system to handle it. Here's what I learned.

The Problem

Our ordering workflow had the usual pain points:

• Multiple supplier portals (Encompass, Marcone) with no unified view
• Manual FedEx tracking checks for dozens of shipments
• Techs waiting 30-40 minutes at the local Marcone branch every morning to pull parts
• No centralized visibility into order status and backorders
• Data scattered across spreadsheets, emails, and browser tabs

Custom development felt like overkill for what was fundamentally an integration problem. I built it in 3 weeks using low-code tools.

The Architecture

I engineered a low-code automation stack that orchestrates multiple systems into a single, intelligent pipeline:

Layer	Technology	Role
Command Center	Airtable	Order tracking, technician management, dashboards
Automation Engine	n8n (self-hosted)	Workflow orchestration, API calls, business logic
Parts Ordering	Encompass API	Direct order submission, availability checks
Shipping	FedEx Track API	Tracking updates, delivery estimates
Alerting	Gmail API	Error notifications

What I Built

Direct API Order Submission

Orders flow from Airtable directly to Encompass's API, bypassing the web portal. A 5-minute manual process now takes seconds.

Switched to Encompass for API Access

Moving to Encompass meant techs no longer wait 30-40 minutes at the local Marcone branch every morning to pull parts. Parts ship directly to them. At $139.50 per call, running 8 calls a day instead of 7 adds up fast.

Unified Multi-Supplier Tracking

All orders appear in one place regardless of supplier. Technicians see their parts; management gets the full picture.

Automated Tracking Updates

FedEx tracking refreshes three times daily. Technicians know when parts are out for delivery without checking manually.

Smart Piggyback Restocking

When a customer order ships, the system automatically checks if the technician has any restock items waiting. It queries the Encompass API to see if those parts are available at the same warehouse. If they are, it consolidates them into the same shipment—no extra shipping cost, no manual coordination. Restock items that would've sat waiting now piggyback on customer orders automatically. Shipping cost is covered by the customer's COD order.

Backorder Monitoring

The system checks backordered parts daily and updates statuses when inventory becomes available.

Error Handling

Failed orders (rate limits, API issues, invalid part numbers) get logged and trigger alerts. I fix exceptions instead of discovering them later.

Delivery Notifications

When FedEx shows "Delivered," customers and our parts team get notified automatically. This helps reduce "where's my part?" callbacks since customers already know their order has arrived.

Results

Metric	Before	After
Weekly Processing Time	~20 hours	~4 hours
Weekly Revenue Per Tech	~$4,880	~$5,580

That extra call per tech per day represents about $700/week in additional revenue. I also eliminated spreadsheet maintenance entirely—order statuses update automatically, and everything lives in one system instead of scattered across tabs and emails.

What I Learned

The hard parts weren't the individual integrations—they were the edge cases: rate limiting, duplicate prevention, handling partial failures, and keeping authentication tokens fresh. Once I solved those problems for my own operation, the framework became reusable.

This approach works for any business dealing with multi-supplier coordination, manual portal workflows, or shipping logistics. The specific implementation varies, but the architecture pattern holds.