A custom optical filter request is easier to review when optical behavior, geometry, quantity and open questions are separated before the first quote conversation.
Prepare a structured Custom Optical Filter RFQ inquiry with optical fields, attachments, commercial notes, and document requests for Lumalyx technical review.
Use this page to prepare a technical inquiry before discussing commercial details. The request should explain the optical function, target values, geometry, quantity, document needs, and the open questions that need review.
Start the RFQ with technical context before commercial timing.
Prepare wavelength or band, bandwidth or cutoff, blocking or attenuation target, AOI, substrate, dimensions, tolerance context, quantity, application context, and attachments. These fields help a technical reviewer understand the request before quoting is discussed.
Fill the technical fields before sending the inquiry.
Quantity, destination, target timing, and document needs are useful, but they should not replace the optical requirement. Pricing, lead time, availability, and commercial terms need confirmation through the request path after the technical context is visible.
Keep commercial notes in the inquiry without treating them as confirmed.
Attach drawings, spectra, current component information, channel maps, size constraints, and test notes when available. If a document is needed from Lumalyx, state the type of document and the reason it matters for the review.
Attach known files and list requested documents.
A clear request separates required values, flexible values, unknowns, and documents. It should make the first response easier to route toward product family review, coating discussion, drawing review, or follow-up questions.
Mark fixed values, adjustable values, and unknowns in separate lines.
Submit the technical package when the optical fields and documents are ready. If some values are still unknown, include the uncertainty explicitly so the response can focus on what information is needed next.
Submit the RFQ package or request document review.
Use these fields to turn the page topic into a reviewable Lumalyx request.
Custom filter searches often mix product, supplier and manufacturer intent. Lumalyx handles this page as an RFQ preparation surface: define the optical task first, then attach the fields needed for review.
Prepare wavelength range, pass or blocked band, CWL, FWHM, OD or transmission target, AOI, substrate, size, thickness, drawing, quantity and application context.
If the request starts from a known family, review spectral filters, neutral density filters, dichroic optics or coated components first. If the part is not clear, start with the RFQ package.
This page keeps inventory, timing, document status, site-control questions and feasibility outside the public text. Those details require RFQ review.
The safest next step is to send known optical values and mark open fields clearly.
These fields move the inquiry from a procurement keyword into a reviewable optical package.
Lumalyx can review a request more efficiently when commercial intent is paired with wavelength ranges, blocking or attenuation targets, AOI, substrate, size, quantity and use context.
Start RFQ packageA custom optical filter inquiry moves faster when optical behavior, geometry, quantities and open questions are separated into review fields.
| Field | Send when | Review note |
|---|---|---|
| Optical behavior | The request involves a pass band, blocked band, cutoff edge or attenuation target. | Name the role first, then add CWL, FWHM, OD, transmission or cutoff values that are known. |
| Mechanical and drawing data | Size, thickness, substrate, AOI, coating side or assembly fit affects the part. | Attach drawings or mark dimensions as open when the optical task is known but the package is still being set. |
| Project and quantity context | The request is for evaluation, pilot build, redesign or recurring sourcing review. | Use stage and quantity to frame the review conversation without implying timing or commercial terms. |
The public page should not answer feasibility, timing or commercial terms. It should help the buyer send enough information for a scoped review.
Useful attachments include spectrum sketches, current references, mechanical drawings, source and detector notes, and channel-layout context.
For DACH, Japan and South Korea pilot pages, local language should only be added after the RFQ vocabulary and buyer task differ from the English global page.
Ask for the optical role, known numeric fields, drawing status, stage and quantity in one request so the review does not depend on a product name alone.
These answers keep the page focused on RFQ preparation.
Include optical role, wavelength ranges, CWL or cutoff, FWHM, OD or transmission target, AOI, substrate, size, drawing, quantity and application context.
Yes. Mark unknown values clearly and include the application, source, detector and any current references.
No. It prepares the request package. Feasibility, timing and commercial terms require RFQ review.
