A manufacturing CRM should turn an enquiry into a clear product requirement, a reviewed quotation and an accepted production handoff. Keep the requested item, specification and quantity together, then identify the confirmed order that planning is authorised to use. Customer interest alone should not become an instruction to make or order materials.
Manufacturing enquiries often need clarification before anyone can prepare an accurate response. A request from a channel partner may describe a finished item informally, omit a variant or combine several desired dates. The CRM record should preserve the question and its owner until the product requirement is understood.
This guide uses ERPNext’s Opportunity and raw-material request documentation as concrete examples. Its original enquiry-to-material worksheet follows a fictional display-unit requirement and exposes the decisions between selling the finished item and planning its component demand.
What should the enquiry record preserve?
ERPNext defines an Opportunity as a qualified lead. ERPNext permits Opportunities against existing customers. These Opportunity behaviours let the evaluation include both new prospects and established relationships. Identify the actual requesting organisation and contact rather than creating a fresh customer record whenever another enquiry arrives.
An ERPNext Opportunity can record required items and quantities. Record the finished-item identity, requested variant, quantity and unit alongside unresolved specification questions. Keep the customer’s description as context, but distinguish it from the internal item selected for quotation. A familiar description can still refer to a different size, finish or assembly.
ERPNext Opportunities provide Next Contact Date and Next Contact By fields for follow-up. Assign the follow-up to a real responsible person. Ask the demonstrator to show how the pending specification question appears to that person and how the response is retained. A request for clarification is useful only when the next action remains owned.
ERPNext can create a Quotation from an Opportunity and copy relevant fields. Inspect the transferred information in the test copy. Confirm that the quoted item and quantity match the reviewed requirement. Do not assume that copied fields make the quotation complete, or that a draft quotation has authorised a manufacturing run.
Where should sales hand the work to planning?
Define the accepted-order event in your process and retain the agreed specification reference. The handoff should identify what has been confirmed, what remains conditional and who accepts the requirement into planning. A sales-stage label is not sufficient evidence of that acceptance.
ERPNext’s raw-material request workflow starts from one submitted Sales Order. The raw-material request guide distinguishes this action from planning across several orders. Ask the demonstrator to start from the correct submitted order in a test copy and show the generated document’s links back to its source.
The raw-material request workflow requires an active default bill of materials for each manufactured item. Review the bill of materials as a controlled input. Check that it describes the intended finished item and output quantity, and record the chosen version or identifier available in the proposed system. A correct calculation from an incorrect specification is still the wrong requirement.
A purchased finished item without a BOM does not produce raw-material requirements through this action. Include a bought-in finished item in the exercise so the team can explain why its treatment differs from a manufactured assembly. That distinction should remain visible in the customer requirement and planning record rather than being inferred from an item’s name.
| Stage | Information to preserve | Owner to appoint | Acceptance evidence |
|---|---|---|---|
| Enquiry | Requesting contact, item description and questions | Sales contact | Clarification retained with the enquiry |
| Quotation preparation | Reviewed item, unit and quantity | Quotation approver | Draft matches the requirement |
| Confirmed order | Accepted specification and order reference | Order owner | Planning source is explicit |
| Material calculation | BOM, quantities and relevant options | Planner | Generated rows compared with expectations |
| Exception | Ambiguity, supply overlap or wrong item | Named resolver | Decision and corrected record remain linked |
How do component options change the material request?
Include Exploded Items uses lower-level raw materials from multi-level BOMs. Decide whether the exercise needs immediate components or underlying materials before choosing the option. Explain the expected difference using an assembly sketch. A longer generated list is not automatically a better planning result.
Ignore Existing Ordered Qty requests the calculated requirement without reducing it for quantities already ordered. Treat that option as a deliberate decision about whether existing supply reduces the new request. The calculation may therefore request the full requirement despite already ordered supply. Review the generated rows and projected position before submission. The documentation directs users to avoid duplicating existing requirements; make the review part of the proposed operating process.
Keep the generated document’s purpose clear. A material request is a planning record to review within the organisation’s process. It should not be described as proof that the requested inputs have been obtained, that production has been scheduled or that the finished goods are ready for delivery.
Original enquiry-to-material worksheet
Use a hypothetical enquiry for four display units. Each unit contains one frame and two brackets. For the exercise, a frame is manufactured from three panels, while brackets are stocked separately. This is a fictional structure chosen for arithmetic and handoff checks, not a production recipe.
Clarification card: Record the finished-item description and proposed internal identifier. Add a deliberate uncertainty about the finish. Assign the question to the sales contact, record the fictional response and confirm that the selected item represents the clarified requirement before preparing the quotation.
Quotation comparison: Compare the draft with the requirement: four finished units, the intended variant and the correct unit. Inspect the copied values and identify any details still entered separately. Keep the draft stage distinct from the subsequent confirmed-order record.
Assembly expectation: Draw the component tree. Four units require four frames and eight brackets. If all frames must be made, the frame portion needs twelve panels. Write those expectations before opening the generated material rows so the test is not defined retrospectively by the software’s output.
Option comparison: Examine the relevant exploded-item setting in the test copy. Compare the observed rows with the drawn structure and explain how an intermediate frame is treated. Retain the exact setting and generated document reference with the calculation.
Existing-supply review: Introduce fictional existing supply for part of the requirement. Inspect the effect of the documented ordered-quantity option without submitting an unintended duplicate request. Record why the selected setting fits the exercise and who approves any exception.
Handoff acceptance: Ask planning to explain the requirement from the order, BOM and worksheet. Record any mismatch and its owner. The handoff is ready only when the team can trace the planned inputs back to the accepted finished-item requirement without reconstructing it from scattered sales messages.
What should the manufacturing CRM brief retain?
Retain item identities, specification questions, follow-up responsibility, quotation evidence and planning links. Include the exceptions demonstrated in the worksheet. This creates a practical comparison of proposed systems through the handoff your business needs rather than a generic CRM feature list.
For broader scope, see business systems and web development. To discuss the workflow, get started with a fictional enquiry, its assembly sketch and the points where sales and planning currently need a clearer shared record.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.