Storefront on your Odoo.
Fintech performance, BR tax, no lock-in.
K-Shop is KMEE's headless framework on top of Odoo + Shopinvader + Elasticsearch + Supabase. You run the storefront as your own code, with Odoo's enterprise foundation underneath.
10–16 weeks to go-live · Free 30-min diagnostic
Built on mature open-source stack · Odoo enterprise backend · Supabase auth · Elasticsearch search · Next.js 15 storefront
Why K-Shop
What changes vs Magento/Shopify/VTEX.
Storefront on top of your Odoo
Products, prices, stock, orders and tax records live in Odoo — the single place your team already works. No re-spreading the catalog, no two systems to reconcile.
Fintech-grade performance
Elasticsearch search, Next.js SSR, edge CDN. Lighthouse 90+. Product pages load in <1s even with 100k SKUs.
Integrated visual CMS
Marketing edits banners, copy, product order and switches themes visually — no PR, no deploy, no dev ticket. Inline editor + visual editor + theme switcher built in.
Native Brazilian localization
NF-e, NFC-e, boleto, Pix Cobrança, Pix Automático, CNAB reconciliation: all via OCA l10n-brazil, maintained by the open-source community.
No lock-in
Open source code under your control. Want to switch ERP later? Take the storefront with you? No hostages — you own the storefront.
Who it's for
3 main client profiles.
Odoo company wanting modern storefront
You run Odoo for tax/operations but the storefront is an old, slow legacy instance. K-Shop transforms the experience without swapping ERPs.
Migrations from Magento, Shopify, VTEX
Expensive platform, poor performance, costs scaling with volume. Migrate catalog + customer base to Odoo + K-Shop and eliminate platform fees.
Startup with Next.js needing a serious back-end
You've already done Next.js frontend but tax, multi-company, orders are missing. Odoo + K-Shop delivers the enterprise foundation without building from scratch.
The stack
Each piece open source, mature, with clear responsibility.
Odoo + Shopinvader
Cart, orders, addresses, tax, stock, shipping, leads.
Elasticsearch
Listings, faceted search, related products, brands and categories.
Supabase
Social login, email/password, recovery. Token flows through to Odoo.
Next.js 15
SSR, edge, app router. Tailwind + Radix with HSL tokens.
What's inside
Ready-made components from our UI library and providers.
Complete headless catalog
Products, variants, categories, brands, price by list, stock by branch. Faceted filters, semantic search, related products via Levenshtein.
Cart and checkout
Persistent cart with UUID + expiry. Multi-step checkout, addresses, shipping (integrated carriers), Odoo payment methods.
Secure shopper auth
Supabase for social/email login, with token flowing through to Odoo via OdooHttpClient. HttpOnly cookies, optional mTLS, password recovery ready.
Wishlist and lists
Wishlist with local persistence + sync to Odoo when logged in. Floating FAB, drawer, header badge — full UX.
Customizable theme + visual CMS
HSL tokens compatible with shadcn + integrated visual editor. Marketing edits banners and switches themes without touching code. Inline editing on content blocks.
Admin and operations
Admin session with HttpOnly cookie JWT, IP rate limit, structured logs. Panel for promotions, banners and curation without touching Odoo.
K-Shop vs alternatives
The criteria that weigh most in the decision.
| Criterion | Magento | Shopify | VTEX | K-Shop |
|---|---|---|---|---|
| Platform fee | High + revenue share | Monthly + revenue share | High + revenue share | Zero — you run it |
| Catalog lock-in | Medium | High | High | None (Odoo) |
| Performance (Lighthouse) | 60-75 | 70-80 | 60-75 | 90+ |
| Visual CMS / WYSIWYG | Page Builder | Theme Editor (Liquid) | Site Editor (IO) | Visual editor + inline + theme switcher |
| Checkout customization | Possible with effort | Limited (Liquid) | Limited (IO) | Total — your code |
| BR tax localization | Paid plug-in | Limited | Native good | Native via OCA l10n-brazil |
| Multi-CNPJ / multi-store | Yes with complexity | Yes (Plus) | Yes | Native Odoo multi-company |
| Open source | Partial (CE) | No | No | Yes — KMEE GitHub |
How KMEE delivers
4 stages, from diagnostic to go-live.
Discovery
We map your current Odoo, catalog, customer base, checkout flow. 1-2 week package.
1–2 weeks
Design and architecture
Storefront wireframes, data architecture, auth and checkout flows. You approve before we code.
2–3 weeks
Implementation
Iterative coding with weekly sprints. You follow in staging from day 1.
6–10 weeks
Go-live and support
Data migration, supervised deployment, and dedicated support for the first 30 days. Optional monthly maintenance.
Ongoing
Frequently asked questions
What we hear most in diagnostics.
I already use Magento/Shopify/VTEX. Worth migrating? ▼
Depends on volume and pain. Above $1M annual GMV, platform fees + revenue share usually pay back the migration in 12-18 months. Below that, it makes more sense if performance or limited customization is blocking growth. Either way, we calculate the payback in the diagnostic — no commitment.
Time from contract to go-live? ▼
10–16 weeks for a B2C storefront with full checkout. B2B with quotes, approval levels and price lists per customer is 14–20 weeks. Large catalog migration (>50k SKUs) or complex tax rules can add 2–4 weeks.
What if I already have Odoo? Do you reuse what's there? ▼
Yes, that's the ideal case. Catalog, prices, stock, tax, multi-company, shipping — everything already configured in your Odoo remains the source of truth. K-Shop only adds the storefront layer on top.
Who owns the code? ▼
You. The k-shop libraries are maintained by KMEE on GitHub and installed as project dependencies. Storefront customizations stay in your repo, under your control. No traffic-based licensing, no monthly software rent.
What about support? Do you maintain the store for me? ▼
We offer monthly support packages (8h, 20h, 40h) with SLA. Includes fixes, incremental evolutions, monitoring. If you prefer to keep it in-house after go-live, we train your team and hand over the documentation for full autonomy.
Does it work for B2B with quotes? ▼
Yes. We support classic B2B flow: customer requests quote → Odoo generates proposal → customer approves online → quote becomes order. Prices per customer, payment terms per customer, internal approval levels — all via Odoo.
Ready to move your store to headless?
In 30 minutes we map your scenario (volume, current platform, existing Odoo) and leave with a realistic plan. Free diagnostic.
Request the diagnostic
Tell us about your current platform, approximate volume and whether you already run Odoo. We'll get back within 1 business day.