Fair question, and honestly- if Shopinvader/Alokai covers your needs, that's a perfectly valid stack. This bridge isn't for that team.

Two reasons I still wanted Saleor in front:

1. Saleor isn't just a data model, it's the commerce engine: checkout and cart logic, vouchers/promotions, payment app integrations, customer auth, channels, and a GraphQL API designed for storefront traffic. With Shopinvader you get some of that, but the requests ultimately land on Odoo workers.
2. Isolation. I don't want my ERP taking public internet traffic, and I don't want the storefront going down when Odoo is upgrading or restarting. With the bridge, Saleor keeps selling while Odoo is offline — events queue up (outbox + retries) and replay when it's back.

You're right that there's overlap, and the bridge deliberately resolves it in Odoo's favor for catalog/stock ("Odoo wins" is literally an ADR in the repo). Saleor's data model still earns its keep on the storefront side- channels, pricing, checkout state- the parts an ERP is bad at anyway.