Blog

2026.11.09

Customer-Supplied Material Management: Receipt, Use and Returns

Customer-Supplied Material Management: Receipt, Use and Returns

When implementing a customer-supplied material receipt, consumption and return management system in manufacturing, the first decision is not the inventory screen. A customer owns the material while your factory holds and uses it. Both parties need evidence of what arrived, which order and work order consumed each lot, what was damaged, and what was returned. This guide helps production, warehouse, quality, finance and IT teams in Thai factories define the data, shop-floor workflow, RFP and acceptance tests.

Conclusion first: a customer column in inventory is insufficient

At minimum, keep the owner, physical custodian, customer supply reference, item and lot, received quantity, usable status, assigned sales and work order, actual consumption, damage or scrap, and return quantity. If the screen adds 50 units purchased by your company to 50 units owned by Customer A and calls the total “100 available,” it can prompt a wrongful issue. Even two lots from the same customer may be restricted to different orders.

Separate physical movements from events that affect ownership reporting and costs. Receipt, inspection hold, location transfer, issue to the line, actual use, damage, unused return to stock and return to the customer are distinct events. A move to the line must not silently become consumption. The balance owed to the customer should be reproducible by work order and lot.

SAP documents externally owned special stock held on your premises and distinguishes stock attributes including owner. Oracle’s contract manufacturing flow describes a contract manufacturer reporting production progress and consumption of OEM-supplied components so the OEM can record them. These are product examples, not universal contract, accounting or tax rules. Confirm your own agreement and finance policy before fixing posting points.

Customer-Supplied Material Management: Receipt, Use and Returns - figure 1

Define the contract: supply, custody and consignment

“Customer-supplied” can mean free-issue components owned throughout by the customer, a consignment arrangement settled on use, or materials bought on the customer’s instruction. Ownership and invoicing differ. Put the exact contract model on page one of the RFP. This guide addresses material that the customer continues to own and the factory receives and uses. A purchase or cost offset needs a different posting design.

Do not force owner and custodian into one supplier field. The customer may own a lot while your warehouse holds it and the production line temporarily holds a container. SAP’s inventory posting guidance treats owner as a stock separator. Owner alone does not grant usage rights: contract, customer order, item revision, lot restrictions, shelf life and quality approval also govern allocation.

Our production material issue control guide covers issue and consumption of materials generally. This article adds customer ownership, supply documents, return duties and reconciliation. For the broader selection programme, see the inventory management system implementation guide.

Seven agreements before the first receipt

Confirm (1) whether title transfers, (2) liability for shortages and damage, (3) permitted substitutions, (4) deadline for unused returns, (5) treatment of scrap and samples, (6) count and reconciliation frequency, and (7) reporting unit and approvers. Map the customer’s item number to the plant number with revision and effective date. Otherwise, a month later the teams may discover that offcuts had to be returned or damaged material required a separate report. A scan history cannot repair an undefined commercial rule.

Connect the receipt event to the supply notice and physical goods

Use the customer supply notice, delivery note or ASN as a candidate reference for expected receipt. Match notice ID, order, customer and plant item numbers, lot, quantity, unit, containers and expected date. Do not copy the notice quantity into confirmed stock automatically. At the dock, scan the physical labels, count the actual quantity and record condition. Shortage, excess, damage and unidentified labels need separate exception states. If photographs are required, bind each to a container ID, operator and time.

A lot alone may not uniquely identify a box. When one lot arrives in several containers or on different dates, assign each container or pallet an ID. Preserve parent-child links when a box is split or containers are merged. GS1’s Global Traceability Standard defines critical tracking events, including receiving and transformation, and their key data elements. EPCIS provides an event structure describing what, when, where and why. GS1 identifiers or EPCIS are not compulsory for this design, but are useful references when data must cross organisations.

Quality decides whether received material is usable. Separate awaiting inspection, released, held and return-pending stock. An inspection certificate supplied by the customer does not replace your physical count and packaging check. Samples taken from stock should have their own event, not disappear as an unexplained variance.

Treat line issue and actual consumption as different transactions

Giving 30 pieces to a line does not mean 30 pieces have entered product. The line may use 20, quarantine two damaged pieces and return eight unused pieces. Oracle NetSuite documents a work-order component issue as a consumption record in its product, but posting semantics differ by system and configuration. Define in your RFP exactly when the warehouse location falls, line location rises, cost changes and the customer balance changes.

Moving 30 pieces from warehouse to line leaves total material in plant custody unchanged. Actual use of 20 against a work order reduces the unused balance by 20. The two damaged pieces may have been consumed in a process or damaged in handling; the customer’s report and liability may differ. The eight returned pieces may need quality hold if their container has been opened.

Backflushing calculates theoretical use from good output and BOM. Rounding, yield, wrong feeds, trials, setup and rework create differences from actual use. Do not turn a theoretical value silently into the final value. Set item-specific tolerances, capture actual quantity and reason, and approve variances when needed. Production output and material use may share a terminal but should retain separate correction histories.

Customer-Supplied Material Management: Receipt, Use and Returns - figure 2

Keep balances by owner, order, lot and container

The minimum stock key is owner, item, lot, location and quality status. Add order and work order where supply is order-specific; add container ID where boxes have their own labels and quantities. Show total, allocable, line-issued, inspection-held, return-pending and customer-returned amounts separately. Decide whether scanning Customer A’s lot for Customer B’s job triggers a hard stop or a controlled exception according to the contract and risk.

The apparent same item may conceal a different revision, and “one box” can mean different piece counts. Keep customer item, plant item, revision, base unit, conversion factor and effective period. Store the original unit and quantity as well as the converted number. An opened box containing 97 pieces must not be overwritten as 100 because its old standard pack size is 100. Weighed materials may require gross, tare and net weight, scale ID and calibration status.

Moving material between orders is not a bin transfer. Record it as a controlled order reassignment with customer permission, approver, source and destination orders, lot, quantity and time. When an order changes, distinguish material still on the line, unopened containers and partly used boxes.

Reproduce reconciliation from the event ledger

Month-end differences are not always counting errors. The parties may use different posting dates, units, order closing dates, scrap definitions or treatment of returns in transit. Define both stock in factory custody and the balance subject to return, then report by customer, supply notice, order, item and lot. The following is a design example, not a contract-specific settlement rule.

Plant custody balance = opening balance + actual receipts − actual consumption − customer returns − approved disposal ± approved corrections. Material awaiting inspection still exists in plant custody. Agree when a return in transit leaves the balance. Unused line-to-warehouse movement does not change the plant total, though it changes location balances. Allocation and release affect the order balance but not the plant total.

Hypothetical example: Customer A supplies 100 pieces of lot L. Allocate 60 to order P and 30 to order Q; ten remain unallocated. Move 50 to P’s line, consume 40, isolate two damaged pieces and return eight unused to the warehouse. Consume 20 on Q and return ten unused pieces to the customer. If the two damaged pieces have not been approved for disposal or physical return, keep them in a “damaged hold” state. Once 60 have been consumed and ten returned to the customer, plant custody is 30 pieces. These numbers illustrate the ledger only; they are not an actual case or performance claim.

EventPhysical locationTotal in plant custodyEvidence needed for customer report
Actual receiptDock or inspectionIncreasesSupply notice, count, lot, container, variance
Warehouse-to-line moveWarehouse to lineUnchangedFrom/to location, work order, operator
Actual consumptionLine into processDecreasesWork order, output lot, actual amount, time
Damage or scrap holdQuarantineNot yet finally classifiedReason, photo, liability, approval
Unused material returnLine to warehouse/holdUnchangedOriginal issue ID, quality decision
Return to customerReturn dock to customerDecreases at agreed handoverApproval, dispatch and receipt evidence
Customer-Supplied Material Management: Receipt, Use and Returns - figure 3

Decide how to handle damage, offcuts, samples and substitutions

Combining damage and offcuts with normal consumption makes yield look simple but removes customer evidence. Record whether damage happened before supply, in storage or during processing, who decides, and who bears it. If it is disposed of, define customer approval, photos, disposal evidence and collector records. If it is returned, keep damaged material labelled and physically separate. If scrap is weighed in kilograms while supply is in pieces, record the conversion basis.

Separate trials, first-article builds and inspection samples from mass-production consumption. Moving trial supply into a production order requires approved reassignment. Substitution is more sensitive: similar part numbers may refer to different drawings or approved processes. Check approval number and validity before suggesting an alternative. Exclude unapproved substitutes, held stock and return-pending stock from available quantity.

A customer’s permission to share a lot across orders should not become a permanent master-data change on the basis of a call or one email. Record permitted orders, quantity limit and validity period. The reason must be understandable during a later customer audit.

Who closes a difference created during production?

The warehouse may correctly report the quantity it gave to the line, production the quantity it used, quality the quantity rejected, and the customer the quantity supplied. Those four correct figures are not supposed to be equal at every moment. Show expected receipt, actual receipt, line movement, use, samples, damage hold and returns in one event history. A difference should lead an operator to look for a missing event before making an adjustment.

If a pouch is opened and a machine stops before the material is used, the warehouse issue is valid and zero consumption is also valid. Returning that pouch must reference the original issue and record its opened state. Quality decides whether it is usable again; a night shift can leave it held for the next shift. Give different approvals to a recount correction, process yield variance, disposal and a loss chargeable to the customer. One administrator button approving all four hides the business decision.

Acceptance must also test the reverse question: for one customer supply notice, which material remains in the factory, which went into output lots, which is held damaged, and which was returned? Split a container, use it on two work orders, return part, then issue that part again and trace every branch to the notice. Show physical location alongside ledger state. A return-approved box still at the return dock is physically in the plant; a dispatched box awaiting customer receipt is in transit. The agreed handover point determines when its balance falls.

If the customer cancels or changes a supply notice, do not erase goods already received. Version the notice and change either the not-yet-arrived expectation or the disposition of stock already in custody. When an order is cancelled, inventory on the line and in unopened warehouse boxes needs separate review of quality and customer instructions. Editing the notice to make an original receipt shortage disappear destroys evidence.

Where several customers’ materials share a rack, use physical labels and hold areas alongside system controls. A wrong box carried to the line still wastes time even if the terminal eventually blocks it. Display owner and order on pick instructions and scan both rack and container before issue. Avoid placing identical items with different owners in adjacent bins where possible.

When a previous month’s use arrives after finance closes the period, do not overwrite the original event. Preserve event time and posting time, link the correction to the original and retain the report already sent to the customer. The contract should say whether to reissue that report or adjust the next month. Keep discovery date, approver and revised report version so the history remains explainable.

Assign the ERP, MES, WMS and QMS system of record

ERP often holds customer, order, contract, item and finance processing; WMS often holds receipt, bin, container and movement; MES often holds work order, operation, input lot, good/reject output and actual consumption. These are common roles, not fixed rules. If your ERP already manages locations and lots, use that capability. Specify the system of record for each event in the RFP.

For example, ERP could own the supply notice; WMS the actual receipt and container; QMS the release decision; MES the work order and use; and ERP the customer balance report. WMS sends one confirmed receipt and stores the ERP document number. If MES sends use to WMS and ERP separately, use an event ID so retries do not deduct the customer balance twice. Specify sender, event ID, event time, registration time, source transaction, version, unit, quantity, error, retry count and acknowledgement.

A copied balance on a shop-floor device is a display, not another authority to edit stock. Repeated taps, timeouts and batch reruns must return the result for an existing event ID instead of adding quantity again. Plan how to resolve out-of-order messages, such as a return received before its original receipt event.

Design screens around exceptions operators really face

A normal demo scans one box matching one notice. Actual docks see unreadable labels, split boxes, different customer and plant codes, missing notices and shortages. Decide for each whether to stop, provisionally receive into quarantine or notify an owner. Do not hide the exception by confirming a clean receipt.

A container scan should quickly show owner, notice, lot, expected count, quality status and allowed orders. Keep routine entry brief. Require a reason and permission for quantity overrides, reprints, order reassignment and disposal. At SAT, check gloves, screen glare, scanning distance and Wi-Fi handover on the real shop floor.

During network loss, decide by item risk whether a terminal may queue events or must stop receipt and use. Two offline devices changing one container can conflict. Keep both device event time and server registration time; hold conflicting messages rather than overwriting silently. If paper emergency forms remain, train staff on later entry and duplicate detection.

Close the return and monthly reconciliation loop

A warehouse return is not yet a customer return. Separate selection, quality check, customer approval, packing, dispatch, transit and customer receipt. Lock return-pending boxes against ordinary allocation. If several original receipts go onto one return pallet, preserve the links back to every container, lot and notice.

The monthly report should show opening, receipts, use, approved disposal, returns and closing by customer, item, lot and order. Each number should drill down to events, and reports need version and approval dates. When the customer ledger differs, investigate missing notices, lot mapping, month-end timing, unit conversion, damage and transit before posting a blind balancing adjustment. Link a correction to its original event; do not erase history.

CSV exchange can be a practical first step if the customer uses Excel. Freeze column meanings and reporting time, and keep a mapping table, exception list, reconciliation result and approval record. An eventual API or EDI connection should preserve event IDs and supply references.

Prepare the data and owners before procurement

Collect one real month of anonymised notices, delivery notes, labels, work orders, good/reject records, return notes and customer balance files. Identify the owner of each data field across customer service, warehouse, production, quality, finance and IT. Count missing lot fields, unknown conversions, uses without orders, ambiguous item mappings and returns that cannot be traced to receipts.

Data or ruleCheckDecision owner
Customer contractTitle, loss, returns, billing boundarySales, finance, customer contact
Supply noticeReference, item, lot, expected amount, cancellationCustomer contact, warehouse
Item and unitTwo item codes, revision, conversion, substitutionEngineering, planning
Container and locationUnique ID, split/merge, hold areaWarehouse, quality
Work orderCustomer order, BOM, operation, changesPlanning, production
Use and damageActual amount, reason, liability, approvalProduction, quality, finance
Return and reconciliationHandover, receipt evidence, cut-off, report unitsWarehouse, customer contact, finance

A full historical migration may not be necessary. A physical count by customer and lot at cutover can become an approved opening balance. Preserve its evidence and access to the old ledger. Keep unresolved in-transit returns and quality holds on a migration exception list.

Make the RFP a set of transactions, controls and evidence

“Supports customer-supplied material” is too vague to compare vendors. Provide anonymised sample data for two customers, purchased and supplied stock of the same item, a split lot, two orders, partial use, damage, return and month-end crossover. Ask for a demonstration and the ledger and CSV after every event.

Require owner/order stock separation, container IDs, lot and quality hold, substitution approval, order reassignment, unused return, damage disposition, customer return approval, reconciliation and audit search. Specify the ERP/MES/WMS/QMS interface owner, direction, timing, retry, deduplication, units and timestamps. Include offline behaviour, roles, logs, backup, language screens and data export. Compare licenses, scanners, printers, Wi-Fi, interfaces, master cleanup, migration, training, support and costs of adding another customer. Measure current reconciliation effort, variances, misuses and return delays before claiming any savings.

Prove the balance in PoC, FAT and SAT

Avoid a one-box happy path. A hypothetical test could start with a 100-piece notice, 98 actually received, two containers, one held for inspection, partial allocation to P, issue, actual use, damage, unused return and customer return. Compare owner, location, allocable amount, work-order balance and customer report after every event. These are test values, not operational results.

FAT reproduces transactions and integration in the vendor environment. SAT repeats them with the Thai plant’s shelves, labels, devices, radio coverage, shifts and actual operators. The pass condition is that wrong-order use is blocked, permitted use posts once, and the return and customer balance can be traced. Include network loss, repeated scans, damaged codes, period-closed corrections and concurrent work.

TestFAT evidenceSAT additionPass condition
Wrong customer scanOwnership rejection and logReal container labelNo wrong use; reason retained
Short receiptExpected/actual difference and holdPhysical recountDifference remains reportable
Partial use and returnOrder, lot, original issue IDOpened box and quality reviewPlant and location balances agree
DamageHold, approval, disposal/returnQuarantine and photographNo unapproved disappearance
Retry and repeated scanSame event ID replayWi-Fi change, device restartOne posting, missing queue visible
Month-end correctionEvent formula and detailsActual customer reportDifference traced and approved

Do not accept a defect that allows another customer’s stock to be consumed or a retry to post twice. Fix and retest. Invite the staff who perform customer reconciliation to SAT, using the real report format.

Roll out to one customer and material group first

Starting with every customer combines different contracts, labels and order conventions. Choose one high-volume or high-risk customer, one material family, one warehouse and one operation. Still cover receipt through return and reconciliation end to end. Digitising receipt while leaving consumption and returns in Excel does not establish a trustworthy customer balance.

At cutover, close the old ledger, count stock, approve an opening balance with the customer, relabel containers and define open work-order treatment. Set a clear parallel-run period and input sequence. Keep holds and unacknowledged returns on an exception list. After launch, monitor customer reconciliation differences, unresolved holds, line stock lacking use records, approval-to-dispatch time and rejected wrong scans. An initial rise in rejected scans may reveal formerly invisible errors; review causes before judging the trend.

FAQ: customer-supplied material management system

Can purchased and customer-owned material share one system?

Yes, if owner, permitted order, valuation and return duty remain separate. Test that the same item and lot do not get pooled for allocation. An existing ERP special-stock feature may be sufficient.

Does customer-supplied material enter cost at receipt?

There is no universal answer. Free-issue custody, purchase and service-fee offset have different accounting consequences. Implement the agreed contract and finance policy, retain quantity evidence, and have finance or a qualified adviser review it.

Is a barcode enough for lot traceability?

No. The ID must connect receipt container, operation input, output lot, damage and return events. Also test splits, merges and manual corrections.

How much does implementation cost?

Cost depends on customers, contracts, ERP/MES/WMS, labels, devices, reports and interfaces. Fix the scope in an RFP and compare initial, ongoing and additional-customer costs.

How is this different from supplying a subcontractor?

When you send your material to a subcontractor, you are the supplying owner. Here your factory is the custodian of the customer’s material. The supply notice, permission to use, balance report and return evidence have different owners. Do not merely reverse an outward subcontracting settlement workflow.

Summary

Implementing customer-supplied material control means connecting receipt, actual use, damage, unused returns and customer returns to owner, order and lot. Agree the contract and system of record first, build an event ledger and balance formula, then test exceptions in RFP, FAT and SAT. A shared, reproducible transaction history makes monthly reconciliation more reliable than unexplained balance adjustments.

If you are still defining how your Thai factory should manage customer-supplied receipt, use, returns and reconciliation across ERP, MES and WMS, contact TOMAS TECH. An early discussion of the current forms and process is welcome.

Sources