Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Shops charge exactly what head office decided, because SAP pricing reaches the Lightspeed point of sale before it takes effect, and each trading day returns at line level ready for posting.
Head office decides pricing in SAP and the shop charges whatever the till last received. When those two drift, staff apply manual overrides, promotions run late or early, and the day's takings arrive as a total that finance cannot break down by product. Store stock is a separate guess, so the webshop sells items that were bought in a shop that morning. A SAP to Lightspeed POS integration through Alumio ties them together: product and price data reaches the till, trading returns as documents SAP can post, and one stock position covers every channel.
DATA THAT FLOWS BETWEEN THEM
Product records
Retail prices
Promotions
Store stock
Sales transactions
Payment types
Refunds
Prices and promotions reach the point of sale from SAP, so a shop charges what head office decided rather than applying overrides to correct a stale price list.
Store sales return to SAP at line level, so finance and merchandising can both see what actually sold rather than only how much the shop happened to take that day.
Store sales reduce the same position the webshop reads, so an item bought in a shop stops being sellable online before the two channels promise the same unit twice.
Adding a location becomes a configuration step rather than another manual routine, so expanding the estate does not add a daily reconciliation task for every new shop.
A price or promotion approved in SAP reaches the point of sale before it takes effect, so staff are not applying manual overrides at the till and customers are charged the figure the business actually intended.
When a store closes its day, the transactions are returned to SAP at line level split by payment type, so the trading day posts correctly and merchandising can see exactly which products moved in which location.
Store sales and receipts update the stock position the online channel reads, so a shop selling the last unit of a line removes it from the website rather than leaving a customer to order something that no longer exists.
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.
More can be connected, and the e-commerce platform is the obvious third, because a shared stock position only pays off when every channel reads it. Alumio keeps SAP as the single source and applies rules per channel, so a store, a webshop and a marketplace can all sell from one position without any of them overselling it.
Yes. Alumio delivers product, price and promotion data from SAP to the point of sale on change or on a schedule, and returns transactions the other way. Alumio lists connector packages across the Lightspeed point-of-sale family, so confirm which product your estate runs before the flows are built, since the retail and restaurant products differ.
Product mapping, price rules, location mapping and transaction posting are configured in the Alumio interface, replacing the manual price updates and daily totalling that retail estates usually run on. SAP landscapes carry business-specific pricing configuration, so the Code Transformer covers a promotion or tender rule that mapping alone cannot describe.
Line-level transactions split by payment type rather than a single takings figure, which is the difference between reconcilable and merely accurate. A total tells finance what came in; lines tell merchandising what sold and let the bank reconciliation match card settlement separately from cash. Alumio returns both, coded to the store, so each question is answerable from the ledger.
The till keeps trading on its last valid price list and no day is posted twice. Alumio records each message with its content, watches both connections in real time, and notifies the team as soon as one is refused, naming the store and the reason returned. Unattended retries clear transient faults, and an unposted day is held in the queue rather than going missing.
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)
