A buyer requests three components and attaches five files. Sales can open every attachment. Engineering finds a drawing revision that differs from the requested revision, while a shared assembly drawing applies to two of the components. The inquiry is readable, but its line-by-line scope is still unresolved.
A useful manufacturing inquiry preserves the relationship between the requested item, its quantity, the applicable document and the revision being quoted. The number of attachments tells the team how many files arrived. The document associations tell the team what those files establish for each line.
That relationship deserves a place in an English RFQ workflow. It helps the supplier ask a precise clarification question and return a quotation whose scope can be checked against the buyer's request.
A commercial line needs its own identity
A part number can occur more than once in a request, perhaps with different quantities, delivery requirements or revisions. Give each commercial line an identity within the RFQ, then attach the relevant item and document information to that line.
UBL 2.4 provides a concrete example of this structure. Its Request for Quotation model permits documents associated with an RFQ line. Its Quotation model provides a reference back to the request line to which a quotation line responds. These documented relationships illustrate why a document list and a commercial-line list serve separate functions. An implementation still needs to follow the schema and the parties' agreed exchange rules. UBL RFQ model, UBL quotation model
A small supplier can preserve the same relationships in a controlled worksheet or intake record. Implementing UBL is a separate system decision. The practical requirement is that a reviewer can identify which request line each quoted item and supporting document belongs to.
Separate file identity from document identity
A file has a received name, content and location. A technical document also has an intended role, identifier, revision and applicability. Those fields can disagree.
A filename ending in _B might contain a title block showing revision A. Two uploads can have the same name and different contents. A renamed copy can preserve the same document revision. A checksum can help distinguish the file bytes, while an authorized technical review determines which revision is applicable.
An intake record should retain the received filename and the supplier's assigned file ID. Keep the claimed document identifier and revision alongside the value actually found in the document. Record unavailable values explicitly and obtain the evidence needed to resolve them.
For each association, identify whether the file is a controlling drawing, a model, an assembly reference, an inspection requirement or background material. The role affects how a disagreement should be handled.
Five files can create six associations
The following package is fictional. It illustrates document mapping and makes no production or engineering acceptance claim.
| RFQ line | Requested item | Requested revision | Quantity |
|---|---|---|---|
| L10 | Housing H-10 | C | 20 pieces |
| L20 | Shaft S-20 | B | 50 pieces |
| L30 | Spacer P-30 | D | 80 pieces |
The buyer provides this document package.
| File ID | Received file | Intended association | Intake finding |
|---|---|---|---|
| F1 | Housing_C.pdf | L10 drawing | Revision C matches the request |
| F2 | Housing_C.step | L10 model | Buyer identifies it as the model for revision C |
| F3 | Shaft_A.pdf | L20 drawing | Revision A differs from requested B |
| F4 | Spacer_D.pdf | L30 drawing | Revision D matches the request |
| F5 | Assembly_E.pdf | L10 and L30 assembly reference | Shared context with two explicit associations |
There are five files, three requested lines and six file-to-line associations. The assembly reference contributes two associations. The mapping exercise has two lines with resolved document references and one line requiring a revision clarification.
That 2/3 result describes only the invented mapping task. Technical manufacturability, inspection planning and commercial approval require their own review. The team should ask the buyer whether revision B is missing or whether the request should explicitly permit revision A for L20.
The shared assembly file also shows why forcing a one-file-to-one-line rule can lose information. Store the relationship explicitly and preserve the file's role. A common reference can apply to several lines without replacing each line's controlling specification.
Resolve authority before calculating the price
When a model and drawing disagree, the intake system can record the disagreement. The purchasing and technical parties need to establish which information governs the proposed supply.
Ask a specific question. Identify the RFQ, line, document, revision and disputed feature. Record the buyer's response with its date and the person or role authorizing the clarification. Link it to the affected line.
For the fictional L20 case, a useful clarification would identify the requested B revision and the received A drawing, then ask for the applicable file or an explicit change to the request. A generic “please confirm the drawings” message leaves the actual conflict difficult to audit later.
Preserve the original package after clarification. Add the accepted replacement and mark which association it supersedes. This lets another person understand both the received request and the scope ultimately quoted.
Make the quotation point back to the request
A quotation should allow the buyer to match each offered item with the corresponding RFQ line. The quote can also state the accepted drawing revision, quantity basis, exclusions and unresolved conditions.
If the supplier quotes L10 and L30 while holding L20, show that partial response explicitly. Two priced lines do not establish that the complete three-line request has been answered. The quotation's line mapping should reveal the missing or conditional scope without requiring the buyer to compare filenames manually.
Preserve alternative offers separately. A proposed material or revision substitute needs an identifiable relationship to the requested item and an explicit approval path. A substituted document should not quietly acquire the status of the buyer's requested drawing.
The UBL model's request-line reference is useful here as a design example. It gives the reply a way to identify the commercial line being answered. Your chosen platform or worksheet should provide an equivalent inspectable relationship appropriate to the exchange.
Test the handoff with a controlled package
Use a clearly labeled internal fixture containing multiple lines, a shared reference and one deliberate revision conflict. Ask the sales recipient to identify every requested line and locate its relevant files. Then ask the technical reviewer to record the unresolved association.
The acceptance exercise should follow the package through the actual proposed route.
| Stage | Evidence to inspect |
|---|---|
| Buyer submission | The line details and files that were actually supplied |
| Intake | Received file IDs, names and the recorded associations |
| Human handoff | The responsible team can open the correct package |
| Clarification | The unresolved line and governing decision remain identifiable |
| Quotation | Each offered line points back to the requested scope |
Include a file with the same name as an earlier file but different content. Include an amendment affecting only one line. Check whether the recipient can distinguish the amendment from the rest of the package and identify what was retained from the original request.
Avoid treating an email notification as the whole handoff. The recipient needs the usable package and the information required to review it. A notification can be one event in that chain.
Keep public qualification content connected to the private workflow
The public website can explain accepted document formats, the information needed for a quotation and the route for questions. Job-specific drawings and buyer documents belong within the agreed inquiry and access workflow.
Clear public requirements reduce ambiguity before the buyer sends the package. For example, explain whether a drawing revision, material designation, quantity unit and delivery destination are needed for the supplier's initial assessment. Give the buyer a way to mark information as unknown.
Xindar's confirmed service scope includes English website inquiry paths and human handoff. A project involving technical attachments should define and accept its document-upload, storage and review requirements individually. The supplier's technical team remains responsible for deciding which drawing and conditions it can quote. B2B export marketing, manufacturing content services
Frequently asked questions
Can one drawing apply to several RFQ lines?
Yes, a shared drawing can supply context for several items. Record each applicable line and the document's role. Confirm which information governs each item being quoted.
Is a filename enough to establish the revision?
Inspect the document identifier, revision information and buyer's governing instructions. Retain any disagreement between the filename, document content and request.
Does a file checksum approve the technical document?
A checksum identifies a particular byte sequence. Technical applicability and approval need their own recorded evidence and responsible reviewer.
Should a partially quoted RFQ be marked complete?
Define the workflow's states clearly. Preserve the offered, conditional, declined and unanswered lines so that the buyer can see the scope of the response.