We implement Salesforce, Duet360 and Epicor Prophet 21 around a defined business process. The first release should give sales reliable operational context, move an approved transaction into an acknowledged Prophet 21 order, and return the status needed to serve the customer.
This guide sets out the decisions, responsibilities, delivery steps and acceptance checks for that implementation. It is intended for executive sponsors, sales, branch and warehouse leaders, finance, data stewards and delivery teams.
Define the role of each platform
| Platform | Role in the proposed design |
|---|---|
| Salesforce | Customer relationships, opportunities, activities and the customer-facing workspace. Select the quote and order objects during design. |
| Epicor Prophet 21 | The operational system of record for the agreed customer, item, pricing, inventory, purchasing, order, shipment and financial information. |
| Duet360 | Our integration and business process orchestration foundation for the agreed Salesforce-to-Prophet 21 scope, with configured mappings, validation, sequencing, monitoring and exception handling. |
Set a practical first release
Start with one selling company, a defined branch or inventory location, a manageable user group and a specific order scenario. Prioritize customer and item references, the approved order handoff and order acknowledgement. Add customer pricing, location availability, shipment, invoice, receivables or service visibility according to the agreed business need and supported interfaces.
Confirm the environment before committing scope
Record the Prophet 21 release, cloud or on-premises deployment, enabled modules, extensions, Salesforce edition and configuration, Duet360 package, licenses and API access. Distinguish packaged functionality from configuration and additional development. Validate permitted reads and writes in a test environment.
This guide covers Epicor Prophet 21. Other Epicor products require their own scope assessment. CPQ, AI, eCommerce, returns, payment processing, vendor-managed inventory and automated purchasing are separate scope decisions.
Establish ownership and address four failure areas
We organize delivery around four areas where an implementation can break down. Each needs a named owner, corrective work and evidence of readiness before the next phase begins.
Poor data quality
Failure to prevent: Duplicate customers, invalid ship-to references, inactive items, inconsistent units and incomplete commercial fields create rejected orders or incorrect commitments.
Required action: Data stewards profile the records needed for the first release. Define mandatory fields, accepted values and identifier rules. Correct defects in the owning application and assign unresolved records to an exception queue.
Readiness check: Business owners approve a set of valid customer, item and order examples, plus representative invalid records. Quality thresholds and defect owners are documented.
Incomplete data integration
Failure to prevent: A connection moves data but loses company, branch, item or fulfillment-location context. Sales cannot tell whether Prophet 21 accepted the transaction.
Required action: The integration owner defines record relationships, update direction, sequence, status mapping, reconciliation and recovery. Test repeat requests and uncertain outcomes.
Readiness check: A Salesforce transaction can be traced to the corresponding Prophet 21 order and its final result. Rejections have an actionable reason and a correction owner.
Missing executive ownership
Failure to prevent: Pricing, customer ownership or operational decisions remain unresolved because no sponsor can settle priorities or allocate staff.
Required action: One executive sponsor owns funding and escalation. A process owner owns the business outcome. Platform leads own Salesforce, Prophet 21, Duet360, security, testing and support.
Readiness check: Approve the charter, decision rights, staffing and escalation deadlines. Endowance and the customer agree delivery and ongoing support responsibilities.
Undefined use cases
Failure to prevent: The project attempts broad synchronization without a measurable first business result or a clear user task.
Required action: Select one frequent task, define its users and boundaries, and measure current effort, rework and transaction volume. Identify permitted actions and exceptions.
Readiness check: Approve a use case brief with a baseline, target outcome, data requirements, acceptance criteria and a business sign-off owner.
Design Prophet 21 data ownership and mappings
Approve ownership field by field. The following model is a starting point. Avoid allowing two systems to independently change the same shared value without a conflict rule.
| Domain | Proposed authority | Decision to document |
|---|---|---|
| Prospects and opportunities | Salesforce | When does a prospect become an order-ready Prophet 21 customer, and who approves creation? |
| Customers and ship-to records | Prophet 21 for operational records | Map Salesforce accounts to the correct Prophet 21 customer and ship-to within each company. |
| Items and units | Prophet 21 | Map Salesforce products to Prophet 21 items. Resolve customer item references, selling units, pack quantities and inactive items. |
| Customer price and terms | Assign by field | Define customer or contract price, quantity breaks, discounts, currency, payment terms, tax and freight. |
| Stock and sourcing | Prophet 21 | Specify company, branch and inventory location, stock definitions, sourcing rules and refresh timing. |
| Orders and fulfillment | Prophet 21 after acceptance | Preserve order and line references, quantities, requested dates, ship-to and approved source location. |
| Shipment and financial status | Prophet 21 | Select the detail visible in Salesforce, update frequency, permissions and retention. |
Preserve company and fulfillment context
Use company-qualified mappings rather than assuming customer or item identifiers are globally unique. Define how the selling company, selling branch, inventory location and ship-to are selected. Include those boundaries in access checks and reconciliation.
Define the transaction contract
Capture the Salesforce source record and version; Prophet 21 customer and ship-to references; company and fulfillment context; customer purchase order where required; item, quantity and selling unit; currency, price, discounts and terms; requested dates; approval references; and a persistent submission identifier.
Decide how Salesforce lines map to Prophet 21 order lines, selling units and source locations. Define split fulfillment, backorders and requested dates. Record which values Prophet 21 calculates or assigns. Confirm the actual fields and transaction operations for the target release before approving the mapping.
Control initial loads and ongoing updates
Load only the records required for the first release. Sequence reference data before dependent transactions. Reconcile counts, identifiers and selected totals, then define incremental changes, inactive records, deletion handling and conflict resolution. Assign a correction owner for every failed mapping.
Configure workflows and controlled recovery
1 Prepare sales context in Salesforce
Select the opportunity, quote or approved order process used to initiate the handoff. Capture the company, customer, ship-to, products, quantities, dates and commercial terms. Resolve missing Prophet 21 references before submission. Route new-customer requests through the agreed approval process.
2 Apply pricing and availability rules
Define how sales retrieves the applicable customer price for the item, quantity, selling unit, location and date. Agree how contracts, quantity breaks and authorized overrides apply. Revalidate changed quotes and expired prices before submission. Finance owns discount, margin and credit exceptions; decide where tax and freight become final.
Show inventory with company, branch or location, selling unit and update time. Define how on-hand, allocated, available and inbound quantities may be used. If stock is short, route a backorder or sourcing request to the authorized owner; a displayed stock balance does not reserve inventory or guarantee a delivery date.
3 Validate and submit through Duet360
Validate the submitted record version, approvals and required references. Configure one approved creation path. Sequence prerequisites and dependent records according to verified Prophet 21 operations. Use the persistent submission identifier to recognize repeat requests.
Select supported Prophet 21 interfaces for each read and business transaction. Confirm API availability, licensing, authentication, access rights and deployment restrictions with the platform owner. Validate the selected order operation and applicable custom rules in the target environment. Use Prophet 21-specific operations and avoid direct database writes as the order path.
4 Confirm acceptance and reconcile
Represent pending, accepted and rejected outcomes distinctly in Salesforce. A completed transmission does not prove order acceptance. Return the Prophet 21 order identifier and reconcile customer, company, order lines, selling units, source locations, currency and commercial values.
A timeout can leave the outcome unknown. Check whether Prophet 21 already committed the transaction before retrying. If an order is only partly created, determine the supported completion or correction procedure before reprocessing.
5 Return operational status
Return the agreed order, backorder, shipment, invoice and receivable information with source references and update times. Preserve ordered, shipped and outstanding quantities by line. Define how multiple shipments, invoices and delayed updates appear in Salesforce. Any alternate location, transfer, direct shipment or substitution needs its own verified process and approval.
6 Control amendments and cancellations
Treat a change after acceptance as a separate authorized transaction. Define who can request it, what must be reapproved and how Prophet 21 confirms the result. Do not overwrite an accepted order by resubmitting a revised quote. Verify downstream impact with operations before cancellation or correction.
Deliver in phases with clear acceptance gates
Agree the schedule after discovery. Interface access, customer data readiness, custom business rules and the number of companies or branches determine delivery effort. Advance when the acceptance evidence is complete.
Phase 1 Discover and prioritize
Map the current sales-to-order process with sales, operations and finance. Select the first use case and baseline its effort and error rate. Inventory Prophet 21 and Salesforce environments, custom fields, business rules, existing integrations and approved interfaces.
Deliverables and gate: Approve the charter, process map, responsibilities, scope and exclusions. The sponsor accepts the business outcome and platform owners confirm technical feasibility.
Phase 2 Design data and process controls
Approve the system-of-record matrix, company and branch routing, customer and item mappings, pricing rules and order-line and fulfillment relationships. Define payloads, triggers, status mapping, approvals, security, duplicate control and recovery.
Deliverables and gate: Sign off the solution design, mapping workbook, interface contracts, data correction plan and test plan. Separate released capabilities, configuration and additional work.
Phase 3 Configure and connect
Prepare the Salesforce workspace and Prophet 21 prerequisites. Configure the agreed Duet360 workflows and reference-data loads. Test with separate development, test and production environments, restricted service identities and controlled credentials.
Deliverables and gate: Complete versioned configuration, component verification and traceable processing diagnostics. A representative transaction produces the expected Prophet 21 result in the test environment.
Phase 4 Validate and pilot
Run integrated scenarios and failure tests. Finance checks commercial values; operations checks order usability; sales checks the workspace and returned status. Pilot with a small user group, measure results and train exception owners.
Deliverables and gate: Approve test evidence, resolved defects, pilot results, training and runbooks. The business owner accepts the workflow and operations accepts support readiness.
Phase 5 Launch and stabilize
Reconcile final reference data and in-flight work. Deploy in the approved sequence and verify the first production orders. Monitor backlog, rejection reasons and returned status throughout the agreed stabilization period.
Deliverables and gate: Record release approval, reconciled production transactions, assigned residual issues and support acceptance. Block expansion while material data or transaction defects remain unresolved.
Manage changes throughout delivery
Document the business need, license implications, delivery effort and additional tests for each scope change. Reapprove affected ownership, mappings and acceptance criteria before releasing the change.
Test Prophet 21 transactions and failure paths
Test with representative customers, items, companies, branches, inventory locations and roles. For every case, retain the submitted version, expected outcome, final Prophet 21 state and business sign-off. Verify outcomes in the owning system.
| Scenario | Required result |
|---|---|
| Valid order with multiple lines | Correct customer, company, terms, items, selling units and values are accepted and traceable. |
| Each case and pack quantities | Selling units, conversion factors, quantities and extended prices reconcile with the accepted order. |
| Missing customer or ship-to mapping | Submission stops with a clear correction request and no unintended order. |
| Invalid customer item reference | The item mapping is resolved explicitly; ambiguous or inactive items cannot enter the order silently. |
| Contract price or quantity break | The accepted price matches the agreed customer, quantity, selling unit and effective date. |
| Credit hold or restricted terms | Finance policy is enforced at the agreed step; missing data cannot imply approval. |
| Wrong company or source location | Routing and access controls prevent incorrect branch fulfillment and unauthorized record access. |
| Prophet 21 business-rule rejection | The user sees an actionable reason; the exception reaches its owner. |
| Repeated submit or duplicate message | The intended transaction produces one order; repetition is recognized and recorded. |
| Timeout after Prophet 21 acceptance | Recovery finds the existing order before making a new create attempt. |
| Short stock and split fulfillment | Backordered and sourced quantities remain visible; no stock reservation or promise is inferred from a lookup. |
| Partial shipment and multiple invoices | Salesforce preserves source references and presents the correct detail and freshness. |
| Override or service interruption | Approvals govern overrides; interruption recovery meets agreed targets without creating duplicate orders. |
Set release thresholds before the pilot
Agree targets for first-pass order acceptance, manual repair, processing time, reconciliation exceptions and status freshness. Include capacity, authentication expiry and recovery tests. Each launch-blocking case must pass; accepted residual issues need an owner and a workable support procedure.
Retest business behavior after changes
Review Prophet 21 custom rules, extensions, user-defined fields and Salesforce automations against the chosen integration operation. Test that required price, credit and sourcing controls execute. Reconcile the final accepted transaction and retest after upgrades or configuration changes.
Launch operate and improve the solution
Complete the production readiness checklist
- Approve the release scope, configuration versions, change window and decision owners.
- Reconcile required customer, ship-to, item, unit, company and inventory location references.
- Confirm production connectivity, service permissions, credentials, capacity and monitoring.
- Record in-flight quotes, queued submissions and manually entered orders; assign each a completion path.
- Enable interfaces in the agreed sequence and verify a controlled batch of complete transactions.
- Confirm user training, exception ownership, escalation contacts and the fallback procedure.
Define stop and recovery decisions
Pause new submissions if material pricing, routing, access or duplicate-order defects occur. The release owner decides whether to isolate a workflow, restore a prior configuration or use the documented manual process. Reconcile queues and uncertain outcomes before resuming.
Restoring integration configuration does not reverse orders already accepted by Prophet 21. Use the approved operational amendment or cancellation process. Check orders entered manually before replaying queued requests.
Agree service responsibilities
Endowance and the customer should document support coverage, severity definitions, response expectations, escalation paths and maintenance responsibilities. Confirm the activities included in the selected Duet360 service scope and those retained by Salesforce, Prophet 21 and internal platform teams.
Each exception needs a source reference, submission identifier, failed step, reason, owner, next action and final disposition. Business owners correct data and policy issues; technical owners investigate processing and connectivity. Close an incident only after reconciling the final result.
Measure business value and control change
Track order entry effort, first-pass acceptance, manual rework, backlog, status freshness and user adoption against the baseline. Assess realized benefits alongside implementation, subscription, support and operating costs. Report released staff capacity separately from cash savings.
Assign owners for mappings, business rules, price changes and interface versions. Test releases against normal transactions and known failures. Review the effect of Prophet 21 and Salesforce upgrades before deployment and retain a recovery plan.
Expand through the same readiness check
Add a company, branch, product family or service workflow only when it has reliable data, verified interface support, an accountable sponsor and a defined business outcome. Update access, routing, training, monitoring capacity and acceptance tests before release.
References & related reading
Epicor’s Duet360 OneOffice product page Epicor’s integration overviewDiscuss your first workflow.
Bring your ERP release, Salesforce setup and one representative transaction.
Discuss your integration