📦
Product & format
Name the product, category, grade or format if known. A general application can also be used when the final product selection has not yet been made.
Contact Atlas
Start with what you already know.
Send a detailed sourcing request, request a quotation or describe the application you are working on. You do not need every technical detail finalized before contacting Atlas.
A product name, approximate quantity, destination and a few key requirements are often enough to begin identifying the most relevant specialist product route and the next information needed.
Before you submit
A few details can make the first response much more useful.
Product sourcing becomes easier when the technical and commercial context is visible from the beginning. You can provide only the information already available and leave the remaining fields open where your project is still developing.
⚖️
Quantity
Approximate quantity helps distinguish samples, trial orders, project requirements, container-scale purchases and recurring supply programs.
🧪
Specification
Include important parameters such as grade, composition, Brix, moisture, dimensions, finish, active content or other characteristics relevant to the product.
📄
Documentation
Mention required specifications, certificates, analysis documents, declarations, labeling requirements or other approval information when applicable.
🌍
Destination
Destination country, port or delivery point provides useful context for logistics, documentation and the requested commercial structure.
🗓️
Timing
A target order, shipment or delivery window helps clarify whether the requirement is immediate, project-based or part of a future purchasing program.
Not sure of the exact product?
An application-led inquiry is also useful.
Buyers do not always begin with a final specification. If you know how the product will be used, describe the application, required function, target characteristics or reference product instead.
That context can help narrow likely product families and identify the technical questions needed before a quotation or product comparison becomes meaningful.
Tell us the end use — Beverage, bakery, confectionery, foodservice,
animal nutrition, retail or architectural project.
Describe the target — Flavor, functionality, format, appearance,
performance or other important characteristics.
Add constraints — Certifications, packaging, technical limitations or
destination requirements can help narrow the route.
Multi-product requests
Several products can stay within one project.
A single RFQ can cover more than one product category. List each item separately in the specification or message field and include individual quantities or requirements where they differ.
Shared information such as destination, target timing and broader commercial context can remain connected while individual product lines are routed toward the specialist program most relevant to them.
What happens next
Your inquiry becomes a sourcing brief.
The information you provide helps establish the most relevant product route and identify which technical, commercial or logistics details need to be clarified next.
01
Requirement review
The product, application, quantity, specification and destination information provide the initial context for the request.
02
Specialist routing
The inquiry can be associated with the product family or specialist program most relevant to the sourcing requirement.
03
Clarification
Additional information may be needed where specifications, packaging, documentation or commercial assumptions require further definition.
04
Commercial discussion
Once the requirement is sufficiently clear, product availability, commercial conditions and next sourcing steps can be discussed on a more meaningful basis.
Frequently asked
Inquiry questions, answered clearly.
Practical guidance for preparing and submitting a sourcing request through Atlas.
What should I include in my inquiry?
Useful starting information includes the product or application, specification if known, estimated quantity, packaging, destination, timing and any required certifications, analysis documents or other technical requirements.
Can I use the form for several products?
Yes. List each product in the message or specification field and include separate quantities, formats or requirements where appropriate. Shared destination and timing information can remain part of the same sourcing project.
What if I only know the application?
That is enough to begin. Describe the intended use, target characteristics, approximate quantity and any important restrictions so likely product families can be considered.
Can I include certification or documentation requirements?
Yes. If your purchasing program requires specific certificates, product analyses, specifications, declarations or other documentation, include those requirements in the specification notes or message.
Do I need to know the Incoterm before submitting?
No. If you already have a preferred delivery term, include it. Otherwise, destination and delivery expectations provide enough context to begin the logistics discussion.
Can I send a quick message instead?
Yes. Use the floating Quick Inquiry button for a shorter message when you do not need the detailed RFQ form. You can always provide additional technical or commercial information later.
Which email receives website inquiries?
Website form submissions are routed to contact@atlastradehouse.com. You can also use that email address directly for a business inquiry.
Where can I learn more before submitting?
Use the Product Finder for known products, review Industries & Applications for application-led sourcing, or read the Sourcing Process for guidance on structuring a stronger RFQ.