Salesforce–Infor CSI/SyteLine Integration: Implementation Guide
A Salesforce–Infor CSI/SyteLine implementation connects sales activity with manufacturing through agreed XML Business Object Document (BOD) messages. Start with one business process. Define data ownership, identifiers, message rules and acceptance tests. Duet360 supplies prebuilt, packaged business processes, with a fixed implementation fee for agreed out-of-the-box functionality.
1. Define the first business outcome
Choose a complete workflow that solves a clear operational problem. Examples include making order status available in Salesforce or sending an approved order request to CSI. Agree what a salesperson, operations user and support reviewer must be able to do at the end.
Write acceptance criteria in business terms. For an order handoff, a successful outcome includes the correct ERP order reference and status in Salesforce. Sending a message alone does not establish that the ERP accepted the order.
Name the process owner and the people who will sign off the result.
Identify the CSI/SyteLine release, deployment, companies and sites in scope.
Document the Salesforce objects, approval steps and business events involved.
Define the first-release scope, exclusions and success measures.
2. Confirm XML BOD messaging for CSI/SyteLine
For the Duet360 CSI/SyteLine integration described in this guide, the ERP exchange uses XML BOD messages. BOD means Business Object Document. It carries business information in a defined XML structure.
Infor documents BOD-enabled integration and distinguishes a document’s noun from its verb. The noun identifies the business object; the verb identifies the message action. Confirm the exact documents supported by the installed release and the selected implementation.
Agree the message route, connection settings and security with the ERP administrator. Where Infor ION is part of the agreed deployment, confirm the connection points and document flows. Do not assume the same setup applies to every cloud or on-premises environment.
List each required BOD, direction, verb, version and business trigger.
Identify the source record, target record and correlation reference.
Confirm mandatory XML elements, identifier formats and company/site context.
Define how acknowledgements, rejected messages and final business status are interpreted.
3. Map customers, items and transaction context
Start with the records that give the workflow meaning. A Salesforce account name is not enough to identify a CSI customer. A product label is not enough to select a manufacturing item.
Record the agreed identifiers for customers, ship-to locations, items, units, currency and selling site. Decide which system creates and maintains each value. Include custom fields and references that the chosen BODs require.
Customer and ship-to: matching keys, addresses and ownership of changes.
Item and unit: part identifiers, units of measure and conversion rules.
Pricing: authoritative source, quantity, currency and approval rules.
Orders: document references, line numbers, requested dates and change handling.
Status: the ERP states and timestamps that Salesforce users need.
4. Configure the prebuilt business processes
Duet360 includes prebuilt, packaged business processes designed to deliver predictable business outcomes. The implementation applies those processes to the agreed CSI/SyteLine environment, mappings and operating rules.
Customers retain flexibility to adapt their business processes. A packaged starting point does not require every company to work in the same way. Agree the required changes and distinguish standard configuration from additional implementation work.
For a quote-to-order workflow, define the checks before XML BOD generation, the approval that permits the handoff, and the status that returns to Salesforce. If Infor CPQ is included, confirm which accepted configuration and revision the order must use.
5. Prepare secure access and clean starting data
Use dedicated integration access with only the permissions needed for the agreed process. Confirm Salesforce API availability, object permissions and field access. Salesforce recommends least-privilege integration users; licensing and access must be checked for the actual org.
Prepare representative customer, item and order records before testing. Resolve duplicate identifiers and missing required values. Agree how the initial data load and later updates will be reconciled so they do not create competing copies.
6. Test the business result and exception path
Use a test environment and representative records. Run the full process from the Salesforce action through the XML BOD exchange to the final CSI result. Include business users in acceptance testing.
Treat delivery, acknowledgement and business acceptance as distinct checks. Determine what each response means for the selected BOD and workflow. A technical receipt must not be presented to a salesperson as a completed order unless the business result confirms it.
Happy path: the intended customer, site, items and approved values produce the expected result.
Data errors: missing customer references, invalid items, units or required XML fields.
Business changes: revised price, quantity, ship-to, approval or configuration revision.
Service interruptions: delayed delivery, missing acknowledgement and recovery after an outage.
Repeated messages: confirm the configured duplicate controls and safe reprocessing procedure.
Reconciliation: compare Salesforce references, BOD references and the resulting ERP transaction.
7. Make logs, Data Quality and support part of launch
Duet360 logs are accessible to authorized users in Salesforce, and the product includes a comprehensive Data Quality component. Include these capabilities in training so users know where to review integration activity and data issues.
Document who corrects business data, who investigates technical failures and who approves reprocessing. Before retrying an order request, establish whether CSI already accepted it. Agree the log references and evidence needed for escalation.
8. Confirm the fixed-fee scope and rollout plan
Duet360 implementation is based on a fixed fee for its out-of-the-box functionality. This is a major differentiator: the prebuilt process foundation is paired with a defined fee for the agreed standard implementation.
Confirm the included business processes, BODs, mappings, companies, sites, data preparation, acceptance tests and exclusions in writing. Subscription charges, third-party licenses, enhanced support and additional work must be clear.
Standard onboarding is planned for four weeks, subject to the agreed scope, access, data readiness and customization. Set the project schedule after discovery. Use a controlled cutover, reconcile the first transactions and assign named support owners.
Existing CSI/SyteLine customer evidence
General Kinematics’ published case study covers Salesforce Sales Cloud, Partner Communities, Pardot and Duet360 for Infor SyteLine/CSI. It reports near-real-time access to opportunities, quotes, orders, shipping, invoicing and receivables, improving global business visibility.
The study describes a 10-week project with its own scope. It is customer evidence, not a promise that every implementation has the same duration, configuration or result.
Bring these items to your implementation discussion
Discuss your Salesforce–Infor integration with Endowance to confirm fit and the agreed standard scope. For distribution requirements, use the separate CSD/SX.e guide.
Your CSI/SyteLine version, deployment, companies and sites.
The first workflow and the people who own it.
Sample customer, item, quote and order records.
Required XML BODs, current connection arrangements and known exceptions.
Desired launch date, acceptance criteria and additional requirements.
Your CSI/SyteLine implementation questions, answered.
Does this CSI/SyteLine guide use XML BOD messages?
Yes. The Duet360 CSI/SyteLine integration described here uses XML Business Object Documents. Confirm the exact BODs, verbs, required elements, message route and acknowledgement behavior for the installed release and agreed workflow.
Does Salesforce–CSI integration require MCP?
No. Model Context Protocol is a separate consideration when a compatible AI client needs access to tools or context. It is not required for the XML BOD business-process integration described here.
Can we start with order visibility before enabling order submission?
Yes, a scoped visibility workflow can be a focused first phase. Agree the source records, permissions and refresh behavior. Assess order submission, approvals and permitted ERP actions separately.
Is standard implementation a fixed fee?
Yes. The fixed implementation fee applies to agreed out-of-the-box functionality. Confirm the included processes, BODs, mappings and exclusions in the proposal. Additional requirements and third-party licensing are separate scoping items.
Can the process be adapted to our business?
Yes. Duet360 provides full process flexibility. Use the prebuilt processes as a foundation, then agree the changes, available ERP operations, approvals and implementation work required for your workflow.
How do we investigate an order that did not complete?
Authorized users can review Duet360 logs in Salesforce and use its Data Quality component as part of the operating process. Match the Salesforce record, message reference and ERP status. Confirm whether CSI accepted the request before reprocessing.
Comments