Industrial exports with AI: organize rubber seal specifications and reply to an inquiry
Turn a rubber seal inquiry into a specification checklist, an English product description and a first reply. Replace practice data with verified product information and keep unknown specifications out of promises.
For industrial exports, I organize product facts before asking AI to write English. A seal is a small part, but a polished email cannot resolve a mismatch in dimensions, material or operating conditions.
This exercise uses a rubber O-ring. You will produce a product fact sheet, customer clarification questions, an English description and a reply draft. Have a colleague review them before using them on a product page or in email.
01 · Prepare verified inputs
Create a product project folder in Codex and add the specification sheet, dimension drawing, product photos, inspection reports and original inquiry. Use the beginner guide below if you need installation help; otherwise create a task in the project.
Remove customer names, email addresses, purchase prices and confidential drawing details. Confirm company permission before using confidential inputs with an AI service. Do not ask AI to infer material, temperature ratings or certificates from a photo.
Include product name; inside diameter and cross-section with units; tolerances; compound grade; hardness and scale; evidence for fluid, temperature and pressure suitability; quantity; packaging; quote validity, lead time and trade terms. Mark unsupported fields as pending confirmation.
02 · Build a fact sheet from practice data
Use this practice brief, which is not a stocked specification or a quote: rubber O-ring; inside diameter 20 mm; cross-section 2 mm; quantity 5,000. Material, hardness, tolerances and operating conditions are unknown. The buyer asks about use in hydraulic equipment, price and lead time.
Paste the next prompt into Codex. You can try the workflow without uploading files, then replace the sample with your own product data.
Organize this rubber seal export inquiry using only the supplied facts. Do not make engineering selections or invent certifications, temperature or pressure ratings, or quotes. Practice input: rubber O-ring, inside diameter 20 mm, cross-section 2 mm, quantity 5,000. The buyer asks about hydraulic equipment suitability, price and lead time. Material, hardness, tolerances, fluid, temperature, pressure, static or dynamic sealing, groove drawing, packaging, quote and lead time are unconfirmed. Create product-facts.md in this project: 1. Columns: field, known value, source, status and person responsible for confirmation. 2. Separate product dimensions, operating conditions and commercial terms. 3. Label sample numbers as practice input and keep unknown fields as pending confirmation. 4. Do not turn an available material option into the material of this product. 5. List information missing for selection or a formal quote. First identify the files you actually read. If none were supplied, state that you used only the practice brief, then create the file.
Open product-facts.md. Check that 20 and 2 are not swapped, millimetres have not become inches and 5,000 has not become the minimum order quantity. Material and operating conditions must remain unconfirmed. Every specific parameter needs a source; a full-looking table is not enough.
03 · Ask questions the buyer can answer
Keep the first reply focused on selection-critical questions: dimension and groove drawings, contacting fluid, temperature and pressure range, static or dynamic use, and specified compound, hardness and tolerances. Technical staff assess suitability; AI organizes the questions.
Oil-resistant or hydraulic use is not a complete specification. Ask for the actual fluid and conditions rather than filling in an assumed answer.
Read product-facts.md and create clarification.md. Write at most six English questions, with a short Chinese explanation under each. Ask selection questions before commercial questions. Group dimensions and drawings, fluid, temperature and pressure, static or dynamic use, compound and hardness and tolerances, and quantity and packaging sensibly. Keep the tone concise and helpful. Explain that the inputs support technical review and quoting. Ask about unknowns instead of inferring them. Do not recommend a compound, conclude suitability or provide guarantees. End with the points technical staff must review after receiving answers.
04 · Write an English description with clear limits
While specifications are pending, describe the product category and information required from the buyer. Do not claim suitability for all hydraulic systems. Dimension drawings, packaging photos and evidence of inspections are more useful than vague quality claims.
Explain that 20 × 2 mm means inside diameter × cross-section, not outside diameter. Mention certificates only when they are held, applicable to this product and available for review.
Read product-facts.md and clarification.md and create product-description.md. Write an English title, an 80–120-word introduction, a specification table and application information to confirm. Label practice values Sample specification and do not promise stock or supply. Use Inside diameter (ID) and Cross-section (CS), keeping millimetres. For unknown material, hardness, tolerances, temperature and pressure ratings, certifications, MOQ, price and lead time, write To be confirmed. Invent no values. Avoid unsupported best, premium or guaranteed performance claims. Add a Chinese comparison and a field-by-field checklist for review before publishing a product page.
05 · Draft the first inquiry reply
The reply should help the buyer provide missing information so you can proceed to technical review and quoting. Acknowledge dimensions and quantity, then ask about the essential conditions instead of starting with a long company introduction.
Confirm price and lead time after receiving complete specifications. For samples, review sample cost, shipping, recipient details and company policy. Do not let AI promise free samples.
Read the three files and create inquiry-reply.md. Practice inquiry: We need 5,000 rubber O-rings, 20 mm ID and 2 mm cross-section, for hydraulic equipment. Can you advise suitability, price and lead time? Write a 120–180-word English reply with a subject line. Acknowledge dimensions and quantity without confirming suitability. Use at most four question groups for operating conditions, drawings and material requirements. Explain that technical review precedes quote, sample arrangements and lead time confirmation. Use placeholders for company and contact names and provide a Chinese comparison. Invent no certifications, stock, test results, payment terms or shipping promises. Do not send email; produce a draft only. End with a human pre-send checklist.
A draft opening could be: Thank you for your inquiry for 5,000 O-rings with a 20 mm inside diameter and 2 mm cross-section. Before we confirm suitability and prepare a quotation, could you share the operating conditions and drawing?
This is sample copy. Update the fact sheet when the buyer answers and ask technical staff to confirm the information. Do not let AI select a compound from a brief description.
06 · Check the draft against the inputs
Check product-description.md and inquiry-reply.md against product-facts.md only. Extract every number, unit, performance claim, certification, lead time, price and commitment. Make a table with original statement, supporting input, match status and proposed correction. Label unsupported statements remove or await human confirmation. Check for ID/CS confusion, quantity treated as MOQ, free sample promises and unapproved hydraulic suitability. Create final-check.md and a revised email with unsupported promises removed. Do not approve engineering selection or send email.
07 · Troubleshooting and completion checklist
Unreadable attachments: ask Codex to list the files and pages it actually read. Replace blurred scans or type in key values. Uploaded does not mean correctly read.
Conflicting dimensions: if the drawing says 20 × 2 and the sheet says 20 × 2.5, pause quoting and send a conflict list to the owner. Do not average the values.
Overly promotional English: retain specifications and questions, remove adjectives and use the first email to advance one next step.
No target buyers: begin with an industry you can supply and understand. Collect actual product pages and procurement requirements before research; invent no purchasing manager addresses.
Completion: the four core files open correctly; numbers and units have sources; unknowns remain unconfirmed; technical questions have owners; English and Chinese agree; a human reviewed the email; nothing was sent without authorization. Log the reply and buyer feedback and update the fact sheet.
08 · Update the facts before replying to new operating details
Continue with the example inquiry for 5,000 O-rings, 20 mm ID and 2 mm cross-section. Suppose the next buyer email says: “Static application. Mineral hydraulic oil. Temperature 40–70°C. Working pressure 80 bar. Drawing attached.” These are illustrative buyer statements, not an approved suitability assessment. Record them without selecting a material or promising delivery.
Retain both original emails and save attachments separately without overwriting old drawings. Name the new file with the buyer code and revision, retaining the email date, original filename and revision printed on the drawing. If none is printed, record “revision not stated”. An unreadable or missing attachment remains unavailable.
Add four columns to product-facts.md: original value, new information, source location and current status. Record static operation as buyer-stated and put temperature and pressure in their own fields. Material, hardness, dimensional tolerance and suitability remain subject to technical review. Distinguish buyer requirements from supplier confirmations.
If the email says 20 × 2 mm but the drawing specifies ID 20 and CS 2.5 mm, keep both and open conflict C01. Ask which specification governs. Do not assume the drawing is approved or average the values. Resolve this before the affected technical assessment and formal quotation.
Read product-facts.md and the new buyer reply. Create revision-review.md, then draft a second English email. Organize information only; do not select engineering specifications or send anything. Original inquiry: O-ring, ID 20 mm, CS 2 mm, quantity 5,000. Illustrative buyer reply: Static application. Mineral hydraulic oil. Temperature 40–70°C. Working pressure 80 bar. Drawing attached. Illustrative drawing summary: ID 20 mm, CS 2.5 mm; material, hardness and tolerance not stated. Without a real attachment, say that you used this text summary only. Output: a change table showing field, old value, new value, source, status and next owner, separating buyer-stated, technically confirmed, unknown and conflicting information; no item is technically confirmed yet. Open C01 for the CS discrepancy without choosing a value. Draft a buyer email acknowledging operating details and asking which cross-section and drawing revision govern; list material, hardness and tolerance for subsequent technical review without re-asking temperature and pressure. Produce an internal handoff of technical questions, buyer follow-ups and commitments still unavailable. Keep the customer email separate from internal IDs, owners and Chinese notes. Do not describe material, suitability, quotation, samples or lead time as approved.
09 · Keep technical and commercial handoffs aligned
A second reply could read:
Thank you for the operating details. We have recorded the static application, mineral hydraulic oil, 40–70°C temperature range and 80 bar working pressure for technical review. Before proceeding, could you confirm whether the required cross-section is 2 mm or 2.5 mm, and which drawing revision we should follow? Please also share any specified material, hardness and dimensional tolerances. We will confirm suitability and commercial details after the requirements and technical review are complete.
This acknowledges information without approving suitability or re-asking temperature. Remove attachment references that do not apply. If the buyer has no material specification, record that explicitly and let technical staff identify further evidence needed. This is an editorial example, not a sent email.
Use three internal handoff rows: sales confirms the governing drawing and quantity; technical staff assess conditions, material requirements, tolerances and validation needs; production or sourcing checks feasibility and scheduling once technical conditions are clear. Add the recipient, outstanding inputs and genuinely agreed follow-up date. If no date is agreed, leave it unconfirmed.
Record technical conclusions with their conditions, source documents and revisions. Approval to evaluate a sample against a drawing is not customer approval for mass production. Any later specification change must reopen the affected material, sample, inspection or schedule decisions.
Keep a small status tracker: waiting for inputs, resolving conflict, technical review, commercial confirmation and ready for buyer review. “Ready for buyer review” must not imply a confirmed order.
Three common misses are updating cross-section in the email but not the product description, attaching an old drawing after a revision, and rewriting a buyer-stated static application as supplier-validated performance. Before sending, search ID, CS, mm, temperature and pressure across the four files and reconcile them to one governing revision.
The next colleague should be able to identify the current revision, unresolved parameters, owners and the single action the next email must advance. That reduces repeated communication better than a long reply.
