Custom Sock RFQ Template for Comparable Wholesale Quotes

Custom Sock RFQ Template for Comparable Wholesale Quotes

A comparable custom sock quote starts with a controlled request for quotation (RFQ). Ask every shortlisted supplier to price the same specification, quantity basis, packaging, sample stages, approval requirements, and delivery basis before comparing unit prices.

This template focuses on three buyer controls:

• Defining the scope each supplier must quote.
• Assigning supplier communication and buyer approval ownership.
• Establishing written escalation paths for cost, specification, quality, and schedule issues.

Include product details only when they affect price, minimum quantity, sampling, approval evidence, packaging, or delivery.

1. Establish One Quotation Baseline

Issue the same controlled RFQ package to every bidder. The cover sheet should state:

• RFQ number and revision.
• Issue date, clarification deadline, and quotation deadline.
• Buyer entity and RFQ owner.
• Attachment list with file names and revision identifiers.
• Quote currency and requested quantity breaks.
• Delivery destination and requested delivery term.
• Required quote-validity period.
• Supplier acknowledgment field.

Require suppliers to repeat the RFQ number and revision on their pricing sheet, specification response, exception register, and preliminary schedule. If a material requirement changes, issue a numbered revision or written clarification to every participating bidder.

A DeadSoxy bulk-buying guide discusses minimum orders, material choices, decoration methods, and shipping timing as sourcing considerations (DeadSoxy). Use these topics to frame RFQ questions, not as evidence of any bidder’s capabilities or commercial terms.

Baseline scope fields

| Scope area | Buyer must state | Supplier must confirm | |---|---|---| | SKU structure | Style, colorway, size range, and quantity by SKU | Quoted quantity, minimum quantity, order increment, and required size or color ratios | | Sock specification | Sock type, target dimensions or size standard, construction, composition, cushioning, cuff, heel, toe, and other priced features | Exact construction and composition quoted, including proposed substitutions | | Branding | Method, location, artwork reference, dimensions, color references, and required appearance | Quoted method, setup requirements, reproduction limitations, and included artwork revisions | | Color control | Buyer’s color reference and required approval evidence | Matching method, evidence or sample provided, limitations, and additional charges | | Packaging | Unit-pack format, labels or bands, bags, inserts, barcode data, carton configuration, and buyer-supplied components | Included materials, pack quantities, carton assumptions, development charges, and exclusions | | Samples | Required stage, quantity, destination, and approval owner | Sample type, cost, courier basis, preparation time, included revisions, and schedule effect | | Quality and release | Buyer-defined acceptance criteria, inspection stage, required evidence, and release conditions | Included inspection or evidence, exceptions, and proposed handling of a failed requirement | | Delivery | Requested delivery term, named place or port, destination, and required dispatch or arrival date | Quoted delivery basis, production period, transit assumption, dependencies, and exclusions |

Do not use undefined descriptions such as “standard,” “premium,” “retail packaging,” or “production sample” as specifications. Replace each one with the construction, material, dimensions, contents, evidence, or sample stage included in the price.

Classify each requirement

Mark every RFQ requirement as one of the following:

• **Mandatory:** Required in the compliant baseline quote.
• **Target:** Preferred, but the supplier may document an alternative.
• **Supplier option:** Optional and priced separately.
• **Open decision:** Requires a named buyer decision before order or production release.

When a supplier proposes a different material, construction, branding method, packaging format, quantity, sample plan, or delivery basis, require:

1. A response against the stated baseline, or a clear statement that the baseline cannot be quoted. 2. A separately priced alternative showing its scope, minimum quantity, approval requirements, exceptions, and schedule effects.

Keep the alternative outside the compliant-baseline comparison unless the authorized buyer approver accepts the scope change.

2. Define the Quoted Program Responsibilities

Labels such as OEM, ODM, private label, and white label are not sufficient for quote comparison because suppliers may assign different responsibilities and deliverables to them. Goren Socks presents these as distinct B2B sourcing models (Goren Socks). Treat the label as descriptive and compare the work expressly included in each quotation.

Require the supplier to identify:

• The program-model label used in the quote.
• Specifications, artwork, packaging information, and other buyer inputs required.
• Design, technical, artwork-preparation, testing, or packaging work included in the price.
• Supplier-standard constructions, components, packaging formats, or processes assumed.
• Development, setup, tooling, and sampling charges.
• Ownership or permitted use of buyer-provided artwork and supplier-created files when relevant to the proposed terms.
• Price, minimum-quantity, sample, approval, and schedule effects of changing the quoted model.

Do not place two quotations in the same comparison row solely because they use the same program-model label. Compare their listed responsibilities, deliverables, assumptions, and exclusions.

3. Require a Standard Supplier Return Package

Send the same response format to every bidder. Require each completed package to contain:

1. Signed RFQ acknowledgment. 2. Itemized pricing sheet. 3. Line-by-line specification response. 4. Exception and assumption register. 5. Preliminary schedule showing buyer and supplier dependencies. 6. Sample and approval plan. 7. Contact and escalation matrix. 8. Commercial terms, quote validity, and change-control terms.

Define blank fields as unresolved. Do not interpret a blank as included, compliant, not applicable, or zero cost.

Supplier quotation table

| RFQ line | Supplier must state | Comparison control | Escalation trigger | |---|---|---|---| | Program responsibilities | Model label and included buyer and supplier responsibilities | Compare deliverables, not labels | The quote depends on unlisted standard components, stock, or buyer inputs | | Specification | Construction, composition, sizes, dimensions, cushioning, cuff, heel, toe, and other priced requirements | Match each entry to the baseline | A mandatory material, construction, or dimension is changed or omitted | | Branding | Method, placement, dimensions, colors, setup, limitations, and revision allowance | Separate baseline branding from alternatives | Buyer artwork cannot be executed within the quoted scope | | Quantity | Pairs by SKU, color, and size; minimums; increments; required ratios; and price breaks | Compare identical quantities and SKU splits | Minimums, increments, or ratios change the buyer’s order quantity | | Samples | Stage, quantity, cost, courier basis, preparation time, revision count, and approval record | Compare equivalent sample stages | The schedule depends on an undefined or unapproved sample | | Packaging | Unit pack, labels, bands, bags, inserts, barcodes, cartons, pack quantities, and buyer-supplied items | Use the same unit and carton configuration | An assumption changes cost, quantity, approval scope, or timing | | Quality scope | Buyer criteria addressed, inspection stage, evidence, exclusions, and proposed defect handling | Apply the same buyer-defined criteria | Required evidence or release conditions are rejected or omitted | | Price | Unit price plus separate development, setup, sample, packaging, inspection, freight, tax, and other charges | Normalize currency, quantity, scope, and delivery basis | A required cost is omitted, conditional, unexplained, or unresolved | | Delivery | Delivery term, named place or port, production period, transit assumption, dependencies, and quote validity | Compare the same destination and delivery basis | A material, approval, booking, closure, or transit dependency is excluded from timing | | Payment and changes | Deposit, balance point, cancellation terms, and process for pricing approved changes | Evaluate separately from unit price | A term conflicts with a mandatory RFQ requirement | | Communication | Named commercial, technical, quality, logistics, backup, and management contacts | Confirm owners and formal channels | An approval or urgent issue has no assigned owner or backup |

4. Control Assumptions and Exceptions

Require one exception register for every departure, exclusion, substitution, dependency, and supplier interpretation. Do not rely on comments scattered across emails, messages, quotation footnotes, or sample discussions.

| Exception field | Required entry | |---|---| | Exception ID | Unique sequential identifier | | RFQ reference | Affected section, table row, SKU, specification, or attachment | | Baseline requirement | Requirement as understood by the supplier | | Supplier response | Comply, cannot comply, proposed exception, or clarification required | | Exception or assumption | Exact exclusion, substitution, dependency, or interpretation | | Reason | Supplier’s stated reason | | Price effect | Amount, increase, decrease, no change, or unresolved | | Quantity effect | Change to minimum, increment, SKU quantity, or pack ratio | | Schedule effect | Time added or reduced and the affected milestone | | Approval effect | New or changed sample, evidence, or approval requirement | | Buyer decision owner | Named role authorized to decide | | Decision deadline | Latest decision date used in the supplier’s schedule | | Status | Open, accepted, rejected, or superseded | | Decision reference | Decision-log entry or written approval reference |

Require a written “no exceptions” entry when a supplier claims full compliance. Verify that statement against the completed specification, pricing, sample, packaging, and delivery responses.

Listing an exception in a quotation does not constitute buyer acceptance. Acceptance requires a written decision from the authorized buyer approver, linked to the affected RFQ revision, specification, SKU, price, and schedule.

5. Assign Communication and Approval Owners

The RFQ should identify who may submit, clarify, recommend, approve, and escalate each issue. A shared inbox may serve as the document channel, but each approval and escalation still needs a named owner and backup.

Contact and authority matrix

| Workstream | Supplier owner | Buyer owner | Authority to define | Backup required | |---|---|---|---|---| | Commercial | Named commercial contact | Procurement or commercial owner | Who may clarify price and terms, and who may approve commercial changes | Yes | | Product and artwork | Named technical contact | Product or marketing owner | Who may clarify specifications and who may approve artwork, samples, and revisions | Yes | | Quality | Named quality contact | Buyer quality owner | Who may clarify acceptance evidence and accept, reject, or conditionally release | Yes | | Logistics | Named logistics contact | Buyer logistics owner | Who may clarify carton data, documents, bookings, and delivery updates | Yes | | Management escalation | Named supplier manager | Named buyer manager | Who may decide unresolved order-risk issues within stated authority | Yes |

Ask both parties to provide:

• Contact name, role, email, and telephone or messaging channel.
• Working hours and time zone.
• Planned closures affecting quotation, sampling, production, or shipment dates.
• Backup contact and the condition for activating that backup.
• Channel accepted for formal approvals.
• Matters the contact may clarify but may not approve.

Calls and instant messages may support discussion. Require the final decision in the agreed written channel whenever it affects specification, artwork, quantity, price, sample status, packaging, delivery basis, or schedule.

Decision-log fields

Record the following for every decision:

• Decision ID and date.
• RFQ revision, SKU, and exception ID when applicable.
• Question, exception, or requested change.
• Options considered.
• Approved decision.
• Named approver and approval authority.
• Specification, artwork, sample, or attachment affected.
• Quantity, price, approval, and schedule effects.
• Effective date.
• Superseded decision, if any.
• Related file, sample, or message reference.

6. Put Approval Gates Into the Quote

Supplier-side custom-sock resources discuss development, sampling, minimum quantities, packaging, and quality-control topics (Velon Socks). Use these as prompts for RFQ submissions and approvals, not as evidence that a bidder includes a particular service or follows a particular process.

| Approval gate | Supplier submission | Buyer approval role | Quote must identify | Escalation trigger | |---|---|---|---|---| | RFQ acceptance | Completed response, pricing, specification confirmation, and exception register | Commercial owner | Clarification deadline and quote validity | Mandatory fields or material exceptions remain unresolved | | Artwork approval | Referenced layout showing method, placement, dimensions, colors, and stated limitations | Product or marketing owner | Included revisions and effect of later changes | Artwork cannot be executed within the quoted method, price, or schedule | | Sample approval | Identified sample stage, dated sample ID, measurements or other required evidence, and correction list | Product or technical owner | Cost, courier basis, preparation time, revisions, and schedule dependency | The sample misses a stated requirement or the response deadline passes | | Packaging approval | Materials, dimensions, artwork reference, labels, barcode data, and pack configuration | Packaging, product, or marketing owner | Included development, sample, setup, and change charges | The submission differs from the priced packaging baseline | | Production release | Final specification, artwork, quantities, price, delivery basis, schedule, and exception status | Authorized commercial owner | Latest release date supporting the quoted schedule | Release is requested while a mandatory approval or exception is open | | Shipment release | Buyer-required inspection evidence and shipping documents | Quality and logistics owners | Evidence, document, and response timing | A defined release condition is not met |

For each gate, specify:

• Required submission contents and file or sample identifier.
• Supplier submission owner and deadline.
• Buyer approver and backup.
• Buyer response window.
• Included revision rounds.
• Cost of additional revisions, when quoted.
• Effect of rejection or late approval on the schedule.
• Formal record that constitutes approval.
• Next gate authorized by the approval.

Custom Sock Lab recommends requesting samples before final production and asking about quantity-based pricing thresholds (Custom Sock Lab). Convert those recommendations into comparable RFQ fields by requesting the same sample stages and quantity breaks from every bidder.

Do not request an unspecified sample. Identify the required stage, such as:

• Digital artwork or placement mockup.
• Prototype or development sample.
• Size-set sample.
• Color or material confirmation sample.
• Pre-production sample made against the release specification.
• Packaging mockup or packaging sample.

Include only stages relevant to the purchase. If the buyer will approve a digital submission instead of a physical sample, record the affected requirement, approver, evidence required, and release consequence.

7. Define Written Escalation Paths

Set escalation levels, recipients, and response windows in the RFQ. Use actual working-hour values instead of undefined terms such as “promptly,” “urgent,” or “as soon as possible.”

| Level | RFQ trigger | Required participants | Required supplier response | |---|---|---|---| | Level 1 — clarification | Missing information or a routine question with no identified effect on scope, price, quality criteria, or schedule | Assigned buyer and supplier workstream owners | Written answer, named owner, or request for missing information within the stated routine window | | Level 2 — controlled exception | Proposed substitution, failed approval submission, unresolved dependency, price change, quantity change, or schedule variance | Commercial owner and affected technical, quality, or logistics owners | Impact statement, options, recommendation, containment action when needed, and buyer decision deadline | | Level 3 — order risk | Approved specification, material quantity, required release condition, purchase term, or buyer-required date is reported at risk | Management contacts and affected workstream owners | Current status, containment, recovery options, accountable owner, decision required, and next-update time |

Define separate response fields for:

• Acknowledgment.
• Initial impact assessment.
• Complete option or recovery proposal.
• Buyer decision.
• Recurring status updates.
• Closure confirmation.

Escalation notice fields

Require every escalation notice to include:

• RFQ and purchase-order reference, if an order has been issued.
• Affected SKU, quantity, and milestone.
• Issue ID, identification date, and reporting date.
• Requirement, approval, sample, or exception affected.
• Available evidence and file or sample reference.
• Confirmed and potential scope, cost, quantity, quality, and schedule effects.
• Immediate containment action and owner.
• Available options with price and schedule effects.
• Supplier recommendation, clearly labeled as a recommendation.
• Buyer decision required and deadline.
• Supplier and buyer owners.
• Date and time of the next update.
• Closure evidence and approving role.

An escalation notice should not change the specification or commercial agreement. Route the selected option through the decision log and the buyer’s defined change-approval authority.

8. Normalize Quotes Before Price Ranking

Build the comparison sheet from the standard supplier return package. Do not rank headline unit prices until each comparison row reflects the same:

• Program scope and included development work.
• Sock specification and branding method.
• Quantity, SKU split, order increment, and required ratios.
• Packaging and carton configuration.
• Sample stages and revision allowance.
• Buyer-defined quality evidence and release conditions.
• Currency and quotation date.
• Delivery destination and delivery basis.
• Approval and schedule assumptions.

Record separate amounts, when applicable, for:

• Unit price.
• Development, setup, or tooling.
• Artwork preparation.
• Samples and additional revisions.
• Sample and document courier charges.
• Unit packaging and carton changes.
• Buyer-required inspection or evidence.
• Freight and other delivery charges.
• Taxes, duties, or buyer-paid charges identified in the quotation.

Mark an unknown amount as unresolved. Enter zero only when the supplier confirms that the item is included at no separate charge or does not apply to the stated scope.

Commercial comparison fields

• Evaluated cost for the normalized scope.
• Currency and buyer-selected conversion basis, if conversion is required.
• Payment timing.
• Quote validity.
• Minimum order, increments, and required ratios.
• Quantity-break prices.
• Change and cancellation terms.
• Open cost assumptions.

Execution comparison fields

• Open and accepted exceptions.
• Required buyer inputs.
• Sample stages and included revisions.
• Approval owners and response windows.
• Supplier workstream owners and backups.
• Escalation coverage.
• Schedule dependencies and decision deadlines.
• Unresolved release conditions.

Keep each supplier alternative on a separate comparison row with its own specification, quantity basis, price, approval requirements, exceptions, and schedule.

9. Ready-to-Send RFQ Instruction

Place this instruction near the beginning of the RFQ:

> Quote against the identified RFQ revision and complete every requested field. Record all exclusions, substitutions, dependencies, and assumptions in the exception register. If you propose an alternative construction, material, branding method, packaging format, quantity, program model, sample plan, or delivery term, respond to the stated baseline or confirm that the baseline cannot be quoted, then price the alternative separately. State the price, quantity, approval, and schedule effect of every exception. No change to specification, artwork, quantity, price, approval status, delivery basis, or schedule is accepted until the authorized buyer approver records the decision in the agreed written channel.

Require every bidder to return the same documents by the same deadline. Set one clarification deadline. If a clarification changes or materially interprets the quotation baseline, distribute the controlled clarification to every participating bidder and identify the affected RFQ sections or attachments.

10. RFQ Release Checklist

Controlled baseline

• [ ] RFQ number, revision, issue date, and quotation deadline
• [ ] Controlled attachment list
• [ ] Clarification process and deadline
• [ ] SKU, color, size, and quantity schedule
• [ ] Construction, composition, branding, and color-control requirements
• [ ] Packaging and carton configuration
• [ ] Delivery destination, requested delivery term, and named place or port
• [ ] Currency, quote validity, and common quantity breaks
• [ ] Mandatory, target, supplier-option, and open-decision labels

Standard supplier response

• [ ] RFQ acknowledgment
• [ ] Itemized pricing sheet
• [ ] Line-by-line specification response
• [ ] Exception and assumption register
• [ ] Preliminary schedule with buyer and supplier dependencies
• [ ] Sample and approval plan
• [ ] Contact and escalation matrix
• [ ] Rule that blank fields remain unresolved
• [ ] Separate pricing for supplier alternatives

Communication and approvals

• [ ] Named buyer owner and backup for each workstream
• [ ] Named supplier owner and backup for each workstream
• [ ] Defined approval authority
• [ ] Formal written approval channel
• [ ] Decision-log fields
• [ ] Sample stages, costs, timing, and revision allowance
• [ ] Production-release conditions
• [ ] Shipment-release conditions when required

Escalation

• [ ] Level 1, Level 2, and Level 3 triggers
• [ ] Acknowledgment and response windows
• [ ] Management contacts on both sides
• [ ] Impact, option, containment, and recovery fields
• [ ] Buyer decision deadlines
• [ ] Recurring update and closure requirements

Comparison gate

• [ ] Same specification and quantity basis
• [ ] Same packaging and sample scope
• [ ] Same delivery basis and destination
• [ ] Separate non-unit charges
• [ ] Unknown costs marked unresolved rather than zero
• [ ] Exceptions linked to buyer decisions
• [ ] Alternatives kept in separate comparison rows

Move a quotation into price ranking only when its quoted scope, assumptions, exceptions, approval dependencies, communication owners, and delivery basis are visible in the comparison sheet. The resulting comparison will reflect each supplier’s documented response to the same RFQ baseline, rather than an unqualified unit price.