SaleShade Operations · Production requisition

The bill of materials becomes material on the move

The bill of materials raises the requisition — available material moves to the workshop now, the shortfall is procured, and both arrive as one inflow.

A workshop waiting for the last item on the list

The job is sold, the bill of materials exists — and the workshop is idle.

The old way1

The job is sold

and the bill of materials exists
2

The kit is gathered

what do we have, what is short
3

A man walks the godown

answering a list on paper
4

The workshop waits

or starts on guesswork

The gap between a finished bill of materials and material actually moving is where solution timelines quietly die.

Available material moves now; the shortfall is procured in parallel

The requisition is raised from the bill of materials itself — nobody retypes a component list.

Production requisition
ComponentNeededIn godownRoute
Ply 18 mm — 8×412 sheets12Moves today
Laminate — walnut9 sheets45 → procurement
Soft-close hinge 110°24 nos24Moves today
Cabinet handle 192 mm12 nos012 → procurement
Available material on a delivery note today · the shortfall procured in parallel
The workshop sees one inflow, whatever the origin.
Illustrative view. Needed and in-godown are the two numbers the fork is decided on.

Available today

moves on a delivery note immediately

Short today

pending from requisition, procured in parallel

One inflow to the workshop

Both routes arrive the same way, so the workshop never has to know which was which.

Production starts with what exists, and the record — not a man's memory — carries what is still owed.

The internal gap closes; the supplier's delay stays honest

Stated plainly: the software closes your gap — the days lost to gathering, chasing and walking the godown.

It cannot manufacture a supplier's stock, and no internal system can predict a supplier's delay.

What it does instead is make the shortfall a recorded, procured, trackable fact from day one — so the wait, where there is one, is known and watched rather than discovered.

What the software closes
  • Your own gap — the days that vanish before a single panel is cut
  • The shortfall is recorded — from day one, not from the day somebody asks
  • Procured and trackable — so the wait is watched rather than discovered
What it does not
  • Manufacture a supplier's stock — no system can, and none should claim to
  • Predict a supplier's delay — the delay stays honest, and stays visible
  • Turn Thursday into Tuesday — it only stops Thursday being a surprise

The workshop reads the job, not a photocopy

What arrives with the material is the job itself: the last finalised estimate, its bill of materials, its drawings — bound to the same revision, with superseded versions unreachable.

Every requisition leaves a stamp

Raised, delivered, pending, procured, received, delivered again — each step recorded with who and when.

The act itself makes the stamp.

Trail — REQ/26/0412
RaisedPriya M.Mon 10:15 AMfrom the bill of materials
Delivered to workshopHarjit S.Mon 2:40 PMavailable lines, on a delivery note
Pending procuredsystemMon 2:40 PMtwo lines short
Shortfall deliveredHarjit S.Thu 4:05 PMsame delivery-note route
Nobody wrote this. Each line is the act of doing the work.
Illustrative view. Times are to the minute, and no line can be edited after the fact.

The kit assembles itself on record

The list stops being paper.

Available material moves the day the order succeeds; the shortfall chases itself through procurement; and the workshop starts working instead of waiting.

Raise one requisition from a real bill of materials, and watch the kit assemble on record.

Ask for a demo