The beacon.store platform provides a comfortable way to configure and setup of beacons during the lifecycle of an app. Developers must not go through an App-Review Process anymore, because updates of the shop beacon-infrastructure are done in realtime. In addition the platform enables a virtual attachment of any programable-web-capable device to act as an additonal remote device, triggered by beacon events. We created this to make the implementation and administration of beacons within a native app as easy as possible. Since beacons by design are not capable of any program-logic operations the platform virtually provides this logic-feature, by providing the possibilty to attach any kind of remote device(s) and message(s) to a beacon. This enables the receiving app not only to react to standard beacon triggered events (e.g.did-enter/did-exit-region), but also to process further information provided by the beacon.store platform (e.g.turn-on-additional-displays/installations,provide-user-data). Any App which is attached to the beacon.store platform is able to retrieve an updated list of currently active beacons for an environment. Beacons can be marked as active/inactive at any time and additional information can be attached to a beacon at any time. Our working scenario could be, that by entering a beacon region additional content (JSON/XML/CSV/Plain text) is delivered to any device (Arduino based device, Philips HUEs, an iPad-App, etc.) via the TCP-Server and processed. This enables the App to trigger any set of interaction within a shop environment. The Platform is a rails application which uses a Python-Based TCP-Server as message dispatcher. The Dispatcher just forwards messages of any kind, to remote devices. So developers can setup messages in the format which the can best process on their remote device. After test 2014 at the Mammut Store Frankfurt, Mammut Germany is planing roll-out the technology for all Stores and We will open source the Beacon.Store plattform.