Platform

Solutions

Resources

Pricing

Start Free

Integration

Native connector

Kōbō and Odoo

Keep product development in a PLM built for fashion, and let Odoo run stock, purchasing and accounts. One product master, pushed across on your terms.

Book a Discovery Call Start Free Trial

Settings / Odoo

Styles and variants

1,009 SKUs

Synced

Suppliers

10 vendor records

Synced

Purchase orders

Draft in Odoo

Synced

Price lists

FOB, landed, wholesale, retail

Synced

One Way, On Purpose

Kōbō is the product master and Odoo receives. An ERP import can never overwrite a spec your factory is working to.

You Press Sync

Nothing moves until somebody decides it should. Check the data, then push it. Full history of what went across and when.

No Connector Fee

API access and integrations are included on every plan. You pay for Kōbō seats and for Odoo, nothing in between.

The mapping

Your product data, on Odoo's own models.

The integration is first-party, not a Zapier recipe or a third-party connector. It maps Kōbō records onto the standard Odoo models your accountant and warehouse already use.

In Kōbō	In Odoo	Notes
Style	product.template	With size and colour attributes, so Odoo generates the variant matrix it expects.
Style SKU	default_code on product.product	Your Kōbō SKU pattern becomes the Odoo internal reference.
Barcode (EAN13)	Odoo barcode field	Assigned from your own GS1 pool in Kōbō, carried across per variant.
Supplier	res.partner vendor	Including contacts and addresses, so purchase orders have somewhere to go.
Purchase order	purchase.order	Optional auto-confirm, or land it as a draft for your team to approve.
FOB, landed, wholesale and retail prices	Odoo price lists	Creates Kōbō Wholesale and Kōbō Retail lists so margin reporting works in Odoo.
Historical catalogue	One-time migration	Bulk-push an existing season rather than starting Odoo from empty.

How it works

JSON-RPC, and a button you press.

Kōbō talks to Odoo over JSON-RPC, the interface a standard Odoo install exposes out of the box. You connect once with your Odoo URL, database name and an API key, and Kōbō validates the connection before it writes anything.

The sync is push-only and manual by design. Kōbō is the product master; Odoo receives. Nothing moves until somebody presses sync, which is exactly what the first customer running this asked for. In his words, he wanted to check the data before pushing it. You get a sync overview, a per-entity breakdown and a full history of what went across and when.

Each entity has its own job, so you can push suppliers today and hold the purchase orders until your chart of accounts is ready. Nothing is all-or-nothing.

Connect once

Odoo URL, database name and an API key. Kōbō validates before it writes anything.

Review the data

Check the styles, costs and suppliers in Kōbō while they're still easy to fix.

Push per entity

Suppliers today, purchase orders when your chart of accounts is ready. Nothing is all or nothing.

Read the history

Sync overview, per-entity status and a log of every push.

Getting connected

Minutes to connect. One conversation to get right.

Connecting takes a few minutes. Getting the mapping right takes a conversation, and we do that part with you.

Connect your Odoo instance

In Kōbō, open Integrations and enter your Odoo URL, database name and API key. Kōbō tests the connection and reports back before storing anything.

Agree the boundary

Decide what Odoo owns and what Kōbō owns. The usual split: Kōbō holds styles, BOMs, samples, specs and supplier development; Odoo holds stock, purchasing, invoicing and accounts.

Check your SKU pattern

Your Odoo internal reference comes from the Kōbō SKU pattern, so set that first. Changing the pattern later rewrites SKUs but keeps the barcodes already attached to them.

Push suppliers, then products

Suppliers first so purchase orders have vendors to attach to, then styles and variants. Use the one-time migration if you're bringing an existing catalogue across.

Decide on purchase orders

Choose whether Kōbō purchase orders auto-confirm in Odoo or arrive as drafts. Most teams start with drafts and switch once they trust the flow.

Good fit

Built for brands already on Odoo.

You already run Odoo, or you're about to, and you don't want to rebuild product data by hand inside it

Your team makes tech packs, tracks sample rounds and works with external factories

You need SKUs and barcodes generated once and used everywhere

You want margin reporting in Odoo built from real BOM costs, not estimates

You would rather your designers never open an ERP

Limits, honestly

What to plan around.

Push-only today

Data flows Kōbō to Odoo. If you need stock levels flowing back into Kōbō, tell us, because that's a roadmap conversation rather than a setting.

Manual trigger

Syncs run when someone presses the button. That's deliberate, but it means it isn't a live mirror.

JSON-RPC only on vanilla Odoo

A standard Odoo install exposes JSON-RPC, which is what we use. If your instance is heavily customised, we will want to look at it together first.

Odoo trial databases sleep

If you're testing on an Odoo SaaS trial, the database can go dormant and the first sync attempt may need a retry.

Common questions

Before you connect Odoo.

Does Kōbō replace Odoo?

No, and it isn't trying to. Odoo is a general business system covering accounting, stock and purchasing. Kōbō is a fashion PLM covering styles, BOMs, tech packs, sample rounds, points of measure and supplier collaboration. Brands that run both keep product development in Kōbō and let Odoo do the accounting it's good at.

Which direction does data flow?

Kōbō to Odoo. Kōbō is the product master and Odoo receives styles, variants, SKUs, barcodes, suppliers, purchase orders and price lists. The sync is push-only by design, so an ERP import can never overwrite a spec your factory is working to.

Is the sync automatic or manual?

Manual, and deliberately so. Somebody presses sync when the data is ready. You get a sync overview, per-entity status and a full history of what was pushed and when.

What happens to my SKUs and barcodes?

Your Kōbō SKU becomes the Odoo internal reference on each product variant, and the barcode goes into the Odoo barcode field. Barcodes come from your own GS1 pool loaded into Kōbō, so they stay yours. Changing your SKU pattern later rewrites the SKU but keeps the barcode attached to it.

Can I migrate an existing Odoo catalogue?

Yes. There's a one-time historical migration for bulk-pushing an existing season, so you aren't starting Odoo from an empty product list or hand-keying a back catalogue.

Do I need a developer to set this up?

No. You need your Odoo URL, database name and an API key, which an Odoo admin can generate. The part worth doing with us is agreeing which system owns what, and that's a conversation rather than a configuration task.

What does the Odoo integration cost?

API access is included on every Kōbō plan, so there's no separate integration fee or per-connector charge. You pay for Kōbō seats and for Odoo separately.

Has anyone actually run this in production?

Yes. The integration was built with a customer running Odoo alongside Kōbō, and it has pushed real products, price lists, suppliers and purchase orders into a live Odoo instance.