Email archaeology
Which round was approved, by whom, and why? It is on the record with the photos — not in a thread from March that three people were cc’d on.
Samples
Every round, every comment, every approval.
Prototype, revision, pre-production, first article — each round is logged with photos, measurements against spec and the comments that go with them. Customers approve from their portal. Nothing lives in an email thread any more.
Where it sits
One chain, this link.
Every flow in Weavwork is a view of the same connected record — so nothing here is a module bolted on beside the others.
- StyleSKU tree · BOM
- Samplerounds · specs
- Ordergrid · price list
- Production managementplan · WIP · QC
- Shipmentvessel · ETA
- Warehousepick · pack · count
- Accountingsample cost · dev spend
A sample is a record of its own, hanging off the style — which is why round three still knows what round one was told. It is also money: the cloth, the trims and the factory’s charge for making it land in accounting as development cost, whether or not the style ever sells.
How it runs
Step by step, on one record.
- 01Raise the request
A sample request opens against the style: which round, which factory, what changed since last time. The tech pack and the spec measurements are already on it, so the factory starts from the record, not from a forwarded PDF.
- 02The factory posts the round
Photos, measurements and notes arrive through the supplier portal — or straight from their email, read by the agent — and land on the round itself. The record fills in whether or not anyone at your end is watching.
- 03Measure against spec
Every point of measure is checked against its tolerance the moment it is entered. A sleeve 1.2 cm long is flagged in red before anyone has to squint at a photo, and the flag stays with the round.
- 04The customer decides
Approve, request changes, or comment — from their portal, on a phone if that is where they are. The decision and the reason stay on the record for the next round, the next season, and the next person who asks.
A week with it
What it looks like on a Wednesday.
Three days from one week, on the sample data that runs through this site.
Monday
Round 3 goes out
The PP request for the Linen Camp Shirt opens against STY-0442 with the round-2 comments and the spec already on it. The factory sees it in their portal before lunch, Vietnam time.
Wednesday
The factory posts
Photos and fourteen points of measure land on the round. One sleeve is 1.2 cm long — flagged red before anyone opens a photo. The agent files the factory’s covering email underneath.
Friday
Northline approves
The customer approves with a note from their phone. The round closes, the style moves to top-of-production, and the note is there for the next season’s request.
What it removes
The jobs that stop existing.
Spec drift
Measurements are checked against tolerance every round, so the third sample cannot quietly wander from the first.
Waiting on a reply
Customers and factories act from their own portals. Nobody is waiting for you to forward a photo before they can say yes.
Who works in it
The same record, three seats.
Design and technical
The spec, the tolerances and every round’s measurements on one screen, with the tech pack that follows the style.
Sales
Which customer approvals are outstanding, and a portal link to send instead of a photo attachment.
The factory
A request that says exactly what changed, and a portal to post the round from the floor.
Questions
The ones we get asked.
Can customers see every round?
They see the rounds you share with them and approve from their portal. Internal notes and factory pricing stay internal.
What if a factory will not use a portal?
The inbox agent reads their email replies against the sample request, so the record stays current either way. Portals are the fast path, not a requirement.
Where do tech packs live?
On the product master. They follow every sample request and every production order automatically, so the factory is always working from the current version.
Does a first article gate production?
Yes. A first-article round is a sample round tied to the production order, and the run waits on its approval.
Keep going
Two more flows, and the whole product.
See it on your own range.
A 30-minute demo, run on your products and your workflow. No slides.
Or write to hello@weavwork.com