What Data Do Textile Firms Need for ERP Purchasing
An ERP purchasing system can organize supplier records, purchase orders, stock information, and approval tasks in one place. Getting those functions to work properly, however, depends on the quality of the information entered before the system goes live.
Textile businesses often build up purchasing records over many years. A buyer may keep supplier quotations in spreadsheets, the warehouse may record incoming fabric separately, and production staff may send material requests through email or internal messages. These arrangements can work when the same people handle the same tasks every day. Problems tend to appear when an employee is absent, an order changes, or several departments need to check the same information.
Moving these records into an ERP system does not automatically solve the underlying problems. If a supplier appears under different names, the material list contains duplicate entries, or stock quantities have not been checked, the new system may carry those issues into daily operations.
Preparation does not have to begin with a large data-cleaning project. A more manageable approach is to identify the information that purchasing relies on, check whether it is dependable, and decide who will maintain it after implementation.
Begin With the Way Purchases Actually Work
Before collecting files, the company needs to see how a purchase moves through the business.
Consider a production team that needs additional fabric for an order. Someone checks the requirement, another employee reviews available stock, and a buyer contacts suppliers. The purchase may then require approval before the order is sent. When the fabric arrives, warehouse staff check the delivery and record the quantity received.
In practice, this process is rarely identical for every purchase. Regular yarn orders may follow an established routine, while a new finishing material could require a technical review. An urgent request may arrive after the normal purchasing schedule has been prepared.
These differences matter when setting up an ERP workflow. A system cannot handle exceptions sensibly if the company has never agreed on how they should be handled.
The purchasing team should first map the main steps and identify the information required at each point. There is no need to document every conversation. The focus should be on decisions, records, and responsibilities.
Questions worth settling include:
- What information must a department provide before requesting materials?
- Who checks existing stock and materials already allocated to production?
- Who is allowed to select a supplier or change an order?
- Which purchases need approval before the supplier is contacted or an order is issued?
- Who records partial deliveries and reports differences between ordered and received quantities?
- What information does finance need when checking an invoice?
These questions often reveal that a problem blamed on software is actually caused by an unclear working arrangement. For instance, if production and purchasing use different versions of a material requirement, the company needs to decide how changes will be communicated and which record takes priority.
The agreed process should become the basis for data preparation. Otherwise, the implementation team may spend time importing records that do not support the way the business operates.
Clean Up Supplier Records First
Supplier information is a sensible starting point because almost every purchasing transaction depends on it.
A textile company may buy yarn from one group of suppliers, fabric from another, and dyes, finishing materials, labels, or packaging from several others. Over time, contact details change and supplier names are entered in different ways. One buyer might use a shortened name, while another copies the name from an invoice.
When these records are imported without review, a single supplier can appear more than once. Buyers may then struggle to find previous orders or compare current quotations with earlier purchases.
The first task is to match duplicate entries and establish a consistent record for each supplier. This does not mean every historical entry should be deleted. Old records may still be needed to trace past transactions, but inactive suppliers should be clearly distinguished from those currently approved for purchasing.
The information to retain depends on the relationship, although most businesses will need a common set of fields.
| Supplier information | Details to prepare | What to check |
|---|---|---|
| Business identity | Supplier name, internal code, address | Whether several records refer to the same business |
| Communication | Ordering contact, sales contact, email and telephone | Whether the details are still in use |
| Commercial terms | Payment arrangements, quotation conditions, applicable order requirements | Whether the terms are current and properly recorded |
| Delivery arrangements | Delivery location, shipping responsibilities, expected lead time | Whether purchasing staff have a realistic planning reference |
| Supplier status | Active, inactive, restricted or under review | Whether the supplier can be used for new orders |
A supplier record should contain information that employees can actually maintain. Adding fields that nobody checks creates extra work without making purchasing more reliable.
It is also worth separating supplier identity from supplier performance. A company may remain in the supplier list even when a particular delivery has caused a problem. That issue should be recorded through an appropriate review process rather than handled by creating another supplier entry or changing the name informally.
Where several departments contact the same supplier, they should use the same approved contact record. This makes it easier to follow quotation changes, delivery discussions, and unresolved order issues when responsibility passes from one employee to another.
Give Every Material a Clear Identity
Material records require particular care in textile purchasing. Similar names do not necessarily mean that two items can be used in the same production process.
Two fabrics may share a general description but differ in composition, construction, finish, color, or intended application. Yarn may be distinguished by fiber blend or count. Finishing materials may have similar names while serving different purposes.
If these differences are missing from the records, a buyer could select an item that looks correct in a search result but does not match the production requirement.
A material master should give each regularly purchased item a consistent code and description. The details attached to that record should help employees distinguish it from similar materials without forcing them to read a long note every time they place an order.
The required fields will vary by material type.
| Material category | Useful identifying details | Frequent source of confusion |
|---|---|---|
| Yarn | Fiber composition, blend, count or grade where relevant | Similar names used for yarn with different properties |
| Fabric | Composition, construction, width, color, finish | Different specifications stored under one general description |
| Dyes and finishing materials | Material identity, grade, intended application | Similar descriptions that conceal different uses |
| Labels and accessories | Item code, style, color, material | Duplicate records created for the same item |
| Packaging supplies | Packaging type, dimensions where relevant, purchasing unit | Different departments using different names for the same supply |
The list should be adapted to the company's actual materials. A field is useful when it affects purchasing, production, inspection, or storage. Details that have no operational purpose do not need to be added simply to make the record more elaborate.
Units of measure deserve a separate review. Fabric might be purchased by length but stored by roll, while other materials may be bought by weight and issued according to a different unit. The system needs a documented way to handle these differences.
Employees should not have to guess whether two quantities are comparable. If a conversion is necessary, the approved method and the person responsible for maintaining it should be recorded.
Material status also needs attention. Discontinued items, old color variations, and materials retained only for occasional orders should not be mixed without distinction into the active list. Historical records can remain available without appearing as ordinary purchasing options.
A clear material list reduces repeated clarification between purchasing and production. It also makes it easier to check whether a new order refers to the exact item previously purchased.
Record Which Suppliers Can Supply Which Materials
A supplier list and a material list become much more useful when the relationship between them is documented.
A supplier may offer several fabric types but only certain finishes. Another may provide a material that has been approved for one production application but not another. These distinctions can be lost if purchasing staff rely entirely on memory or old email exchanges.
For each relevant supplier-material relationship, the company should record the information needed to place an order with reasonable confidence.
This may include the approved material code, current quotation conditions, normal lead time, minimum ordering requirements where applicable, and any relevant quality documentation. If a supplier is approved only for a particular specification, that restriction should be clear.
Price records need context. A quotation may depend on the order quantity, delivery arrangement, or other commercial conditions. A price copied into a spreadsheet without those details can be misleading when a buyer compares it with a newer offer.
Historical prices should remain identifiable as historical information. They can help explain past purchasing decisions, but they should not be mistaken for a current commitment from the supplier.
Lead times need similar treatment. A previous delivery may have arrived quickly because stock was available at the time. That does not necessarily mean the same material can be supplied on the same schedule for the next order.
The purpose of linking suppliers and materials is not to lock buyers into one source. It is to show which purchasing options have been reviewed and what conditions apply to each one. When an alternative supplier is considered, the business can identify which approvals or checks are still needed.
Check Stock Before Importing Inventory Data
Purchasing decisions are difficult to make when stock records cannot be trusted. A material may appear available in the system even though it has been reserved for production, is awaiting inspection, or has been set aside because of a quality concern.
These distinctions can affect whether a new purchase is necessary.
Imagine that a fabric delivery arrives shortly before a production order is due to start. The warehouse records the physical arrival, but the material has not yet passed inspection. If purchasing treats the full quantity as available stock, it may cancel a planned order too early. If the inspection later identifies a problem, the production schedule could be affected.
The ERP system therefore needs inventory information that reflects how the warehouse actually operates.
Before migration, the company should separate the main stock situations:
- Available stock: Material that can be used for normal business requirements.
- Reserved stock: Material already allocated to a production order or another confirmed requirement.
- Incoming stock: Material covered by an order that has not been fully received.
- Stock awaiting inspection: Goods that have arrived but are not yet cleared for use.
- Obsolete stock: Material retained in storage but no longer expected to support routine purchasing or production.
The names may differ between companies. What matters is that staff understand the meaning of each status and apply it consistently.
Opening balances should be checked against physical inventory records. Importing a quantity from an old spreadsheet is not enough if the warehouse has since moved, consumed, returned, or written off some of the material.
Storage locations should be standardized at the same time. If one record identifies a warehouse and another identifies a shelf or storage area, the company needs a consistent structure that employees can follow.
There should also be a clear division of responsibility. Warehouse staff generally record physical movements, while purchasing staff maintain order commitments. Both activities affect the information used to plan new purchases, but they are not the same task.

Review Open Purchase Orders Separately
Completed purchase orders and outstanding orders serve different purposes during ERP migration.
Historical orders may be needed for reference, supplier reviews, or spending analysis. Open orders affect current operations because they represent materials that may still arrive and quantities that may still need to be paid for.
The company should therefore review open orders individually rather than treating them as part of a general historical import.
For each outstanding order, confirm the supplier, material code, ordered quantity, unit of measure, agreed price, expected delivery, and current status. The quantity already received and the quantity still outstanding need particular attention.
Partial deliveries are a common source of confusion in older records. An order may originally have covered several rolls of fabric, but some of the goods have already arrived. If the received quantity has not been entered correctly, the system may show an inaccurate outstanding balance.
Changes and cancellations need the same scrutiny. An order that has been replaced by a revised version should not remain open without explanation. Otherwise, purchasing staff may believe that more material is on the way than the supplier has actually agreed to deliver.
A useful review involves comparing purchasing records with warehouse receipts and supplier confirmations. Where invoices or payment commitments are part of the migration scope, finance should check the relevant records as well.
Not every old order needs to be loaded into the new system in full. The company should decide which historical details are needed for day-to-day work and which can remain in an accessible archive. That decision should be made before migration begins, not after the new system has become crowded with records that employees rarely use.
Prepare Purchase Request and Approval Information
ERP purchasing also depends on how employees request materials and authorize spending.
A request that simply says additional fabric is needed leaves several questions unanswered. Which material is required? What quantity should be ordered? When must it arrive? Which production order or department needs it?
If these details are missing, the buyer has to go back to the requester before the order can move forward.
The company should define the information required for different types of purchase requests. A regular material replenishment may need fewer supporting details than a new finishing material that requires technical review.
Approval responsibilities should be documented before they are configured in the system. In one business, a department manager may confirm the need while purchasing checks supplier conditions. In another, finance may also review certain spending commitments.
The aim is to make the decision path clear without adding unnecessary steps.
A practical responsibility structure may include:
- Requesting department: Describes the requirement and confirms the intended use.
- Purchasing team: Checks material details, supplier options, and commercial conditions.
- Approver: Confirms that the request follows the company's authorization rules.
- Warehouse team: Records receipts and reports differences between the order and the delivery.
- Finance team: Checks invoices and payment information according to its responsibilities.
Smaller businesses may assign several of these duties to the same employee. Even so, the required checks should be clear, especially where one person can create an order, approve it, and confirm its receipt.
Exceptions also need a defined route. Urgent purchases happen in textile operations, but an informal exception should not leave the company unable to identify who authorized the commitment or why the usual process was bypassed.
Agree on Data Ownership Across Departments
Purchasing information is not maintained by the purchasing team alone. Production provides requirements, the warehouse records movements, quality staff handle inspection decisions, and finance maintains financial information.
When each department uses its own descriptions and status terms, the ERP system may contain several versions of what should be the same business record.
The company should decide which department owns each data category and which employees can change it. This does not mean other departments cannot use the information. It means changes should follow an agreed process.
| Data category | Responsible function | Main task |
|---|---|---|
| Supplier records | Purchasing | Maintain approved supplier identity and commercial details |
| Material records | Materials management with technical input | Maintain codes, descriptions, and relevant specifications |
| Inventory records | Warehouse or inventory control | Record stock movements and reconcile balances |
| Purchase orders | Purchasing | Track order changes, receipts, and outstanding quantities |
| Approval rules | Relevant managers | Define authorization responsibilities |
| Payment information | Finance | Maintain financial and payment records |
The exact arrangement will depend on the company's structure. A business with a separate materials management team may assign material records there, while a smaller operation may keep that responsibility within purchasing.
What matters is avoiding a situation where several employees can change the same information without knowing about one another's changes.
Naming conventions should also be agreed upon. Supplier names, material descriptions, units, date formats, and order statuses should follow consistent rules. If a material specification changes, the company needs a way to distinguish the revised record from the previous one without losing the history of earlier purchases.
A straightforward ownership arrangement can prevent many routine data problems. It also gives employees a clear person to contact when they find an error.
Test the Data Before Daily Purchasing Moves Into ERP
Data preparation is not complete when the spreadsheets have been cleaned and imported. The records need to be tested against actual purchasing tasks.
Start with a small group of representative transactions. A normal material order is useful, but it should not be the only test. The team should also check a partial delivery, an amended order, a supplier with several similar materials, and a delivery that requires inspection before use.
These cases expose problems that may remain hidden in a simple demonstration.
Before the system goes live, check for duplicate suppliers, incomplete material descriptions, inconsistent units, unexplained stock differences, and open orders that no longer reflect the supplier's commitment.
It is also important to confirm that approval rules work as intended. A request should reach the appropriate person, and an unauthorized change should not pass through simply because the underlying record is incomplete.
Employees who handle purchasing and receiving should take part in the tests. They are more likely to notice practical issues, such as a missing field for partial receipts or a material description that does not distinguish between two commonly purchased fabrics.
If an error appears, the team should identify whether it comes from the original data, the workflow configuration, or the way the system handles the transaction. Correcting the source of the problem is more useful than repeatedly fixing individual records after go-live.
Move the Data in a Controlled Order
The order of migration matters because purchasing records depend on one another.
Supplier and material records generally need to be ready before open purchase orders can be imported reliably. Inventory balances also need to reflect the agreed transition point, while outstanding orders should be reconciled with actual receipts and supplier confirmations.
A migration plan should identify the source of each data set, the person responsible for checking it, and the conditions that must be met before it is accepted.
The company also needs to decide how to handle changes made during the transition. If a buyer updates a quotation or changes an order after the data has been extracted, that change must not disappear when the new system starts operating.
A defined cutover process helps employees know when to stop using the old records as the main source of operational information. Historical files should remain accessible when they are needed for traceability or reference.
After migration, selected records should be compared with the approved source data. Supplier details, material codes, stock quantities, open order balances, and approval settings all warrant checks appropriate to their role in the process.
Training should use the same records and situations employees will encounter in normal work. Staff need to know not only how to create a purchase order, but also how to correct a material record, record a partial receipt, report a discrepancy, and follow an approval request.
An ERP purchasing process is easier to maintain when employees know where the information comes from and who is responsible for keeping it accurate.
The preparation work may take time, particularly when records have accumulated across different files and departments. That effort is more manageable when the company focuses first on information that directly affects purchasing decisions.
Clean supplier records, identifiable materials, dependable stock balances, accurate outstanding orders, and clear approval responsibilities provide a workable foundation. The system can then support purchasing operations without requiring employees to keep correcting the same underlying problems by hand.

