⭐ Featured Project

Device Ordering & Inventory Automation

Automated the integration of device orders and inventory data into Salesforce, replacing siloed tracking systems with a centralized, up-to-date operational view.

Technologies & Tools

Google Apps ScriptSalesforce APIOAuth 2.0ETL

📊 Impact: Real-time inventory visibility across operations

Problem

Tech Goes Home distributes laptops, Chromebooks, hotspots, and other devices to learners as part of its digital equity programs. However, device order details, inventory counts, and fulfillment statuses lived across multiple disconnected systems, making it difficult to track orders end-to-end and maintain accurate inventory levels. Device orders were tracked across multiple spreadsheets and vendor systems, inventory counts were frequently out of date, order statuses required manual follow-ups and reconciliation, and leadership lacked visibility into device distribution at scale.

My Role

I owned the solution end-to-end, including designing the ETL architecture and data model, integrating multiple order and inventory data sources, automating data refresh and synchronization into Salesforce, ensuring data accuracy, idempotency, and update logic, and supporting downstream reporting and operational workflows. This was a core operational system, not a reporting-only solution.

Solution

Designed and built an automated ETL pipeline that integrated device order data from multiple sources into Salesforce, creating a central, up-to-date system of record for ordering, fulfillment, and inventory tracking. Although this project reused the same technical tools as previous integrations, it addressed a fundamentally different operational problem with higher complexity and broader organizational impact.

Architecture

High-Level Data Flow

1

High-Level Data Flow: (1) Scheduled Apps Script jobs pull device order and inventory data from multiple sources

2

Data is normalized and mapped to Salesforce objects

3

OAuth-secured API calls upsert records into Salesforce

4

Existing records are updated to reflect latest order and fulfillment status

5

Salesforce becomes the authoritative source for device operations. Reused proven OAuth + API patterns from prior automations, reducing development risk and maintenance overhead. Designed ETL logic to update only changed records, improving performance and reliability.

Key Design Decisions

🔹Single Source of Truth - Salesforce designated as the system of record, eliminating conflicting inventory counts
🔹Reusable Integration Patterns - Reused proven OAuth + API patterns from prior automations
🔹Incremental Updates - Designed ETL logic to update only changed records for better performance

Results

  • Created real-time visibility into device orders and inventory
  • Reduced manual tracking and follow-ups by operations staff
  • Improved fulfillment accuracy and planning
  • Enabled scalable device distribution across programs
  • Strengthened Salesforce as the operational backbone

Technologies Used

Google Apps ScriptSalesforce APIOAuth 2.0ETLData Integration