Features
Everything a request needs, in one place
cbThread covers the whole life of a request between a garment manufacturer and its buyer: how it’s asked for, how it’s discussed, how it’s decided, and how everyone keeps track.
01 · Requests
Every request, complete from the start
Request management
Every request between you and a buyer in one list, with its own number (like REQ-DG-128) and a clear status: pending, approved or rejected. Filter by request type, buyer or status.
Request types
Start with cbThread’s ten garment defaults, from lab dips and yarn dips to proto, SMS, size set and TOP samples. Keep the ones you use, add your own, and archive what you stop using. Its history stays.
Dynamic request forms
Each request type asks for exactly what it needs: text, paragraphs, numbers, dates, dropdowns and yes/no fields, in your order, required or optional. A lab dip asks for season, fabric and Pantone; a size set can ask for something else.
02 · Collaboration
One conversation, seen by both companies
Buyer collaboration
Manufacturers and buyers work on the same request page. Either side can raise a request, and both see the same details, files and conversation.
Comments
Discuss a request where it lives. New comments appear on an open page by themselves, and you can edit or delete your own for 15 minutes after posting.
Attachments
Swatch photos, spec sheets and reports sit on the request, each with a name of its own. Originals are kept exactly as uploaded, with quick previews for images.
Approval and rejection
The buyer approves or rejects, and the manufacturer sees it at once. The decision is final. An approved request is locked, while a rejected one stays open for the conversation about why.
03 · Visibility
Know what’s waiting without asking
Manufacturer dashboard
Totals by status, a card for each request type that only lights up when something is pending, your latest requests and what just happened.
Buyer multi-manufacturer workspace
A buyer works in one manufacturer’s workspace at a time, with that manufacturer’s own request types and requests, or in All Manufacturers for a combined view. Each manufacturer’s data stays with that manufacturer.
Activity and notifications
Recent Activity on both dashboards. Everyone else on a request is emailed when someone comments, with a link straight to the comment. A comment that goes unanswered for a week gets a reminder.
04 · Control
Set up your way, kept that way
Workspace configuration
A short guided setup: request types, the form for each, and the order of your dashboard. Activating it finalizes the configuration, so every request is raised on the same forms. Later changes are made by cbThread’s team as a configuration service.
Team roles and buyer access
Admins, managers, staff and viewers. Choose which buyers each team member works with; viewers can read everything but change nothing.
Subscription-based access
One plan, paid online or by bank transfer. If a subscription lapses, the workspace becomes view-only. Nothing is deleted, and paying again restores it at once.
05 · Security
Your data, kept where it belongs
Security in cbThread is built into how it works, not added on top. Every rule below is checked by the server on every request. Hiding a button is never what protects your data.
A database for every manufacturer
Each manufacturer’s request forms, conversations and files are kept in a database of its own, separate from every other manufacturer’s.
Access checked on every page
A buyer only ever reaches the manufacturers it’s connected to, and only its own requests. Team members see only the buyers assigned to them. Every page and every action checks this again.
Passwords handled properly
Passwords are stored only as one-way hashes, never as readable text. Everyone starts with a temporary password and must choose their own before they can do anything else. Deactivated accounts can’t sign in.
Files checked and locked away
Only permitted file types are accepted, checked by their content, not just their name. Files are stored under random names in a place the web can’t reach, and every download checks that the person may see that request.
A complete audit trail
Every change is recorded: who made it, when, from which network address, and what it was before and after. Failed sign-in attempts are logged as well.
Payments through Razorpay
Card and bank details are entered on Razorpay’s own checkout and never reach cbThread. Every payment is verified with Razorpay, signature and amount, before it counts.
And also
- Every form is protected by a security token, so another website can’t act on your behalf. Session cookies can’t be read by scripts, and a new session starts each time you sign in.
- Database queries are parameterised, so nothing typed into cbThread is ever run as a command.
- Comment emails carry a link to the comment, never the comment itself.
- If something goes wrong, you see a reference code, never internal details.
Custom & white-label
Want cbThread under your own brand?
We also build customised and white-label versions of cbThread: your name and branding, set up around the way your teams and buyers work. Tell us what you have in mind.
See the features at work
Watch a lab dip go from request to approval.
The guided tour shows these features in the order you’d meet them, on both the manufacturer’s side and the buyer’s.