Implementation / 2026

RV Inventory Sync Automation

Automated RV inventory sync and feed generation between listing and dealer platforms while preserving a headful, human-in-loop flow for 2FA, CAPTCHA, and UI-only steps.

Client

Vehicle Dealership Group

Technologies

Python 3.12+
Playwright
Persistent Browser Profiles
Manifest Pipelines
Google Merchant Feeds
Artifact Logging

Human-in-loop

Automation style

RV listings

Source truth

Merchant feeds

Extra output

Implementation

Project Type

01 – Challenge

The problem

Inventory parity across external listing systems and the dealer platform was manual, repetitive, and easy to drift out of sync. The workflow also had to survive real-world UI friction like CAPTCHA, 2FA, modal-only editing, and media handling.

02 – Approach

The strategy

Designed the automation to respect reality instead of pretending the browser was optional. Used persistent profiles, staged manifests, modal-safe runbooks, and artifact capture so the workflow could stay reliable even when full headless automation was not practical.

03 – Solution

What was built

Built a Playwright-based sync system with RVTrader manifest export, unit scraping, InteractCP update flows, delta handling, artifact logging, and Google Merchant feed generation from the synchronized inventory.

04 – Outcomes

The results

Reduced repetitive cross-platform inventory maintenance work

Handled login friction and UI-only steps without throwing the whole workflow away

Created a repeatable manifest-driven process for sync and feed generation

Improved recoverability when a run hits selector drift or auth interruptions

05 – The Story

How the work actually came together

This is a good example of automation that works because it respects the constraints of the real system. The browser, the modal flow, and the login friction were part of the job, not bugs to ignore.

So the design stayed headful where it needed to, preserved profiles, and treated artifacts and runbooks as first-class parts of the system.

That makes the automation slower on paper than a demo-perfect API integration, but much more useful in production.

It is the difference between flashy automation and automation that the business can actually rely on.

What mattered

The point was not to install software and walk away. The point was to create an operating layer the business could trust, improve, and own after handoff.

That meant documenting the system, making the workflow legible, and removing the extra work that shows up when teams are forced to manage operations across disconnected tools.

Next project

Membership-Backed Marketplace Platform

Continue through the work to see another example of strategy, systems, and execution translated into a better operating result.

Think of me as your Director of Infrastructure and Operations à la carte. With extensive experience and a hands-on approach, I provide customized solutions to help your business grow and thrive.

Navigate

Remote / United States

Availability

Currently accepting new engagements