DOC ROI
BUSINESS SPECIALIZATION · SALES · ORDERS & COLLECTIONS

Sales Orders & Collections Lab

Turn SQL-WON and direct MQL conversion orders into a purchase-ready experience: configure bank-transfer rules, legal acceptance, instalment options and the customer confirmation curtain; then inject the checkout into the final MQL Product Page and produce one traceable handoff for Orders & Collections. Existing SPO customers can also reuse a synthetic account on file in the classroom example.

01 · INTAKE

Bring the conversion evidence into Sales

Sales receives the conversion orders that are already commercially qualified. The final MQL Product Page is also required because this lab adds the final purchase curtain to its Buy action. SPO is loaded as relationship context and is carried into the downstream handoff when a customer key is available.

READY CHECK

What Sales knows now

Load the required files or use Load Don Espadín Example.
02 · PAYMENT MODE

Configure the bank-transfer teaching model

This exercise deliberately avoids card interchange and real student payments. The Product Page will show a bank-transfer purchase step, but this standalone classroom HTML does not move money. A production deployment requires a secure bank / PSP integration, mandate and legal review.

CUSTOMER DELIVERY DATA

Require the minimum data needed to deliver the order

At checkout Sales asks for recipient name, phone and delivery address. These fields travel with the order to Orders & Collections so the next process can actually fulfil the purchase.

Don Espadín example: all names, phones and street addresses are synthetic classroom data. Only the Madrid city / Comunidad de Madrid geography and postal-code format are used as realistic location context.

Academic lift. In this case, “hold” is a simulated business state: the customer payment instruction is recorded, the order waits for delivery evidence, and the case resolves to RELEASED or REFUND. It is not a regulated escrow service by itself.
04 · CUSTOMER CONFIRMATION

Write the curtain that replaces checkout after purchase confirmation

Order numberDE-SALES-000001

05 · CHECKOUT EXPERIENCE

See the final MQL Product Page become a real purchase step

Select any upstream conversion order and test the same HTML that will be downloaded. The existing Level 1 / Level 2 logic remains intact; only the final Buy action receives the Sales checkout curtain.

Customer —
Move customer by customer. SPO customers can reuse a synthetic account on file in the Don Espadín example.
06 · OUTPUT

Hand one complete transaction row to Orders & Collections

The downstream CSV keeps upstream commercial evidence and adds the customer identity and delivery address, payment decision, bank-account reference, payment plan, GDPR acceptance, General Conditions acceptance, order number, collection state and SPO context. The final HTML is the deployable customer-facing Product Page with the checkout curtain already injected.

FINAL CUSTOMER HTML
—

Sales-enabled Product Page

MQL Information in Cascade + Buy checkout curtain + confirmation step.

DOWNSTREAM HANDOFF
0

Orders & Collections · CSV

One row per customer/order, including customer name, phone, delivery address, payment choice, legal evidence and SPO enrichment when available.

EVIDENCE WINDOW · FIRST 5 ROWS
METHODOLOGY AT THE END OF THE JOURNEY

DIIIP explains how a commercial conversion becomes an executable order

Sales creates value when qualified commercial intent becomes a traceable customer payment decision, legal evidence and a clean handoff to Orders & Collections.

D
Data

SQL-WON conversion orders, direct MQL ecommerce orders, customer/SPO context, Product Page HTML, price, quantity, offer and source attribution.

I
Information

The purchase record structures order identity, customer, payment method, account reference, instalment choice, legal acceptances and collection state.

I
Intelligence

Payment-plan rules, the 48-hour delivery-confirmation rule and incident-state logic turn the transaction into an auditable next action.

I
Insights

The handoff reveals which conversion sources become executable orders and which customers require additional collection or service attention.

P
Personalization Actions

The customer chooses the payment plan, accepts the legal evidence and receives an order-specific confirmation while SPO remains available for future service.

KAI·ROI EQUATION · CUSTOMER EQUITY

Sales turns demand into accountable economic evidence

This lab does not redefine KAI·ROI. It creates the order-level evidence needed for downstream revenue realization, service execution, productivity and Customer Equity analysis.

Continue through the DOC ROI ecosystem

The next operational step consumes the Sales handoff to create the executable order and collection process.

Open My Cabinet →