Omnichannel + WooCommerce Colombia
Omnichannel brain (owned stock + dropship) with HITL panel, Dropi radar, catalog API and Colombia-only Woo store.
Keep marketing separate from checkout: the omnichannel brain decides what to publish; WooCommerce Colombia charges. Includes opportunity radar, AI enrich with template fallback, and Tecnopets as a Woo vertical.
The challenge
- 1Hybrid owned stock + dropship.
- 2No junk publish: score + human approval.
- 3Woo REST/webhooks integration.
- 4Day-to-day ops via panel, not only scripts.
The approach
Domain + worker
Pricing/inventory packages and radar worker.
HITL panel
Jinja/HTMX to approve winners before publish.
Woo as checkout
woo-store-co as Colombia canonical store.
Enrich with fallback
Optional AI; template if no key—resilience.
Dropi feeds → worker/scoring → HITL panel → FastAPI catalog → WooCommerce CO, with Postgres/Redis.
System layers
- 01Feeds / Dropi
- 02Worker + scoring
- 03Operator HITL panel
- 04FastAPI catalog
- 05WooCommerce REST
- 06Postgres + Redis
Applied stack
- Python
- FastAPI
- HTMX
- Postgres
- Redis
- WooCommerce
- Docker
Design decisions
HITL vs full-auto publish
Protects margin and catalog reputation.
Woo as canonical checkout
Landing sells services; store sells products.
Package monorepo
Clear domain / api / worker boundaries.
Outcomes
- HITL
- Radar → score → approval
- Woo
- Operable catalog publish
- CO
- Colombia-only checkout
Key points
- Commerce brain with human control where margin matters.
- Clean split between landing and store.
- VPS-ready compose stack.
Fit / how to hire
Hire this if you need a commerce integrations lead who knows where to put human control without slowing the business (marketplaces, Woo, pricing). We start with a channel map, move to a panel MVP, and automate in stages.
Book a technical call
