Tech Pack vs PDM: Tools for Managing Bag Specifications

The two are often presented as a choice between an old way and a new one, and that framing is wrong. A pack is the right tool for a single product and for a range where every style is genuinely different. A system is the right tool where the same component appears in many styles and has to change in all of them at once.

The test is simple and it can be run on a spreadsheet in an hour. List every component line across the range and count how many references are shared by more than one style. Where that count is small, a pack per style is sufficient. Where it is large, every change to a shared component is a change to several documents, and those are the changes that get missed.

What follows is a comparison rather than a recommendation, because the answer depends on the range and not on the tool. The sections below set out what each does, what each costs, and the point at which the second becomes worth the money.

What Is a Tech Pack in Tool Terms?

A self-contained document for one product, usually a file with a drawing, a materials list, a construction note, an artwork block and a BOM. It is written by one person, it is sent as a file, and it is read by a sample room and by a cut room. Everything the product needs is inside it.

That self-containment is the strength and the weakness. It means the document can be sent to anybody and read without any context, which is exactly what a buyer needs when a style moves between suppliers. It also means the same zipper line is written again on every pack that uses it.

The failure mode of the pack is therefore duplication rather than loss. A component changed on one pack and not on the others produces a range that is inconsistent in a way nobody decided, and the inconsistency is only visible when two styles sit side by side.

What Is a PDM or PLM System?

A database of components, materials and documents that products are assembled from. Product data management, written PDM, is the component and document layer; product lifecycle management, written PLM, extends the same idea across development, costing and sourcing. For a bag programme the useful part is the component layer.

In a PDM the zipper exists once, with its six fields, its supplier and its test figures. Twenty styles reference it. When the supplier changes the part, one record changes and twenty products are updated, and there is a list of which twenty.

The second capability is the audit trail. A system records who changed what and when, which a file does not. Where a programme has to demonstrate that a restricted-substance declaration was current on a date, that record is the evidence, and a file name is not.

What Does a Spreadsheet Do Well and Where Does It Break?

A well-built spreadsheet does most of what a bag programme needs, and it does it for no licence cost. A components tab with one row per reference, a styles tab referencing those rows, and a revision column on both gives a programme the reuse and a good part of the audit trail.

It breaks at three points. It breaks when two people edit it at once, which produces two versions and no record of which is current. It breaks when the reference list grows past a few hundred rows, because the lookups become fragile and the file becomes slow. And it breaks when somebody needs to know what a component was on a date in the past, because a spreadsheet holds the current state and not the history.

Those three are the real triggers for moving to a system, and the third is usually the one that forces it. A programme that has to answer a question about what was specified eighteen months ago cannot answer it from a file.

What Does a PDM Add That a Pack Cannot?

Three things, and only the first is obvious. The first is the where-used list: given a component, which products use it. That single query is what turns a supplier change from a search into a report, and on a range of twenty styles it is the difference between an afternoon and a minute.

The second is the history. A system keeps what the record was before each change, so a question about what was specified on a particular order can be answered from the record rather than from memory. On a compliance question that difference is the whole answer.

The third is controlled vocabulary. A system makes a buyer choose a component from the list rather than type one, which is what stops the same zipper appearing under four spellings. On a spreadsheet that discipline is possible and it is not enforced, and in practice it does not survive contact with a busy week.

What Does a PDM Cost Beyond the Licence?

Data entry, and it is larger than the licence. Every component has to be created once with its full set of fields, and a range of twenty styles carries several hundred component records. At ten minutes a record that is a person-week of work before the system is useful at all.

The second cost is discipline. A system with half-populated records is worse than a spreadsheet, because it looks authoritative and is not. Where a programme cannot commit to completing every field on every record, the spreadsheet is the better answer for now.

The third cost is export. Suppliers work from documents, so whatever the system holds has to come out as a pack anyway. A system that produces a clean pack per style is worth having; one that produces a report nobody can send is not.

How Are Revisions Handled in Each Case?

In a pack, by a revision letter and a date on the document, with the previous version kept as a file. It works, and it depends entirely on somebody filing the old version. Where two people hold copies, two revision letters are in circulation and neither is provably current.

In a spreadsheet, by a revision column and, in a better-built one, by a change log on a separate tab. It works for one editor and degrades fast with two, because the log is only as good as the discipline of filling it in.

In a system, by a versioned record with an author and a timestamp, which is the only one of the three that is enforced rather than voluntary. That is the single largest practical difference between the tools, and it is the one that matters most on a compliance question.

How Does Either Reach the BOM and the Supplier?

As a document, in both cases. A supplier works from a pack, from a materials list and from an approved sample, and none of those is improved by being a database record. Where a programme uses a system, the system has to produce the pack as an export rather than expecting the supplier to log in.

The BOM is the second export. It is a table of consumption per component per bag, extended by the order quantity and by the size run, and it is the document the price is built from. Whether it comes from a pack or from a system, it has to come out with the component references on it rather than with descriptions.

The third export is the compliance file. A declaration or a certificate attached to a component record is only useful if it can be produced for a shipment, and that is a report the programme should test before it needs it rather than on the day it does.

What Does a Small Programme Actually Need?

One pack per style, held in one place, with a named revision; one component list shared across the range, held as a spreadsheet with one row per reference; and one folder of certificates and declarations, named to match the references. That is the whole of it, and it answers most of what a growing range asks.

The two disciplines that make it work are naming and archiving. A reference named once and used everywhere, and an old version kept rather than overwritten. Both cost minutes and both are what a system would otherwise enforce for a licence fee.

Where a programme does outgrow it, the migration is straightforward, because the component list is already the table the system needs. Building that list early is the single best preparation for a later move, and it costs nothing.

What Goes Wrong When a System Is Adopted Too Early?

The data is never completed. A system bought before the range justifies it gets populated for the styles in development and not for the ones already shipping, which produces a tool that is right about half the range and trusted about none of it.

The second failure is that the export is never built. A system that holds good data and cannot produce a pack per style creates a second manual step, and the manual step is where the pack drifts from the record. Where a system is adopted, the export is the first thing to build rather than the last.

The third is that nobody owns it. A system without a named owner becomes a place where records are created and not maintained, and within two seasons it holds more wrong data than a spreadsheet would have. The owner matters more than the tool.

How Does Either Tool Handle a Compliance Declaration?

A restricted-substance declaration, a recycled-content certificate or a laboratory report is a document carrying a date and a scope, and the question a programme eventually has to answer is whether it was current on the date a shipment was made. A pack can hold the document as an attachment and it cannot answer that question, because a pack has no history.

A spreadsheet can answer it where somebody built a column for it, and usually nobody did. Where declarations are filed by component reference the answer takes minutes; where they are filed by supplier or by the date received it takes an afternoon, and sometimes it cannot be found at all.

A system answers it in one query, and that is the single capability most likely to justify the cost. Where a programme sells into a market that asks for evidence — the European Union under REACH, the United States under CPSIA and Proposition 65, or a retailer asking for a transaction certificate against a recycled claim — the record is the answer rather than a search.

The preparation is the same in all three cases and it costs nothing: name the file after the component reference and the date rather than after the supplier. A folder named by reference is the beginning of a system, and a folder named by supplier is the beginning of a search.

What Is the Short Rule on Packs Against Systems?

Build the component list before buying anything. One row per reference with the full set of fields, used by every pack in the range, is the thing a system needs and the thing most programmes do not have.

Then move when the where-used question starts costing real time. That is the point at which the tool pays for itself, and it is measurable rather than a matter of taste.

Frequently Asked Questions

People Also Ask