Skip to content

For garment manufacturers and their buyers

A simpler way to connect garment manufacturers and buyers.

cbThread is one shared workspace for the requests that pass between a manufacturer and its buyers: lab dips, strike-offs, samples. Each request is raised on the manufacturer’s own form. Its files, its conversation and the buyer’s approval stay together in one thread that both companies see, not scattered across email, chat and spreadsheets.

Explore cbThread Get Started

The demo is a guided tour with sample data. There’s no sign-up.

The problem

Sampling runs on scattered threads

A single lab dip can pass through a dozen emails, chat messages and calls before anyone approves it. When the conversation is scattered, so is the answer to the simplest question: where does this stand?

Requests arrive everywhere

Email, chat, calls, spreadsheets. Each request starts somewhere different, and nobody sees all of them at once.

Status is a guess

Is it approved? Which version? Who is waiting on whom? The answer is in someone’s inbox, if it’s written down at all.

Files lose their context

The right swatch photo sits in the wrong thread, with no record of what was decided about it, or by whom.

The cbThread way

One request. One thread. Both companies.

Every request gets a page of its own, which both the manufacturer and the buyer see. Everything that happens to it happens there.

  • Raised on the manufacturer’s own form for that request type, so it arrives complete.
  • Details, files, comments and the decision all stay on the request, in order.
  • Both sides are notified when something changes, and the link goes straight to it.
  • Once the buyer approves, the request is locked: a record of exactly what was agreed.
Demo Garments · REQ-DG-128Sample data

Lab Dips

REQ-DG-128

Pending

Request Details

Season

SS27

Fabric Description

100% cotton single jersey, 180 GSM, reactive dyed

Color

Classic Blue

Comments

2 comments
H

Hannah Clarke

Northwind Apparel

Yesterday

Thanks, Priya. Option B is the closest, but it reads slightly green under TL84. Could you check it against the standard and send a revised B?

P

You

3 hr ago

Checked under D65 and TL84 — agreed, B leans green. We’ve re-dyed it as B1 with the green pulled back. The photo is under Attachments and the physical swatch goes out today.

How it works

Raise, collaborate, review, approve, track

  1. 01

    Raise

    Either side raises a request on the manufacturer’s form.

  2. 02

    Collaborate

    Comments and files, on the request, for both companies.

  3. 03

    Review

    The buyer sees the details, the files and the whole conversation.

  4. 04

    Approve

    The buyer approves or rejects. The decision is final.

  5. 05

    Track

    Dashboards show what’s waiting and what just moved.

See how it works →

Features

Built around how sampling really works

All features →

Your request types, your forms

Lab dips, strike-offs, proto, SMS, size set, TOP. Every type asks for exactly the fields your team needs.

One conversation per request

Comments and files on the request itself, seen by both companies, with an email when someone replies.

Approvals that stay settled

The buyer decides, the manufacturer sees it at once, and an approved request can’t be quietly changed.

A dashboard that points at work

Request types light up only where something is pending, so the eye goes straight to it.

Buyers with many manufacturers

One sign-in, a workspace per manufacturer, and a combined view of everything waiting on you.

Set up once, then locked

A guided setup shapes the workspace, then activation fixes it, so every request is raised the same way.

Security

Your data, kept where it belongs.

Every rule is checked by the server on every request. Hiding a button is never what protects your data.

How cbThread protects your data →
  • A separate database for every manufacturer
  • Buyers reach only the manufacturers they’re connected to
  • Passwords stored only as one-way hashes
  • Files checked by content and kept off the open web
  • Every change recorded in an audit trail
  • Card details stay with Razorpay, never with cbThread

The product

This is what your team works in

The manufacturer’s dashboard, with sample data. The guided tour walks through a request from start to finish, on both sides.

Take the guided tour
Demo Garments · Manufacturer workspaceSample data
cbThread

Good morning, Priya.

Demo Garments

Here’s what’s happening with Demo Garments today.

+ New Request

Overview

Total Requests

128

Pending

14

Approved

97

Rejected

17

Request Types

LD

Lab Dips

4 pending26 total

View Requests →

YD

Yarn Dips

0 pending9 total

View Requests →

SO

Strike-offs

2 pending11 total

View Requests →

DL

Desk Loom

0 pending4 total

View Requests →

PR

Proto Sample

3 pending17 total

View Requests →

Manufacturers and buyers

Two companies, one view of the work

For manufacturers

  • Your own request types, and a form for each one
  • A dashboard that shows where work is waiting
  • Choose which buyers each team member works with
  • Unlimited users for your team

For buyers

  • One sign-in for every manufacturer you work with
  • Raise, discuss, approve or reject in each manufacturer’s workspace
  • All Manufacturers: everything waiting on you, in one place
  • No subscription of your own: the manufacturer’s plan covers you

Pricing

One plan, priced by the buyers you work with

Every feature and unlimited users, for up to 5 buyers. Add buyers when you need them.

See pricing

Thread Core · yearly

₹1,20,000

a year + GST, including 5 buyers

2 months free compared with paying monthly

₹8,000 a year for each extra buyer · 10 GB of storage, plus 2 GB for each extra buyer

See it for yourself

Follow one lab dip from request to approval.

The guided tour takes a few minutes and uses sample data, so there’s nothing to sign up for. When you’re ready, we’ll set up your workspace.

Explore the demo Get Started