Material Issue and Return Controls from Stores to Production

An extra issue needs a reason and a destination

A sewing supervisor asks stores for another 400 buttons. The order has already received its planned quantity. Production needs support quickly, but the request leaves several questions open. Are they replacing damaged buttons? Has the order grown, or are the missing buttons in another line’s tray?

A clear issue-and-return procedure makes this handoff prompt and easy to check. It links the goods leaving stores to an order and lot. It records the amount and who received it. Later, the record shows what went into garments, what became waste, and what came back. It also shows any stock still in production.

The procedure fails if every extra issue is treated as waste. It also fails if the factory avoids recording extra issues to keep the report looking good. The purpose is to follow the actual material and give each exception a visible route for review.

This guide focuses on fabric and trims moving between stores and production. The examples are invented and use simple quantities. They show a control method, not a standard allowance or universal document format.

Separate reservation, staging, issue and use

A reservation assigns stock to a requirement. It does not prove that the goods moved. Staging places material at a production supply point. In some systems, this is a transfer between stock locations. It does not yet record use against an order.

An issue records material against the relevant production order or operation. Physical use happens when the process consumes or incorporates it. Those events may be close together, but they are not always simultaneous.

SAP’s goods-issue guidance describes staging before a goods issue. It also explains manual and automatic posting. The factory needs to be just as clear about the event behind each entry.

For example, a trolley of thread may reach the line before anyone uses a cone. If that move is recorded as full consumption, the records must still account for unused cones. If it is a stock transfer, the line-side balance needs a custodian and later consumption records.

Draw the boundary once and use it throughout the order. Changing the terms halfway through a report can count the same buttons twice. They may appear as issued material and also as new line stock.

Start from the approved requirement

The request should name a released order and its current material plan. The plan identifies the item, variant, unit and approved amount. It also shows whether the amount includes an allowance for process loss.

Suppose an order for 2,000 garments requires five buttons each. Net product need is 2,000 × 5 = 10,000 buttons. An approved planning allowance of 2% of net need adds 200, giving an initial issue plan of 10,200.

The 2% is an assumption for this example. It is not a recommended loss rate. It also has an explicit base: 2% of 10,000, rather than 2% of the final gross requirement.

Do not add another allowance to a requirement that already includes one. Rounding up to a full pack is a separate choice from allowing for process loss. If stores issues a larger pack, record the excess stock. Someone must later account for its use, return or other fate.

The approved requirement can change. A revised size mix or added garment feature may affect material use. Keep the old version and the approval for the change. They help explain why the order needed more material.

Make the request identify the intended handoff

A short request can carry the necessary information without repeating the entire order file. It should tell stores which stock to pick and tell production what it is accepting.

Use a unique request or transaction reference. If the request is revised, the picker needs to know which version is active. Two printed copies of one request should not become two issues.

For a partial issue, record the quantity supplied and the amount still open. A request for 1,000 labels with 600 supplied should not appear fully complete. Check this open balance before raising another request for 400 labels. Otherwise, both requests might be filled.

Stores may suggest another lot or pack size. The change still needs approval through the agreed process. The fact that a substitute is available does not make it suitable for the garment.

Pick from released stock and preserve lot identity

Availability is more than an on-hand number. A roll may be present but still await inspection. It could also be reserved for another order or limited to one shade group.

Before picking, match the requested item and permitted lot with the stock’s current status. ApparelDiary’s fabric receiving checklist explains the evidence behind roll acceptance. The issue record carries that release status forward. It should respect the receiving decision without repeating the whole check.

For fabric, retain the roll and dye-lot identifiers through the transfer. If only part of a roll is issued, the remaining piece must retain a link to its parent roll and a reliable quantity. Mixing unlabelled remnants can destroy information that took effort to establish at receipt.

For trims, check the design, size, colour and any buyer-specific identification. A button with the same diameter may still have the wrong shade or branding. Similar packaging is a reason to verify identity carefully, not a substitute for it.

ApparelDiary’s shade-segregation guide provides the wider roll-to-cutting method. The issue record keeps that approved grouping intact. It also shows which material reached the order.

Confirm quantity when custody changes

The person receiving material should confirm the actual amount and identity at handoff. A signature on an unread list is weak evidence. So is a photograph of a closed carton whose contents have not been verified.

Use a practical count or measurement method suited to the item. Full verified packs can be counted by pack, with the conversion shown. Open packs need their remaining quantity. Fabric length or mass must use the stated measurement basis and unit.

Suppose the picker supplies 950 pieces against a request for 1,000. Both sides should confirm 950 at handoff. The remaining fifty stays open or is formally cancelled. Recording the requested quantity instead creates a false shortage later in production.

Partial packs need a clear conversion to pieces. Imagine a request for 625 labels in verified packs of twenty-four. Twenty-six full packs provide 624 labels, so one additional loose label completes the request. The opened pack then contains twenty-three labels. Both the issued quantity and the remaining pack quantity need clear identification.

If the store chooses to issue twenty-seven full packs instead, the physical handoff is 648 labels. That leaves twenty-three above the request. The receiver must confirm 648. The extra stock needs approval, and the order review must account for it later. Recording only 625 would hide the stock that actually left stores.

The choice may depend on handling cost, pack protection and the expected next use. In each case, record what actually moved. Then explain the link between that amount and the request. A convenient pack size must not silently change the transaction unit.

Keep material secure and identified during transport. A handler may collect goods before the line accepts them. During that trip, a transit or custody record must show who holds them. Goods should not disappear from both locations while moving between them.

The GS1 traceability framework links events with the data that describe them. For this handoff, record the item, lot and amount. Add where it came from, where it went, when it moved and who handled it. A label identifies the goods; the event record explains what happened to them.

Post the movement once, at the defined event

The physical record and system transaction should refer to the same movement. Name who posts the entry and which event time it uses. Decide how the team will find failed postings.

Microsoft’s production-posting documentation describes the effect of posting a production picking-list journal. It records material consumption and reduces stock on hand. This software event affects the accounts. It is not proof that every physical piece has already entered a garment.

A factory using this approach still needs visibility of unused issued material. The issue may charge the order while the components remain in a line tray. A later return needs the right entry to reverse or correct that record. The exact method depends on the system.

If the network is down, use the approved temporary record and give it a unique reference. Mark it as awaiting posting. When service returns, match that list to the completed entries. This check prevents the team from posting one movement twice.

Do not change a transaction’s time merely to make a daily balance agree. Preserve the physical event time and the posting time when they differ. A delayed entry is a process exception that should remain visible.

Give extra issues a controlled route

An extra issue request needs the order, item, amount and reason, plus the current position. Before asking for more, the supervisor needs the issue and return totals. They also need a count of what remains on the line.

The order quantity or approved design may have changed. Buttons may be damaged, or a lot may have been rejected. Each reason needs a supporting record. “Shortage” describes the immediate problem but may not explain its cause. It can stay as the initial reason while the team investigates.

In Oracle’s material-transaction documentation, settings can restrict additional manual material issues. This illustrates a control that should match the factory’s authority rules. A software permission alone does not explain why the extra material was needed.

For urgent production needs, define a timely exception path with a named approver. It should retain the same item, quantity and order evidence. The line may be unable to wait for the next review meeting. Its urgent request still needs a record.

The extra issue is then followed to closure. Suppose someone later finds the missing buttons in another tray. Record their return or transfer in the same order history.

Receive returns as a separate controlled event

Production should return unused material with its order reference, identity, quantity and condition. Stores checks what actually arrives before accepting the transaction.

The return may contain released, suspect and damaged material. Those groups need separate quantities and status. A mixed bag labelled “balance buttons” does not tell the next picker which pieces can be issued.

Infor’s job-material return workflow links a return to the job and operation. It also records the material, warehouse, location and relevant lot details. These fields show why a return needs more than a negative number in the issue column.

Check the return against the relevant issue history. A different lot may be legitimate only if the factory can explain how it reached the order. Do not assign it the issued lot number simply to make the software accept it.

Oracle also documents configurable restrictions on returned lot numbers. Keep the actual lot identity and use the approved route to resolve an exception. System settings should support that evidence, rather than encourage a false identity.

Keep quality-held returns separate from usable stock

A returned item is not automatically suitable for another order. Fabric may have lost its identification or been exposed to contamination. Trims may be mixed, damaged or outside the approved condition.

The receiving person records the material and its observed condition. Quality decides the release or disposition where review is required. Until then, the stock needs a clear hold status and a location that prevents accidental issue.

In the main example, stores accepts 250 unused buttons as released stock. Another eighty go into quality hold. All 330 have left production custody, but only 250 are ready for a new issue. The eighty must not inflate the released balance.

The value of a held return depends on the likely recovery and the factory’s accounting policy. That financial decision is separate from the record of who holds the goods. A move to a hold area alone proves no saving. It also does not settle which costs belong to the original order.

For partial fabric rolls, preserve the roll link, shade group and remaining amount. If a return lacks clear identity, the team may need to investigate. A correct length alone does not resolve that problem.

Follow the 10,600-button issue to its final locations

The order initially receives 10,200 buttons. A later approved request adds 400, giving 10,600 issued. At the review point, all 2,000 garments are accepted with five buttons each. The example has no opening button stock assigned to this order.

The team compiles the physical accountability record below. The 220 scrapped buttons are documented damaged or unusable pieces. The thirty on the line are counted unused stock, not buttons already attached to garments.

The unexplained amount is 10,600 − 10,580 = 20 pieces. The order is not fully reconciled. The reviewer needs to investigate those twenty. Calling them scrap without evidence would conceal the gap.

Net withdrawal from stores into production is 10,600 − 250 − 80 = 10,270 pieces. That is not the same as confirmed physical consumption. It still includes the thirty unused pieces on the line and the twenty unexplained pieces.

Accounted consumption is 10,000 + 220 = 10,220 pieces on this example’s basis. Each total answers a different question. Stores issued 10,600; after returns, the net amount is 10,270. Product use and recorded scrap support consumption of 10,220.

The net-issue figure alone is not enough to close the order. Someone must decide what to do with the line stock and investigate the gaps. Held returns also need a decision on their use or disposal.

What the extra 400 pieces actually represent

The original plan allowed 10,000 buttons for garments and 200 for expected process loss. Actual documented scrap is 220, twenty above that allowance.

The additional 400 issued pieces reconcile as 330 returned + 30 still on the line + 20 unexplained + 20 scrap above plan = 400. The entire extra issue was not waste. Nor was it all a justified increase in required product content.

If the thirty unused pieces are later returned, link that receipt to the order. If the twenty missing pieces are found, retain the discovery and transaction trail. If they remain unexplained after review, the authorised adjustment should say so honestly.

Compare fabric use with the actual approved output

A material-usage comparison needs the right output quantity. Consider a separate fabric example. An order was first planned for 500 garments at an approved gross requirement of 1.4 metres each. That rate already includes the expected cutting loss on its stated basis.

The original requirement was 500 × 1.4 = 700 metres. The customer later cuts the approved order to 480 garments. The factory has not made the cancelled twenty. All 480 are accepted, and there is no remaining work in progress in this example.

Production received 720 metres and returned thirty metres as verified released stock. For this example, production began with no fabric for the order and has no unused fabric left. All other movements have been reconciled. Net physical consumption is therefore 720 − 30 = 690 metres. Comparing it with the old 700-metre plan would suggest a ten-metre saving.

The valid allowance for the completed quantity is 480 × 1.4 = 672 metres. The actual difference is therefore 690 − 672 = 18 metres above plan, or about 2.7% of the revised allowance.

The calculation identifies a difference to explain. It does not reveal the cause. Marker performance, material changes or recutting could each play a part. Keep the supporting cutting and waste records. The 1.4-metre rate already includes its approved loss allowance. Adding a generic waste percentage would count that allowance twice.

Check automatic consumption against physical exceptions

Automatic consumption can reduce routine data entry. It needs the correct material requirement and posting event to work well. It can also leave a timing gap between the physical move and the recorded use.

Microsoft’s flushing-principles guidance describes manual, start, finish and available-at-location methods. These register material at different stages. The chosen method needs to fit how the factory controls quantities and lots.

Consider a simple backflush based on five buttons per garment. Confirming 100 garments records 500 buttons. Now suppose eight more buttons were damaged during assembly. The standard entry does not describe that extra use. Those eight need their own record and the correct posting treatment.

A return can create a different problem. The automatic posting may have assumed another lot or quantity. Check that original entry before making a correction. Otherwise, a manual change and a later automatic correction may count the event twice.

Review failed transactions as well as successful ones. A completed garment confirmation does not guarantee that every related material posting succeeded. The person handling these failures needs a visible list. Each case should close only when the physical and system records agree.

Handle transfers between lines without losing the order trail

One line may lend material to another during a rush. Without a handoff record, the first order looks short. The second may appear to have used less material than it really did. It can also mix buyer or lot restrictions.

Use the approved transfer or return-and-reissue route. Identify the source order, destination order, item, lot, quantity and accepting persons. Check that reassignment is permitted before moving customer-owned or restricted stock.

A shared supply point needs a clear method for attributing consumption. The same tray cannot be treated as a full issue to two orders. If the factory shares stock and assigns use later, define that method. The pool also needs its own balance check: opening stock plus receipts, less use, must agree with closing stock.

The physical flow may be fast, but the evidence must travel with it. A scan or approved transfer slip can preserve the link. The goods need not travel back through central stores solely to create that record.

Close the order with a material review

Before closing an order, collect its approved requirement and gross issue total. Compare them with returns, recorded use, waste and stock still on hand. Include pending entries and returns on quality hold. Another department may own the next decision, but the order review still needs to show those amounts.

The review should assign a destination or action to every remaining quantity. Reusable material may return to a defined stock location. Restricted leftovers may need buyer or internal approval before reuse. Damaged material follows the approved route for use or disposal. Keep its identity and quantity until that record is complete.

Use the result to repair the handoff that failed. Repeated extra issues caused by unrecorded line transfers need a transfer-control change. Repeated mixed returns need better containers and identification. A recurring excess-consumption pattern needs a production investigation.

A completed form is useful only when it describes the physical material accurately. The stronger result is a traceable order. Its record follows the approved request through use, return and final disposal or reuse. Any unexplained difference remains visible to the people who must resolve it.

References

1. SAP Learning. Material staging and goods issues for production orders.

2. GS1. Traceability events and the data that describe them.

3. Microsoft Learn. Production posting and material consumption.

4. Oracle. Reporting work-order material issues and returns.

5. Infor. Returning material to inventory from a job.

6. Microsoft Learn. Controlling raw-material consumption with flushing principles.