Technology 04
AiESL middleware and APIs connect shelf labels, footfall analytics, ERP, POS, and inventory systems — so price changes and store insights move without manual exports.
Capabilities
System Architecture
The base station carries edge computing — so stores keep operating even offline, while the cloud platform manages every store centrally.
Data flow
The platform is middleware: it does not replace your ERP or POS, it moves their data to the shelf and brings store data back.
| Data | Source | Destination | Direction |
|---|---|---|---|
| Prices and promotions | ERP or pricing system | Shelf labels via base stations | Out to stores |
| Product master data | ERP / PIM | Label templates | Out to stores |
| Stock state | Inventory system | Labels and store dashboards | Two-way |
| Label status | Labels via roll-call | Central platform and HQ reports | Back to HQ |
| Footfall and occupancy | Pyroglaux analytics | Central platform dashboard | Back to HQ |
| Templates and campaigns | HQ marketing | Store groups | Out to stores |
Integration path
Integration is planned before the pilot store, so price pushes work on day one.
Map ERP price, product and promotion fields to AiESL templates; agree on SKU and barcode keys.
Connect through the documented AiESL APIs; we confirm the exchange method and sync frequency for your ERP.
Set up stores, store groups and roles for HQ, regions and franchisees.
Run price changes end to end in one store, including offline operation on the base station.
Switch on scheduled pushes and roll-call checks; extend store by store.
Use cases
These are the workflows retail chains use the platform for most often.
One price change reaches every store in a group, with an audit trail of who changed what.
Role-based access separates what HQ, regions and franchisees are allowed to change.
The base-station business system keeps binding, refresh and roll-call working without the cloud.
Promotion templates go to selected store groups on a schedule.
Footfall and label status in one dashboard make store performance comparable.
AiESL acts as the entry point for other retail systems and custom workflows.
Integration checklist
Having these ready before the integration plan meeting usually saves a full round of questions.
ERP, POS, inventory and pricing systems in use, with versions and who supports each.
Where regular price, promotion price, unit price and validity dates live.
Which identifier links a product to its shelf position: SKU, barcode or both.
How many price changes a day per store, and at what times they are published.
Firewall, VPN and store-network policies the base stations must work within.
Who at HQ, in regions and in stores should be able to change what.
FAQ
No. AiESL is middleware between your ERP, POS and inventory systems and the shelf. Your ERP stays the system of record.
The base station runs its own business system on the local network, so staff can bind, refresh and roll-call labels while the cloud link is down.
Any ERP, POS or inventory system that can exchange data through APIs. We confirm the method during field mapping.
Yes. Store groups and role-based access separate HQ, regional and franchisee permissions.
A local backend handles server and network settings, key management and firmware upgrades for labels and base stations, while the cloud platform manages stores centrally.
The platform runs in more than 6,000 stores through the group's retail brands. Ask for a demo through Request a Quote.