Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Orders leave JTL Software with the channel they arrived on attached, so Salesforce fills up with the customers a rep can actually call rather than with every buyer who ever checked out.
JTL Software records every order the same way whether it came from your own shop, a marketplace or a phone call, and only some of those leave you a customer worth a CRM record. Push all of them into Salesforce and the account list becomes a transaction log: thousands of one-time buyers, no way to see which accounts matter, and reps who stop trusting the pipeline because most of what is in it was never a relationship. Connecting JTL Software and Salesforce puts the channel to work as a filter, so what reaches the CRM is the part of the order book somebody can sell into.
DATA THAT FLOWS BETWEEN THEM
Sales orders
Order channels
Customer records
Order values
Delivery addresses
Account records
Each JTL Software order carries the channel it came from, so the rule deciding which orders become Salesforce accounts turns on how the customer arrived, not on order value.
Reps work an account list that holds relationships instead of transactions, which is the difference between a CRM somebody opens daily and one ignored after a quarter.
Order history reaches the Salesforce account, so a buyer who has quietly ordered four times through your own shop is one prospect worth calling, not four unrelated records.
Alumio connects to JTL Software through its available API, as it would any reachable system, so the channel and order detail travel without a nightly file anybody maintains.
Alumio reads each JTL Software order with the channel attached and creates a Salesforce account only where your rule says the order represents a relationship, so the CRM grows with customers rather than with transactions.
Repeat orders from the same buyer are matched to the existing Salesforce account, so somebody ordering steadily through your own shop appears as one account with a history instead of as a series of unconnected first-time sales.
Orders arriving through channels you have decided are not relationships stay in JTL Software and never create a Salesforce record, so the account list is never diluted by buyers a rep could not have contacted anyway.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
Which of these orders is actually a relationship is the question that decides the next connection too. A marketplace channel manager is the usual addition, because it is the system that knows which listing and which channel an order came through, and JTL Software records the order rather than the reason it exists. Alumio holds both connections and reuses the Salesforce account matching already configured, so the channel detail reaches the same record the order does.
The channel decides everything else, so it is read first. Alumio takes each JTL Software order with its channel, applies the rule you set for which channels create a Salesforce account, and writes the order value and history against the account it matched. Orders from excluded channels are read and left alone, which keeps the CRM proportionate to the part of the business somebody sells into.
No, and the rule that matters is a setting rather than a script. Which JTL Software channels create Salesforce accounts, which only update an existing one, and which are ignored entirely are choices in Alumio's interface, and they will change as the business adds a channel. Writing that in code means the sales team asks a developer every time the answer changes, which is how these connections stop being maintained.
No, and treating every order as one is what ruins a CRM. JTL Software records orders from your own shop, from marketplaces and from direct contact identically, but only some of those leave a customer you can contact again with any expectation of a reply. Using the channel on the order to decide which ones reach Salesforce keeps the account list something a rep can work rather than a second order book.
An account created for nobody is the failure worth catching, because a CRM full of them looks like growth. Alumio monitors each transfer in real time and logs the JTL Software order and the channel rule it applied, so an order Salesforce refuses, or one that matched the wrong account, raises an immediate alert with the reason. Retries run where configured and unresolved orders stay listed rather than defaulting into a new record, so nothing is created or dropped quietly.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
