Kōbō vs Zedonk

The key difference: Kōbō is a product-first platform built by a fashion founder — design and development flow naturally into production, inventory, and sales. Zedonk is an established ERP that recently added PLM capabilities with Z.Studio. One starts with the product, the other starts with the business.

At a Glance: Kōbō vs Zedonk

A side-by-side look at pricing, capabilities, and approach. The table below covers every major feature area so you can see exactly where each platform stands.

What Is Zedonk?

Zedonk is a UK-based fashion ERP platform founded in 2006. Their core strength is operations — production, inventory, and sales order management. In 2024, they launched Z.Studio, a lightweight tech pack tool, but product development remains secondary to their ERP focus.

Zedonk Characteristics

Z.Studio: What It Adds and Where It Falls Short

Z.Studio is Zedonk’s answer to the PLM gap in their platform. Launched in 2024, it bolts a tech pack builder onto the existing ERP. For brands who already run on Zedonk and just need to capture basic specs in the same system, that’s genuinely useful. For brands evaluating PLM as a primary purchase, Z.Studio is closer to a feature than a product.

What Z.Studio handles well: single-page tech packs with construction notes, simple BOM entry tied to existing material records, PDF export for supplier sharing, and integration with sample tracking inside Zedonk’s existing workflow. If your supplier list is already in Zedonk and your team already lives there, the friction of capturing a tech pack is reduced.

Where it falls short for product teams: there’s no design ideation surface, no version-controlled multi-colourway management, no integrated supplier portal where factories see specs and submit revisions, and no in-line sample comments or photo capture against specific style versions. Sample rounds still happen via email and PDF exports. The fashion-specific BOM features that dedicated PLMs invest in heavily — landed costing across multiple currencies, automatic component substitution, supplier-side cost negotiation — aren’t in Z.Studio yet.

In practice, Z.Studio works as a tech-pack add-on for Zedonk customers, not as a competitive PLM. Brands buying Kōbō are typically replacing both an ERP-with-Z.Studio setup and a parallel Illustrator-plus-Excel tech-pack workflow with a single product-first platform.

What Is Kōbō?

Kobo is a complete product lifecycle management platform built by a fashion founder who spent a decade living the spreadsheet chaos. It covers the entire journey — from initial design concept through production, inventory, and wholesale delivery — in one integrated system with a design-forward interface creative teams actually want to use.

Kōbō Strengths

Pricing & Total Cost

Both platforms publish entry-level prices, but the comparison only makes sense once you map them to the modules your team actually uses.

Zedonk’s modular tiers

Zedonk’s Essential plan starts at £159/month and scales up through Professional (~£395) and Enterprise (~£1,395) tiers, with additional fees for Z.Studio and module add-ons. The tiers gate features rather than seats — so a small team with all the modules turned on can cost more than a larger team on a lower tier with fewer modules. Pricing isn’t per-user, which sounds friendly but means you can’t scale costs linearly with headcount. To compare apples-to-apples with a per-user PLM, you have to estimate which tier you’ll outgrow and when.

Kōbō’s per-user pricing

Kōbō publishes a flat per-user price: $140/user/month for Studio Lite (design + development), $210 for Studio Pro (adds planning + custom workflows), $90 add-on for Ops & Supply (production + inventory), and $160 for Sell & Deliver (wholesale). Annual billing saves 15%. Supplier seats are free, regardless of how many factories you work with.

For a typical small fashion brand — 4 designers + 2 production team + 8 supplier seats — Kōbō runs around $560-$840/month all-in. For the same setup on Zedonk, you’d likely sit on the Professional tier with Z.Studio add-on, similar nominal cost but with the per-tier feature-gating logic complicating any expansion.

The Core Difference: Product-First vs ERP-First

The fundamental distinction between Kōbō and Zedonk comes down to where each platform starts. This shapes everything — the interface, the workflow, and the features that get the most attention.

Kōbō Philosophy

End the "v2_FINAL_actualfinal.pdf" chaos. Replace 10 spreadsheets with one dashboard. Stop being the human middleware between design and production.

Zedonk Philosophy

Modular approach — pay for each capability separately. Strong on operations, lighter on product development.

Migrating from Zedonk to Kōbō

Migration from Zedonk happens in stages. The product-development side of the move is fast because Z.Studio doesn’t hold much that’s hard to extract: tech packs export to PDF, BOMs come out as CSV, and supplier records are simple contact entries. The Kōbō team imports those directly into the corresponding records, usually within a week.

The longer side of any Zedonk migration is operational data — open POs, inventory positions, supplier contracts, and historical sales orders. Most brands either run both systems for one production cycle (using Kōbō for new development while Zedonk closes out in-flight orders) or set a clean cut-over after a season ends. We’ve helped brands do both. The cleanest pattern is to onboard new collections into Kōbō and let Zedonk wind down naturally over 2-3 months.

Finance integration is the one piece that needs planning: Zedonk has native Xero/QuickBooks links, Kōbō runs Xero and QuickBooks through Zapier or direct API. The end result is the same — books stay in sync — but the cutover needs an accountant on the call. Migration support is included with onboarding at no extra cost.

Frequently Asked Questions

Is Z.Studio comparable to a full PLM?

Not yet. Z.Studio handles single tech packs and basic BOMs inside the Zedonk ecosystem, but it doesn’t cover design ideation, multi-colourway variants, supplier-side revisions, or sample tracking with photo attachments. Brands evaluating dedicated PLM typically need more than Z.Studio offers today.

Can Kōbō replace both an ERP and a tech pack tool?

Yes — that’s the typical Kōbō setup. Studio Lite or Pro covers design and development, Ops & Supply handles production and inventory, and Sell & Deliver runs wholesale. Most brands replacing Zedonk also drop a separate tech pack tool (Illustrator-plus-Excel, Techpacker, etc.) since Kōbō covers that natively.

How do supplier seats work on each platform?

Zedonk charges per supplier seat as you scale. Kōbō’s supplier portal is included with every plan, regardless of how many factories you onboard. For brands with a long supplier list (10+ factories across multiple categories), the supplier-seat difference can be material over a year.

What about implementation time?

Zedonk implementations are guided and typically take several weeks with vendor onboarding sessions. Kōbō is self-serve in 1-2 weeks, with optional onboarding support included. The Z.Studio side of Zedonk is faster to set up but layered on top of the existing ERP, so the total time is similar end-to-end for full PLM-plus-ERP capability.

The Bottom Line

Both platforms serve fashion brands, but they solve different problems first. Your choice depends on whether product development or operations is the center of your workflow. Weighing other vendors too? Here's our guide to the best fashion PLM software.

Choose Kōbō if

Consider Zedonk if

The best PLM is the one that matches how your team actually works — not the one that forces your team to change.

Disclaimer: Competitor information was gathered from publicly available sources as of May 2026 and may not reflect current offerings, pricing, or features. We recommend verifying details directly with each vendor.

Ready to see how Kōbō compares in practice?

Book a discovery call and we'll walk through how Kobo handles your specific workflow — from tech packs to delivery.