Sales
Orders as variant grids, every customer on their own price list, stock and transit visible as you promise dates. The portal takes the orders you used to key.
Product
One record, every flow.
A style, its samples, the orders it sells on, the run that makes it and the shipment it lands in are one connected record in Weavwork — and every screen is a view of it. This is how it fits together.
Search a customer, land on their order, see the production run covering the shortfall and the container it is on. That is the record model at work — one search, the whole thread.
The record model
Everything hangs off one thread.
Most systems bolt a sample tool to an order book to a spreadsheet of shipments. In Weavwork the objects are linked at the root, so a number keyed once is right everywhere it appears — and a change on the floor shows up on the order, the shipment and the customer’s portal without anyone forwarding it.
- StyleThe product master: its SKU tree, tech pack and bill of materials.
- SampleRounds, photos and measurements against spec; the customer approves from their portal.
- Sales orderA variant grid against the customer’s price list, allocated on landing, invoiced into your accounting.
- Production orderRaised from that demand, drawing down materials, moving stage by stage — with supplier bills and landed cost rolling into your accounting.
- ShipmentThe vessel, the ETA and the orders inside — bookable before it lands. Or skip the leg entirely and go straight to a 3PL in the factory’s own country.
The same records, four shapes. Wholesale is demand-led: the order pulls the run and Weavwork raises the invoice. Direct to consumer is forecast-led: replenishment drives the run, and the goods either go straight to a 3PL in the factory’s own country or are shipped in and landed into your warehouse — your store keeps the sales ledger and tells Weavwork about stock, returns and faults. Retail runs the same way to the warehouse, then feeds your own floors by transfer and counts back. Contract manufacturing inverts the start: the brand supplies the spec, you supply the floor, and the make charge is what you invoice.
The product tree
One base garment, every code below it.
A customer wants the polo in bamboo cotton instead of poly/cotton. That is not a new product — it is a new branch. This is the create-product screen: pick the fit, the fabric, the component, the decoration and the colour, and Weavwork generates the code, inherits the pattern and the tech pack, builds the bill of materials from the branch and costs it. Three fits, three fabrics, three plackets, three decorations, four colours and eight sizes is 2,592 codes that most systems would have you keep in step by hand.
Create product · new variant
Polo — short sleeve, unisex
Branching off the base item. The pattern, the tech pack and the base specification come with it — you are choosing, not retyping.
WW-0520
Fit
Fabric
Components
Decoration
Colour
Size
A regular-fit M takes 1.32 m of bamboo cotton 185. Sizes apply as a grid at order time, so the tree holds one record — not eight near-duplicates of it.
No level is a closed list — add a fourth component, a fifth colour, a fabric you have never bought and every code beneath it generates itself. These choices only exist here in create product: once the variant is on the tree, sales pick it off an order grid and the factory reads it off the docket.
New code
WW-0520-REG-BAM-PLK3.PKT1-EMB-NVY-M
Rolls down: 3 fits × 3 fabrics × 18 component builds × 8 decoration sets × 4 colours is 5,184 sellable leaves, 41,472 codes once sizes apply. Components and decorations add up rather than pick one — a placket with two pockets, a logo and a back print, is a build and not a fourth product. Nobody types 41,472 of anything.
Rolls up: all 41,472 still report as one product. Cost, cover, margin and sell-through answer at any height of the tree, and a twenty-school range is twenty branches on the decoration level, not twenty products.
First run of this variant
2,000 units · navy · regular fit
The bill of materials builds up the branch you picked and the source you make it at. Cloth and rib are held per colour, so a bottle run and a navy run draw on different shelves.
PO-4471
Made at
- Bamboo cotton 185 — navy2,640 mon hand 1,480 mshort 1,160 m
- Collar and cuff rib — navy2,000 eaon hand 6,400 eacovered
- Buttons — 3 a placket6,000 eaon hand 34,000 eacovered
- Pocket facing — one a garment2,000 eaon hand 2,400 eacovered
- Embroidery — logo, 8,400 stitch2,000 eaon hand 9,500 eacovered
- Woven main and care label4,000 eaon hand 12,000 eacovered
Cost, from the branch
- Fabric
- A$7.26
- Trims
- A$1.71
- Decoration
- A$0.85
- Make
- A$2.33
- FOB a unit
- A$12.15
Lands at A$15.07 once this shipment’s freight and duty are apportioned across the box it came in. Change a branch or the factory and it re-costs itself — nobody reprices a spreadsheet.
One line will not cover the run
The replenishment agent has already drafted what covers it, and worked the dates back from the ex-factory date on the order.
- 1,200 m bamboo cotton 185 — navy · from the mill, dyed to colour38-day lead · place by 30 Jul to hold 18 Sep ex-factory
Change any branch — or add one. The code, the consumption and the dates all follow.
Those dropdowns exist in create product and nowhere else — once the variant is on the tree, sales pick it off an order grid and the factory reads it off the docket. What follows it everywhere is the bill of materials: the moment a production order is raised, the run is priced against stock rather than against a spreadsheet, and anything short is the replenishment agent’s problem before it is yours. It drafts the mill and trim orders, works the dates back from the ex-factory date, and tells you the day the run stops being possible.
RFID
Tag the pallet, the carton, the garment — or all three.
RFID is not one feature at one level. A pallet can carry a tag whether or not its cartons do, and a carton can carry one whether or not the garments inside it do. Weavwork reads whatever is there against the record it already holds — and where there is nothing to read, the barcode and the packing list still run the flow.
Pallet P-0041tagged
One pass of the reader returns 313 reads: 1 pallet, 24 cartons, 288 garments. Each one lands on the record it belongs to.
Where it reads
- Goods-in
- A portal at the door or a handheld on the dock. The container reconciles against the shipment as it is unloaded, not the following Tuesday.
- Despatch
- A portal at the loading door reads the pallet as it goes on the truck and checks it against the consignment before it moves.
- On the floor
- A handheld for putaway, cycle counts and the full stocktake — the aisle instead of the clipboard.
- At the store
- A fixed reader or a handheld for floor stock, back-of-house and what came back over the counter.
Ordinary EPC Gen2 hardware — fixed portals or handhelds, bought from whoever you like. Weavwork is what they read into.
At this level
Tag the garment and stock stops being an estimate.
Every unit answers for itself — on the floor, in the box, at the till and on the way back.
- Goods-in in one passA container reconciles at the door: every pallet read as it comes off, against the shipment Weavwork already knew was landing. What is missing is a fact before the driver leaves.
- Where the pallet isEach pallet reads to a location on your floor or your 3PL’s, with the shipment, the production order and the styles inside it one click away.
- Despatch verified at the doorRead the pallet as it is loaded and every carton on it is checked against the consignment. A carton that belongs to another customer is flagged before the truck moves.
- Carton-level handoverYour 3PL receives by carton against the packing list Weavwork sent them, so a short delivery is a reconciled number rather than an argument three weeks later.
- Stocktake without countingWalk the aisle with a reader and the count is done in minutes, reconciled to the ledger, with the variance broken out by SKU instead of by guess.
- The right unit in the right boxThe pick reads as it is packed. A 2XL in a carton the slip says is size M never leaves the building, and the customer portal shows what actually shipped.
- A return reads back to the runA garment that comes back carries its own identity: the order it sold on, the run that made it, the fabric lot it was cut from. A fault becomes a pattern you can see, not an anecdote.
Turn any level off. They are independent — a tagged garment inside an untagged carton still reads, and so does a tagged pallet of cartons that carry nothing but a barcode.
Eight flows
Pick the one your week is about.
In the order the record runs, from the style down to the ledger. Each has its own page: how it runs step by step, what it removes, what it works with, and the questions people ask before they switch.
Products & SKUs
A product tree from base item to sellable code — fabric, components, decoration, colour — with costing and sizes riding along.
Samples
Sample rounds with photos, measurements against spec and customer approvals on one record.
Sales orders
Sales orders keyed as variant grids, with price lists, allocation and back-orders resolved on landing.
Production management
Production orders against real demand, material drawdown, stage-by-stage progress and ex-factory dates that move.
Freight
Shipments tracked by sea and air, stock in transit bookable, and freight and duty landed onto the goods.
Warehouse & fulfilment
Allocation, picking, packing and despatch from your own floor or a connected 3PL, with counts that agree with the ledger.
RFID
RFID at the pallet, the carton and the garment, in any combination, read against the records Weavwork already holds.
The agents
An inbox agent that reads supplier email against the right record, and a replenishment agent that drafts what to order — down to the fabric.
Who works where
Every seat sees its own week.
The same record, a different view per job. Nobody scrolls past another team’s screens to find their own.
Production management
Production orders raised from demand, materials drawn down as they are placed, every factory’s WIP on one screen and ex-factory dates that move with the floor.
Warehouse
Picks, packs and despatches from your floor or your 3PL, stock counts that agree with the ledger — by scan or by RFID — and inbound containers already allocated before they land.
Finance
Invoices and bills flow to MYOB or Xero matched to their orders; landed cost and margin per style are derived, not spreadsheeted.
Design and technical
Styles, the SKU tree, tech packs and bills of materials as one product master — every sample and production order starts from the current version.
Owner and GM
The dashboard: what is open, what is late, what is landing, what the range is actually making. Search anything and land on the record.
Derived, not typed
Numbers that stay right.
The figures a manufacturer argues about are calculated from the record, every time it changes — never copied into a sheet that is already out of date.
$18.42
Landed cost per unit
FOB, duty and the freight share of the box it came in — per unit, per shipment, as it lands.
41%
Margin on the range
Quoted against actual, per style and per order, once the true cost is known.
3.0 mo
Cover by SKU
Months of stock at the current rate of sale, with the run that will exhaust it forecast to the unit.
18 Sep
Ex-factory that moves
Pulled in or pushed out as the factory posts progress — and the customer date follows.
Illustrative figures from the sample data on this site.
Questions
The ones we get asked.
Is it one product or a set of modules?
One product. Every flow on this page is in the plan, on one database, with one login. There are no modules to buy later and nothing to integrate between the parts.
Do we have to run every flow?
No. A distributor with no factories never opens production; a brand that outsources never runs a floor. Turn on what you run and the rest stays out of the way.
How deep can the product tree go?
As deep as the product does. The levels are yours to name — fabric, component, decoration and colour for a garment, or material, finish and fitting for something that is not one — and every path still resolves to one standard code that orders, production, stock and your web store all agree on.
Do we need RFID to use it?
No. Every flow runs on scanned barcodes and the packing list. RFID is an upgrade you can take at the pallet, the carton or the garment, in any combination, and Weavwork reads whatever is there against the records it already holds.
Where does the data live?
On AWS in Sydney, backed up daily, exportable in open formats at any time. Roles, permissions and an audit log cover who did what.
Does it replace our accounting?
No, and it is not meant to. Weavwork raises the invoices and bills against their orders and shipments; MYOB or Xero stays your ledger.
How long does a switch take?
Your products, customers, suppliers, price lists and open orders are mapped and loaded by us, then the two systems run side by side until the last order is through. The pricing page has the fee; the demo has the plan for your data.
Can we see it on our own products?
Yes — that is the demo. Bring a range and a live order and we run the flows on them, not on ours.
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