Start with end use, then lock the correct standard
Remove DIN EN 14533 from the default conversation unless the customer gives the full citation, revision and application clause in writing. Buyers sometimes receive copied or outdated references that are wrong, obsolete or simply outside the scope of a loose throw. If the cited standard cannot be tied to the article category and installation context, hold lab booking until the approval owner confirms the applicable method in writing.
For 300gsm polyester throws, the real route is usually one of a few specific paths. ISO 12952 is used for bedding items and bedding assemblies under smouldering cigarette and small open-flame logic, so it can be relevant where the throw is supplied as bedding-adjacent use. BS 7175 is an end-use specification for mattresses, mattress toppers, divans and bed bases; buyers sometimes mention it loosely, but a throw alone is not automatically within that scope unless it forms part of a wider bedding scheme defined by the specifier. BS 5852 Source 0 is commonly used inside UK furniture and furnishing schemes for cover fabrics or composite seating-related constructions; it should not be presented as a general throw standard unless the project consultant explicitly places the throw within that furnishing approval route. For marine work, the route is normally an IMO FTP Code clause defined by the vessel programme, article classification and installation use case. For aviation, buyers may ask for FAR 25.853, but the exact clause, specimen orientation and article classification are programme-specific rather than generic blanket rules.
Be explicit about 16 CFR Part 1610. That US rule is for the flammability of clothing textiles. For home-textile throws, it is usually not the governing legal route. Some retailers still use it as an internal screening tool, especially where one textile test is required across mixed product categories, but it should be labelled clearly as buyer screening evidence, not as the blanket's main regulatory approval route.
Where the throw is sold into a furnishing package, ask whether the project sits under a UK furniture or contract-interior compliance scheme. That can change the acceptance logic completely. A decorative throw sold with a furnished apartment, student accommodation room or hotel fit-out may be reviewed by the buyer's consultant, insurer or fire engineer under project documents rather than by a simple retail home-textile checklist. The sourcing action rule is simple: do not rely on a copied standard title; get the end use, installation context and named test clause confirmed before sampling.
Separate regulation, contract spec and insurer preference
Sourcing confusion starts when every fire request is treated as law. In practice there are usually three layers, and they should be separated on the tech pack, quote sheet and PO notes.
Regulatory or statutory requirement means a law, code or mandatory rule tied to the product category and end-use context. Project or buyer specification means the brand, operator, architect, consultant or tender document requires a named method whether or not another route might also be lawful. Insurer or risk-engineering preference means the project may be technically sellable without it, but cover terms, handover or internal release can stall.
This distinction matters because the evidence strength changes with the request type. A hospital group asking for tested and laundered article specimens is usually managing repeatability, traceability and laundry durability, not just one-off ignition. A cruise technical team may require trim disclosure and programme-specific article classification. A US retailer asking for 16 CFR Part 1610 may only want a screen in the compliance file. Those are not interchangeable requests.
A workable buyer note uses one of three labels: Required for legal sale, Required for customer release, or Supporting evidence only. That wording prevents a fabric-only pass report from being misread as finished-article approval. It also stops suppliers from over-testing where the customer only needed a development screen.
Who decides, who approves, who signs release
Do not treat 'the customer' as one approval owner. In live programmes, control is often split across five parties and each controls a different step.
Method owner defines the test route and revision year. That may be the brand QA team, a fire consultant, an architect/specifier, airline engineering, shipowner technical team or a hospital procurement standard. Deviation owner accepts or rejects substitutions such as fabric-only data, alternate colourway grouping, or unwashed instead of post-laundered specimens. Lab booking owner instructs who commissions the test and where. Commercial release owner decides whether the PO can proceed. Final sign-off owner may be the client, consultant, insurer or authority having jurisdiction, depending on the project.
For sourcing teams, the action rule is practical: the supplier should not guess. Hold the lab booking until the approval owner confirms four points in writing: named standard and revision, article scope, specimen condition, and pass/fail basis. If one party names the method and another signs release, both should be copied on the confirmation. That single email often saves one failed submission cycle and 2 to 4 weeks of delay.
Decision matrix buyers can use before sampling
Use the matrix below as a buying tool. It is not legal advice; it is a pre-sampling control sheet. The approval owner still needs to confirm the exact route before the lab receives specimens.
| End use | Likely test path | Evidence normally expected | Approval owner | What to send the lab |
|---|---|---|---|---|
| Retail throw for home use | Usually buyer internal spec; 16 CFR Part 1610 only if the retailer uses it as a screening method | Article spec, fibre declaration, care label, any requested internal flammability screen | Retail QA or compliance team | 3-5 finished throws, final colourway, finished size, GSM tolerance, all trims declared, care instructions, packaging status if tested as sold |
| Hotel guest-room decorative throw | Project-specific route; may reference BS 5852 Source 0 only where the consultant places the item in a furnishing scheme | Finished-product report, BOM-linked approval, trim inclusion, laundering condition if requested | Brand QA, fire consultant or project specifier | 5-8 finished throws, article code and revision, finished dimensions, seam and edge details, branding trims, precondition or wash history, colour family declaration |
| Bedding-adjacent throw or bed runner | Often ISO 12952 logic or a brand bedding standard, depending on whether the throw is used on or with bedding | Report stating assembly scope, ignition source, laundering status and exact construction | Operator technical team or consultant | Minimum specimen set requested by the lab, plus BOM, care method, wash cycle count if applicable, fibre content, pile height and edge construction |
| Student accommodation or serviced apartment furnishing pack | Tender-defined route, commonly UK-led BS methods where specified | Finished throw test, production article code, care label, lot traceability plan | Procurement plus property or fire consultant | 5 finished throws, one retained control sample, final label set, supplier BOM revision, packaging declaration if the article is packed with ribbon or belly band |
| Healthcare or care environment | Usually article-level route with stronger focus on laundering validation, repeatability and traceability | Finished-product report, wash protocol, article traceability, change-control note | Technical buyer, laundry lead, compliance team | Finished specimens after defined laundering if required, wash protocol, detergent/temperature record, thread and trim declaration, lot ID plan |
| Cruise or marine cabin | Programme-specific IMO FTP Code route linked to the vessel file and article classification | Marine-scope report, exact specimen description, trim declaration, article approval file | Owner technical team, consultant, class-related reviewer if applicable | Finished article, programme clause, article use description, all labels and trims, BOM, colourway, preconditioning and any requested after-wash specimens |
| Aviation passenger throw | Programme-specific FAR 25.853 requirement if named by the customer | Aviation-scope report, exact material declaration, article description, packing format if relevant | Airline engineering or cabin-interior approval team | Finished article, clause reference, article drawing, materials list, seam and trim declaration, conditioning status and any customer template forms |
If the end use sits between categories, do not 'take the stricter interpretation' by instinct. Use a buyer action rule instead: hold submission until the method owner confirms article scope and specimen condition in writing. That is more reliable than guessing, and usually cheaper than a rejected report.
Why 300gsm polyester throw construction changes fire risk
A 300gsm polyester throw is not one construction. In sourcing terms, it is usually a finished weight around 290-310gsm, often in coral fleece, flannel fleece, microfleece or low-pile polar constructions. The risk profile shifts with the pile height, brushing level, edge build, sewing thread, trim chemistry and whether the article is tested as received or after laundering.
GSM and pile height. Heavier does not automatically mean safer. A denser 300gsm fleece may shrink back differently from a 230gsm article, and a higher brushed pile can give a faster local flame spread on the surface even if the fabric body is heavier. Typical pile height on these throws may sit around 2.5-5.0mm. Higher loft and looser brushed faces tend to increase surface fuzz and can change ignition behaviour. A shearing change of even 0.5-1.0mm can alter how the face catches and retreats.
Face finish and brushing. Double-brushed faces, raised nap and softener-heavy finishing can change the first-flame response. Commodity polyester fleece often melts and shrinks away rather than sustaining cellulosic-style flaming, but that does not make trims irrelevant. Brushing debris, loose fibres and very open pile surfaces can increase inconsistent edge behaviour between lab and bulk.
Edge finish. Overlock, lock-hem, whipped stitch and satin binding do not behave the same. Satin binding is often a higher-risk addition because it changes the exposed edge geometry and may introduce a different polymer, finish and basis weight. On a buyer file, the edge finish should be declared by stitch type, thread count and trim composition. If the sold article uses binding, test the bound article; a fabric-body-only report is not release evidence.
Sewing thread and trim. A common polyester sewing thread for throws may be around 150D/2 to 300D, but thread denier, filament type and lubricant finish vary. Woven labels, transfer films, embroidery backings, silicone badges, anti-slip prints and elastic loops can all create local ignition or molten-drip differences. A care label substrate alone can trigger consultant queries if it was omitted from the specimen declaration.
Print and decoration. Pigment print, transfer print, puff print, reflective film and patch adhesives can change flame response in the printed zone and at the interface with the fleece body. If the logo area exceeds a meaningful portion of the test specimen or sits near the edge, declare it. For branded programmes, treat decoration as a BOM-controlled variable, not as artwork-only detail.
Laundering. Home laundering under ISO 6330 or a buyer's wash protocol can change pile openness, remove finish, tighten shrink-back or expose stitch lines differently. A throw that behaves one way as received may behave differently after 5 or 10 washes. If the operator cares about repeat use, the laundering condition must be frozen before testing, not argued after a fail.
Define the evidence hierarchy before PO
Fire evidence is not one report. Buyers should define a hierarchy because development, customer approval and production release do not need the same evidence strength.
Level 1: development fabric report. Useful for feasibility on the base cloth only. Example description: 100% polyester fleece body, nominal 300gsm ±5%, pile height about 3-4mm, no trims, no labels, no print. This should be labelled non-release supporting evidence. It helps screen material direction, but it should not release a finished article with binding, labels, patches or decoration.
Level 2: finished-product test report. This is the minimum practical file for most contract-style programmes. The report should identify article code, revision, colourway or approved colour family, finished size, GSM tolerance, fibre content, pile structure, edge finish, sewing thread, declared trims, care condition, test date and the exact submitted specimen description.
Level 3: BOM-linked approval. This is where a pass result becomes commercially usable. The report should be tied to the approved BOM revision: base fabric supplier, yarn or fabric code, sewing thread, labels, binding, transfer film, embroidery backing, anti-slip print, hang loop and any packaging elements included in the tested sale unit. If the pass sample cannot be mapped to the released BOM, the report is weak evidence.
Level 4: production-lot verification. Higher-control channels may require retained sample comparison, incoming GSM and pile checks, periodic re-submission after colour or trim changes, or a fresh test after supplier transfer. This is common sense where the same SKU runs repeatedly over long programmes or across more than one mill.
Level 5: change-trigger retest. Retest is normally triggered by any meaningful BOM or process shift. Typical triggers are fibre-source change, recycled-content source change, colour chemistry change, GSM drift outside tolerance, brushing or shearing change, pile-height shift, softener or finish change, edge-finish change, new label substrate, new decoration film, new anti-slip print, different sewing thread, added lamination, change from unwashed to washed requirement, factory transfer, or a failed verification against the retained approval sample. Put these triggers on the PO, not only in internal email.
What a competent lab means in practice
Do not write 'tested by a competent lab' unless you define it. For buyer-side due diligence, the minimum practical standard is usually ISO/IEC 17025 accreditation for the relevant method or a clearly related scope, plus report traceability to a unique sample ID, stated standard revision, test date, specimen conditioning and declared deviations if any.
Check the scope, not only the logo. A lab may be accredited for tensile, colourfastness or pilling and still not hold the flammability method you need. The report should show the lab name, report number, issue date, page control, sample receipt date, sample description, conditioning details and enough construction information to tie the specimen back to the approved article.
If the report only says 'client sample as received' with almost no specimen detail, its release value is weak. A stronger report states the article identity clearly: for example nominal size, 100% polyester fleece throw, measured mass per unit area, pile surface description, edge finish, labels and trims present, and whether the sample was unwashed or washed. For useful submission support, keep one retained counter-sample sealed with the report copy and BOM revision.
Fabric-only versus finished-product: settle it once
Put one rule in the purchase file: fabric-only data is for development; finished-product data is for approval unless the buyer signs a written exception. That removes most arguments before bulk.
On a 300gsm polyester throw, the variables that change approval outcome are usually assembly details, not the fibre name alone. These include 3-thread or 4-thread overlock, fold hem with lockstitch, whipped stitch, satin binding, woven logo label, embroidered patch, heat-transfer branding, silicone badge, anti-slip print, hanging loop, ribbon set, belly band or retail sleeve attached at sale. Any of these can change edge ignition, shrink-back, molten drip or local afterflame behaviour.
Typical values worth freezing on the spec sheet are: finished GSM 290-310gsm; pile height 2-5mm depending on fleece type and shearing; sewing thread commonly polyester 150D/2-300D; overlock density roughly 3-5 stitches/cm; lock-hem around 2.5-4.0 stitches/cm; satin binding width often 25-38mm; dimensional change after home laundering often targeted within about ±3% to ±5% depending on construction and buyer standard. The exact acceptance values are buyer-specific, but if these inputs are not frozen, the fire report is difficult to defend as article-specific evidence.
If the programme also needs broader performance validation, align the fire file with adjacent controls such as pilling and laundry stability. For fleece throws, that often means keeping the same article revision across the flammability file and physical-quality file, for example the controls discussed in anti-pilling test requirements for polar fleece blankets, ISO 6330 domestic laundering protocols for coral fleece throws and the practical checkpoints in blanket quality control inspection.
What to send the lab before sample cutting
Most delays are not caused by the lab. They come from weak submission packs. A usable submission should let the lab and approval owner understand exactly what article was tested and under what condition.
Send these minimum items with the booking: 1) named standard and revision year; 2) end-use description and installation context; 3) article code and BOM revision; 4) finished dimensions and nominal GSM with tolerance; 5) fibre content and fleece type; 6) edge construction, stitch type and thread declaration; 7) all trims and decoration called out; 8) colourway or approved colour family; 9) care label and laundering condition if applicable; 10) packaging status if the article is tested as sold.
For specimen quantity, follow the lab's method-specific requirement, but in sourcing practice send more than the bare minimum. For a throw programme, 3-8 finished pieces is a sensible planning range depending on the method, number of orientations, after-wash needs and whether reserve specimens are needed. If the customer requires both unwashed and washed testing, send enough units for both conditions plus one retained factory control sample.
Include a simple declaration sheet with measured values from pre-submission QC: actual GSM, finished size, pile height estimate, edge type, label count and trim list. That sheet does not replace the test report, but it reduces the risk of the report being issued against a vague specimen description.
PO gate checklist buyers should not skip
Before placing the PO, freeze the approval file with a checklist. At minimum, the purchase record should show these fields as completed: 1) standard and revision year; 2) end use; 3) installation context; 4) pass/fail criterion or named clause; 5) specimen definition including finished article or fabric only; 6) preconditioning and laundering condition; 7) BOM revision tied to the tested sample; 8) retest triggers.
Add four more fields if the channel is higher-risk: 9) approval owner and sign-off chain; 10) lab name and accreditation status for the method; 11) colour grouping rule, for example whether dark and light shades can share one report; 12) shipment hold rule if the report is pending, failed or issued against the wrong specimen condition.
This checklist belongs on the PO release gate, not only in supplier development notes. If the order moves before these fields are fixed, the cost of re-testing, label replacement, trim correction or bulk hold can exceed the original sample saving very quickly.
Top reasons reports get rejected
Buyers rarely reject reports because the PDF looks informal. They reject them because the report cannot be tied cleanly to the sold article or the specified route.
The most common rejection reasons are: wrong standard or wrong revision year; fabric-only report submitted where a finished article was required; missing trim disclosure; unwashed specimens submitted where post-laundry testing was required; report not tied to article code and BOM revision; colourway or decoration not representative; lab scope unclear for the named method; and consultant or customer template fields missing.
A frequent sourcing failure is using an old pass report from a visually similar fleece. A 300gsm polyester throw with a different binding, print film or recycled-content source may still look interchangeable to merchandising, but it is a different test article for approval purposes. Treat prior reports as reference evidence only until the approval owner confirms equivalence in writing.
For commercial risk control, label the evidence properly in your internal file: supporting fabric evidence, article approval report, or non-conforming/out-of-scope report. That simple filing discipline cuts down accidental misuse during PO release.
Retest triggers that should be written into the programme
The cleanest retest rule is not 'retest if material changes'. That is too vague to enforce. Write the triggers as sourceable conditions.
Recommended triggers for a 300gsm polyester throw programme are: measured GSM outside approved tolerance; fleece face changed from single-brushed to double-brushed or vice versa; pile height change beyond about ±0.5mm; change in edge finish from overlock to binding or hem; sewing thread denier or composition change; new label substrate or added patch; new print or transfer technology; new finish such as extra softener or water-repellent treatment; factory or key subcontractor change; mandatory wash condition added or revised; or any failed comparison to the sealed approval sample.
Where the article is part of a broader sourcing programme, keep change control aligned with adjacent article files. If you are comparing alternative constructions, related references such as FR-treated polyester fleece blankets to BS 7175, Trevira CS fleece blankets for cruise cabins and the cost-control logic in custom blanket lead times and shipping help buyers judge whether to test commodity polyester, move to inherently FR fibre, or split the range by channel instead of forcing one construction across all end uses.
Buyer action rule before PO
If the customer asks only for 'burn data', do not commission a test on assumption. Hold the booking until the method owner confirms the standard and revision, end use, article scope, specimen condition and approval sign-off chain in writing. That is the practical sourcing rule.
For a standard 300gsm polyester throw, use development fabric reports only to screen feasibility. Use finished-product reports for approval. Tie every accepted report to the article code, BOM revision, test date and exact specimen description. If any of those links are missing, treat the report as supporting evidence rather than release evidence.
If you need the shortest route for low-risk retail, the simplest file is often a tightly described finished article with frozen trims and clear care condition. If you need marine, aviation, healthcare or furnishing-scheme approvals, assume the customer-specific route will override generic home-textile logic and budget the sampling time accordingly.
Frequently asked
Is BS 5852 Source 0 a normal standard for loose polyester throws? Not by default. BS 5852 Source 0 is commonly used within UK furniture and furnishing approval schemes, especially for cover fabrics or composite seating-related constructions. A loose throw should only be tested to that route if the buyer's consultant, specifier or project document places the article within that approval scheme. Do not present it as a universal throw standard.
Can I use 16 CFR Part 1610 for a home-textile throw sold in the US? Usually only as a buyer screening method if the retailer asks for it. 16 CFR Part 1610 is a clothing-textile flammability regulation, not the normal governing route for home-textile throws. If a buyer requests it, label it as internal or customer screening evidence rather than as the main legal route for the throw.
What is the minimum acceptable fire-test evidence before PO? For most contract-style or project-led programmes, the minimum practical file is a finished-product report tied to the exact article code and BOM revision. The report should state the named standard and revision, specimen description, test date, trims present, care or laundering condition, and the article's end-use context. Fabric-only data should be marked non-release supporting evidence unless the buyer signs a written exception.
How many specimens should we send the lab? Follow the method-specific lab requirement, but in sourcing practice send more than the bare minimum. For throw programmes, 3 to 8 finished pieces is a sensible planning range depending on whether the lab needs reserve specimens, multiple orientations, trim areas, or both unwashed and washed samples. Always send one retained control sample for your own file.
Does the colourway matter for fire testing? It can. Dark and light shades, print coverage, transfer films and certain finishes may change behaviour enough that a consultant or buyer asks for representative colour grouping or separate submissions. Do not assume one report covers all colours. Get the grouping rule confirmed in writing and keep it in the approval file.
What changes normally trigger a retest? Typical triggers are GSM outside tolerance, pile-height or brushing change, edge-finish change, sewing-thread change, new trim or label substrate, new print or transfer technology, finish change, factory transfer, or a new laundering requirement. If the tested article no longer matches the released BOM and specimen condition, the report should not be relied on without approval or retest.
Have a project in mind? Send us your spec — we'll reply within one business day with indicative pricing and a sample plan.