Skip to main content
GullySystem
A practical guide

Why customer release changes leave the shop floor on old quantities

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

The shop floor runs on old quantities because one person reads the release, retypes it into a spreadsheet, and it reaches the plan only at the next run. Issued work orders are never compared with it. A release-driven plan shows the difference.

Where the new release gets stuck

Most releases arrive as an EDI 830 planning schedule, a supplier portal download or an emailed Excel sheet, and the lines that moved are not always marked. One person opens it. Everyone else hears later, sometimes only at the morning production meeting, after the press shop has already loaded coil for the old quantity.

That person copies the numbers into a workbook, and the workbook feeds a weekly MRP run that only fires on Monday morning. If the release landed on Tuesday, the press shop builds against last week’s demand until Monday, while dies, coil and operators stay committed to quantities the buyer changed.

Nothing here is careless. Each step is reasonable. Together they open a gap, and it widens when the buyer revises a pull-in or a pushout twice in one week, with the weekend shift already loaded.

  • Release read by one inbox or one person
  • Numbers retyped into a spreadsheet
  • Planning run weekly, not on arrival
  • No alert when the quantity moves

Firm, forecast and shipped are three different numbers

A release line holds a firm quantity for the near weeks and a forecast quantity beyond them, and the two mean very different things to the press shop. Firm is a commitment. Forecast can fall or rise. Many plants add both into one demand figure. A forecast dip then cancels real work.

Shipped is the third number. The buyer tracks a cumulative received count at the dock, while your plan must track cumulative shipped from the last advance ship notice. If the two disagree, the next release shows a shortfall that was really a truck still on the road, and someone expedites parts that are already moving.

Keep the three apart on screen. Firm drives work orders. Forecast drives material and capacity. Shipped drives the balance still owed.

  • Firm quantity: schedule and ship
  • Forecast quantity: plan material and capacity
  • Cumulative shipped: balance still owed
  • Cumulative received: the customer’s count

Work orders do not move when the release does

Each released work order carries its own quantity. Changing the sales schedule does not touch it. Someone must find the order, check whether the job card has started, then amend or split the batch while the press operator waits for an answer.

Without a comparison nobody knows which orders are hit. A release that halves one bracket and raises another looks small in a spreadsheet, because the totals across both parts barely move. On the floor it means a die change, a fresh coil, a re-sequenced press shift and a second set of first-off checks.

The cost is the blanks already cut or the resin already dried for the old quantity, and both are paid for before anyone notices the release moved. Surplus finished stock sits in the bay. It ties up racks and cash.

What a release-driven plan does differently

It stores every release as a dated version. On arrival it compares each line with the previous version and lists the parts whose firm or forecast quantity moved, so the planner sees the delta first.

Next it links each change to open work orders and raw material requirements, so orders not yet started can be amended on the spot. Started orders are flagged with the extra quantity. Steel or resin shortages show the same day, not at the weekly run, because the requirement is recalculated when the release lands.

It also keeps the previous release, so a disputed quantity can be settled by pointing at the document and the time it was received.

Check how far behind you are

Take last week’s release and its work orders. Compare them part by part. Note the day the release arrived, the day the plan changed and the day the press shop saw the new number on its own job cards.

That gap is your lag. One mismatched part shows what waiting costs.

Share the sheet with the planner and the shift supervisor and agree one rule for who acts on a release the hour it arrives.

Release change log

One sheet, one row per part number. Columns hold the release date, old and new firm quantity, old and new forecast, cumulative shipped and the affected work order numbers. Final columns name the action taken, who acted and the time the shift supervisor told the press shop, the weld cell and the packing bay.

Open a blank worksheet to print

Questions owners ask

How often should a release be loaded?

On arrival, or at least daily. A weekly load leaves several days when the press shop, the weld cell and the packing bay work from outdated demand until the next run.

What is the difference between firm and forecast?

Firm is a commitment the customer expects you to ship, while forecast is only an indication for planning material and capacity that can change without notice.

Why does the cumulative shipped number matter?

Customers measure what they received against what they asked for, so your balance owed must start from the same cumulative count, or shipments in transit will look like shortages.

Can a spreadsheet handle release changes?

For a few parts, yes, if someone compares versions every time, but as parts and customers grow the comparison is skipped and old quantities stay on the floor.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements