BK Neo is BlueKaktus’s vendor-centric PLM, where internal teams and vendors collaborate on one shared record. A vendor collaboration platform sits between the systems you own and the vendors you don’t.
It connects the ERP, PLM and planning systems used internally with the people and companies outside your organisation who actually execute the work.
BK Neo reaches vendors through channels they already use, including WhatsApp, Excel and email, alongside its vendor portal and other integrations. Customers report 95% vendor adoption, although results depend on scope, data quality and implementation.
Most PLMs are designed primarily for people inside a company, with vendors added as an external extension.
BK Neo is designed around the collaboration between the brand and its supply chain.
Your design, sourcing and quality teams and the vendors outside the company collaborate around one shared record for each style and order.
The objective is simple: information should not become different depending on who has received it.
The tech pack a merchandiser updates should be the tech pack the factory sees.
The date a vendor confirms should be the date visible to the merchandiser.
The status should not have to be reconciled manually across email threads, spreadsheets and internal systems.
Your ERP holds the transactional record: purchase orders, costing, inventory and payments.
Your PLM holds the product record: styles, tech packs, BOMs and sampling.
Your planning system holds calendars, milestones and schedules.
These systems are primarily designed to operate within the company’s own environment, with controlled access for employees and internal teams.
Vendors sit outside those boundaries.
A vendor collaboration layer connects the internal systems with the external supply chain. It reads relevant information from the ERP, PLM and planning systems and allows vendors to send information back through channels that work for them.
ERP + PLM + Planning → Vendor Collaboration Layer → Vendors
The collaboration layer becomes the interface between the company’s internal systems and its external supply network.
BK Neo spans the internal systems and reaches vendors through multiple channels, including its portal, mobile app, WhatsApp, WeChat, Excel, email and AI-powered document processing.
A typical vendor may work with multiple brands at the same time.
If every brand asks the vendor to log into a different portal, the vendor has to learn and maintain multiple software workflows simply to send routine updates.
In practice, many updates continue to arrive through WhatsApp, email and spreadsheets.
The result is a familiar problem:
The company has a vendor portal, but the vendor still works outside it.
That is why simply deploying another vendor portal does not necessarily solve the adoption problem.
The issue is often not the portal itself.
It is the assumption that every vendor will change the way they work for every customer.
BK Neo takes a different approach.
Instead of requiring every vendor to adopt one new workflow, it accepts information through multiple channels and reconciles that information into the shared record.
A vendor who prefers Excel can continue using Excel.
A vendor who communicates through WhatsApp can continue using WhatsApp.
A vendor who wants a dedicated workspace can use the portal or mobile app.
The objective is to make the technology adapt to the supply chain rather than asking the entire supply chain to adapt to another piece of software.
| Channel | What it does |
| Vendor portal + mobile app | POs, samples, deadlines and updates in one place for vendors who want a dedicated workspace |
| WhatsApp & WeChat bots | Vendors can respond through familiar messaging channels; configured checks can parse responses and update the relevant record |
| Excel plugin | Vendors can pull and push information without leaving their spreadsheet workflow |
| AI data agent | Reads PDFs, scans and screenshots and routes relevant information to the correct PO |
| Email action centre | Monitors incoming email, classifies updates and posts activity against the relevant PO |
| CLO 3D & Adobe Illustrator plugins | Allows styles and tech-pack information to move directly into the system without manual exports |
A vendor who normally communicates through WhatsApp does not necessarily need to stop using WhatsApp.
A vendor who works primarily in Excel does not necessarily need to abandon Excel.
The collaboration platform brings those interactions together into one operational record.
BK Neo customers report 95% vendor adoption. Actual adoption can vary depending on the vendor population, implementation scope, data quality and execution.
A vendor collaboration platform should create value for both sides.
For vendors, a shared system can provide visibility into:
This creates a more transparent relationship between the brand and its vendors.
It can also reduce the dependence on a single person inside the buying or sourcing organisation.
Traditionally, one person may coordinate a particular vendor and become the primary source of information about that vendor’s performance.
With shared visibility, other members of the organisation can see the same information.
A vendor’s performance becomes part of the operational record rather than something that exists primarily within one relationship.
For brands, that means more consistent visibility.
For vendors, it means a clearer view of what is expected and how their performance is being measured.
The same collaboration principle applies on the manufacturing side.
In BK Mozart, BlueKaktus’s ERP for manufacturers, vendor-facing capabilities allow suppliers to participate directly in relevant operational workflows.
Depending on the configured process, vendors can:
The objective is not to turn the ERP into another messaging application.
It is to bring supplier communication into the operational workflow so that important updates remain connected to the purchase order and manufacturing process.
Yes.
BK Neo is designed to operate as a middleware layer with platforms including Centric, Infor, SAP and WFX.
Your existing PLM can remain the system of record while BK Neo provides additional vendor-facing channels and collaboration capabilities.
This approach avoids forcing a company to replace its entire technology stack simply because vendor collaboration is the weak point.
Instead, the collaboration layer can sit between the existing systems and the supply chain.
See Why Middleware Is the Right Answer for Sourcing.
BK Neo also brings a vendor network.
BlueKaktus states that 25,000+ suppliers are already live across India, China, Vietnam, Bangladesh, Sri Lanka, Turkey and Europe, covering Tier 1, Tier 2 and Tier 3 suppliers.
This creates a distinction between buying a software licence and joining an established network.
A licence gives you a system.
A network can potentially give you a system plus existing connections to parts of your supply base.
The relevance of that network depends on your specific vendor base and how much of it is already represented.
A vendor collaboration platform is not a replacement for every system in the IT stack.
Purchase orders, costing, inventory and financial transactions remain in the ERP.
The collaboration platform connects vendors to the relevant operational information.
Ledgers, statutory reporting and financial filings remain within the appropriate accounting or ERP systems.
Technology cannot automatically create operational discipline.
If vendors are not required to confirm orders, update milestones or flag delays, simply providing another communication channel will not necessarily change the behaviour.
The collaboration layer works best when it is connected to clearly defined processes, responsibilities and escalation rules.
BlueKaktus provides vendor collaboration capabilities across both its ERP, BK Mozart, and PLM, BK Neo.
That gives brands and manufacturers the option to connect external suppliers to the operational system where the relevant information already lives.
For a fashion brand managing a large vendor network, the collaboration challenge may be getting suppliers to stay current on styles, samples, T&A, shipments and quality.
For a manufacturer, the challenge may be coordinating suppliers, subcontractors and job-work partners around purchase orders and production.
In both cases, the underlying problem is similar:
The people executing the work need access to the same information as the people managing it.
A vendor collaboration layer provides that connection without requiring the entire supply chain to adopt the same internal systems.
It connects a company’s ERP, PLM and planning systems with its external vendors so both sides can work from current operational information rather than repeatedly re-keying updates from email, spreadsheets and messaging applications.
BK Neo supports multiple vendor-facing channels, including a portal and mobile app, WhatsApp and WeChat bots, an Excel plugin, email workflows and an AI agent that can process documents such as PDFs and scans.
One reason is workflow fragmentation.
Vendors may work with multiple brands, each with its own portal and process. Asking them to learn another dedicated system can create friction, particularly for routine updates that are already handled through WhatsApp, email or Excel.
Adoption can improve when a collaboration platform supports the channels vendors already use.
BK Neo customers report 95% vendor adoption, although actual results depend on implementation scope, vendor behaviour, data quality and execution.
A shared system can give vendors visibility into their own performance, including OTIF, T&A milestones, shipments and quality information.
It can also make performance more visible across the brand rather than leaving the vendor dependent on a single internal contact for recognition or escalation.
It becomes increasingly relevant when managing vendor status, documents, confirmations and agreements consumes significant time across a growing supply base.
The business case depends on factors such as vendor count, transaction volume, the number of manual follow-ups, existing system integration and the cost of delays or missing information.
For smaller vendor bases with straightforward processes, a dedicated collaboration platform may not yet be necessary.
No.
BK Neo is designed to work as a middleware layer with platforms including Centric, Infor, SAP and WFX, adding vendor-facing collaboration capabilities while the existing PLM remains the system of record.
This allows a business to address its vendor collaboration problem without necessarily replacing its existing PLM.
ERP, PLM and planning systems solve different problems.
The ERP manages transactions.
The PLM manages product information.
Planning systems manage timelines and milestones.
But none of those systems completely solves the problem of getting external vendors to consistently participate in the workflow.
That is where a vendor collaboration layer fits.
The most effective approach is not necessarily to give every vendor another portal and expect them to change their behaviour.
It is to connect the systems you already use with the channels your supply chain already uses—and turn those interactions into structured, shared operational data.
That’s the role a vendor collaboration platform can play in the modern apparel IT stack.
Get your vendors on one record without asking them to change. 95% reported vendor adoption, a 30-day proof of concept on your own styles. Book a BK Neo demo · See the vendor portal
