We implement Salesforce, Infor CPQ, ERP and Duet360 as one coordinated business process. The first release should move a valid, approved quote into an acknowledged ERP order and return the execution information needed by sales and service.
This guide gives executive sponsors, process owners and delivery teams the decisions, work products and readiness checks needed to plan that release. Expand into shipment, invoice and receivables visibility when the supporting records and interfaces are ready.
Define the role of each platform
| Platform | Role in the proposed implementation |
|---|---|
| Salesforce | Customer relationships, opportunities and the sales workspace. Select the quote objects and user experience during design. |
| Infor CPQ | Product selection, configuration rules and quoting logic. Confirm the licensed modules and how prices, documents and configuration outputs will be produced. |
| ERP | Accepted sales orders, operational execution and financial records. Assign ownership of items, availability, customer terms and other master data during discovery. |
| Duet360 | The integration and business process orchestration foundation for the agreed cross-system handoffs, with configured mappings, validation, sequencing, monitoring and exception handling. |
Set the architecture boundary
In our implementation approach, Duet360 is the required foundation for the Salesforce-to-ERP processes in scope. Document every handoff, including any direct CPQ-to-ERP interface. Give each transaction one approved creation path and one recovery owner so separate integrations cannot submit competing updates.
Infor CPQ is the configurator in this guide. Salesforce CPQ and other Salesforce revenue products are separate scope decisions. Confirm the exact Salesforce configuration, Infor CPQ modules, ERP product and release, deployment model, licenses and supported operations before selecting the final architecture.
Agree the first release
Choose a bounded product family, selling company, site and user group. Document exclusions such as dealer portals, complex engineering, CAD outputs, payment processing, returns and automated order amendments. Add these only through an approved scope change.
Establish ownership and prevent delivery failures
We plan around four areas where the implementation can break down. Each requires a named owner, concrete corrective work and evidence of readiness.
Data quality
Failure to prevent: Duplicate customers, invalid ship-to records, incomplete product rules and inconsistent units allow a quote to look complete while failing downstream.
Action and owner: Data stewards profile the first-release records, define required fields and correct defects in the owning application. Engineering verifies configuration examples; finance verifies commercial reference data.
Readiness evidence: Approved reference records, measured completeness and validity, and a defect backlog with assigned owners. Test invalid records as well as accepted examples.
Data integration
Failure to prevent: Systems exchange records but lose configuration revisions, customer relationships, commercial terms or order acknowledgements.
Action and owner: The solution architect and integration owner define identifiers, payloads, triggers, sequencing, reconciliation and recovery. Confirm each operation against the target interfaces.
Readiness evidence: A quote can be traced to the exact accepted configuration and ERP order. Rejected and repeated submissions have controlled outcomes.
Executive ownership
Failure to prevent: Unresolved pricing, engineering or data decisions delay delivery because no sponsor can settle priorities or fund the work.
Action and owner: One executive sponsor owns funding and escalation. A business process owner owns the workflow and adoption. Assign decision deadlines and conduct a regular steering review.
Readiness evidence: A signed charter, allocated staff, an escalation route and named owners who can accept the release and its ongoing operation.
Defined use cases
Failure to prevent: The project attempts to connect every product and process without a measurable first outcome.
Action and owner: The business process owner selects a specific sales task and order scenario. Record users, volumes, baseline effort, expected improvement, boundaries and acceptance measures.
Readiness evidence: An approved use case brief and representative transactions that business specialists can verify from quote through ERP acknowledgement.
Make responsibilities explicit
Assign accountable leads for Salesforce, CPQ rules, ERP operations, data, integration, security, testing and support. Endowance and the customer should agree who configures, supplies inputs, approves decisions and resolves incidents for each workstream.
Design data ownership and transaction contracts
Treat the following ownership model as a starting point. Approve ownership field by field, especially where quoting and ERP pricing overlap. Each shared field needs one authoritative writer and a defined update direction.
| Data domain | Proposed authority | Decision to record |
|---|---|---|
| Prospects and opportunities | Salesforce | When does a prospect become an ERP customer, and who approves that creation? |
| Sold-to and ship-to records | ERP for order-ready records | Map Salesforce accounts to ERP customer and location IDs within each company. |
| Items and operational units | ERP | Map CPQ selections to sellable items and supported units; define new-item handling. |
| Configuration rules and revision | Infor CPQ | Identify the approved model version and preserve the accepted configuration snapshot. |
| Price and discounts | Assign by component | Separate base price, options, contract price and discretionary discount; define final authority. |
| Credit tax freight and terms | Assign explicitly | Define the source, calculation stage and authorized approval for each component. |
| Order and financial status | ERP | Define which statuses and totals return to Salesforce and their refresh requirements. |
Specify the quote to order contract
Record the Salesforce account, opportunity and quote identifiers; quote version and line IDs; CPQ configuration identifier and revision; ERP company, site, sold-to and ship-to identifiers; item or configuration references; quantity and unit; currency; agreed price and discounts; requested dates; payment and delivery terms; approval references; and customer purchase order details where required.
Define mandatory fields, valid values, decimal precision, rounding, date and time conventions, payload version and attachments. Decide whether a configuration produces one order line, multiple components or a separate manufacturing structure. Do not assume every CPQ output can be imported by every ERP.
Define acknowledgement and reconciliation
Use a submission identifier that persists across retries and links the quote version to the ERP result. Return the ERP order number and acceptance or rejection details. Reconcile line references, quantities, prices, currency and totals, with agreed tolerances for ERP-calculated charges.
For each interface, document the trigger, payload, authentication, business validation, expected response, timeout handling, duplicate control and support owner. Confirm required freshness and whether updates are event-driven, scheduled or requested by a user.
Configure the complete quote to order workflow
1 Prepare customer and opportunity context
In Salesforce, capture the selling company, customer, contacts, opportunity and intended ship-to. Resolve missing ERP identifiers before submission. Agree whether new customers are created before quoting or held for finance review before order acceptance.
2 Configure the product in Infor CPQ
Pass the approved customer and transaction context into the selected CPQ experience. Configure allowed options, dependencies, exclusions, defaults and required attributes. Test the model against engineering-approved examples. Record the model version and configuration revision with the quote.
Where the licensed solution produces items, a bill of materials, routings, drawings or documents, define the expected output and its receiving process. Engineering must approve how the configured product becomes buildable in the selected ERP.
3 Calculate and approve commercial terms
Apply the agreed source for each price component. Define currency, quantity breaks, customer-specific prices, discount limits, effective dates and quote validity. Decide where tax, freight, margin and credit checks occur and which values are provisional until ERP acceptance.
Route sales, engineering and finance exceptions to named approvers. Freeze the submitted quote and configuration version. Changes to price, quantity, terms or configured options must trigger the agreed revalidation and approval steps.
4 Submit through the agreed Duet360 process
Validate the required references, accepted revision and commercial values before the ERP handoff. Sequence prerequisites and dependent records according to the verified interfaces. Use the persistent submission identifier to prevent a repeat request from creating a second order.
Show the user that an order is pending while acceptance is unresolved. A completed transmission is insufficient evidence of ERP acceptance. If the request times out, check whether the ERP already committed it before retrying.
5 Acknowledge the order and return status
Return the ERP result and order identifier to the sales workspace. Route rejections with a clear business reason and correction owner. Preserve the original submission and record the corrected attempt so support can reconstruct what happened.
For the scope selected, return shipment, invoice and payment-related status with record references and update times. Agree how partial shipments, backorders and multiple invoices appear to users.
6 Control changes after acceptance
Treat changes and cancellations as separate business transactions. Confirm ERP support and authority before exposing them. Define approval, amendment version, financial impact and customer communication. Never overwrite an accepted order by silently resubmitting a revised quote.
Deliver in phases with explicit acceptance gates
Plan by workstream and readiness rather than assuming a fixed duration. Product modeling, source data correction and interface limitations can determine the schedule. Approve an implementation plan after discovery.
Phase 1 Discovery and business scope
Run workshops with sales, engineering, operations and finance. Select the first-release product family and process. Inventory environments, modules, licenses, interfaces and customizations. Review sample accepted orders and difficult exceptions.
Deliverables: Charter, use case brief, process map, responsibility assignments, baseline measures and exclusions. Gate: The sponsor approves the scope and business owner; technical owners confirm feasibility.
Phase 2 Solution and data design
Approve the system ownership matrix, quote objects, CPQ interaction, pricing rules, configuration outputs and order contract. Define access, approvals, status mapping, reconciliation and recovery. Separate available packaged functions from configuration and additional development.
Deliverables: Design specification, field mappings, interface contracts, data remediation plan and test plan. Gate: Business and platform owners sign off on the design and unresolved decisions.
Phase 3 Configure and integrate
Build the Salesforce experience, CPQ product model and quote documents. Configure ERP prerequisites and the agreed Duet360 handoffs. Use separate development, test and production environments and controlled service identities. Complete developer and component verification before integrated testing.
Deliverables: Versioned configuration, documented integration, initial data loads and support diagnostics. Gate: A representative quote produces the expected ERP result in the test environment.
Phase 4 Validate and pilot
Run integrated business scenarios, exception tests, permission checks and volume tests. Business specialists approve configuration outputs and commercial calculations. Pilot with a limited user group and measure completion, correction effort and user adoption.
Deliverables: Test evidence, defect resolutions, pilot scorecard, training and operating runbooks. Gate: The process owner accepts business behavior and operations accepts support readiness.
Phase 5 Cut over and stabilize
Complete final data reconciliation, production access checks and release approval. Activate the agreed interfaces in sequence and verify the first orders. Monitor closely during an agreed stabilization period before handing over to normal support.
Deliverables: Cutover record, reconciled production transactions, support acceptance and expansion backlog. Gate: No unresolved launch-blocking defects; named owners accept service operation.
Manage changes to scope
Document the business reason, design impact, delivery effort, license implications and additional tests for each change. Reapprove affected mappings, product rules and acceptance criteria before release.
Test the business process and failure paths
Test with representative product combinations, companies, sites and user roles. For each case, capture the input quote version, expected outcome, actual ERP result, evidence and business sign-off. Fix launch-blocking defects before release.
| Scenario | Expected evidence |
|---|---|
| Valid standard and configured quote | Correct approved revision, quantities and terms reach the intended ERP company and site. |
| Invalid product combination | CPQ prevents completion or routes the agreed engineering exception. |
| Missing customer or ship-to mapping | Order submission stops with an actionable correction request. |
| Expired price or excessive discount | Required repricing and approval occur before the order proceeds. |
| Credit hold or unavailable credit data | The workflow follows finance policy and cannot imply approval from missing data. |
| Changed configuration after approval | The change creates the required revision and invalidates affected approvals. |
| Duplicate event or repeated submit | One intended order results; repeat processing is recognized and traceable. |
| Timeout after ERP acceptance | Recovery finds the accepted order before any new create attempt. |
| Partial processing or ERP rejection | The outcome is visible; recovery cannot create orphan or duplicate records. |
| Partial shipment and multiple invoices | Returned status and references reflect each relevant line or transaction. |
| Unauthorized role or company access | Access is denied without exposing restricted commercial or customer data. |
| Peak volume and delayed updates | Processing and recovery meet agreed capacity and freshness requirements. |
Validate manufacturing and commercial outputs
Engineering verifies that selected options and generated structures match the approved design. Finance checks prices, discounts, currency, rounding, charges and applicable approval limits. Operations confirms that accepted orders are usable for the intended downstream execution.
Set measurable release thresholds
Agree targets before the pilot for quote completion, order acceptance, manual corrections, processing time, reconciliation exceptions and status freshness. Verify that all launch-blocking cases pass and that every accepted residual issue has an owner and an approved workaround.
Use business outcome measures as well as interface success. An order that arrives with the wrong configuration or requires manual repair has not met the intended acceptance criteria.
Launch operate and improve the solution
Prepare the production cutover
- Approve the release scope, deployment package, configuration versions, change window and decision owners.
- Reconcile required customer, location, item, pricing and configuration references. Apply a data or configuration freeze where needed.
- Confirm production identities, permissions, credentials, certificates and the required interface capacity.
- Record in-flight quotes and submissions. Decide which complete in the existing process and which start in the new process.
- Activate interfaces in the approved order. Check an initial batch of complete transactions before wider use.
- Confirm user training, escalation contacts, monitoring coverage and the fallback procedure.
Define stop and recovery decisions
Stop new submissions if material pricing, configuration, access or duplicate-order defects appear. The release owner decides whether to isolate a workflow, revert configuration or use the documented manual process. Reconcile queued and in-flight transactions before resuming.
A configuration rollback does not reverse orders already accepted by ERP. Record those orders and use the approved business correction or cancellation process. Revalidate orders captured manually before replaying queued transactions.
Operate with clear service responsibilities
Agree the division of support among Endowance, customer platform teams and relevant vendors. Define coverage, severity levels, response expectations and escalation contacts in the operating agreement. Confirm which monitoring and maintenance activities are included in the selected service scope.
Every exception needs a transaction reference, affected system, reason, owner, next action and final disposition. Business owners correct source data or policy exceptions; technical owners address connectivity and processing faults. Reconcile the final result before closing the issue.
Measure value and maintain the product model
Review quote turnaround, first-pass order acceptance, manual rework, integration backlog and user adoption. Compare results with the baseline and include platform, implementation, support and operating costs when evaluating value. Count released capacity separately from realized cash savings.
Assign an owner for product rules, price changes and effective dates. Test model and interface changes against approved examples, including previously rejected combinations. Keep version history, approval evidence and regression tests with each release.
Expand through a repeatable readiness check
Add a product family, company, site or downstream process only after confirming data quality, supported interfaces, executive ownership and a defined business outcome. Update mappings, access, training, operating capacity and the test set before approving expansion.
References & related reading
Duet360 OneOffice Enterprise on Infor MarketplaceDiscuss your first workflow.
Bring your ERP release, Salesforce setup and one representative transaction.
Discuss your integration