Lotvera, a B2B SaaS Platform for Liquidation Data
B2B SaaS and browser automation platform for processing complex liquidation and inventory data, transforming supplier workflows into structured ERP-ready outputs.
Visit LotveraSaaS Platform
B2B platform that collects, normalizes, prices, and exports liquidation and inventory data.
Chrome Extension
Manifest V3 bridge that automates authorized supplier-portal work inside the existing browser session.
~2h → ~45m
Processing time reduced by more than 60% for a workflow of 200+ shipments and about 600 pages.
Context
Lotvera is a B2B SaaS platform for automating complex liquidation and inventory-data workflows. It collects data from authorized supplier sources, processes and normalizes large datasets, applies configurable business and pricing rules, and generates structured outputs ready for ERP systems and sales channels.
A custom Chrome extension, built with Manifest V3, bridges authenticated supplier portals with Lotvera and automates work that would otherwise take hundreds of repetitive browser operations. The extension does not replace authentication or bypass access controls. It runs inside the user's existing authorized session, and it does not store source passwords.
Problem
Processing a liquidation deal often means opening a supplier portal, moving through hundreds of shipments and nested pages, downloading spreadsheets and product images, cleaning inconsistent data, applying pricing formulas, and preparing a file an ERP or sales channel can import.
In one production workflow, that meant more than 200 shipments and about 600 pages across three data levels. The work had to finish inside a limited daily window, and it took about two hours.
My role
Founder, software architect, and full-stack developer. I designed the product, the data-processing pipeline, and the browser integration, and I built the Laravel SaaS platform and the Chrome extension.
- Product design for a real liquidation and wholesale data workflow
- SaaS architecture with separated tenant data
- Laravel backend, Filament administration, and queue-based processing
- Manifest V3 Chrome extension for authorized browser-session collection
- Configurable cleaning templates, pricing formulas, field visibility, validation, and exports
Solution
I designed and developed Lotvera as an automation layer around that process. Instead of treating every supplier file as an isolated spreadsheet, the platform runs a structured pipeline: collect, normalize, clean, validate, apply reusable business and pricing rules, review, and export.
The interactive work stays in the authorized browser session. Heavier processing continues in the background, so a large workflow is not trapped inside a single request. The result is a repeatable pipeline rather than a collection of manual operations.
Implemented scope
- Authorized data collection through the Chrome extension and platform integrations
- Normalization of inconsistent supplier files into one internal data model
- Reusable cleaning and mapping templates
- Configurable pricing and profit formulas, so different deal types can use different calculations
- Control over which fields appear in the final dataset and which stay hidden
- Preview and validation before the final output is generated
- Structured exports for ERP systems, internal inventory, and sales-channel workflows
- Multi-level shipment and product collection, including available files and product images
- Product and inventory mapping, with brand and item-level restrictions
- Background processing through queues, with resumable long-running workflows
- Processing history, and separation of tenant data
Key engineering decisions
- Treat the work as a deterministic pipeline, not as a file download: browser automation, collection, normalization, validation, business rules, pricing, then export.
- Use a Manifest V3 extension as the bridge where a supplier portal does not expose the needed data through a convenient API.
- Keep the extension inside the authorized browser session. It does not replace login, bypass access controls, or store source passwords.
- Run heavy processing on background queues so a large workflow can continue without blocking the user in one browser request.
- Keep pricing formulas, cleaning templates, and visible fields configurable instead of hard-coding one calculation for every deal.
Architecture
Lotvera is a Laravel SaaS application with a separate Manifest V3 Chrome extension. The extension collects data inside the user's authorized supplier-portal session and sends structured payloads to the backend. Interactive work stays in the browser. Larger jobs run on Redis-backed queues through Laravel Horizon, with MariaDB for application data and Cloudflare R2 for stored files.
A single deal can cross hundreds of pages, several hierarchy levels, different file formats, product metadata, images, pricing rules, restrictions, and destination-specific requirements. The pipeline keeps that workflow recoverable and manageable.
- Browser automation
- Data collection
- Normalization
- Validation
- Business rules
- Pricing
- Export
Technologies
Outcomes
- The same production workflow dropped from about two hours to about 45 minutes.
- Processing time was reduced by more than 60%.
- More than 200 shipments and about 600 pages across three levels became a repeatable pipeline instead of a manual pass through the portal.