We implement Salesforce, Duet360 and Epicor Kinetic around a defined business process. The first release should give sales reliable operational context, move an approved transaction into an acknowledged Kinetic 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 and operations 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 Kinetic | The operational system of record for the agreed customer, part, pricing, inventory, order, manufacturing, shipment and financial information. |
| Duet360 | Our integration and business process orchestration foundation for the agreed Salesforce-to-Kinetic scope, with configured mappings, validation, sequencing, monitoring and exception handling. |
Set a practical first release
Start with one selling company, a defined site or fulfillment scope, a manageable user group and a specific order scenario. Prioritize customer and product references, the approved order handoff and order acknowledgement. Add inventory, shipment, invoice, receivables or service visibility according to the agreed business need and supported interfaces.
Confirm the environment before committing scope
Record the Kinetic release, cloud or on-premises deployment, enabled modules, customizations, Salesforce edition and configuration, Duet360 package, licenses and interface permissions. Distinguish packaged functionality from configuration and additional development. Validate permitted reads and writes in a test environment.
This guide covers Epicor Kinetic. Other Epicor products require their own scope assessment. CPQ, AI, portals, payment processing, returns and automated manufacturing changes 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, obsolete parts, 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, part 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, site, line or delivery-release context. Sales cannot tell whether Kinetic 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 Kinetic 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, Kinetic, 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 Kinetic 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 Kinetic customer, and who approves creation? |
| Customers and ship-to records | Kinetic for operational records | Map Salesforce accounts to the correct Kinetic customer and ship-to within each company. |
| Parts and units | Kinetic | Map Salesforce products to Kinetic parts. Define selling units, conversions and obsolete-part behavior. |
| Price and commercial terms | Assign by field | Define the authority for price, discount, currency, payment terms, tax and freight. |
| Availability and fulfillment | Kinetic | Specify company, site and warehouse scope, inventory meaning, refresh timing and permitted use. |
| Orders lines and releases | Kinetic after acceptance | Preserve the order, line and release relationships and their relevant dates and destinations. |
| Shipment and financial status | Kinetic | 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 part identifiers are globally unique. Define how the selling company, operating site, warehouse and ship-to are selected. Include those boundaries in access checks and reconciliation.
Define the transaction contract
Capture the Salesforce source record and version; Kinetic customer and ship-to references; company and fulfillment context; customer purchase order where required; part, quantity and unit; currency, price, discounts and terms; requested dates; approval references; and a persistent submission identifier.
Decide how a Salesforce line maps to Kinetic order lines and delivery releases, including split quantities or destinations. Confirm the actual supported fields and service operations for the target release. These are business mapping requirements, not an API field specification.
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 Kinetic references before submission. Route new-customer requests through the agreed approval process.
2 Apply pricing and availability rules
Define when sales retrieves a price, which date and customer terms apply, and when a price must be revalidated. Record whether tax and freight remain provisional until Kinetic acceptance. Route price overrides, discount exceptions and credit decisions to authorized owners.
Show inventory with its company, warehouse, unit and update time. Define how on-hand, allocated and available quantities differ for the chosen process. A displayed quantity must not become an unsupported delivery promise.
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 Kinetic operations. Use the persistent submission identifier to recognize repeat requests.
Kinetic offers service-based integration options. The technical team should select supported business services or approved Epicor Functions for actions and assess Business Activity Queries for scoped reads where appropriate. Verify authentication, permissions, business-rule execution and deployment constraints in the actual environment. Do not implement 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 Kinetic order identifier and reconcile customer, company, line quantities, delivery releases, currency and agreed commercial values.
A timeout can leave the outcome unknown. Check whether Kinetic 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
For the agreed scope, return order, shipment, invoice and receivable information with source references and update times. Define how partial shipments, open releases, multiple invoices and delayed updates appear to sales and service users. Include manufacturing or job information only when scoped and permitted.
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 Kinetic 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 sites 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 Kinetic 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 site routing, customer and part mappings, pricing rules and order-line-release 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 Kinetic 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 Kinetic 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 Kinetic transactions and failure paths
Test with representative customers, parts, companies, sites, warehouses and roles. For every case, retain the submitted version, expected outcome, final Kinetic state and business sign-off. Verify outcomes in the owning system.
| Scenario | Required result |
|---|---|
| Valid order with multiple lines | Correct customer, company, terms, parts, units and values are accepted and traceable. |
| Split delivery releases | Quantities, dates and destinations match the approved source intent; no releases are omitted. |
| Missing customer or ship-to mapping | Submission stops with a clear correction request and no unintended order. |
| Invalid part or unit conversion | The record is rejected or routed for correction before an unusable order proceeds. |
| Expired price or unapproved discount | The workflow applies the agreed repricing and approval policy. |
| Credit hold or restricted terms | Finance policy is enforced at the agreed step; missing data cannot imply approval. |
| Wrong company or unauthorized user | Routing and access controls prevent cross-company mistakes or disclosure. |
| Kinetic 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 Kinetic acceptance | Recovery finds the existing order before making a new create attempt. |
| Partial order creation | The supported correction path leaves no untracked or duplicate transaction. |
| Partial shipment and multiple invoices | Salesforce preserves source references and presents the correct detail and freshness. |
| Peak volume or service interruption | Queues, retries and catch-up meet agreed processing and recovery targets. |
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 the effects of Kinetic business process rules, custom fields, Functions, queries and Salesforce automations. A technically successful request can still change an unexpected value. 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, part, unit, company and warehouse 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 Kinetic. 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, Kinetic 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 Kinetic and Salesforce upgrades before deployment and retain a recovery plan.
Expand through the same readiness check
Add a company, site, 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