// the find
i-love-flamingo/flamingo-commerce
Flexible E-Commerce Framework on top of Flamingo. Used to build E-Commerce "Portals" and connect it with the help of individual Adapters to other services.
Flamingo Commerce is a Go e-commerce framework built on the Flamingo web framework, using DDD and ports-and-adapters to keep your business logic decoupled from whatever backend (Magento, custom microservices, etc.) you plug in. It targets teams replacing a monolithic e-commerce platform who want Go performance without building cart, checkout, and product models from scratch. You still write the adapters yourself — this gives you the domain skeleton, not a turnkey shop.
The domain model for cart is genuinely well thought out: multi-delivery, multi-payment-transaction, gift cards, vouchers, and loyalty prices are first-class concepts rather than bolted-on afterthoughts. The ports-and-adapters structure is consistent across every module, so swapping a Magento adapter for a custom one is a real thing you can do, not just a marketing claim. Fake adapters ship with every module, which means you can run the full application stack in tests without any external service. The state-machine checkout (with PlantUML diagrams committed to the repo) makes the order flow auditable and easy to extend without touching unrelated states.
The API is self-described as Beta and has been for years — the README warns you'll need to adjust code on updates, which is a real adoption risk for a production commerce system where a breaking cart model change is painful. It's tightly coupled to the Flamingo framework, so if Flamingo's DI system or template engine doesn't fit your architecture, you can't use just the domain models. Community size is thin at 588 stars and 95 forks; finding someone who has already solved your specific adapter or payment integration problem is unlikely. Documentation lives across scattered per-module READMEs and an external docs site, with no unified API reference — you'll be reading source more than docs.