CEO at Foxycom, Adobe Commerce Solution Architect (Belgrade, Serbia)
I have spent almost twenty years in software, more than fifteen of them with Magento and Adobe Commerce.
I started in 2008 as a PHP developer and software consultant in Belgrade. I came to Magento a few years later, while Magento 1 was still the standard, and I never really left it since. I moved from developer to senior developer, then to technical lead, and spent close to ten years as CTO of an e-commerce company before founding Foxycom in 2020, where I am CEO today.
Over those years I have worked on platforms for industrial B2B suppliers, subscription and media businesses, sports equipment retailers and international enterprise groups – first on-premises, later on Adobe Commerce Cloud. Most of them were not new builds. They were live platforms carrying years of business logic, large catalogs and integrations that were not allowed to fail.
My specialty is B2B: complex integrations, large data volumes, ERP systems such as SAP and Salesforce as the source of truth, and everything around performance and scalability. I like the projects where the standard Magento architecture is not enough and has to be extended, replaced, or moved outside the platform entirely.
Being CEO has not taken me away from the technical side. I still do the architecture and design myself, review code, and take on the problems nobody else wants to look at. That is the part of the work I enjoy the most.
Meet Magento Poland 2026 will be my first conference talk, so I chose to focus on something I have built and maintained rather than on theory.
Meet Magento Poland 2026
Scaling Magento to Support Over a Billion B2B Prices
B2B pricing can become one of the biggest scalability challenges in Magento when every customer has their own negotiated prices.
In this case study, I will show how we built a pricing architecture for an Adobe Commerce implementation with approximately 15,000 products and 6,500 business partners, where pricing was maintained in SAP ERP and the number of customer-specific price combinations grew to more than one billion.
Storing and processing this pricing data through Magento’s standard database and pricing mechanisms was not a practical option. In the original Adobe Commerce on-premises implementation, we moved the pricing data outside of Magento and built a dedicated Redis-based pricing layer. Magento retrieved the relevant prices at runtime while SAP remained the source of truth.
The architecture had to evolve again when the platform was later migrated to Adobe Commerce on cloud infrastructure. The original approach could not simply be reproduced within the constraints of the cloud environment, so we separated pricing further by introducing a dedicated pricing API service, allowing Commerce to consume customer-specific pricing without owning the complete pricing dataset itself.
During the session, I will walk through the architecture, how pricing data was synchronised from SAP, how Magento resolved prices for logged-in B2B customers, the role Redis played in keeping price lookups fast, and how the design changed during the cloud migration.
I will also cover the problems and trade-offs we encountered, what we would do differently today, and the architectural lessons that can be applied to other large-scale Adobe Commerce B2B implementations.