Convert quote to order and release fulfillment

The runtime does not expose a one-click convert action on the quote row. That matters because operators need to understand the actual UX: once the quote is accepted or otherwise ready, the next controlled step is to create a Sales Order and link the commercial record through Source Quote.

Teach learners to see that link as an accountability trail. The order is not a replacement for the quote. It is the execution record that inherits the commercial promise and carries it into fulfillment and billing work.

Evidence should come from the customer record, quote or order state, approval trail, fulfillment posture, billing document, receipt, or credit workflow. For Conversion starts in Sales Orders, not in a magic button, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

When creating the sales order, the operator should complete the operational header deliberately: Source Quote, Customer, Contact, Invoice To, Ship To, Order Date, Requested Delivery, Confirmed Delivery when known, Currency, Payment Term, Shipping Method, Incoterm, Customer PO details, and Salesperson.

Those fields are the promise the warehouse and finance teams will now execute. A released order with the wrong warehouse, shipping method, address, or customer PO context is not progress. It is a better-organized mistake.

For Build the order header for execution, not just for paperwork, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The Sales Orders tab exposes the real release gates: Credit Check, Place Hold, and Release. Operators should understand what each gate means. Credit Check asks whether the account posture is still acceptable. Place Hold keeps the order visible but intentionally blocked. Release turns a draft commitment into warehouse-facing execution.

That means order release should be taught as a controlled checkpoint. If risk, address quality, customer PO evidence, or delivery readiness is still uncertain, the right action is often hold or correction, not optimistic release.

Use this section to confirm the learner understands more than the page label. They should connect Release is a decision, not a default to the business state, owner, and consequence behind it.

After release, Reservations show whether the order actually has allocatable stock behind it. An active reservation with a valid warehouse, sales-order line, product, and positive reserved quantity is the precondition for Create Pick List. Without that, the workflow is still blocked upstream.

Pick Lists then prove the reservation has become warehouse work. Shipments carry the order into physical dispatch. In that tab, the operator creates the shipment with the sales order, customer, warehouse, carrier, service level, and shipment date, then records Dispatch when the goods leave and Deliver when the receipt is confirmed.

Use this section to confirm the learner understands more than the page label. They should connect From released order into warehouse flow to the business state, owner, and consequence behind it.

The healthy outcome is not just “order created.” It is an order linked to the source quote, released intentionally, with hold and credit posture understood, allocation visible, picking underway or complete, and shipment state recorded honestly.

That is the moment the sales team can say the commercial promise has entered controlled execution rather than merely changing labels from quote to order.

For What good looks like at the end of this job, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Run the lesson as a quote-to-cash operating rehearsal. Start with the practical task: understand how the runtime turns an accepted quote into an operational order without hiding the source commercial record. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from the customer record, quote or order state, approval trail, fulfillment posture, billing document, receipt, or credit workflow. The practice should end with the learner connecting the action back to the lesson summary: teach the next live job after quote acceptance: create the sales order with source-quote traceability, decide credit and hold posture, release the order, and push it into reservation, picking, and shipment execution.

Close the exercise by asking the learner to restate the objective in operational terms: understand how the runtime turns an accepted quote into an operational order without hiding the source commercial record. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let revenue work move forward only because the next button is available. The learner should check commercial terms, customer context, fulfillment readiness, and finance impact first. In this lesson, watch for that risk while learners work on this objective: understand how the runtime turns an accepted quote into an operational order without hiding the source commercial record.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain why the runtime uses Sales Order creation with Source Quote instead of a quote-row convert shortcut and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain why the runtime uses Sales Order creation with Source Quote instead of a quote-row convert shortcut, keep the lesson in practice mode before marking it complete.