Spec discipline converts assumptions into documented terms before negotiation starts.<\/p>\n\n\n\n
Procurement managers and operations leaders sourcing kraft paper, packaging materials, or finished paper products will gain a copy-ready template and gate-based workflow here, preparing them for the detailed RFQ tables and evaluation process that follow.<\/p>\n\n\n\n
Five quotes sit open in a spreadsheet. One lists GSM without a tolerance. Another says “equivalent grade acceptable.” A third quotes CIF but doesn’t name the destination port. The fourth references “standard quality” with no test method. The fifth looks promising until you notice the Incoterms edition isn’t specified.<\/p>\n\n\n\n
Which one is actually cheapest?<\/em><\/p>\n\n\n\n The honest answer: you can’t tell. Not because the suppliers are hiding anything, but because the RFQ invited assumptions. And assumptions, once baked into a quote, become disputes after the award.<\/p>\n\n\n\n This is the core problem with separating “technical” from “commercial” requirements. When specs travel in one document and pricing terms in another\u2014or worse, when either is left vague\u2014every supplier fills the gaps differently. The result isn’t a price comparison. It’s a comparison of interpretations.<\/p>\n\n\n\n A spec-driven RFQ solves this by treating technical requirements, evidence expectations, and commercial terms as a single integrated specification. Every field that changes what you’re comparing belongs in the same document, with the same precision.<\/p>\n\n\n\n What follows is a copy-ready template that forces like-for-like responses, plus a short evaluation workflow that prevents the clarification loops and post-award renegotiations that consume procurement cycles. Whether you’re sourcing kraft paper<\/a>, packaging paper<\/a>, or paper bags<\/a>, the structure applies. Adapt the specific fields to your product; keep the discipline intact.<\/p>\n\n\n\n Quote variance rarely reflects market dynamics. More often, it reflects three categories of ambiguity that the RFQ failed to close.<\/p>\n\n\n\n Spec ambiguity<\/strong> occurs when a property is named without units, tolerances, ISO or test methods. “80 GSM kraft paper” sounds precise until you realise one supplier measured grammage per ISO 536<\/a> on conditioned samples, another used an in-house method on unconditioned stock, and a third rounded from 78 g\/m\u00b2. The numbers match; the paper doesn’t.<\/p>\n\n\n\n Method mismatch<\/strong> compounds the problem. Burst strength reported in kPa per ISO 2758<\/a> cannot be compared directly to a figure derived from TAPPI T 403<\/a> without understanding the test geometry and sample conditioning. Quoting a number without naming the method is quoting noise.<\/p>\n\n\n\n Delivery basis mismatch<\/strong> is the commercial equivalent. FOB Shanghai and CIF Rotterdam may both be valid Incoterms\u00ae rules, but they allocate freight, insurance, and risk differently. A quote that omits the named place\u2014or references an outdated Incoterms edition\u2014cannot be normalised to your door without assumptions. Those assumptions become invoice disputes.<\/p>\n\n\n\n A spec-driven RFQ closes all three gaps through four design principles:<\/p>\n\n\n\n Standardizing these fields ensures data parity, preventing subjective interpretation during the bid-leveling phase.<\/p>\n\n\n\n The technical section of an RFQ performs two jobs. First, it tells the supplier exactly what you need. Second, it tells your QA team exactly what to verify on arrival. If the RFQ can’t do both, it’s incomplete.<\/p>\n\n\n\n The specific properties depend on your product category, but the structure remains constant. For kraft paper and packaging paper applications, the minimum typically includes:<\/p>\n\n\n\n For finished goods like paper bags, add construction parameters: ply count, handle attachment method, print specifications, and any food-contact or certification requirements.<\/p>\n\n\n\n A number without a method is a number without meaning. When specifying burst strength, don’t write “minimum 250 kPa.” Write “minimum 250 kPa per ISO 2758:2014<\/a>, tested on conditioned samples per ISO 187<\/a>.”<\/p>\n\n\n\n This serves three purposes. It eliminates method-driven variance between quotes. It gives suppliers a clear compliance target. And it gives your incoming inspection team an unambiguous acceptance criterion.<\/p>\n\n\n\n For properties where multiple standards exist, pick one and state it. If you accept equivalents, define what “equivalent” means: same test geometry, same conditioning protocol, same units. Vague equivalence clauses invite the very ambiguity you’re trying to eliminate.<\/p>\n\n\n\n Common method references for paper specifications include:<\/p>\n\n\n\n For a deeper explanation of which test methods to require and why, see TAPPI\/ISO in Plain English<\/a>.<\/p>\n\n\n\n Specifications without evidence are promises. Evidence turns promises into verifiable claims.<\/p>\n\n\n\n At minimum, require suppliers to attach:<\/p>\n\n\n\n This isn’t about distrust. It’s about creating a quote-time evidence pack\u2014sometimes called a “material passport”\u2014that accelerates internal approvals and reduces post-award verification cycles. For guidance on structuring evidence requirements, see Build a ‘Passport’ for Your Material<\/a>.<\/p>\n\n\n\n A technical spec tells you what you’re buying. Commercial terms tell you what you’re paying\u2014and where risk transfers. Separating them creates the illusion that price is independent of delivery basis. It isn’t.<\/p>\n\n\n\n Every international quote should specify three elements: the Incoterms\u00ae rule (FOB, CIF, CPT, DAP, etc.), the named place (the specific location where risk or cost transfers), and the edition (Incoterms\u00ae 2020<\/a>).<\/p>\n\n\n\n “FOB” alone is incomplete. The use of FCA (Free Carrier) is generally preferred for containerized paper shipments to avoid the ‘On Board’ liability gap inherent in FOB. However, if using FOB Shanghai Port, Incoterms\u00ae 2020, ensure the named port is accurate, though risk will technically strictly transfer only when the goods are on board the vessel, not at the terminal gate. The named place determines where your responsibility begins; omitting it invites disputes over local charges, THC allocation, and insurance coverage.<\/p>\n\n\n\n If your RFQ doesn’t mandate a specific Incoterms rule, require suppliers to state their preferred basis clearly\u2014then normalise all responses to a common comparison point. For a detailed breakdown of how Incoterms selection changes your delivered cost, see Incoterms for Paper Supply<\/a>.<\/p>\n\n\n\n Beyond Incoterms, define the logistics lane explicitly:<\/p>\n\n\n\n Ambiguity here is expensive. A quote that appears 5% cheaper can flip to 8% more expensive once destination charges surface. Define responsibilities upfront; compare on a to-door basis.<\/p>\n\n\n\n Require suppliers to state:<\/p>\n\n\n\n This doesn’t mean locking in every detail at the RFQ stage. It means ensuring that every quote is built on the same structural assumptions, so variances reflect genuine cost differences rather than hidden terms.<\/p>\n\n\n\n For more on normalising quotes across different delivery bases, see Kraft Paper RFQ Fields That Change the Quote<\/a>.<\/p>\n\n\n\n A structured RFQ produces structured responses. But responses still need evaluation\u2014and evaluation without a framework becomes debate. QA wants to discuss method equivalence. Finance wants to discuss payment terms. Logistics wants to discuss transit times. Procurement wants to close the deal.<\/p>\n\n\n\n An evaluation layer converts stakeholder concerns into sequential gates, so each question gets answered in the right order.<\/p>\n\n\n\n Before comparing prices, convert all quotes to the same delivery basis. If you received a mix of FOB, CIF, and DAP quotes, normalise them to your door (or to a consistent intermediate point like destination port).<\/p>\n\n\n\n This requires:<\/p>\n\n\n\n The goal isn’t perfect accuracy\u2014freight rates move. The goal is consistent methodology so that the ranking reflects genuine cost differences rather than delivery-basis artefacts. For a practical method, see when freight flips the winner<\/a>.<\/p>\n\n\n\n If logistics cost is a material component of landed cost\u2014and for paper products, it typically is\u2014don’t rely on a single freight estimate. Model scenarios:<\/p>\n\n\n\n Check whether the supplier ranking changes under each scenario. If a “cheaper” origin supplier becomes more expensive under stress conditions, that’s a risk factor\u2014not a reason to reject, but a reason to document and discuss.<\/p>\n\n\n\n Not every quote deserves a price comparison. Create sequential gates:<\/p>\n\n\n\n Quotes that fail any gate exit the comparison before price ranking begins. This prevents the common trap of awarding to the lowest bidder only to discover, post-award, that critical documentation is missing or specs are misaligned.<\/p>\n\n\n\n Below is a modular template structured into seven sections. Copy and adapt the fields to your specific product category; maintain the structure to preserve comparability.<\/p>\n\n\n\n Use this table for the properties that materially affect converting performance or claims risk. The ISO\/TAPPI method examples below are common references; buyers should select the methods that match internal QA practice and the application.<\/p>\n\n\n\n Suppliers should attach evidence at quote time, not after award. Treat the evidence pack as part of the bid, not an afterthought. If evidence is unavailable, suppliers should state a dated plan to provide it prior to production.<\/p>\n\n\n\n This section is where many RFQs fail. Treat it as mandatory, not optional.<\/p>\n\n\n\n To compare bids, every quote must be convertible into the same delivered basis.<\/p>\n\n\n\n This is the buyer’s response format template. Quotes that do not follow this format should be treated as non-comparable until corrected.<\/p>\n\n\n\n
\n\n\n\nWhy Most RFQs Fail: Separating “Spec” from “Commercial” Lets Assumptions Leak into the Quote<\/h2>\n\n\n\n
![\"\u201cRFQ](\"https:\/\/www.paperindex.com\/academy\/wp-content\/uploads\/2026\/01\/rfq-failures-due-to-unclosed-gaps.png\")
<\/figure>\n\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ol>\n\n\n\n
\n\n\n\nPrinciple 1: Technical Requirements Must Be Measurable, Test-Method-Named, and Auditable<\/h2>\n\n\n\n
Define the Minimum Technical Field Set<\/strong><\/h3>\n\n\n\n
\n
Mandate Test Method Naming<\/strong><\/h3>\n\n\n\n
\n
Require Evidence at Quote Time<\/strong><\/h3>\n\n\n\n
\n
\n\n\n\nPrinciple 2: Commercial Terms as Technical Constants<\/h2>\n\n\n\n
![\"\u201cEnsuring](\"https:\/\/www.paperindex.com\/academy\/wp-content\/uploads\/2026\/01\/ensuring-comparable-quotes-in-rfqs.png\")
<\/figure>\n\n\n\nIncoterms\u00ae Rule + Named Place + Edition<\/strong><\/h3>\n\n\n\n
Lane Definition and Charge Allocation<\/strong><\/h3>\n\n\n\n
\n
Price Structure, Validity, and Change Triggers<\/strong><\/h3>\n\n\n\n
\n
\n\n\n\nPrinciple 3: Add an Evaluation Layer So Responses Can Be Scored, Not Debated<\/h2>\n\n\n\n
Normalise to a Single Comparison Basis<\/strong><\/h3>\n\n\n\n
\n
Stress-Test Freight Scenarios<\/strong><\/h3>\n\n\n\n
\n
Create Pass\/Fail Gates Before Price Ranking<\/strong><\/h3>\n\n\n\n
\n
\n\n\n\nThe Spec-Driven RFQ Template<\/h2>\n\n\n\n
A. RFQ Header and Scope<\/strong><\/h3>\n\n\n\n
Section<\/strong><\/td> Field<\/strong><\/td> Buyer Input (Fill In)<\/strong><\/td> Supplier Must Provide<\/strong><\/td> Why It Matters<\/strong><\/td><\/tr> RFQ ID & dates<\/td> RFQ reference, issue date, bid deadline<\/td> RFQ-___ \/ ___ \/ ___<\/td> Confirmation of bid validity period (days)<\/td> Prevents last-minute repricing and expired offers<\/td><\/tr> Product identity<\/td> Kraft paper grade \/ type (e.g., unbleached\/bleached; virgin\/recycled; sack\/corrugating use-case)<\/td> ___<\/td> Exact grade name, furnish description (high-level), and data sheet<\/td> Ensures the quote maps to the intended application<\/td><\/tr> Intended use-case<\/td> End use (paper bags, corrugating, wrapping, etc.)<\/td> ___<\/td> Confirmation of suitability + known limitations<\/td> Aligns tests and risk controls to real performance<\/td><\/tr> Annual demand & forecast<\/td> Annual volume + call-off pattern<\/td> ___<\/td> Capacity confirmation + allocation approach<\/td> Reduces supply risk and lead-time surprises<\/td><\/tr> Trial vs production<\/td> Trial lot \/ first order \/ ongoing contract<\/td> ___<\/td> Trial support, sample policy, and ramp plan<\/td> Sets expectations for qualification and scaling<\/td><\/tr> Required documents<\/td> List required compliance \/ regulatory documents (if applicable)<\/td> ___<\/td> Confirmation + copies \/ certificates (or timeline)<\/td> Avoids post-award compliance delays<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n B. Technical Specification Table (Test-Method-Named Requirements)<\/strong><\/h3>\n\n\n\n
Parameter<\/strong><\/td> Target<\/strong><\/td> Unit<\/strong><\/td> Tolerance \/ Acceptance Window<\/strong><\/td> Test Method (Specify ISO\/TAPPI Code + Version)<\/strong><\/td> Supplier Evidence at Quote Time (Attach)<\/strong><\/td> Notes (Buyer Guidance)<\/strong><\/td><\/tr> Basis weight (grammage)<\/td> ___<\/td> g\/m\u00b2 (GSM)<\/td> \u00b1 ___<\/td> ISO 536<\/a> (or equivalent)<\/td> COA\/test report with method code + sample conditioning<\/td> Anchor for cost, runnability, and weight claims<\/td><\/tr> Moisture content<\/td> ___<\/td> %<\/td> ___ to ___ at receipt<\/td> ISO 287<\/a> (or equivalent)<\/td> COA showing conditioning and test conditions<\/td> Moisture affects curl, dimensional stability, and GSM accuracy<\/td><\/tr> Cobb (water absorptiveness)<\/td> ___<\/td> g\/m\u00b2<\/td> Max ___ (state time)<\/td> ISO 535<\/a> (state Cobb\u2086\u2080\/Cobb\u2081\u2082\u2080)<\/td> COA with test duration explicitly stated<\/td> Controls sizing; affects printing\/adhesive performance<\/td><\/tr> Burst strength<\/td> ___<\/td> kPa (or psi)<\/td> Min ___<\/td> ISO 2758<\/a> (or equivalent)<\/td> COA showing units + method code<\/td> Common legacy spec; validate relevance to end use<\/td><\/tr> Tensile strength (MD\/CD)<\/td> ___ \/ ___<\/td> kN\/m<\/td> Min ___<\/td> ISO 1924-2<\/a> or TAPPI T 494<\/a> (state MD\/CD)<\/td> COA including MD\/CD values<\/td> Directional properties matter; request MD and CD<\/td><\/tr> Tear resistance (MD\/CD)<\/td> ___ \/ ___<\/td> mN<\/td> Min ___<\/td> ISO 1974<\/a> (or equivalent)<\/td> COA including MD\/CD<\/td> Predicts tear propagation in converting and handling<\/td><\/tr> Caliper \/ thickness<\/td> ___<\/td> \u00b5m<\/td> \u00b1 ___<\/td> ISO 534<\/a> (or equivalent) Note: Caliper variability impacts roll diameter and stacking strength<\/td> COA<\/td> Helps match machine settings and packing density<\/td><\/tr> Formation \/ visual defects<\/td> N\/A<\/td> N\/A<\/td> Buyer-defined acceptance criteria<\/td> Buyer-defined inspection method<\/td> Photos or sample roll (if requested)<\/td> Use when surface appearance drives print quality<\/td><\/tr> Roll width<\/td> ___<\/td> mm<\/td> \u00b1 ___<\/td> Measurement method (define)<\/td> Stated capability + slitting tolerance<\/td> Out-of-tolerance width creates waste and downtime<\/td><\/tr> Roll OD \/ ID (core)<\/td> ___ \/ ___<\/td> mm<\/td> \u00b1 ___<\/td> Measurement method (define)<\/td> Confirmation + core spec sheet<\/td> Prevents incompatibility with unwind stands<\/td><\/tr> Reel build \/ winding hardness<\/td> ___<\/td> (define)<\/td> Buyer-defined<\/td> Buyer-defined<\/td> Stated winding profile \/ hardness<\/td> Controls telescoping and runnability<\/td><\/tr> Splices per roll<\/td> ___<\/td> count<\/td> Max ___<\/td> Buyer-defined<\/td> Supplier commitment<\/td> Impacts downtime and waste<\/td><\/tr> Packaging & moisture barrier<\/td> ___<\/td> N\/A<\/td> Must comply<\/td> Buyer-defined<\/td> Packaging description + photos<\/td> Prevents damage in transit and storage<\/td><\/tr> Palletization<\/td> ___<\/td> N\/A<\/td> Must comply<\/td> Buyer-defined<\/td> Pallet spec (size, wrap, labeling)<\/td> Avoids handling damage and warehouse inefficiency<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n C. Evidence Pack (“Material Passport”) Requirements<\/strong><\/h3>\n\n\n\n
Evidence Item<\/strong><\/td> Supplier Must Attach (Yes\/No + File)<\/strong><\/td> Minimum Content<\/strong><\/td> Why It Matters<\/strong><\/td><\/tr> Certificate of Analysis (COA)<\/td> Yes<\/td> Lot-level results, method codes, units, conditioning\/test conditions, lab identification, traceability to lot IDs<\/td> Enables objective quote comparison and faster incoming QA<\/td><\/tr> Product data sheet \/ technical spec<\/td> Yes<\/td> Grade description, typical ranges, storage\/handling guidance<\/td> Prevents misunderstanding of grade capability<\/td><\/tr> Quality system statement<\/td> Yes<\/td> QA controls, calibration approach, internal testing frequency<\/td> Signals consistency risk (process control discipline)<\/td><\/tr> Traceability statement<\/td> Yes<\/td> How reel IDs map to production date\/shift and test results<\/td> Supports root-cause analysis if defects occur<\/td><\/tr> Sustainability \/ compliance docs (if required)<\/td> As applicable<\/td> Certificates and scope statements<\/td> Avoids shipment holds or customer non-compliance<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n D. Commercial Terms (Comparable Bids, Comparable Risk)<\/strong><\/h3>\n\n\n\n
Commercial Field<\/strong><\/td> Buyer Requirement (Fill In)<\/strong><\/td> Supplier Must Quote \/ Confirm<\/strong><\/td> Why It Matters<\/strong><\/td><\/tr> MOQ \/ order bands<\/td> ___<\/td> MOQ, price breaks by band, and any fixed fees<\/td> Avoids post-award “MOQ surprises” and enables banded awards<\/td><\/tr> Lead time<\/td> ___<\/td> Standard lead time + max variance + expediting options<\/td> Lead-time variability can be more costly than unit price<\/td><\/tr> Validity period<\/td> ___ days<\/td> Validity (days) + triggers for repricing<\/td> Prevents frequent renegotiation<\/td><\/tr> Payment terms<\/td> ___<\/td> Payment terms offered + currency<\/td> Impacts cash flow and total cost<\/td><\/tr> Price basis & currency<\/td> ___<\/td> Currency + FX assumptions (if any)<\/td> Enables apples-to-apples landed cost modeling<\/td><\/tr> Price adjustment mechanism<\/td> Buyer preference (fixed \/ indexed \/ agreed triggers)<\/td> Supplier proposal (clearly defined)<\/td> Avoids ambiguous mid-contract increases<\/td><\/tr> Packaging\/pallet charges<\/td> Included \/ itemized<\/td> Explicit line items for pallets, wrapping, labels<\/td> “Hidden” charge that alters total price<\/td><\/tr> Claims and dispute window<\/td> ___ days<\/td> Claims window, evidence required, and resolution timeline<\/td> Reduces friction when defects appear<\/td><\/tr> Replacement \/ credit logic<\/td> ___<\/td> Replacement lead time and credit terms<\/td> Converts quality failures into predictable outcomes<\/td><\/tr> Change control<\/td> Required<\/td> Commitment to notify and approve any changes in furnish, process, or method<\/td> Protects against silent spec drift<\/td><\/tr> Confidentiality<\/td> Required \/ optional<\/td> Acceptance of NDA (if applicable)<\/td> Protects designs, volumes, and commercial terms<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n E. Logistics and Incoterms (Normalize to One Basis)<\/strong><\/h3>\n\n\n\n
Logistics Field<\/strong><\/td> Buyer Requirement (Fill In)<\/strong><\/td> Supplier Must State (Required)<\/strong><\/td> Why It Matters<\/strong><\/td><\/tr> Incoterms rule + named place<\/td> “___ (named place) Incoterms\u00ae 2020”<\/td> Confirmation of rule + named place exactly as stated<\/td> Small wording changes shift costs and risk<\/td><\/tr> Delivery point definition<\/td> Door \/ dock \/ port \/ terminal<\/td> Exact delivery point + unloading responsibility<\/td> Prevents “delivered” disputes<\/td><\/tr> Freight lane assumptions<\/td> If buyer-arranged: origin pickup terms; if supplier-arranged: route basis<\/td> Lane details, carrier type, and surcharges included\/excluded<\/td> Supports landed cost normalization<\/td><\/tr> Insurance<\/td> Required level (if applicable)<\/td> Coverage type and who buys it<\/td> Insurance obligations vary by Incoterms<\/td><\/tr> Local charges<\/td> Must be itemized<\/td> THC, documentation, handling, customs, etc.<\/td> Local charges can exceed freight in some lanes<\/td><\/tr> Packaging for transit<\/td> Required<\/td> Moisture barrier, edge protection, roll covers<\/td> Prevents transit damage and claims friction<\/td><\/tr> Delivery schedule<\/td> Call-off cadence<\/td> Shipping frequency and consolidation options<\/td> Impacts working capital and warehouse space<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n F. Standardized Supplier Bid Sheet (Required)<\/strong><\/h3>\n\n\n\n
Line Item<\/strong><\/td> Supplier Must Provide<\/strong><\/td> Unit<\/strong><\/td> Price<\/strong><\/td> Included \/ Excluded Notes<\/strong><\/td> Evidence Reference<\/strong><\/td><\/tr> Base paper price<\/td> ___<\/td> ___<\/td> ___<\/td> Basis weight, grade, and roll format assumptions<\/td> COA \/ data sheet<\/td><\/tr> Packaging \/ pallets<\/td> ___<\/td> ___<\/td> ___<\/td> Included or itemized<\/td> Photo\/spec<\/td><\/tr> Freight (if supplier-arranged)<\/td> ___<\/td> ___<\/td> ___<\/td> Lane, carrier type, surcharges<\/td> Quote \/ assumption note<\/td><\/tr> Insurance (if supplier-arranged)<\/td> ___<\/td> ___<\/td> ___<\/td> Coverage level<\/td> Policy note<\/td><\/tr> Local charges<\/td> ___<\/td> ___<\/td> ___<\/td> Itemized list<\/td> Quote \/ assumption note<\/td><\/tr> Total delivered basis<\/td> ___<\/td> ___<\/td> ___<\/td> Delivered basis definition<\/td> Summary<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n G. Copy-Ready Clause Blocks (Paste into the RFQ)<\/strong><\/h3>\n\n\n\n