Files can help, but product, quantity, destination, packaging, and timing are enough to start the request.
Attachment guidance
Use files only when they make the custom sock RFQ clearer.
You can inquire before artwork or packaging files are ready. If you have useful references, send the current files and a short note about what they explain. We can help with the details you are still deciding.
Primary useOptional file support
Best fitChanged or missing support files
Main outputsCurrent files and a short explanation
Send updated files with a short note about what changed. You do not need to submit another RFQ.
Files are optional
Send a file, reference or short note if it helps explain your product, packaging, documentation, destination or timing. You can contact us before these details are final.
If files are needed, use one small pack with one short summary note.
Tell us which files to use and what each one explains. A short note helps us review the update alongside your original inquiry.
- Skip extra files when the RFQ already explains the product, quantity band, destination, packaging, and timing clearly.
- Group only the files that support the same product, quantity band, and destination path already in the RFQ.
- Attach a design mockup or template only when it clarifies style, placement, colorway, packaging, or sample-review intent.
- State what each file is supposed to solve: artwork, color direction, packaging format, compliance request, or shipment context.
- Use simple file names that identify the project, purpose and current version.
- Keep duplicate logos, old concepts, and unrelated channel examples out of the same attachment pack.
- Add one short summary note explaining what changed since the RFQ instead of rewriting the entire brief.
Choosing useful files
Current files and a short note make updates easier to review.
What a strong attachment pack looks like
Current files and one short note are enough. Tell us which version to use and what each file explains; we can discuss anything that is still undecided.
What can stay outside the file pack
Anything that does not change product direction, pack-out logic, documentation scope, or shipment assumptions can usually wait until the next focused review stage.
What causes the most file-review drag
Mixed logo versions, no file naming logic, and references with no note about what should actually carry into the sock program usually create another clarification loop.
File types
Group artwork, packaging references and documents so we can review each clearly.
Artwork and reference files
Group logo files, placement notes and relevant references so we can review the intended design together.
- One preferred logo file set
- Placement note or annotated reference
- Directional sock design mockup or template draft
- Only the product references that still matter
Packaging and commercial support files
Wraps, sleeves, carton ideas, barcode notes, and retail examples should stay together when they influence pack-out or launch readiness.
- Preferred wrap, sleeve, or box direction
- Retail-facing label or barcode notes
- Any shelf-ready or gifting references that should carry over
Documentation and shipment context
Group importer requirements, document requests and delivery notes separately from artwork so each is easy to review.
- Named documentation or standards request
- Destination or importer note
- Shipment or carton assumptions that changed after the RFQ
Example file packs
Use examples only when a file pack will clarify the buyer problem.
Private-label shelf-ready attachment pack
Use this when the RFQ is already in and the team still needs to add cleaner retail-facing artwork, packaging, and barcode support files.
- One preferred logo file plus one placement reference
- Front-of-pack wrap or sleeve reference
- Barcode or label-content note if retail carryover matters
Promotional run attachment pack
Use this when the product direction is clear but the team still needs to send simpler branded references, gift-kit pack-out examples, or revised timing notes.
- One logo mark and one campaign color note
- Simple wrap, insert, or kit-example reference
- Short note on deadline changes or destination pressure
Design mockup handoff pack
Use this when the RFQ is ready but the buyer still needs to show a rough visual direction without pretending the mockup is production-ready art.
- One current mockup, simulator draft, or annotated template
- Short note on what is fixed versus directional
- Primary logo or color reference only if it changes the first review
Compliance-sensitive attachment pack
Use this when the core brief is already in but destination, importer, or document context still needs to be attached clearly.
- Named standards or importer request
- Destination or retailer context note
- Any file proving which product family the request applies to
Design template and mockup files
A template can clarify the RFQ, but it should not pretend to be final production artwork.
Can a sock design template replace artwork?
No. A template can show visual direction, but production review still needs the preferred mark, placement intent, color direction, product family, packaging role, and sample approval context.
When should I attach a mockup?
Attach a mockup when it shortens the first reply: logo location, stripe direction, color blocking, grip placement, packaging presentation, or a changed direction after the RFQ.
What if there are no files yet?
Tell us about the sock type and order you have in mind. Share the quantity, market, packaging, destination, timing or document requirements you know, and ask us about any open questions.
Summary note templates
Send one short note that explains what changed and what should be used first.
What changed since the RFQ
Since the RFQ, we narrowed the preferred logo file, confirmed the packaging direction, and attached the retail-facing references that should carry into the first proof review.
What the factory should use first
Please use the attached primary logo file, packaging reference, and destination note as the current working set for the next production reply. Older concepts should be ignored unless we call them back in later.
What still stays flexible
Fine artwork scale and minor insert details can still tighten later. The core product family, quantity band, destination, and packaging path should remain the same as the original RFQ.
Naming rules
Use simple names that identify the current file.
- Use one clear project stem such as `brand_program_type_date` across all files.
- Separate artwork, pack-out, document, and shipment files into distinct names instead of versioning everything as one mixed folder.
- Mark the preferred version with `primary` or `current` so we know which file to use.
- Name rough mockups as `directional` or `draft` so they are not mistaken for final production artwork.
- Avoid sending old concepts, duplicate exports, or screenshots with no note about why they still matter.
Sample filenames
Name files by project, purpose and version.
Private-label retail pack
brand_private-label_logo_primary.aibrand_private-label_packout_reference.pdfbrand_private-label_barcode_note.txt
Keep the preferred logo, retail packaging reference and label or barcode notes together.
Promotional campaign pack
brand_promo_logo_current.svgbrand_promo_color_direction.jpgbrand_promo_delivery_update.txt
Use when the team needs a cleaner campaign mark, color direction, and timing note without reopening the product brief.
Documentation request pack
brand_docs_importer_request.pdfbrand_docs_destination_note.txtbrand_docs_product-scope_reference.pdf
Use when the document request is tied to a destination, importer, retailer, or product-family scope.
Do not send
Leave out outdated or unrelated files.
Every historical logo export
Send the preferred working mark and one fallback only if needed. A full brand archive makes the next proof path slower.
Inspiration images with no carryover note
References only help when the note says what should carry into the sock, packaging, or color system.
Template screenshots labeled as final
Mockups, templates, and simulator drafts should say what they clarify and what still needs production review before sampling.
Mixed compliance requests with no destination
Certification or audit files need market, importer, or retailer context before they can support a useful production reply.
Related preparation guides
Find more guidance on the detail you want to discuss.
Artwork prep
Open artwork prep if the main problem is still logo files, placement notes, or proof-direction cleanup rather than the attachment pack itself.
Open artwork prepPackaging prep
Open packaging prep if the attachments are really about wraps, labels, cartons, or shelf-ready presentation decisions.
Open packaging prepDocumentation prep
Open documentation prep if the attachments are blocked by standards, audit context, or importer-facing proof requests.
Open documentation prepQuote prep
Use the quote guide to organize your quantity, timing, destination and other order details, including open questions.
Open quote prepSend production RFQ
Use the RFQ when the product, quantity, destination, and packaging frame are ready. Files can be added only if they clarify the review; they are not required to start.
Send production RFQReady to turn the file pack into a production request?