Book a demo

What manufacturing sales and order-intake teams need to verify before planning review

A customer date should not move straight from an email into a promise. Sales first creates one reviewable version of the request. Planning returns a candidate with its assumptions, and only a company-designated authority decides what sales may communicate.

Review one order setRead the due-date review guide
Primary readers
Manufacturing sales leaders, order-intake teams, and review participants
Five states
Request, candidate, authorized promise, communicated promise, and revised promise
Current boundary
Read-only APS review, planner assessment, and company authorization

Define the sales boundary, then open the order review

Job titles and authority vary. One manufacturer may have a sales leader coordinate intake, another may use an order-management team, and another may involve an owner, operations lead, or planning manager. This page separates the actions needed for review without prescribing an organization chart.

Sales records the customer's words, clarifies the requirement, assembles the review package, starts internal review, and communicates the authorized version. A planner produces a production candidate and explains risk. The company's own authority rules determine who can accept the order, approve an exception, or make an external promise.

An inquiry, quotation, customer order, manufacturer acceptance, and order confirmation are not one event. A purchase order or an order number does not by itself establish that the business accepted the order or released anything to production.

Turn the customer request into reviewable order fields

When a customer asks for delivery by month-end, clarify whether that means production completion, shipment from the factory, or receipt at a named location. Record product, specification or revision, quantity and unit, place, time zone, split permission, and the earliest and latest condition the customer can accept.

Mark whether the event is an inquiry, quotation response, customer order, or change request. When drawings, specifications, or attachments have several revisions, name the version used in this review. Conditions still awaiting engineering, purchasing, quality, or customer confirmation should not remain hidden in chat.

This step records the request. It is not a planning candidate, an authorized promise, or the final version sent to the customer. Vague date language is how factory shipment and customer arrival become one misleading field.

Fix the data cutoff and review-package version each time

The handoff from sales to planning needs a review ID, order scope, data cutoff, and time zone. It should also identify the timestamps or versions of the order, routing, critical material, resource calendar, current schedule, and known operating exceptions.

An order file from this morning, a material file from yesterday, and a schedule that omits the latest downtime form a snapshot, not a current operating truth. Customer changes, shortages, feedback, or plan revisions received after the cutoff are outside the result.

A first review does not need every master-data field for appearance's sake. Cover the facts that can change the decision and list missing labor, tooling, maintenance, quality, post-processing, or subcontracting constraints. The planner can then state what the candidate covers and what remains unknown.

Let the planner return candidate dates with assumptions and limits

The planner uses the current orders, supply, routings, resources, shifts, and schedule to form a candidate. It should identify the quantity, production-completion or shipment milestone, place, data time, plan version, and material impact on existing orders.

Third-party products use terms such as available-to-promise (ATP), capable-to-promise (CTP), advanced available-to-promise (aATP), and Global Order Promising to calculate supply and dates. Their configurations and algorithms differ. They explain possible review depth but are not current Kavop feature names.

Overtime, subcontracting, substitute material, alternate resources, or split delivery belong in a candidate only when their facts and approvals exist. A mathematically possible option does not establish shop-floor availability or decide which existing customer commitment should move.

Communicate a specific version only after authorization

Keep the planning candidate, company authorization, and customer communication as separate records. The planner explains feasible dates, risks, and affected orders. A company-designated authority decides the quantity, milestone, date, split, and exception terms that sales may communicate.

The customer version should state quantity, whether the milestone is shipment or arrival, place, time zone, date, and applicable conditions. Retain sender, channel, send time, attachment version, and customer acknowledgement status. Internal approval does not establish customer acceptance.

A company may assign planning, authority, and customer communication to one person, but the three actions should remain distinguishable. The record can then show which date was a candidate, which became an authorized promise, and which was actually communicated.

Hand accepted conditions to planning and operations

After the customer and business confirm the order, sales hands the effective product revision, quantity, date milestone, split arrangement, exception terms, and customer attachments to production planning, purchasing, and the relevant operating teams. An external answer does not automatically become a production plan.

Sales should not present unapproved overtime, substitutes, subcontracting, or rush priority as a confirmed arrangement. Planning also needs more than an order number. It needs to know whether the customer accepted a full quantity, a split, factory shipment, or customer arrival.

The handoff records the effective version, recipients, time, open actions, and next review trigger. Authority to firm, release, or write into an ERP or MES remains governed by the manufacturer's system and control rules.

Recheck impact and issue a revised promise after a change

A change to quantity, specification, place, customer date, supply, capacity, schedule, or expected completion may invalidate the earlier candidate or promise. Sales should open a new version with the old value, new value, requester, time, and reason instead of editing one date in a chat thread.

The planner recalculates from a new cutoff and lists the delta, affected orders, and unresolved risks. An authorized owner then decides whether to hold the promise, revise it, split it, defer commitment, reject the change, or escalate. The system does not make that choice for the business.

When the decision changes, sales sends the revised promise and retains the customer's response. Keep the earlier version as history. Even an earlier candidate needs review against the customer's earliest receipt conditions and downstream arrangements before sales communicates it.

Start with a read-only review of one order set

A first round can use one de-identified order set and a fixed cutoff for customer requirements, ERP exports, spreadsheets, the current schedule, and operating rules. Sales brings the request and conditions, the planner compares the current plan with candidates, and an authorized owner reviews which dates may be used externally.

The review tests whether data reconcile, candidates are explainable, affected orders are visible, and role handoffs can be checked. A read-only file import is not a real-time connection, and one sample does not establish a plant-wide sales-order workflow.

APS production scheduling and due-date analysis remain Kavop's most mature product today. Kavop does not currently quote or accept orders, approve promises, notify customers, or write automatically into a CRM, ERP, or MES.

Common questions

Is manufacturing sales order intake one uniform role
No. Titles, reporting lines, and authority vary by manufacturer. This page separates customer requests, planning candidates, authorization, and communication while actual responsibility follows the company's structure.
Can sales promise a candidate date as soon as scheduling returns it
No. A candidate applies to a defined data set, scope, and assumptions. A company-designated authority first decides which quantity, milestone, date, and conditions may be communicated.
Does Kavop quote, accept orders, or send promises for sales
Not today. Kavop currently focuses on APS scheduling, candidate comparison, and risk explanation. The manufacturer's responsible people retain order acceptance, promise authorization, and customer communication.
Does the first round write into a CRM, ERP, or production system
No. The first round uses de-identified, read-only material for review by sales, planners, and authorized owners, with no automatic write-back to a CRM, ERP, MES, or another execution system.

Public sources

These official sources distinguish inquiries, orders, date calculations, internal approval, customer communication, and order changes. Each vendor's terms and configuration apply only to its own products. They do not establish equivalent Kavop capabilities or imply vendor endorsement.

  1. Microsoft Learn sales and marketing overview
  2. Microsoft Learn on creating sales orders
  3. Microsoft Learn on order promising
  4. Microsoft Learn on calculating sales-order delivery dates with CTP
  5. Microsoft Learn on confirming sales orders
  6. SAP Advanced Available-to-Promise
  7. SAP review of availability check results
  8. SAP approval workflows in your system
  9. SAP approval statuses and authorizations
  10. SAP Manage Sales Orders functional details
  11. Oracle Check Availability
  12. Oracle Refresh Results
  13. Oracle promised ship and arrival dates
  14. Oracle Order Management statuses
  15. Oracle overview of managing change during order fulfillment

Put one order set, its planning candidates, and the customer version side by side.

The first round uses de-identified data and compares the current plan with candidates for review by planners and company-authorized owners. The first round stays read-only. Findings from one sample cannot be extrapolated to the whole plant. File or snapshot intake does not establish real-time synchronization, bidirectional integration, conflict handling, or production-system write-back. Current material must not present sample validation as a customer case, customer outcome, fixed ROI, industry result, or scaled deployment.

Book a sales order review