Promotion, coupon and store systems for retail
Campaigns, coupons, omnichannel and traffic peaks at campaign launch: we know the rhythm of retail and build tools that let marketing teams set their own pace.
What we have built in this industry
What we know from this industry
What we often find
- Campaigns and coupons as a permanent backlog
- Monolithic content management
- Omnichannel across store, web and app
- Heavy load during campaign periods
- Handover to internal teams
What we make of it
- Self-service tools for marketing
- Headless CMS for all channels
- Scalable microservices
- Shorter time to market for campaigns
- Less dependence on service providers
When every marketing campaign becomes an engineering task
At the scale of a retail group, every couponing program and every campaign is a technical project. Without dedicated tools, everything ends up as a ticket in the developer backlog.
We build the systems that let marketing and sales work on their own: coupon and promotion platforms, dashboards, headless CMS integrations and the microservices behind them.
We work embedded in the client's teams and hand over solutions that the enterprise runs on its own.
The typical situation
Marketing managers want to plan, create and end campaigns themselves, without tying up engineering capacity for every change. At the same time, the enterprise is moving its content from a monolithic setup to a decoupled headless architecture, so frontend and content teams can work independently.
How we approach it
- One tool for coupons and promotions: a web dashboard built on React and MUI, with a GraphQL API and a microservice backend.
- End-to-end tests with Cypress and a clean CI setup, so the tool stays maintainable without us after handover.
- Handover with documentation and knowledge transfer to the internal teams.
- Engineering guidance and implementation during the move to a headless CMS on Contentful.
We worked for MediaMarktSaturn from 2020 to 2023. In 2023 the coupon tool was handed over to the internal teams. It has been running inside the group ever since, without our active involvement. That works because the codebase was designed for handover from the start.
Common questions from this industry
How can marketing create campaigns without a developer ticket?
With a dedicated tool. For MediaMarktSaturn we built a web dashboard where internal staff plan, create and end coupons and promotions. It is based on React and MUI, with a GraphQL API and a microservice backend. Marketing managers run their campaigns themselves. Not every change ties up engineering capacity, and campaigns no longer end up as tickets in the developer backlog.
Can internal teams run the tool themselves later?
Yes, we design for that from the start. We built the coupon tool for MediaMarktSaturn with end-to-end tests in Cypress and a clean CI setup. That test coverage is what keeps the tool maintainable without us after handover. The handover included documentation and knowledge transfer to the internal teams. Since the handover in 2023, the tool has kept running inside the group.
Do you support the move to a headless CMS?
Yes. At MediaMarktSaturn, alongside the coupon tool, the group-wide move from monolithic content management to a decoupled headless architecture was underway. The goal was for frontend and content teams to work independently of each other. We provided engineering guidance and helped implement the frontend integration with Contentful. Our contributions became part of the group's headless architecture.