After an export website receives an enquiry, connect requirements, quotation revisions, delivery evidence and the next follow-up action through the original submission ID. Sales first confirms specifications and delivery assumptions, sends an approved quotation with a clear expiry, and records the recipient and next owner action. A controlled register and company email can serve a small team; approvals, cross-site reconciliation and automated reminders warrant a scoped CRM or quotation-system integration.
This guide addresses quotation delivery after a buyer submits an enquiry for equipment, components or custom products. See the enquiry form guide for intake and email faults, and the sales routing checklist for assigning ownership. The workflow, register and acceptance examples below can support a project brief.
1. Record intake, quotation delivery and customer confirmation separately
Assign one primary salesperson and a backup to each request. Record the current stage, missing information, next action and scheduled time. A manual register might use awaiting information, awaiting pricing, awaiting review, sent, awaiting customer response, expired, handed to orders and closed; keep the stages relevant to your actual process. Every change has an actor and supporting evidence.
The website record captures a request; a sales email delivers a particular quotation revision; the customer response must identify the version being discussed. Orders, contracts, payments and fulfilment continue in the systems and processes approved by the business. Keep evidence of sending, recipient delivery and explicit customer confirmation separately. Technical open tracking provides a contact clue.
2. Confirm six groups of information before pricing
- Request identity: source site, form and submission ID, company, contact, reply language and approved communication channel.
- Product lines: model, specification, quantity, unit, customer part number and reference-document revision. See the multi-product enquiry checklist.
- Application: medium, operating environment, certification or customisation requirements; engineering identifies the missing details.
- Delivery scope: destination, target dates, packaging and transport responsibilities, with the agreed conditions recorded.
- Price basis: currency, pricing unit, quantity tier, tax and freight inclusions, and items awaiting confirmation.
- Approval responsibilities: pricing owner, technical reviewer, person approving the external version, and responsibility for checking later changes.
Label gaps as awaiting customer confirmation and schedule the next contact. Track technical files by identifier and revision using the attachment access and handover checklist. The responsible business specialists approve specific trade, tax and payment terms.
3. Give every quotation an identity, scope and deadline
One possible reference chain is enquiry E-017, quotation Q-017 and revision R01. Agree your own numbering convention. Chinese and English documents share the business reference and identify their language; compare product codes, values, currencies, quantities and the meaning of terms line by line. Include at least the following:
| Part | Suggested record | Check |
|---|---|---|
| Identity | Quotation ID, revision, date, customer and owner | Trace to the enquiry and approved version |
| Lines | Model, specification, quantity, unit, unit price and line amount | Match the buyer’s requested lines |
| Scope | Currency, tax, freight, packaging and applicable conditions | State inclusions and pending items clearly |
| Deadline | Expiry date, time zone and lead-time assumptions | The buyer can identify the applicable version and validity |
| Revision | Change summary, superseded version and reviewer | Keep a verifiable copy of each delivery |
Use an unambiguous deadline such as 2026-11-30 18:00, Asia/Shanghai (UTC+8). The business determines validity, lead-time triggers and extension handling. Odoo’s quotation deadline documentation explains expiry and template validity settings. Agree deadlines, reminders and expiry handling for your business; the CatchCMS implementation scope is explained below.
4. Preserve the sent revision and schedule a specific action
- Before sending, business and technical reviewers check the final file, recipient, currency, quantities, expiry and sensitive attachments.
- Keep a controlled copy of the actual sent file with its revision, sending time, recipient and email reference. Apply appropriate access scopes to public product literature and customer-specific quotations.
- When the customer changes quantities or specifications, create a revision with a change summary and retain the earlier delivery evidence. State which version the new email supersedes.
- Record the next contact date, responsible person and specific question, such as confirming a drawing revision or purchase schedule. Follow the customer’s agreed cadence, time zone and working calendar.
- A backup takes over pending actions during absence or departure. Review price, availability and terms before extending or replacing an expired quotation.
Copy this register: site/submission ID | customer | quotation ID/revision/language | requirement-file revision | currency/scope | approver | expiry/time zone | delivery evidence | customer-confirmed revision | owner/backup | next action/time | closure reason. Record silence, bounced email and an explicit refusal as separate observations. Base sales-stage decisions on actual communication.
5. Where does CatchCMS fit?
CatchCMS currently provides content models, dynamic fields, multilingual content management, and public-form validation, submission records and email notification foundations. Configure product descriptions, specifications and public literature for the project and connect them to the theme; see dynamic fields and multilingual maintenance. Sales can begin with a saved enquiry and manage quotation handover in a controlled register or existing business system.
Customer-specific quotation generation and private storage, frozen revisions, price calculation, approval, customer access, automated reminders, CRM synchronisation and failure retries each require scoped project development and acceptance. The current official-site article model serves public content. Customer-specific quotations belong in a workflow with designed access controls. Evaluate contracts, orders, payments, inventory and subscriptions individually, including their owning systems and integration scope.
For integration, associate the source site, form and submission ID with the original request, and assign separate quotation and revision identifiers. Reconcile delivery retries using stable identifiers; retain separate records for later new requests. Record website persistence, business-system receipt, owner acknowledgement and quotation delivery separately, with an assigned duty person handling exceptions.
6. Fictional example: revising a quantity
All models, identifiers, amounts and deadlines here are fictional rehearsal data. English enquiry E-017 requests 20 pieces of PX-240 with a G1/4 specification. Sales prepares Q-017-R01 in a test register at USD 50 per piece, giving a goods subtotal of USD 1,000. Freight and taxes await separate confirmation. The quotation expires on 2026-11-30 at 18:00 UTC+8. These figures serve workflow and arithmetic checks.
The buyer changes the quantity to 23 pieces. Sales confirms the same USD 50 unit price and creates R02 with a USD 1,150 goods subtotal. The change summary records quantity 20 to 23 and the revised subtotal; expiry and lead-time conditions receive another check. After delivery, sales records that the buyer confirmed R02 and retains R01 and its delivery evidence. Chinese internal notes and the English customer file use the same figures.
Then rehearse expiry, the primary salesperson’s absence and file-access permissions. The backup can see pending actions, the customer obtains the applicable file through the agreed channel, and public access exposes only approved public content. The business reconfirms every production price and term.
7. Accept seven outcomes before launch
- Source association: separate Chinese and English test submissions have distinct IDs and traceable quotations and owners.
- Lines and amounts: use two products and different units to check quantities, currency, line amounts, total and rounding rules against the actual business calculation.
- Language consistency: compare product codes, document revisions, values, currency and deadlines, with defined handling of language differences.
- Revision history: changing quantity creates a new version, with the actual sent file, reason and customer-confirmed revision traceable.
- Expiry handling: rehearse before expiry, after expiry and an extension, checking messages, renewed confirmation and document delivery.
- Access and exceptions: use customer, salesperson, backup and anonymous identities in isolation to check access; rehearse bounced email, synchronisation timeout and manual reconciliation of retries.
- Handover: every pending item has a next action and time, the backup can take over, and order handover has evidence in its separate business process.
Use an isolated test environment and sanitised information. Keep expected outcome, actual result, evidence, handler and recheck time. Operational measures can include acknowledged enquiries, valid quotations, explicit customer responses and order handovers; define the period and deduplication method and evaluate acquisition using actual records.
8. Frequently asked questions
Does a small team need a quotation system immediately?
Start by completing one real business sample with company email, a controlled folder and a shared register. Repeated approval, revision or handover problems provide concrete requirements for evaluating an integration.
Can AI automatically quote to customers?
AI can organise requirements and draft explanations. Authorised staff verify fit, prices, currencies, lead times and terms to produce an approvable version. Automated external delivery and calculation require corresponding rules, permissions and project verification.
What should we bring to the website team?
Prepare a sanitised enquiry, quotation template, actual revision example, language requirements, primary owner and backup, and existing CRM interface information. Use CatchCMS project consultation to scope the website intake, manual handover and integration work, then accept one complete enquiry-to-quotation-confirmation sample.