Commerce operations had to stay consistent across different product models, warehouses and external systems.
02 / How I approached it
How I approached it
After the lead developer left, I took over development and redesigned the application and database architecture. I implemented an asynchronous FastAPI backend, complex PostgreSQL queries and integrations across commerce and warehouse systems, while coordinating the team and advising the CEO on feasibility.
System flow
Suppliers
Shared catalog
Inventory & orders
Fulfillment & tracking
What that means in practice
Architecture & decisions
01
From developer to technical owner
I joined the startup working alongside an experienced lead. When they left, I took responsibility for the architecture, database and backend, coordinated a small cross-functional team and guided the product through implementation, support and further development. Discussions with the CEO connected business ideas to technical feasibility and delivery decisions.
02
One model across different channels
The original platform was designed for a broader multichannel scenario: a product from one source could be published into another channel. I worked with Amazon, Walmart, eBay, TikTok Shop, Shopify and warehouse integrations, reconciling products, external identifiers, real and virtual warehouses, stock, orders and tracking. That original scope helped give rise to MySellerHub as the products evolved.
03
Asynchronous services and complex SQL
I built and documented API methods with FastAPI, asynchronous processing, threads and queue management. PostgreSQL work included dynamic queries and optimization over large datasets. Recurring-task tooling, parsers and PowerBI analysis complemented the core backend, so integration work and operational processing had their own supporting tools.
04
Architecture that evolved with the product
The platform grew into related products with different responsibilities: supplier operations, retailer workflows and the dedicated high-load catalog. I worked on both architecture and implementation, including subscriptions and one-time payments. Onlihub later appeared as an Amazon MCF integration; that product milestone is separate from my own engineering responsibilities.
03 / The outcome
The outcome
The work connected the product lifecycle from catalog and inventory to orders, fulfillment and tracking, with ownership extending beyond individual services.