Every sustainability claim a brand makes is only as strong as the paperwork sitting behind it, and for most brands that paperwork lives across a hundred different vendor inboxes rather than in one place. That’s the actual problem “digital supply chain visibility” is meant to solve, even though the phrase itself has been stretched thin by marketing.
Digital supply chain visibility means every style, BOM, vendor PO, supplier document and production update lives in one live record instead of scattered email and spreadsheets. Sustainable brands need it because a sustainability claim is only as strong as the supplier data behind it. BlueKaktus Neo collects that data through channels vendors already use — WhatsApp, WeChat, email and Excel.
This is worth getting precisely right, because it’s the claim most likely to be checked. The Ecodesign for Sustainable Products Regulation (ESPR) entered into force in 2024, and the European Commission designated textiles a priority category in April 2025. The textile-specific delegated act that will set Digital Product Passport requirements is expected in late 2026 or 2027, with obligations phased in after that. It’s coming — it just hasn’t taken effect yet, and a brand told otherwise should treat that claim with caution. The sensible move is to start assembling supplier data now, ahead of those dates, rather than waiting for a deadline that isn’t confirmed. [Link: ESPR textile delegated act status.]
It’s rarely resistance — it’s friction. If sending a GRS or OEKO-TEX certificate means logging into a new portal, remembering a password, and uploading a file in a format the brand’s system expects, a busy vendor admin team quietly deprioritizes it. Adoption improves sharply the moment data collection uses the channel a vendor is already in — a WhatsApp bot that accepts a photo of a certificate, an Excel plugin, or an AI agent that reads a scanned PDF directly. Neo’s stated adoption figure is 95%, largely because the ask is “send it the way you already send things,” not “learn a new system.”
Neo meets vendors on WhatsApp and WeChat, email, Excel, or through CLO 3D and Illustrator plugins where design data is involved. An AI data agent reads PDFs, scans and screenshots into the same live record, so the brand gets structured data without asking vendors to change how they work.
Neo runs as middleware on Centric, Infor, SAP and WFX rather than requiring a separate platform migration — which matters most for brands that have already invested heavily in a PLM and don’t want a second system of record for compliance alone.
It’s worth being direct about what this can and can’t do, because overclaiming here carries real risk. Neo can hold supplier declarations, certifications and material data in one place, and flag when a document like a GRS certificate is missing or nearing expiry, surfacing that as a same-day exception rather than something discovered during an audit. It cannot detect labour practices, verify a supplier’s claims independently, generate a Digital Product Passport, or calculate Scope 3 emissions or a life-cycle assessment. Those require separate tooling; Neo is the record-keeping layer underneath them, not a replacement for them.
| Sustainability data need | Can Neo help? | What it actually does |
|---|---|---|
| Supplier certifications (GRS, OEKO-TEX) | Yes | Central record; flags missing/expiring documents |
| Material composition data | Yes | Held against BOM and style records |
| Tier-2/3 supplier visibility | Partial | Depends on whether those vendors are onboarded into the record |
| Digital Product Passport generation | No | Not a current capability |
| Scope 3 carbon / LCA calculation | No | Not a current capability |
| Labour-practice verification | No | Software surfaces missing paperwork, not conduct |
Bata operates across 70+ markets on BlueKaktus; Blackberrys moved from a fully manual, two-year process to a data-driven one. Across the network, BlueKaktus connects 25,000+ suppliers and 50,000+ certified users. Worth flagging plainly: these are reported outcomes from customers using the platform generally, not sustainability-specific case studies — precision matters more here than in most other topics.
Neo doesn’t generate a Digital Product Passport, and it doesn’t independently verify a claim like “no forced labour” — it can flag when the paperwork behind that claim is missing or expired, but the underlying verification is still a human or third-party audit process.
Building toward the delegated act, not scrambling when it lands? Talk to BlueKaktus about what supplier data your vendor base can realistically supply today.
Does BlueKaktus generate a Digital Product Passport? No. It holds the underlying supplier and material data that a DPP would eventually draw on, but it doesn’t generate the passport itself.
When do EU Digital Product Passport requirements for textiles take effect? Textiles were designated a priority category in April 2025. The delegated act setting the specific requirements is expected late 2026 or 2027, with obligations phased in after that — it has not yet taken effect.
Do vendors need to use a new portal to share compliance certificates? No — Neo collects this data through WhatsApp, WeChat, email, Excel and an AI document reader, meeting vendors where they already work.
Can software verify that a supplier isn’t using forced labour? No. Software can flag missing or expired compliance documents; it can’t independently verify labour conditions on the ground.
What’s the difference between supplier data collection and Scope 3 carbon calculation? Supplier data collection (what Neo does) gathers the underlying material and certification records. Scope 3 calculation is a separate analytical step that uses that data as an input — Neo doesn’t perform the calculation itself.
Can this run alongside our existing PLM? Yes — Neo runs as middleware on Centric, Infor, SAP and WFX rather than requiring a separate system.
