How to raise a change request<\/h2>\n
A change request is not a problem, as long as it arrives before the point where changing it costs more than the change is worth. Every change should be written, numbered and acknowledged, so the factory is working from a document rather than an instruction. Say what changes, why, and by when, and ask for the effect on price and lead time in the same message. A change that moves the print position is cheap before the screen is made and expensive after. A change that moves the fabric weight can change the whole bag, so it should trigger a new sample rather than a note. The discipline is simple: no change without a revised spec, and no revised spec without both sides confirming it.<\/p>\n
![\"bag](\"https:\/\/tiiocti.com\/wp-content\/uploads\/2026\/04\/preproduction-sample-bags-material-verification-and-reach-co-highlight-scaled.jpg\")
<\/p>\n
The paper trail that saves an order<\/h2>\n
The strongest protection is a signed sample. Before bulk production, both sides sign and keep the same physical sample, sometimes called the golden sample, and every later question is answered against it. The approval should record the date, the spec revision it represents, and any note about what is still open. Test reports belong in the same file, so a claim about restricted substances, colour fastness or seam strength can be checked against the report rather than the memory of a meeting. Where a buyer works to a recognised material standard, such as the restricted-substance limits published by OEKO-TEX<\/a>, the report reference should sit in the spec so it travels with the order.<\/p>\n The same four mistakes appear again and again. A verbal change is made on a call and never written down, so the factory builds to the old spec. A sample is approved but not kept, so nobody can prove what was agreed. A spec is updated in one place but not in another, so two versions circulate. And an assumption is made on a field that was left blank, usually the cord or the packing. Each one is prevented by the same habit: write it, number it, sign it, keep it.<\/p>\n A written spec gives every variable a value both sides can read back, so a later question is answered by the document rather than by memory. Chat threads do not pin down fabric, cord, print or packing.<\/p>\n Finished dimensions with tolerance, fabric and GSM with the test method, cord or handle details, print artwork and position, thread colour, packing and carton details, and a revision number on every page.<\/p>\n A change is cheap before tooling and expensive after. Moving a print position is low cost before the screen is made, while changing the fabric weight can require a new sample and moves both price and lead time.<\/p>\n It is the approved physical sample that both sides sign and keep. Later questions are answered against it, and it proves what was agreed far better than a photo or a message.<\/p>\n Number and date every revision, replace the previous version rather than editing in place, and confirm receipt in writing. A superseded spec should never be left in circulation.<\/p>\n Write the spec, number the revisions, sign and keep the sample, and raise every change in writing with its cost and lead-time effect. That discipline protects the buyer and the factory, and it is far cheaper than arguing about a bag that was built to the wrong version. If you want bag orders run from a written spec with controlled changes and a signed sample, talk to our bag manufacturing team<\/a>.<\/p>\n Related reading: our post-consumer fiber blend guide<\/a> and our drawstring bags range<\/a>.<\/p>\nWhere these orders usually go wrong<\/h2>\n
![\"incoming](\"https:\/\/tiiocti.com\/wp-content\/uploads\/2025\/08\/Gloved-hands-using-magnifier-to-inspect-red-non-woven-bag-samples.jpg\")
<\/p>\nFAQs about bag order spec change requests<\/h2>\n
Why put a bag spec in writing instead of agreeing by message?<\/h3>\n
What should a bag spec sheet include?<\/h3>\n
When is it too late to change a bag order?<\/h3>\n
What is a golden sample?<\/h3>\n
How do I keep control of spec revisions?<\/h3>\n
Communicate the order like a document<\/h2>\n