In product development for bags, handbags, footwear and apparel, it is entirely normal for a style to go through multiple sampling rounds.
After the first sample, the customer may request a color change. The second round may change materials, hardware or a local structure. By the third round, new colorways may be added on top of the existing design. Each change may look small, but drawings, material consumption, the BOM and downstream production documents may all need to change with it.
The most difficult problems often appear after the sample has already been approved.
Engineering may have a file called “Final,” sales may have saved a “Customer Approved” version, and the shared folder may also contain “Final 2” and “Latest Revision.” Every file seems plausible, yet quotation, material preparation and production preparation still have to ask: Which round did the customer finally approve? Which BOM belongs to this colorway? Which DXF corresponds to the current BOM? Did material consumption change with the drawing?
If only one engineer can answer these questions from memory, the company is not truly managing product data; it is managing individual memory.
Sangely.PDM addresses precisely this relationship problem in multi-round development. It connects sample orders, development rounds, colorways, DXF files, material consumption and BOMs so that the company can judge the current product state and determine which documents downstream operations should use.
1. BOM version confusion is more than a problem of “too many files”
Many companies already have BOMs and shared folders, and engineers save another Excel sheet or file whenever the customer makes a change.
Even so, the information can become increasingly difficult to manage.
A BOM can show what materials a product uses, but it does not necessarily explain the development state to which it belongs.
The same style may have several colorways, with different shell fabrics, linings, accessories and hardware. A single colorway may also pass through several sampling rounds. When the drawing changes, material consumption and the BOM may need to be recalculated or revised.
A company therefore cannot decide whether a BOM remains usable only by its modification date or by the word “Final” in its file name.
It must confirm which sample order, development round and colorway the BOM belongs to, and which drawing and consumption data were used at that time.
When these relationships are missing, every individual sheet may appear correct while the wrong one is still used in an actual business process.
2. PDM manages the product-change process, not merely the files
Traditional folders are effective at storing files, but they do not explain why the files are related in a particular way.
Sales saves the customer information, engineering saves another file after processing the drawing, the BOM sits in a different directory, and colorway data may remain in an Excel file or conversation record. Everyone is carefully retaining documents, but each role is preserving only a different fragment of the product-development process.
When the customer repeats an order months later, or the original engineer is on leave or reassigned, the company must reconstruct what happened.
The team is no longer searching for only one file. It is trying to answer:
Why did the material change in this version? Why is this colorway different from the previous one? Why should production use the BOM from this round?
This is one of the fundamental differences between PDM and ordinary file management.
PDM does not simply centralize files. It should allow the company to understand how a product was formed step by step.
When development rounds, sample status, drawings, colorways and BOMs are recorded around the same product object, “many files” begin to become an understandable product-development process.
3. Sangely.PDM establishes product-development relationships from the sample order
Sangely.PDM can begin creating the sample-development record as soon as customer information enters the company.
Customer PDF or Adobe Illustrator files can be used to form a sample order, while employees can manually correct the relevant content according to the actual business situation.
The key point is not merely to store the customer file in the system.
The sample order serves as a unified entry point for the product-development process.
If sales, engineering and quotation personnel read the customer file separately and each creates an independent record, any subsequent style change, color change or material substitution can lead the roles to different interpretations.
When development data continues to be maintained around the same sample order, later revisions can be understood as changes within one product-development process rather than as unrelated new files.
This is the first condition for effective version management.
4. Keep DXF, material consumption and BOMs within the same product-development relationship
For bags and handbags, a BOM usually cannot be understood independently of geometric data.
The Sangely product suite can receive DXF geometry exported by CAD and use the relevant data for material-consumption calculation, nesting layouts and BOM processing.
This matters because customers often change more than a written description.
Changes in dimensions, structure or components may first appear in the geometry and then affect material consumption and the BOM.
If the DXF is one version, consumption is calculated from another, and engineering rebuilds the BOM independently, downstream departments can easily proceed from different sources of truth.
Sangely.PDM keeps these documents as closely as possible within the same product-development process. When an engineer reviews a BOM, the engineer sees not only a material list but can also find the corresponding geometry and development status.
This reduces a common situation in which the BOM has been updated but its users do not know why the update occurred.
5. Multiple development rounds and multiple colorways are two dimensions that must be managed together
Repeated sampling is already complex, while bag, handbag, footwear and apparel manufacturers usually have to manage colorways at the same time.
For example, after the third-round sample is approved, the customer may request black, beige and blue versions. The product structure is the same, but each color may use different shell fabric, lining, hardware or material combinations.
The company cannot simply know that “this is round three.”
It must also know:
“Which colorway within round three?”
The Sangely product suite supports colorway-specific BOMs and can also retain BOMs from different development rounds.
These two dimensions answer different questions.
The development round identifies how many product-modification cycles have occurred.
The colorway BOM identifies which materials are used by each color solution within the same product state.
Once the two dimensions are separated, the company no longer has to infer business status from names such as “Black Final,” “Black Final 2” or “Blue Customer Approved.”
What should be identified is the colorway within a specific development round and the BOM that corresponds to it.
6. Version management keeps downstream roles from repeatedly asking engineering
BOM version confusion appears to be an engineering problem, but it disrupts the rhythm of the entire business.
If engineering cannot confirm the current BOM quickly, sales cannot answer the customer accurately. If quotation does not know the current materials and consumption, it must verify them again. If purchasing is uncertain about colorway-to-material relationships, it cannot prepare materials with confidence. If production preparation receives a BOM with no clear status, it must find someone to reconfirm it.
Management may see only that “engineering took a little longer to find the document,” while the real cost is that several roles are all waiting for the same confirmation.
Managers can use a few practical questions to test whether their product data is sufficiently clear:
Does every style have a clear sample order that carries its development data? Can BOMs from different development rounds be recorded separately? Does each colorway have a corresponding colorway BOM? Can the relationship among DXF, material consumption and BOM be traced clearly?
If only a senior engineer can answer these questions, the company’s product knowledge has not yet truly entered the system.
7. Sangely.PDM extends product data into ERP and production operations
The value of BOM version management does not stop inside PDM.
After product development, the company must continue into quotation, orders, purchasing, warehousing and production preparation.
Within the overall Sangely product suite, samples, materials, BOMs and process data created in PDM provide a product foundation for ERP. ERP then manages orders, materials and resource planning before downstream business proceeds into manufacturing execution.
The important point is not simply that several systems are connected.
It is that product data already approved during development requires less rebuilding and re-explanation when it enters downstream operations.
If PDM has already identified the development round, colorway and corresponding BOM, quotation, purchasing and production preparation can work more easily from related data.
This reduces a very typical risk:
Development has moved to a new version, while downstream departments continue working from the old one.
8. The company needs an assessable current state, not a file called “Final”
Many companies continually create new file names when managing product versions.
“Final,” “Final 2,” “Customer Final Approval,” “Latest Production Version” …
The names grow longer, but users still ask:
“Which one is the real one?”
The problem is not a lack of stricter naming. It is that the product state itself has not been managed.
For a product that has undergone several revisions, the valuable information is the current development round, the corresponding colorway, the drawing in use, whether the BOM has completed the necessary confirmation, and which business stage it may enter next.
Once these relationships can be evaluated, the company no longer needs to trust a document merely because its name contains the word “Final.”
This is the core value of Sangely.PDM in addressing BOM version problems.
It does not simply help a company store more files. It clarifies the relationships among customer information, sample development, development rounds, colorways, DXF, material consumption and BOMs.
Conclusion: Sangely.PDM manages the current product state, not merely which file is newest
Repeated sampling is not inherently dangerous, nor are continued customer requests for color and material changes.
Real product development is a process of continuous change.
The danger appears after sample approval when quotation, purchasing and production must still ask a particular person which BOM should be used.
Sangely.PDM does not delete all historical information and retain only a so-called “final version.”
Instead, it preserves the development process and records the relationships among sample orders, development rounds, colorways, DXF, material consumption and BOMs.
After several revisions, the company can then answer:
Which development round does this BOM belong to? Which colorway does it represent? Which drawing and consumption basis were used? Why is it valid now? Which business stage should it enter next?
When these answers no longer depend on one person’s memory, the BOM becomes more than a material list. It becomes product data the company can continue to manage and use.
FAQ | Common questions about Sangely.PDM BOM version management
Q1: Is it a problem for one style to have multiple BOMs?
Not necessarily. Different development rounds and colorways can naturally produce different BOMs. The real management requirement is to identify which product state each BOM represents and which one the current business process should use.
Q2: Why not keep only the “final BOM”?
Historical development data has value for traceability and experience reuse. A better approach is to retain historical rounds while clearly identifying the currently usable product state, rather than simply deleting old versions.
Q3: What is the difference between a development round and a colorway BOM?
A development round distinguishes the product’s successive modification stages. A colorway BOM distinguishes different color and material combinations within the same product state. Together they help the company determine the product state represented by the current BOM.
Q4: How does Sangely.PDM connect DXF and BOM data?
The Sangely product suite can receive DXF geometry exported by CAD and use the relevant data for material-consumption calculation, nesting layouts and BOM processing, keeping geometry more closely connected with downstream manufacturing data.
Q5: Why does BOM version management affect ERP and production?
Quotation, purchasing and production preparation all depend on correct product structures and material information. If development has changed but downstream roles still use an old BOM, the risks of repeated verification, waiting for confirmation and document rework increase.