ClearStock is live on the Shopify App Store.Install free →

← All blogs

Guides8 min read

WIP inventory for small makers — what counts, why it hides problems, and how to track it without ERP

WIP inventory explained for small Shopify makers — what counts as work in process, why it hides problems, and simple tracking without ERP software.

InventoryX is in development and not available today. ClearStock is the live Shopify app.

WIP inventory — work in process — is everything you've started making but can't yet sell: cut fabric that isn't sewn, sauce in the kettle, jewelry mid-assembly. For a small maker, WIP is usually the least visible inventory you own: it doesn't sit on a finished-goods shelf, it doesn't appear in Shopify, and it's often uncounted entirely. That invisibility is expensive for two reasons — WIP is real cash sitting on workbenches, and its size is a diagnostic: bloated WIP is how a production queue tells you something upstream is wrong. This article covers what counts as WIP for a small operation, why growing WIP is a warning rather than a comfort, and a tracking method that fits on one spreadsheet tab.

What counts as WIP (and what doesn't)

The boundary is conversion: once a raw material is committed and transformed — cut, poured, partially assembled — it's WIP; before that, it's raw material; after final QC and packaging, it's finished goods.

Stage Example: apparel studio Classification
Fabric on the roll 40 yards of canvas on the shelf Raw material
Fabric cut into panels 40 apron kits, cut and bundled WIP
Partially sewn Aprons on the machines, half-done WIP
Sewn, awaiting QC or labels Finished but untrimmed, unlabeled WIP (borderline)
Tagged, packed, sellable On the finished shelf, listed in Shopify Finished goods

Two boundary calls worth making deliberately rather than by accident:

  • The "sewn but not sellable" zone counts as WIP. Unlabeled, untrimmed, unpacked units are not finished goods — if you count them as sellable, your Shopify quantity will lie about what you can actually ship. Pick a precise sellable definition ("tagged and bagged") and treat everything before it as WIP.
  • Batch staging can be WIP or raw material, but be consistent. Components kitted for a specific production run are WIP; the same components in storage are raw material. The moment you pull and stage, the money changed jobs.

Why WIP hides problems instead of just costing money

The counterintuitive part: in many small workshops, WIP grows when things are going wrong, not right, and it often feels productive — "look at all this in progress." Four mechanisms:

  1. WIP is a buffer against revealing a bottleneck. If cutting is fast but sewing is slow, cut piles accumulate in front of sewing. The pile feels like progress; it's actually inventory waiting on the constraint. The bigger the pile, the longer the feedback lag on every problem upstream of it.
  2. WIP delays defect discovery. A bad batch of fabric discovered at the cutting stage costs a cut; discovered after sewing, it costs finished aprons. More WIP between stages means problems travel further before anyone notices.
  3. WIP distorts your finished-goods numbers. If half-done units get counted as sellable "because they're basically done," you'll take orders you can't ship on time — the same self-inflicted gap that receiving lag causes on the inbound side.
  4. WIP is where cash goes to get vague. You can price a finished apron and value a roll of canvas; the forty half-made units on the rack are the hardest inventory to value and the easiest to forget. When a maker says "I have $20k in inventory" and can only document $13k of it, the missing chunk is usually WIP.

The lean-manufacturing instinct — keep WIP deliberately small so problems surface immediately — is well established at factory scale (it's core to the Toyota Production System's Just-in-Time pillar — making only what's needed, when it's needed, in the amount needed — per Toyota's own [TPS overview](https://global.toyota/en/company/vision-and-philosophy/production-system/, accessed October 2026)); for a two-person studio the practical version is simpler: cap your batches. Ten aprons in process, finish them, then cut ten more. The discipline isn't about efficiency ideology; it's that a small batch surfaces a broken machine or a bad zipper within a day, while a hundred-unit batch hides it for a week.

Simple WIP tracking for shops without ERP

You don't need manufacturing software to see WIP; you need a tab that answers three questions per batch: how many units, which stage, how old.

Batch SKU Units Stage (as of Mon Oct 26) Entered WIP Age Next action
B-114 APRON-CNV-01 10 Sewing Oct 17 9 days Finish + QC by Oct 31
B-115 APRON-CNV-01 10 Cut, staged Oct 24 2 days Queue behind B-114
B-112 PIN-ENAM-07 300 Plating (outsourced) Oct 5 21 days Chase supplier this week

Rules that keep the tab honest:

  • One row per batch, not per unit. You're tracking flow, not piecework.
  • A "date entered WIP" column is the whole game. Age exposes stuck batches — batch B-112 above, 21 days at an outside plater, is exactly the kind of thing that never surfaces without a date. Chase it.
  • Update stage counts on a fixed rhythm — Monday morning works, and it pairs naturally with your finished-goods count routine: one pass through the shop, both tabs updated, ten minutes.
  • Close batches explicitly. When a batch becomes finished goods, mark it done and move the count into Shopify. A batch that lingers "basically done" for two weeks is a data leak — it's finished, count it.
  • Cap WIP on purpose. Write down a max (in batches or units) per product line. When the cap's hit, the rule is finish, don't start. That single rule surfaces bottlenecks faster than any report.

For valuation, keep it rough but real: value WIP at material cost consumed plus a reasonable labor allocation if you pay production labor — and if that sounds like too much bookkeeping, value it at materials only and note the convention. Consistency matters more than precision here; the number needs to be defensible at year-end, not perfect.

How the three inventory types fit together

The accounting distinction is a flow: raw materials + direct labor consumed in production become WIP; completed WIP becomes finished goods; finished goods become cost of goods sold when they sell. Each stage is the same dollars wearing a different label. What changes at each boundary is who can see the money: raw materials are countable, finished goods are tracked in Shopify, and WIP is the stage where visibility goes to die — which is why it deserves its own tab more than the other two deserve better software.

Where tools land, honestly: Shopify tracks finished goods (quantities, POs, counts) but has no native concept of production stages or WIP as of October 2026. InventoryX works that finished-goods layer — the weekly Buying List sizes replenishment on true demand and lead times — and does not do WIP or production tracking; BOMs and manufacturing stages are ERP territory and outside V1. For a small maker, the spreadsheet tab above plus Shopify's finished-goods tracking is a legitimate stack, not a compromise you'll regret.

Common questions

What is WIP inventory? Work in process inventory is product that's begun production but isn't finished or sellable — cut fabric, partially assembled goods, units awaiting QC or packaging. It sits between raw materials and finished goods, is valued at consumed materials plus labor, and is invisible to your storefront until it's done.

What's the difference between WIP and raw materials? Raw materials are untouched inputs in storage; WIP is materials that have been committed to a production batch and partially transformed. The practical test: if it's been pulled, cut, poured, or staged for a specific run, it's WIP — even if the transformation just started.

How do you calculate WIP inventory value? For each open batch: materials consumed so far, plus any direct labor applied. Small shops often simplify to materials-only and state that convention consistently. The number matters mainly at year-end as part of total inventory valuation, so rough-but-consistent beats precise-but-never-updated.

How much WIP should a small maker carry? Less than feels comfortable. Cap it deliberately — a fixed number of batches per line — and finish before starting more. Excess WIP hides bottlenecks, delays defect discovery, and ties up your least-visible cash; a small cap makes production problems surface within days instead of weeks.

Do I need ERP software to track WIP? No. A spreadsheet with one row per batch — units, stage, date entered WIP, next action — covers small operations completely. ERP-grade BOM and production modules earn their cost at higher volume and complexity; until then, the discipline of batch rows and age columns does the real work.

Next step

Walk your production space today and write down every batch in progress with its stage and your best guess of when it started. The batches older than your typical cycle are your answer — they're sitting on the bottleneck, and that's the constraint to fix before you buy a single new roll of anything.

An aging pass over WIP, incidentally, is the same instinct as an inventory aging report on finished stock: age is where stuck inventory confesses. And when you size the next batch, let order-quantity math — not studio optimism — set the number.