Re-keying from spreadsheets
Orders arrive from the portal, from Shopify, or as a grid you fill once. The same numbers never get typed twice.
Sales orders
Orders that understand variants.
Key a whole range as a variant grid — style × colour × size, or whatever your product splits by. Price lists, allocations and back-orders resolve the moment the order lands, from your team, from the portal, or from your Shopify store.
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
- Accountingquote · invoice value · committed
An order carries a value the moment it is keyed — the quote, then the invoice. A production order raised against it commits the materials it will need without drawing them down: the cloth is spoken for and reserved, and book value has not moved yet.
How it runs
Step by step, on one record.
- 01Key the grid
A style opens as a grid of its colours and sizes. Type the quantities, or paste them from the customer’s own sheet, and the line items build themselves with the right codes.
- 02The price list resolves
The customer’s wholesale tier, terms and any agreed specials apply as the lines are keyed. What they see on their portal is what you invoice.
- 03Allocation on landing
Stock is allocated the moment the order confirms — from the warehouse, from the 3PL, or from a container that has not landed yet. Anything short becomes a back-order with a date, not a mystery.
- 04Fulfil from anywhere
Pick and pack from your own floor or push the order to your 3PL. Despatch, tracking and the invoice flow back onto the order, and into your accounting, without being keyed again.
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
The grid arrives filled
Northline keys their winter order in the portal against their own price list — 1,240 units across three colours — and it lands as SO-1187, confirmed, with 1,020 allocated and 220 on back-order against PO-2041.
Wednesday
A Shopify weekend
Sixty web orders from the weekend arrived as sales orders on their own, inventory in sync, and are already with the 3PL. Nobody exported a CSV.
Friday
The container books
The back-ordered 220 are booked against SH-0492 before it lands. The customer’s portal shows the date; the invoice for the first despatch is already in Xero.
What it removes
The jobs that stop existing.
Overselling
Allocation happens at confirmation against stock on hand and stock in transit, so two customers cannot be promised the same carton.
The price-list phone call
Every customer carries their own tier and terms. The portal shows their prices, so the question does not get asked.
Who works in it
The same record, three seats.
Sales
Orders as grids, each customer on their own tier, availability and transit visible while you promise a date.
Warehouse
Allocations that say where the stock is — your floor, the 3PL, or on the water — and picks that arrive without a phone call.
Finance
The invoice raised from the despatch and matched in the ledger, deposits and terms per customer.
Questions
The ones we get asked.
Can customers place orders themselves?
Yes — from the customer portal, against their own price list, with stock availability shown as they order.
How do Shopify orders come in?
They land as sales orders automatically, inventory stays in sync, and fulfilment runs the same way as any other order.
What happens to a back-order?
It is raised with the expected date from the production order or the shipment behind it, and released as that stock lands.
Can one order ship from two places?
Yes. Lines allocate to wherever the stock is — your warehouse, your 3PL, or a mix — and each despatch tracks separately on the order.
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