Custom Sock RFQ Template: Compare Capacity Evidence and Schedule Risk

Custom Sock RFQ Template: Compare Capacity Evidence and Schedule Risk

When buying custom socks with a logo at wholesale volume, the RFQ should answer two questions before prices are ranked:

1. Are all bidders quoting the same product, quantity, packaging, approval process, and delivery endpoint? 2. Does each proposed delivery date reconcile with capacity evidence for this specific order and production window?

A headline unit price is not comparable when required work is excluded, quantities are treated differently, or delivery dates rely on unstated assumptions. A general statement about factory capacity also does not show that compatible equipment and downstream operations are available when this order needs them.

Use the RFQ to collect three distinct records from each bidder:

• A scope-compliant commercial quotation.
• A capacity calculation tied to the quoted construction, quantity, and production dates.
• A dated milestone schedule showing dependencies, reservation conditions, and recovery commitments.

Set the RFQ Evidence Boundary

Buyer guides can help identify fields to request, but bidder-specific capacity and schedule claims must come from the bidder’s response and supporting records.

Classify each material claim as:

• **Bidder-stated:** supplied without an attached supporting record.
• **Document-supported:** accompanied by an identified, dated planning extract, production record, material confirmation, or similar artifact.
• **Buyer-verified:** checked through a defined buyer verification step.

Record the status without upgrading it. A statement does not become buyer-verified simply because it appears in a signed quotation.

Before requesting prices, define the common comparison basis:

• Order quantity and permitted quantity tolerance.
• Product, branding, and packaging scope.
• Sample, revision, and approval stages.
• Currency, tax treatment, and evaluated charges.
• Delivery rule, named place, and comparison endpoint.
• Required handover or arrival date.

1. Issue One Revision-Controlled RFQ Package

Send every bidder the same files and response tables. Require the supplier to identify the RFQ revision used and disclose every exception, substitution, exclusion, dependency, and conditional assumption.

Suggested cover instruction:

> Quote the requested base scope and quantity matrix without unstated substitutions. Complete every response field and identify the revision of each document used. List all technical and commercial exceptions. Show alternatives separately. Support the proposed production window with an order-specific capacity calculation, dated allocation evidence, and a milestone schedule.

The DeadSoxy B2B buyer guide covers purchasing variables such as MOQ, materials, customization, and shipping timelines. Use those topics to help structure RFQ fields, then require each bidder to state the values and assumptions governing its own quote.

Controlled RFQ attachments

• Quantity matrix by SKU, size, colorway, design, and destination.
• Product construction and measurement specification.
• Artwork, placement dimensions, and color references.
• Packaging, assortment, carton, and marking requirements.
• Sample, approval, and revision requirements.
• Requested inspection or testing scope.
• Required delivery endpoint and milestone dates.
• Commercial, capacity, schedule, and recovery response sheets.

Give every controlled document a revision number and issue date. If a revision changes price, capacity, or timing, require a revised and dated quotation.

2. Lock the Product and Delivery Scope

Complete the buyer-input column before release. Each bidder should confirm every row or state a specific exception.

| RFQ field | Buyer must specify | Supplier must return | Comparison or schedule issue exposed | |---|---|---|---| | Product basis | Style, intended use, size range, measurements, and required features | Quoted construction and technical exceptions | Different products are being priced under one description | | Quantity basis | Pairs by SKU, size, colorway, design, and destination | MOQ application, price breaks, aggregation rules, and tolerance | Quoted quantities are not equivalent | | Material | Required composition, color references, and permitted alternatives | Quoted composition, sourcing status, development needs, and release date | Price or timing depends on an unstated material assumption | | Construction | Cushioning, rib, compression, reinforcement, toe, heel, and measurement requirements as applicable | Construction confirmation and machine-compatibility basis | Capacity is calculated for a different construction | | Branding | Method, placement, dimensions, colors, artwork files, and permitted adjustments | Method quoted, setup requirements, and artwork limitations | Price or output assumes another branding method | | Packaging | Band, label, hangtag, barcode, bag, assortment, carton, and marking requirements | Included components, separate charges, MOQs, sourcing status, and preparation time | Packing work or materials are excluded | | Samples and approvals | Sample type, review allowance, revision rounds, and approval authority | Cost, duration, included revisions, and bulk-release condition | Dates rely on an unstated approval assumption | | Quality scope | Acceptance requirements, inspection stage, and requested records | Responsibility, timing, exclusions, and treatment of nonconforming output | Inspection or corrective work is absent from the plan | | Delivery | Endpoint, named destination, requested delivery rule, and required date | Ex-factory date, carrier-handover date, named place, and arrival estimate if requested | Buyer and supplier are committing to different endpoints |

If bidders use sourcing-model labels, require them to define responsibility for specifications, product development, artwork conversion, and approvals. The Goren Socks B2B guide discusses OEM, ODM, and private-label categories, but the RFQ should use an explicit responsibility matrix instead of relying on the category name alone.

3. Normalize the Commercial Quote

Use a fixed response sheet. Separate recurring unit costs, mandatory one-time charges, optional charges, and costs triggered only by a stated condition.

| Commercial field | Required supplier response | |---|---| | Unit price | Price by SKU, size, colorway, design, and quantity tier | | Development charges | Sampling, artwork conversion, setup, tooling, and other one-time charges | | Packaging charges | Each required component or operation not included in unit price | | Quality charges | Requested inspection or testing not included in unit price | | Logistics | Freight, insurance, handling, and other included or excluded costs to the comparison point | | Quantity rules | MOQ by design, color, size, SKU, and total order; permitted aggregation rules | | Quantity tolerance | Permitted overrun or shortage, approval rule, invoicing basis, and disposition of excess units | | Commercial basis | Currency, tax treatment, payment terms, and quote-validity period | | Delivery basis | Delivery rule, named place, quoted endpoint, and date attached to that endpoint | | Exceptions | Every exclusion, substitution, dependency, conditional price, and unpriced requirement |

Calculate each evaluated total using the same accepted quantity and scope:

**Comparable evaluated total = accepted quantity × unit price + mandatory one-time charges + mandatory packaging charges not included in unit price + mandatory inspection or testing charges + logistics required to reach the common comparison point.**

Show taxes, duties, and similar amounts separately when bidders have not calculated them on the same basis. Do not mark a total as comparable while required scope remains unpriced or the delivery endpoint is undefined.

Keep supplier-proposed alternatives outside the base comparison. For each alternative, require the exact specification change and its effect on price, capacity, and milestones.

4. Require an Order-Specific Capacity Bridge

The capacity response must connect the quoted quantity to compatible equipment, allocated time, demonstrated output, downstream operations, and calendar dates. Record total factory output or total machine count only as background; neither identifies the capacity assigned to this order.

Capacity response fields

| Capacity field | Required supplier response | Supporting detail to request | |---|---|---| | Compatibility basis | Machine or line class proposed for the quoted construction | Relevant machine configuration or equivalent planning category | | Total compatible count | Equipment technically capable of producing the construction | Definition used to classify equipment as compatible | | Allocated count | Compatible equipment assigned or conditionally held for the order | Allocation dates and reservation status | | Scheduled hours | Hours per machine by day or week | Shift pattern, working days, planned downtime, and overtime assumptions | | Output rate | Gross pairs per machine-hour or another defined unit | Rate source and whether it represents knitted output or accepted finished pairs | | Rate basis | This construction, an identified comparable construction, a trial, or a theoretical rate | Date, quantity, and relevant comparison characteristics | | Planning efficiency | Factor for operating loss not already included in the rate | Included loss categories and calculation method | | Yield basis | Allowance for output not expected to become accepted pairs | Whether yield is already included in the rate | | Changeovers | Time for design, color, yarn, size, setup, or other planned changes | Number of changeovers and hours assigned to each | | Downstream capacity | Capacity for every required post-knitting operation | Allocated rate, queue assumption, start date, and completion date | | Subcontracting | Each externally performed operation | Responsible party, committed dates, transport time, and control method | | Contingency | Unallocated time or additional capacity included in the plan | Trigger, amount, availability condition, and decision owner |

Require every output rate to be labeled gross or net. A usable calculation structure is:

**Planned daily accepted-pair output = allocated compatible machines × productive hours per machine per day × gross pairs per machine-hour × planning-efficiency factor × first-pass-yield factor.**

**Estimated knitting days = quoted order quantity ÷ planned daily accepted-pair output.**

If the quoted rate already represents accepted pairs, set any efficiency or yield factor already embedded in that rate to 1.00 and identify what the rate includes. Deduct changeover time from available productive hours or add it as separate machine-hours, but do not count it twice.

Time-phased capacity bridge

| Capacity bridge row | Supplier entry | |---|---| | Quoted order quantity | Pairs included in the base quote | | Additional planned production | Quantity, reason, commercial treatment, and disposition | | Required run machine-hours | Formula and inputs | | Changeover machine-hours | By planned changeover | | Total required machine-hours | Run hours plus separately counted changeover hours | | Allocated machine-hours by week | Dated allocation for the proposed production window | | Capacity margin | Allocated hours less required hours | | Reservation status | Reserved, conditionally held, scheduled after approval, or not allocated | | Reservation expiry or release condition | Date or event that removes the allocation |

A positive aggregate margin does not resolve schedule risk when the allocated hours fall after a required finishing, packing, or handover date. The allocation and milestone schedule must reconcile by date.

Downstream capacity response

Require one row for every operation included in the quoted construction and packaging scope, including applicable finishing, inspection, labeling, assortment, packing, and subcontracted work.

| Operation | Input quantity and unit | Allocated capacity per day | Queue time | Start trigger | Start date | Completion date | Evidence status | |---|---:|---:|---:|---|---|---|---| | Supplier to complete | | | | | | | |

This response prevents a knitting-completion date from being presented as evidence that the complete order will be ready for handover.

Capacity evidence to request

Ask for dated, order-relevant support, with unrelated customer information redacted where needed:

• Machine-availability or line-loading extract covering the proposed production weeks.
• Planner calculation showing equipment, hours, rate, loss factors, and constraints.
• Production record for the quoted construction or an identified comparable style.
• Explanation of how the comparable style matches the required equipment, construction complexity, and output unit.
• Written material-status confirmation and the latest release date compatible with the proposed slot.
• Dated capacity plan for required finishing, inspection, labeling, and packing.
• Commitment and schedule for each subcontracted operation.

For every artifact, record its title, owner, as-of date, covered dates, and relationship to the order. The Velon Socks knowledge base may provide background on materials, customization, packaging, and quality-control topics, but a general resource does not establish a bidder’s equipment allocation, material status, or available hours for the quoted window.

Capacity clarification questions

• Which compatible machines are allocated, on which dates, and for which shifts?
• Is the rate measured as individual socks, matched pairs, knitted pairs, or accepted finished pairs?
• Does the rate come from this construction, a named comparable style, a trial, or a theoretical calculation?
• Which losses are included in the demonstrated rate, efficiency factor, and yield factor?
• How many changeovers are planned, and where is their time counted?
• Which operation controls the completion date?
• Are downstream operations allocated for the same order and dates?
• What event causes the proposed allocation to expire or move?
• Which operations are subcontracted, and what supports their committed dates?
• What additional compatible capacity can be activated if actual output falls below plan?

Do not accept descriptions such as **high capacity** or **fast production** in place of dated allocation data and a quantity-reconciled calculation.

5. Convert Lead Time Into Dated Milestones

Require calendar dates rather than only a total number of days. The bidder should identify whether durations use working or calendar days and specify the calendar and time zone governing approval deadlines.

Each milestone should include:

• Start trigger and predecessor.
• Responsible party.
• Planned duration.
• Planned start and completion dates.
• Buyer input or approval required.
• Material or capacity reservation condition.
• Latest date that preserves the quoted handover date.
• Consequence and revised date if the dependency is missed.

| Milestone | Required schedule detail | Comparability or risk question | |---|---|---| | Technical closure | Date specifications, measurements, artwork, and exceptions are resolved | Can material or capacity be released while technical items remain open? | | Material release | Booking date, color-approval dependency, status, and latest safe release date | Does material timing support the allocated production window? | | Sample preparation | Sample type, quantity, start trigger, duration, and completion date | Is the required sample stage included in price and schedule? | | Buyer review | Review allowance, responsible approver, and included revision rounds | Does the plan rely on same-day or first-round approval? | | Bulk release | Approval condition, target date, and latest safe date | When does a missed approval move or cancel the allocation? | | Primary production | Start date, allocated equipment, hours, changeovers, rate, and completion date | Does the duration reconcile with the capacity bridge? | | Finishing and inspection | Operation-level start, capacity, queue, and completion dates | Are all required post-production steps scheduled? | | Packing | Packaging-material status, packing capacity, and carton-completion date | Are components and packing capacity available when finished goods arrive? | | Ex-factory readiness | Date goods meet the quoted release condition | Is this date distinct from carrier handover? | | Carrier handover | Date, named place, and transport assumption | Is this the endpoint being compared? | | Arrival estimate | Transit assumption and named destination if requested | Is the estimate based on the same handover date and delivery basis? | | Recovery | Trigger, action, owner, added capacity, cost effect, and revised dates | Is the response to a named delay specific and executable? |

The Custom Sock Lab ordering guide discusses samples in the custom-sock ordering process. In the RFQ, define the exact sample stage and require each bidder to state its cost, preparation time, included revision rounds, and bulk-release condition.

For every approval-dependent plan, require:

• **Target approval date:** used in the base capacity and milestone plan.
• **Latest safe approval date:** deadline for retaining the quoted allocation and handover date.
• **Post-deadline commitment:** revised dates, or the rule for establishing them, if approval is late.

Also require one reservation status:

• Reserved before approval through a stated date.
• Conditionally held subject to a stated event or payment.
• Scheduled only after approval.
• Not yet allocated.

Transfer the accepted status, expiry date, and release condition into the final commercial record.

6. Request Risk-Specific Recovery Commitments

Name the schedule risks that could change the quoted production window. Require a separate response for each risk instead of asking only whether a contingency plan exists.

| Named risk | Trigger supplier must define | Required recovery response | |---|---|---| | Material release delay | Date or event after which the slot is affected | Permitted substitute proposal, new material date, slot effect, and revised handover | | Sample or artwork approval delay | Missed target or latest safe approval date | Hold expiry, next available allocation, and revised milestones | | Output below plan | Measured rate or cumulative-output threshold | Additional machines or shifts, activation lead time, added cost, and revised completion | | Equipment allocation removed | Reservation condition not met or allocated equipment unavailable | Replacement compatible capacity and effect on downstream dates | | Finishing or inspection delay | Queue or throughput threshold | Added downstream capacity, resequencing action, and revised carton-completion date | | Packaging-material delay | Latest component-release or receipt date missed | Permitted packaging alternative and revised packing date | | Subcontracted operation delay | Subcontractor milestone missed | Escalation owner, replacement plan, transport effect, and revised handover |

Each recovery commitment should identify the action owner, decision deadline, capacity available for recovery, commercial effect, and revised dates. A general promise to expedite production is not a dated recovery commitment.

7. Compare Quotes Without Hiding Schedule Risk

Use one column per bidder. Keep commercial completeness, capacity support, and unresolved schedule risk as separate decision fields.

| Decision field | Supplier A | Supplier B | Supplier C | |---|---|---|---| | RFQ and specification revision quoted | | | | | Scope-compliant base quote | | | | | Evaluated total at common comparison point | | | | | Unpriced or conditional requirements | | | | | Technical substitutions or exceptions | | | | | Compatible equipment allocated | | | | | Allocation dates and reservation status | | | | | Output basis and evidence status | | | | | Required hours reconcile with quantity | | | | | Allocated hours reconcile with schedule | | | | | Changeovers counted once | | | | | Material status and latest release date | | | | | Latest safe approval date | | | | | Downstream capacity documented | | | | | Subcontracted operations identified | | | | | Handover endpoint and date defined | | | | | Recovery commitments documented | | | | | Remaining unsupported assumptions | | | | | Remaining schedule risk at award | | | |

Apply pass-or-clarify gates before ranking evaluated cost:

1. **Scope gate:** Is the requested base scope priced, with every exception identified and quantified? 2. **Commercial gate:** Can the evaluated total be calculated at the same quantity, scope, currency basis, and delivery point? 3. **Capacity gate:** Do required machine-hours reconcile with quantity, construction, rate basis, and dated allocation? 4. **Downstream gate:** Are all required post-production operations included in both capacity and schedule responses? 5. **Schedule gate:** Do material, approval, production, packing, and handover milestones have explicit dependencies and dates? 6. **Recovery gate:** Do named schedule risks have documented triggers, owners, actions, costs, and revised commitments?

If a response fails a gate, clarify the affected fields and obtain a revised, dated quotation before award. Preserve the superseded quotation in the comparison record.

RFQ Issue and Award Checklist

Before issuing the RFQ

• [ ] Assign the RFQ number, issue date, revision, response deadline, and required quote validity.
• [ ] Define the common quantity, scope, currency basis, and delivery comparison point.
• [ ] Complete the quantity matrix by SKU, size, colorway, design, and destination.
• [ ] Attach construction, measurement, artwork, color, packaging, and approval files.
• [ ] Separate mandatory requirements from permitted alternatives.
• [ ] State sample stages, review allowances, and approval authority.
• [ ] State the required delivery endpoint and date.
• [ ] Include fixed commercial, capacity, milestone, and recovery response sheets.

Require each bidder to return

• [ ] A base quote using the supplied scope and quantity structure.
• [ ] All assumptions, exclusions, substitutions, dependencies, and exceptions.
• [ ] MOQ, aggregation, price-break, quantity-tolerance, and invoicing rules.
• [ ] Sample cost, timing, revision allowance, and bulk-release condition.
• [ ] Compatible-equipment basis, total count, allocated count, and allocation dates.
• [ ] Scheduled hours, output-rate basis, efficiency, yield, changeover, and required-hours calculations.
• [ ] Dated support for allocation, output rate, material status, and downstream capacity.
• [ ] Operation-level production, finishing, inspection, packing, and handover milestones.
• [ ] Details and committed dates for subcontracted operations.
• [ ] Target approval, latest safe approval, and post-deadline commitment dates.
• [ ] Reservation status, expiry date, and release condition.
• [ ] Risk-specific recovery triggers, actions, owners, costs, and revised dates.
• [ ] Delivery rule, named place, currency, payment terms, and quote validity.

Before award

• [ ] Resolve every exception in writing and obtain a revised quotation.
• [ ] Compare evaluated totals at the same quantity, scope, and delivery point.
• [ ] Reconcile quoted quantity with required and allocated machine-hours.
• [ ] Confirm that allocation dates cover the required production window.
• [ ] Confirm the output unit and prevent double-counting of efficiency, yield, or changeover losses.
• [ ] Confirm material status and latest safe release and approval dates.
• [ ] Confirm that downstream capacity and queue time are included.
• [ ] Record the evidence status of each material capacity and schedule claim.
• [ ] Record reservation conditions and named recovery commitments.
• [ ] Transfer the accepted scope, exceptions, charges, milestones, delivery endpoint, and reservation conditions into the purchase order.

The award record should preserve the common RFQ scope, evaluated cost basis, capacity calculation, dated supporting evidence, milestone commitments, and schedule risk still unresolved at award.