Manufacturing CRM requirements should explain how a customer request becomes a technically understood, commercially approved order. The difficult part is often the connection between sales promises and production reality. A useful brief defines that handover, preserves quotation history and gives salespeople reliable information without asking the CRM to become a second production planning system.
Map the enquiry-to-order journey before choosing fields
Follow one recent enquiry from first contact through drawings, feasibility questions, quotation revisions and order acceptance. Identify the decisions made at each step and the person authorised to make them. A salesperson may own the relationship while an estimator owns the costing and an engineer confirms whether the specification is workable.
Write stages around those decisions. “Awaiting technical information” should mean something different from “quote being prepared”. Give every waiting state an owner and a next action. Otherwise a pipeline can look busy while nobody knows whether the customer, engineering team or supplier is holding up progress.
Represent companies, sites and people separately
A manufacturer may sell to a purchasing office while delivering to several factories. Model the customer organisation, delivery sites and individual contacts as distinct records with explicit relationships. Record contact roles such as buyer, engineering reviewer and accounts contact. Do not assume that the person requesting a quote can approve a changed specification.
Allow a contact to be relevant to more than one site when the business needs it. Keep the customer account identifier used by the order system alongside the CRM identifier. Decide which system controls address changes and who reviews disagreements. Copying an old delivery address from the most recent quote is not a dependable master-data process.
Make quotation revisions traceable
A quotation needs more than a document attachment. Define fields for the requested item or service, quantity breaks, currency, specification reference, revision, assumptions and validity information. Where drawings matter, link the quote to the specific drawing revision used during assessment. A link that always opens the newest drawing can obscure what the customer originally accepted.
Separate draft, issued, superseded and accepted versions. Issuing a revision should preserve the earlier version and explain what changed. Require explicit approval where a change crosses an internally agreed threshold, such as an unusual delivery commitment or departure from standard commercial terms. The threshold belongs in your process definition, not in a salesperson's memory.
Define the boundary with ERP or MRP
Decide where each business fact is authoritative. A workable arrangement might put enquiries, contacts and opportunity activity in the CRM, while the existing operational system controls stock, production schedules and order fulfilment. That is a design choice to document and test, not a universal rule about every software product.
For every exchanged field, record its direction, identifier, update frequency and failure owner. If sales can view an estimated dispatch date, show when it was last refreshed and which system supplied it. Do not make stale data appear current. When the connection fails, users need a visible warning and a practical route to obtain an updated answer.
- Define the event that creates an order request from an accepted quotation.
- Include the accepted quote revision and customer reference in that request.
- Prevent retries from creating duplicate order requests.
- Require an acknowledgement before showing the handover as complete.
- Assign failed handovers to a named operations queue.
Worked hypothetical example: a fabricated bracket enquiry
A fictional fabricator receives an enquiry for 300 brackets against drawing revision B. Engineering asks for a tolerance clarification, so the opportunity moves to “awaiting customer specification” with the salesperson responsible for chasing it. The customer supplies revision C. The estimator prepares quote version two against C, preserving the earlier estimate against B.
The customer then sends an order referencing the first quote. The CRM flags the mismatch instead of automatically creating a production order. Sales confirms the intended revision with the buyer, engineering verifies the specification and the accepted quote version is recorded. Only then does the system send an order request to operations.
If the operational system is unavailable, the CRM shows “handover pending”, retains the request identifier and alerts the responsible coordinator. A later retry uses that same identifier. This example describes hypothetical controls and workflow behaviour; it is not a claim about a client implementation or financial outcome.
Ask for reports that expose stalled work
Request an enquiry ageing report by waiting reason, a quotation report by revision status and a handover exception report. A single total pipeline value cannot explain why estimates are delayed. Show the number and age of opportunities awaiting engineering information separately from those awaiting a customer's decision.
Define opportunity value consistently. If a customer asks for prices at three alternative quantities, those alternatives should not automatically become three additive sales opportunities. Agree how expected demand, one-off orders and possible repeat business are represented. Keep estimates distinguishable from accepted orders so management does not confuse interest with committed work.
Turn the requirements into acceptance tests
Use a small set of realistic scenarios: two delivery sites, a superseded drawing, an amended quantity, a lost opportunity reopened later and a failed order handover. Ask sales, engineering and operations to complete their part of each scenario. Check that the next person receives enough context without reopening a chain of emails.
Include access tests. A salesperson may need a customer-facing quote without access to every costing assumption. A production coordinator may need the accepted specification but no reason to edit the sales forecast. Define these permissions according to roles and verify them with separate test accounts, rather than testing everything as an administrator.
Prepare a brief suppliers can answer
Your requirements pack should contain the stage definitions, record relationships, quotation revision rules, integration boundaries and acceptance scenarios. Identify which requirements are essential for the first release. Defer convenience features until the enquiry-to-order handover works reliably, especially where the current operational system already performs the underlying task.
Use the CRM data migration checklist when deciding how to preserve historic quotes and account references. Explore Visuosofts CRM development for a system built around these workflows, or contact Visuosofts with an anonymised quotation journey and the systems that currently hold your order data.