Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Order lines, refunds and the email each order was placed under reach Microsoft Power BI together, so a customer figure counts people rather than counting the addresses they happened to type in.
Lightspeed eCommerce records orders reliably and says very little about customers, because a guest checkout produces an order with an email address and no identity behind it. Reporting that in Microsoft Power BI gives a repeat-purchase rate that really measures how often somebody used the same address twice, and a first-time customer count containing people who have bought four times. Acquisition budgets get set on it anyway. Connecting Lightspeed eCommerce and Microsoft Power BI with the matching applied in transit fixes the input rather than the chart, so orders arrive already resolved to a customer.
DATA THAT FLOWS BETWEEN THEM
Orders
Order lines
Refunds
Customer emails
Shipping addresses
Discount codes
Lightspeed eCommerce orders are resolved to a customer before they reach Microsoft Power BI, so a count of people and a count of email addresses stop being quietly the same number.
Refunds arrive with the orders they reverse rather than as a separate feed, so revenue and customer value in Microsoft Power BI reflect what the business kept, not what it billed.
The rule that decides when two orders belong to one person lives in Alumio, so every report inherits one definition instead of each measure carrying its own copy of it.
Because the data is staged and reused, Microsoft Power BI refreshes without querying Lightspeed eCommerce repeatedly, which keeps reporting load off the shop during a trading peak.
Alumio reads Lightspeed eCommerce orders on the schedule you set, applies the rule that decides when two orders belong to one person, and delivers the result to Microsoft Power BI, so repeat purchase rate counts customers.
Refunds are read alongside the orders they relate to and delivered together, so a Microsoft Power BI view of customer value nets off what came back rather than showing a total that only accounting knows is wrong.
Discount codes travel with the order lines they applied to, so a Microsoft Power BI report can show what a promotion actually did to margin for the customers it reached rather than for everybody who ordered that week.
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.
A loyalty program is the addition that changes the numbers you already have rather than adding new ones. It is the one system that recognises a person across orders, which is precisely what Lightspeed eCommerce cannot supply, so connecting it corrects the customer figures in Microsoft Power BI instead of producing another chart nobody asked for. Alumio holds both connections, so the identity arrives with the order rather than being joined up afterwards.
Yes, and the matching happens before the data lands rather than inside the report. Alumio reads Lightspeed eCommerce orders and refunds on the schedule you set, applies the rule that decides when two orders belong to the same person, and delivers the result into the Microsoft Power BI model. Every report then counts customers the same way, because the definition sits in one place instead of in each measure.
No, and there is less to this than people expect. One rule decides what counts as the same Lightspeed eCommerce customer, and it is a setting in Alumio rather than logic in a Microsoft Power BI report: which field to match on, how to treat a changed address, what to do with a blank one. That replaces the copy of the same assumption living inside every measure somebody wrote.
It is measuring repeated email addresses rather than repeated customers, unless something resolved identity first. A Lightspeed eCommerce guest checkout produces an order with a contact address and no customer record behind it, so one person ordering from work and from home is two customers, while a household sharing an address is one. Deciding the matching rule and applying it before the data reaches Microsoft Power BI is what makes the figure mean what it says.
A number that moves for a matching reason is the failure here, and it presents as a marketing problem: if the rule stops resolving, repeat rate falls and a team spends a month discussing retention. Alumio monitors each Lightspeed eCommerce read in real time and logs what reached Microsoft Power BI, so a change that cannot be applied alerts immediately with the order and the reason. Retries run where configured and the previous figure keeps its timestamp, so nothing passes quietly as behaviour.
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)
