Diesel Auto Power needed a cleaner way to receive outside inventory, tie it back to Fishbowl, match it into Miva, and turn it into customer-facing website visibility. This project turned a disconnected process into a structured inventory pipeline with a real operational backbone behind it.
Diesel Auto Power inventory flow
Diesel Auto Power already had inventory data inside Fishbowl, but outside vendor inventory and website visibility were still disconnected. Incoming files could arrive in inconsistent formats, regional ownership needed to stay controlled internally, and the website had no clean way to show meaningful availability to customers.
Inventory lived internally, but the path from outside supplier files to usable website visibility was fragmented.
The fix had to be more than a front-end tweak. The intake, matching, and website layers all had to work together.
The visible website result only worked because the messy pieces underneath it were solved in the right order. Intake had to be controlled first, ownership had to stay inside Fishbowl, and matching into Miva had to be reliable enough to publish customer-facing inventory.
I built the intake foundation around a secure SFTP workflow tied back to vendor setup inside Fishbowl.
Once intake was controlled, the next problem was turning outside files into usable website data without trusting fragile file structure too much.
With the backend path validated, website inventory could be pushed into a display layer customers could actually use.
Outside inventory comes in through the controlled SFTP intake path.
Vendor setup and region ownership stay managed inside Fishbowl.
Incoming inventory is normalized and tied to the right website products.
The website can now surface meaningful availability to the customer.
Once the update path was working, the remaining decisions became mostly visual. The same backend process could support different display directions without rebuilding the actual workflow underneath it.
The site could now display meaningful availability information instead of leaving that part invisible to the customer.
Different visual treatments could be explored without changing the intake and matching foundation behind them.
The intake foundation was built, the Miva update path was validated, and the product-page display logic was working. At that point, the remaining choice was mostly visual rather than technical.
I build practical workflows that connect the messy parts between ERP, inventory, file intake, and the systems people actually use.