Onlihub
Technical ownership of a commerce platform
E-commerce & marketplace integrations
A store connection should lead to a usable business process: products match, inventory is understandable, and orders can move toward fulfillment. As CTO at Onlihub, I work across the domain model, backend and integration boundaries. The difficult part is keeping several independently changing systems consistent enough to operate.
How I approach the work
Define ownership and mappings
Model the product-to-listing and order-to-fulfillment relationships. Keep external IDs and provider capabilities explicit. Decide which side owns inventory, price and each order status before implementing synchronization.
Make background work recoverable
Record intent, assign bounded worker ownership and preserve retry state. The Onlihub case shows idempotency keys, an outbox and PostgreSQL job leases. A local job claim does not guarantee exactly-once effects at an external provider.
Design for reconciliation
Webhooks provide timely signals; periodic checks and explicit failure states help reconcile missed changes. Separate provider adapters from domain services so marketplace-specific behavior does not spread through the whole application.
A decision to make early
Real-time everywhere is rarely the right promise. Agree on acceptable delay, API limits and recovery rules per operation. Public integration listings in the linked cases verify the products; they are not personal certifications.
Relevant work
MySellerHub
A shared model across independent commerce channels
Onlihub Catalog
Different data paths for different workloads
Zipurch
Making commerce activity visible on a map
Tell me about your task
Name the platforms you need to connect, the data that must move and where synchronization currently breaks. Include rough volumes if available; credentials are not needed to discuss the architecture.
Discuss the task