ACE to ELERA
ACE to ELERA is a lightweight bridge for retailers moving from Toshiba ACE to the ELERA Commerce Platform. It keeps existing ADDMI maintenance flows working while ELERA catalogs, price lists, change plans, and node assignments come online.
The bridge speaks both sides natively: binary ACE item maintenance and item files on one side, ELERA REST APIs and event-driven change plans on the other.
->
<-
The bridge is designed around the practical reality that ACE and ELERA often run side by side for months. These workflows keep item data moving without duplicate entry or manual reconciliation.
Existing EAMMAINT files can be dropped into watched inbox folders or uploaded through the web UI, then translated into ELERA catalog and price list operations.
Bulk-load a store's ACE item file into ELERA to seed a new node with current catalog and price data before or during cutover.
Executed ELERA change plans can be translated back into binary EAMMAINT files for stores that are still running ACE.
ACE maintenance records and ELERA change plans are mapped into the native operation expected by the receiving platform.
| ADDMI input | ELERA action |
|---|---|
| Full item record | Create or update catalog item and price record |
| Price segment | Update price list record |
| Description segment | Update catalog display name |
| Department segment | Update item group assignment |
| Delete record | Deactivate price record |
| ELERA change | ACE output |
|---|---|
| Item added to catalog | Full item record in the store's configured format |
| Item removed from catalog | Delete record |
| Price changed | PINFO maintenance segment |
| Display name changed | ItemName maintenance segment |
| Department changed | Department maintenance segment |
Each ACE store can keep its own item record format, key length, and ELERA node mapping. The export pipeline writes byte-compatible EAMMAINT files for the stores that still need ACE maintenance delivery.
The built-in web interface gives support teams a dashboard, guided imports, ADDMI inspection, watcher status, file metrics, and manual ELERA export triggers.
The bridge is built as a Docker-deployable service with configurable storage and broker backends.
docker compose up -dRuntime configuration is handled through environment variables or YAML, so the same bridge can run in local, on-premise, or cloud-oriented deployments.
Use local filesystem folders, Azure Blob Storage, or SFTP for inbox and outbox file handling.
Listen to ELERA change-plan events through RabbitMQ for on-premise environments or Azure Service Bus for Azure-hosted deployments.
Map ACE store numbers to ELERA node names with per-store record length, key length, enabled status, and description fields.
REDList can help you keep item maintenance, catalog setup, store routing, and change-plan export aligned while both platforms are active.