# Retter — Full Site Content > Retter designs, builds, integrates and operates enterprise platforms: commerce, loyalty, backoffice, integrations and cloud infrastructure, with AI put to work inside them. We replace legacy platforms for brands such as Starbucks, A101, CarrefourSA and Costa Coffee, connect them to the systems the business already runs, and stay responsible for operating and improving them. Our work spans retail, grocery, food service, airports and insurance across Türkiye and the Gulf. Backend engineering is Retter’s core strength: replacing legacy commerce and loyalty platforms (SAP Hybris, Oracle Commerce Cloud, closed SaaS vendors) on AWS serverless, integrating banks, airlines, stores and delivery partners, and operating the result with the same engineering team after launch. Customers include Starbucks, Gratis, CarrefourSA, A101, MMI, PAUL (Azadea Group), Costa Coffee, Pret A Manger, Shake Shack, Spinneys Abu Dhabi, Emirates Leisure Retail, istegelsin, Lululemon, Unifree, İstanbul Sabiha Gökçen Airport and Medisa Sigorta. A detailed specification is not required to start: scope, integrations and launch requirements are agreed with the customer, with experienced people handling architecture, validation, compliance and ongoing operation. Build across business domains. Grocery, retail, F&B, loyalty and commerce show areas of deep experience, not the limits of the offering. Customer evidence: each published case study describes a specific engagement. Historical platform results are not forecasts for new projects or measured AI performance. Contact: hello@retter.io or https://www.retter.io/contact. Offices in İstanbul, Düzce and Dubai. ## About Retter Source: https://www.retter.io/about Retter designs, builds, integrates and operates enterprise platforms: commerce, loyalty, backoffice, integrations and cloud infrastructure, with AI put to work inside them. We replace legacy platforms for brands such as Starbucks, A101, CarrefourSA and Costa Coffee, connect them to the systems the business already runs, and stay responsible for operating and improving them. Our work spans retail, grocery, food service, airports and insurance across Türkiye and the Gulf. ### Frequently asked questions Source: https://www.retter.io/ **Q: What does Retter build?** Retter designs, builds, integrates and operates enterprise platforms: commerce, loyalty, backoffice, integrations and cloud infrastructure, with AI put to work inside them. We replace legacy platforms for brands such as Starbucks, A101, CarrefourSA and Costa Coffee, connect them to the systems the business already runs, and stay responsible for operating and improving them. Our work spans retail, grocery, food service, airports and insurance across Türkiye and the Gulf. **Q: Do we need a detailed plan to start?** No. Tell us what you want people to be able to do. We help turn that into a plan, show you working software as we build it and agree what needs to be checked before launch. **Q: Why work with Retter?** Starbucks, A101, CarrefourSA, Gratis and Emirates Leisure Retail run on platforms we built and still operate. We take on the whole system, from the customer app to the backoffice, integrations and cloud infrastructure, including replacing legacy platforms such as SAP Hybris and closed SaaS vendors. **Q: Can you build tools for our team?** Yes. We build tools to manage orders, help customers, prepare reports and control who can see or change information. Making the team’s work easier is a large part of what we do. **Q: Can you build an online shop or rewards programme?** Yes. We build shops, ordering apps and rewards that work on the website, in the app and in store. We can also add AI to help prepare offers, check products or answer questions about sales. **Q: Can we keep the tools we already use?** Yes. We start by looking at what works and what should change. Often we can connect your existing tools or add something alongside them, without replacing everything. **Q: What happens after launch?** The same team stays involved. Before launch, we agree who handles support, how we spot problems and how often improvements will go live. We then keep the software working as your business grows and changes. ## How we build Source: https://www.retter.io/approach 1. Tell us what needs to change. Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. Deliverable: A clear plan, price and timeline. 2. Try it as we build it. Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. Deliverable: Something you can use and give feedback on. 3. Get ready for real customers. We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. Deliverable: Tested software and a plan for launch and support. 4. Launch. Learn. Keep improving. The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Deliverable: A live platform and the team that operates it. **Q: Do we need a detailed plan before we start?** No. Tell us what you want to make easier and who it is for. We help work out the details with you, then agree what the first version should do and how we will test it. **Q: What makes Retter different?** We take responsibility for the complete system: customer experiences, payments, stock, business operations, integrations and cloud infrastructure. The same engineers stay to operate it, fix problems and release improvements after launch. **Q: How long will our project take?** That depends on what the first version needs to do, which tools it connects to and whether information needs to be moved. We agree a timeline for your project. Trying an early version and opening it to all your customers are separate steps. **Q: Can we keep the software we already use?** Yes. We can connect your existing tools, improve one part of the job or build something new alongside them. First, we check how those tools can share information and what you want to achieve. ## Solutions ### Apps & business tools Source: https://www.retter.io/solutions/custom-software-development Customer platforms and the operational systems behind them, built for enterprise scale. Tell us what the business needs to do. We build the platform around it, connect it to the systems you already run and stay to operate it. Custom software is an app or tool built for the way your business works. It could help customers place an order, partners track a request or staff finish a task without another spreadsheet. We work out the details with you, show you working software as it takes shape and check it with the people who will use it. After launch, the same team keeps it working and improving. Capabilities: - Apps for customers and partners: Let people order, book, ask for help or check progress without calling your team. - Tools for your team: Give staff one place to manage requests, check information and approve the next step. - Tools that work together: Connect the new app to your orders, payments and customer information so people do not have to enter things twice. #### What could you build for us? An app for customers, a staff tool, a partner website or a way to manage a whole part of your business. We begin with what people need to do and the information they need to do it. The examples on this site show our experience. Your idea can be different. If a product you already use does part of the job well, we can work out how to connect it to the new software. #### How will we know it is right? You try the software as we build it. A working order, booking or report makes it easier to spot what is missing than a long document does. We use your team’s feedback to improve the next version. We also check who can see information, how the app connects to other tools and what happens when something goes wrong. Together we agree what must work before it goes live. #### Who looks after it after launch? We agree support and responsibilities before launch. That includes how to spot problems, who fixes them and how your team asks for changes. Retter can continue to develop and look after the software as your business changes. Our customer stories show how that responsibility extends beyond the app to payments, rewards and everyday staff tools. Illustrative brief: Give our partners one place to send requests and see what happens next. We would agree who can use it, what each request needs, who checks it and how people receive updates. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: PAUL PAUL demonstrates a connected customer-platform engagement. Its published results describe that project, not a promise for every custom build. - 9 countries - Multi channels - End-to-end platform FAQ: **Q: Are you limited to shops and rewards apps?** No. Our work also includes airports, insurance and tools used by business teams. Tell us what you want to make easier, even if it is different from the examples here. **Q: Do we need a technical specification?** No. Start with what you want to achieve and who will use it. We help work out the details and agree the first version with you. **Q: How do you work out the cost and timing?** We look at what the first version should do, what it needs to connect to and what information needs to be moved. Then we agree a plan for your project. ### Customer rewards Source: https://www.retter.io/solutions/agentic-loyalty-engagement Give customers a reason to come back, wherever they shop. Give customers rewards they can earn and use in your shops, on your website and in your app. Make it easier for your team to prepare the right offer. A rewards programme helps customers get more from shopping with you. We build the software that keeps track of membership, purchases, points and offers so they work together. We can start a new programme, improve the one you have or help your team prepare offers with AI. Our experience includes rewards and payment apps for Starbucks and Emirates Leisure Retail. Capabilities: - Membership and rewards: Keep track of who joined, what they earned and what they can use on their next visit. - The same rewards everywhere: Connect purchases and rewards in the shop, on the website and in the app. - Help preparing offers: Let AI suggest an audience and prepare an offer for your team to check. #### What makes a rewards programme work? Customers should understand what they earn and how to use it. Staff should be able to find a member, explain a balance and help if something does not look right. We work through the rules with your team: which purchases count, when rewards expire and what happens after a refund. Then we make sure the app, website and shop agree. #### Can you improve our existing programme? Yes. We start by looking at your current members, points, offers and the tools that hold that information. You may need a new app, a connection to the shop tills or a better way to manage offers. If information needs to move, we plan the change and check the results with your team. Customers should know where their rewards are and what they can do with them. #### Where can AI help? AI can help find a group of customers, prepare an offer or explain how the last campaign performed. Your team decides which information it may use and what needs approval. The rewards programme can work without AI. We add it where it makes a useful task easier and keep the rules clear for staff and customers. Illustrative brief: Let customers earn and spend their rewards in our shops and online. We would check how purchases are recorded, agree the rewards rules and connect them to the places where your customers shop. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: Starbucks The Starbucks story documents loyalty and platform delivery across three countries. It is evidence of infrastructure experience, not a claim that AI delivered those historical results. - 50K+ daily transactions - 65% lower cloud cost - 10x faster development FAQ: **Q: Can rewards work both in store and online?** Yes, when the shop and online tools can share the information they need. We check those connections before agreeing the build. **Q: Can we keep existing members and points?** We review the records available, plan how to move or connect them and check the balances with your team. **Q: Do we have to use AI?** No. Membership, points and rewards are useful on their own. AI can be added to suitable jobs such as preparing offers or reports. ### Online shops & ordering Source: https://www.retter.io/solutions/agentic-e-commerce Make browsing, buying and getting an order easy. An online shop or ordering app that fits your customers, products and the team behind each delivery. An online shop needs more than a checkout. Customers need the right product information, accurate stock and a clear way to pay and receive their order. Your team needs the tools to make all of that happen. We build the website or app and connect it to your product, payment and delivery tools. We can also improve an existing shop, add customer rewards or help staff check new product listings. Capabilities: - Websites and shopping apps: Help customers browse products, place orders, pay and check what happens next. - Orders that reach the right team: Connect the shop to stock, payments and the people preparing each delivery. - Help with product listings: Use AI to prepare product information or check for missing details before your team publishes it. #### What happens beyond the checkout? A customer needs to know what is available, what it costs and when it will arrive. After paying, they need updates and a clear way to ask for help or return something. We build those steps around the way your team works. Orders, stock, payments and delivery information need to stay in step so staff can make the promises customers see. #### Can you work with our current shop? Yes. We can improve a part of the shopping experience, add an app or connect an existing store to better staff tools. We first check what your current software allows us to connect. When a bigger move is needed, we plan around the live business. Product information, customer records, payments and delivery rules all need to be checked before customers use the new shop. #### How can AI make the work easier? For a marketplace, AI could check whether a seller has supplied the required product details and prepare a request for anything missing. Your team can review the suggestion before sending it. Other useful tasks include helping customers find products or preparing offers. We start with a clear job, the right information and the decisions you want a person to check. Illustrative brief: Let our customers order online and choose delivery or collection. We would agree the shopping steps, check stock and payment connections, and make sure each order reaches the team preparing it. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: PAUL PAUL provides a published example of ordering, loyalty and engagement across nine countries. This is delivery experience; outcomes for a new commerce project depend on its scope. - 9 countries - Multi channels - End-to-end platform FAQ: **Q: Can you build both the app and website?** Yes. We can build both around shared product, order and customer information, with an experience suited to each screen. **Q: Can we keep our payment and delivery providers?** Often, yes. We check how those providers let us connect and what the checkout and delivery process needs to do. **Q: How quickly can the shop launch?** It depends on the products, payments, delivery choices and information that needs to move. We agree a timeline for your first version and test it before opening to customers. ### Connect your business tools Source: https://www.retter.io/solutions/digital-transformation Keep information up to date and stop doing the same job twice. Make your existing tools work together, replace a slow task or build a better way for your team to get things done. When orders, stock and customer details live in separate tools, people spend time moving information between them. We help those tools share the information they need. We start with the job that causes the most trouble. That might mean connecting an app to your stock system, making reports easier to prepare or replacing an old tool in manageable steps. Capabilities: - Connect the tools you use: Let orders, stock and customer information move between the right places without copying it by hand. - Replace a slow manual job: Turn emails and spreadsheets into one clear place to make requests, track progress and approve work. - Improve older software: Plan a manageable move from tools that are hard to change, while keeping the business working. #### Where should we start? Start with the task that wastes time or causes mistakes. An order entered twice, a stock count that arrives too late or a report someone spends every Monday preparing is a useful place to look. We follow the job with the people doing it. That shows which information is needed, who checks it and which tools need to work together. #### Will we need to replace everything? Usually the first question is what should stay. We can connect existing tools, add a missing step or improve one part of the work before tackling the next. If an older tool cannot support what the business needs, we plan a move in stages where possible. We agree how information will be checked and how staff will learn the new way of working. #### What does a successful change look like? We agree what should improve before building: less time spent on a task, fewer repeated entries or faster answers for customers. Your team then tries the new way of working. After launch, we keep an eye on what happens and make improvements. Our Emirates Leisure Retail story shows how customer details, rewards and payments can be brought together across many locations. Illustrative brief: Stop our team copying orders from the website into a spreadsheet. We would follow an order through the business, find which information each person needs and agree how the tools should share it. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: Emirates Leisure Retail Emirates Leisure Retail documents CRM, loyalty and wallet modernization across 300+ outlets. Its cost and delivery results apply to that engagement. - 300+ F&B outlets - 70% lower cost - 10x faster development FAQ: **Q: Can you connect software from different suppliers?** We first check what each supplier lets us connect to. That determines which information can be shared and how the connection should work. **Q: Can the business keep running during the change?** We plan the work around the live business, including testing, timing and a way to recover if a step fails. The right approach depends on the systems involved. **Q: Does the project need AI?** No. Sometimes a clear staff tool or a reliable connection between systems is the improvement you need. We add AI where it helps a specific task. ### AI for everyday work Source: https://www.retter.io/solutions/agentic-backend-systems Let AI prepare, check and organise. Keep your team in charge. Check product listings, prepare customer offers and answer questions about your business. You decide what AI can do and when it needs your approval. An AI agent is software that can carry out a task using information and tools you give it. For example, it could check whether a product listing has the required details and prepare a request for anything missing. We choose a useful first task with your team, connect the information it needs and set clear limits. Your team can review the work, approve the next step and see a record of what happened. Capabilities: - Prepare work for your team: Draft offers, organise requests or check listings so people can spend more time on the decisions. - Use your business information: Connect the records and tools the task needs, with limits on what AI can see and change. - Keep people in charge: Ask for approval at the right moments, set a spending limit and keep a record of what happened. #### Which job should AI do first? Choose a repeated task with a clear result. For example, a product listing either has the required information or needs a follow-up. A campaign starts with a group of customers and an offer for someone to review. We look at the information available and what a good result means. A small, useful first job makes it easier to test the work and decide where AI can help next. #### How do we stay in control? You decide which information the AI can use, which tools it may access and which actions need a person’s approval. You can also set spending and usage limits. We keep a record of the information used, the steps taken and the approvals given. If the AI cannot complete a task reliably, there should be a clear way to ask a person for help. #### Can AI work with what we already use? We check how your existing tools can share information and accept updates. The AI may be able to work alongside them, so the team can keep using familiar systems. Before launch, we try normal requests, missing information and mistakes with your team. We agree what should happen in each case and who will look after the task once people depend on it. Illustrative brief: Check new product listings and tell the seller what is missing. We would agree what a listing needs, show your team the proposed checks and ask for approval before contacting a seller. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: Starbucks The Starbucks case study demonstrates Retter’s production-platform experience. It does not report performance results for the illustrative agents described here. - 50K+ daily transactions - 65% lower cloud cost - 10x faster development FAQ: **Q: Will AI make every decision?** No. You choose the work it may do and the points where someone must check or approve the result. **Q: Can AI change or send things without asking?** Only within the permissions and limits agreed for that job. We design approval steps for the actions your team wants to control. **Q: Are the examples on this website live?** No. They use made-up information to show the steps. Nothing is sent, published or changed in a customer’s business. ### Reliable cloud software Source: https://www.retter.io/solutions/serverless-development Keep your apps working as more people use them. Build software that can handle changing demand, with experience from customer apps, rewards and payments running on Amazon’s cloud services. Cloud services provide the computing and storage behind an app. Amazon Web Services, or AWS, is one provider. Retter has years of experience building and looking after business software using these services. Serverless means the cloud provider manages much of the underlying computing capacity. Your application still needs to be designed, secured, tested and supported. We look after those details with your team. Capabilities: - Prepare for changing demand: Plan how the app handles more visitors, orders or payments as the business grows. - Keep information moving: Make connections between your tools dependable, including when one is slow or unavailable. - Look after access and costs: Control who can use the software, spot problems and understand what the service costs to run. #### When is this useful? An app may be quiet one day and busy the next. Cloud services can help it use more computing capacity when demand rises and less when it falls. We look at the app’s needs, the tools it depends on and the cost of running the whole service. A particular cloud setup is only useful if it fits the business. #### What still needs looking after? The app must protect customer information, handle payments correctly and recover when a connected service has a problem. Someone needs to spot issues and know how to fix them. Retter plans those responsibilities with your team. We test busy periods and failure cases, agree who has access and make the running costs visible. #### Can our existing app move to the cloud? We first look at the app, its information and the other tools it connects to. Sometimes one part can move first; other projects need a wider change. Our Starbucks and Emirates Leisure Retail stories describe specific projects and their results. For your business, we agree what should improve and check the result against your own starting point. Illustrative brief: Keep our ordering app working when a campaign brings more customers. We would look at busy periods, payments and other connected tools, then agree what to change and how to test it. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: Emirates Leisure Retail Emirates Leisure Retail is a documented AWS modernization engagement. Its reported savings are project-specific and are not a forecast for another workload. - 300+ F&B outlets - 70% lower cost - 10x faster development FAQ: **Q: Does serverless mean there is nothing to look after?** No. The cloud provider handles much of the computing capacity. The app still needs someone to manage access, check that it works, fix problems and make changes. **Q: Will moving to the cloud always save money?** No. Cost depends on how the app is used and built. We review the current costs and expected demand before recommending a change. **Q: Can you help with an app already using AWS?** Yes. We can review a problem, improve a connection or plan a larger change. We start with what is not working well for the business. ### Reports & business answers Source: https://www.retter.io/solutions/agentic-reporting-analytics Ask a question. See the numbers and how they were worked out. Turn information from across your business into useful reports. Add AI so your team can ask questions in everyday language. Your team should be able to find out how a campaign performed, what sold last week or where an order is stuck. We build reports and tools that bring the right information together. With AI, people can ask a question instead of building a report by hand. We make sure the answer shows where the information came from, how the numbers were counted and what the person is allowed to see. Capabilities: - Reports people can use: Put useful figures in one place so the team can see what needs attention. - Questions in everyday language: Let people ask about sales, offers or orders and get an answer with the figures behind it. - Clear numbers and access: Agree what each figure means and make sure people only see information they are allowed to use. #### What makes an answer trustworthy? People need to know where the information came from, what period it covers and how the figures were counted. For example, sales before refunds are different from sales after refunds. We agree those definitions with your team. A useful report should let someone check the calculation and understand what the numbers do and do not show. #### Can this work with our current reports? Yes. We can add a clearer report, connect another source of information or put a question-and-answer tool alongside what you already use. We first check which records are available, how often they change and who may see them. Those details matter more than how fluent an AI answer sounds. #### How do we test the answers? Your team provides questions and reports it already understands. We compare the new answers with those examples and check missing information, unusual cases and differences in wording. After launch, we use real questions to improve the reports. A new figure or filter becomes a change the team can review and understand. Illustrative brief: How did last week’s campaign perform? We would agree which sales belong in the report, where those records come from and who is allowed to see them. How an engagement runs: 1. Tell us what needs to change.: Who is it for? What should be easier? We work out what to build first, which tools it needs to connect to and when it can be ready. 2. Try it as we build it.: Your team gets working software to try. See how an order, a payment or a daily task will work, then tell us what to change. 3. Get ready for real customers.: We check that it works with your other tools, protects the right information and can handle busy days. We agree who will help if something goes wrong. 4. Launch. Learn. Keep improving.: The people who built it stay involved. We keep it running, fix problems and add what your customers and team need next. Related experience: Starbucks The Starbucks story illustrates the scale and integration of a Retter-built business platform. It is not an analytics accuracy benchmark or a measured AI reporting case study. - 50K+ daily transactions - 65% lower cloud cost - 10x faster development FAQ: **Q: Do we need to replace our reporting tools?** No. We can work alongside them, connect additional information or build a simpler way to get the answers your team needs. **Q: Can everyone see every report?** No. We agree who can see which information and apply those permissions to the reports and AI answers. **Q: Can you build reports without AI?** Yes. A clear report or a scheduled update may be all you need. AI is useful when it makes asking and following up on questions easier. ## Industries ### Grocery & delivery Source: https://www.retter.io/industries/grocery-quick-commerce Brands: istegelsin · CarrefourSA · A101 · Spinneys Show what is in stock, suggest replacements and get orders to the door. Build grocery commerce, internal tools and connected workflows with a team that knows what happens between the basket and the doorstep. Grocery software needs to connect the customer experience to a changing physical operation. Availability can move while an order is being picked; a substitution affects the basket; delivery capacity changes the promise a store can make. These details shape the application and the systems behind it. Retter brings grocery and quick commerce experience to customer apps, ordering platforms, operational tools and integrations. A new tool can start from a short description of the problem. Our role is to understand the business rules and connections that make it useful in the daily operation, as we do today for istegelsin, CarrefourSA, A101 and Spinneys. #### Start with the workflow that needs attention. The first project does not have to replace the entire grocery platform. It could make substitutions easier to manage, connect a stock feed, improve a customer journey or give store teams a shared view of exceptions. We identify the people involved and the systems that own the relevant records before defining the release. For a wider platform build, the same questions extend across catalog, price, payment, picking and delivery. We work through how those systems exchange information and how the operation responds when information is delayed or incomplete. Testing should include the difficult everyday cases, not only a successful order. #### Use AI where the operation can evaluate it. AI can help interpret a shopping request, prepare a response or summarize operational information. The task needs appropriate product and order data, clear limits and a way for the team to check the result. Stock commitments, payment changes and customer communication require explicit rules about who or what can act. Our industry knowledge helps identify those boundaries. The goal is to improve a real workflow while preserving accountability for the customer promise. A conversational interface is one possibility; a reliable integration or a better staff tool may be the more useful first step. Challenges Retter solves: - Availability changes between browsing and picking. → Define where stock is owned, when it is reserved and how unavailable items or substitutions are communicated to the customer. - A delivery promise depends on more than a postcode. → Connect store selection, service areas, capacity and order status so the application reflects the fulfillment model. - Store teams handle exceptions across disconnected tools. → Create focused operational views for picking issues, missing information and customer decisions, with clear ownership of the next action. Published project results: istegelsin (project-specific) - Millions weekly shoppers - Real-time inventory - 100k/s request capacity FAQ: **Q: Can Retter build a grocery ordering application?** Yes. Scope can include the customer app, catalog and availability connections, order handling and operational tools. We define store, picking and delivery requirements with your team. **Q: Can we improve one part of our existing grocery platform?** Yes. A contained workflow or integration can be a practical starting point. Retter assesses the available interfaces and system ownership before agreeing the implementation. **Q: What grocery experience can we review?** The customer directory includes istegelsin, Carrefour and A101. The published istegelsin story describes a grocery platform engagement. The depth of published detail varies by customer; our team can discuss relevant scope. ### Shops & online stores Source: https://www.retter.io/industries/marketplace-omnichannel Brands: Gratis · MMI · Lululemon · Unifree Keep products, orders and rewards connected in the shop, on the website and in the app. Bring stores, digital channels and business systems together, with practical experience in retail, marketplaces and omnichannel operations. Retail software connects what a customer sees with the information and processes behind a purchase. A product, price, order or return may move between online, in-store and back-office systems. A useful digital experience depends on those connections being understandable and consistent. Retter builds customer applications, commerce platforms and internal tools, and modernizes the systems already in place. Our retail experience helps shape the details, from the weekly release cadence and audit-driven backoffice work we run for Gratis to the hybrid on-premises and cloud backend behind Unifree’s duty-free limits. A new build or an iteration can start from a simple brief, whether the need is a full platform or one operational improvement. #### Build around your retail model. A retailer with stores, a direct-to-consumer brand and a marketplace may share a checkout pattern but have different operating needs. We begin with channels, users and the order lifecycle, then identify how catalog, payment, fulfillment and customer-service systems interact. The first release might improve an account experience, expose loyalty in a new channel, connect order information or give staff a better tool. A larger commerce build can follow the same approach in stages. The scope is driven by the business problem and the systems already working well. #### Modernize without losing the operational detail. Changes to commerce affect more than the storefront. Customer identity, promotions, consent, stock and returns each have owners and rules. Retter works with those teams to agree how information moves and what a successful change looks like before rollout. AI can support product discovery, staff assistance or reporting when the underlying information is suitable. We define what it can access, which changes it can propose and when a person must review. The result should make work easier while remaining traceable to the data and decisions behind it. Challenges Retter solves: - Online and store information drift apart. → Define the authoritative sources for stock, price and customer records, then build connections with clear update and exception behavior. - A return affects several systems at once. → Map how order status, payments, inventory and rewards change so teams can follow the transaction across channels. - Marketplace sellers need visibility and guidance. → Build onboarding, listing approval and operational tools around the marketplace model, with explicit responsibilities and permissions. Published project results: MMI (project-specific) - Winner RetailME 2025 - One backend, every brand - Omnichannel commerce FAQ: **Q: Can Retter connect online and in-store experiences?** Yes. The integration scope depends on the available POS, commerce, customer and inventory interfaces. We establish data ownership and transaction flows with the teams responsible for each system. **Q: Do you build marketplaces as well as stores?** Yes. Seller onboarding, product approval, order workflows and supporting tools can be part of a marketplace engagement. We scope them around the commercial and operating model. **Q: Do we have to rebuild our storefront?** No. An integration, staff application or focused workflow may address the need. We assess the existing platform and agree whether extending or replacing a component is appropriate. ### Restaurants & cafés Source: https://www.retter.io/industries/qsr-food-beverage Brands: Starbucks · PAUL · Costa Coffee · Pret A Manger · Shake Shack Make ordering, paying and earning rewards easy, wherever your customers visit. Build ordering, loyalty and operational systems with experience from coffee, bakery and multi-brand food service businesses. Food and beverage software has to reflect the location taking the order. Menus, modifiers, hours, availability and fulfillment choices can differ between branches and markets. Customers also expect payments and rewards to work across the channels they use. Retter has delivered customer platforms for Starbucks, PAUL and Emirates Leisure Retail. That experience informs ordering applications, loyalty infrastructure, wallets and business integrations. For Costa Coffee, Pret A Manger and Shake Shack the work spans loyalty apps, catering web and backoffice. We also build internal tools and new workflows, starting from the problem your team needs to solve. #### Connect the experience to the store. An order needs to reach the correct operation with enough information to fulfill it. That includes product choices, payment state, pickup or delivery details and any updates after submission. We map those events with the business and define how the app and store systems stay informed. A multi-market platform also needs a deliberate balance between shared capabilities and local rules. Language, payment methods, customer programs and partners may vary. Our work with multi-country platforms helps frame those decisions before implementation hardens them into separate systems. #### Make customer engagement useful to the team. Loyalty and CRM tools should help teams understand customers and run programs with clear rules. A useful campaign workflow connects audience information, consent, reward eligibility and approval. Reporting then needs agreed definitions so that teams can compare results consistently. AI can help prepare a campaign or explore performance, while the surrounding software enforces access and action boundaries. The same development approach can support a new operational tool, partner portal or application outside ordering and loyalty. The published projects demonstrate our experience, while your brief determines what we build next. Challenges Retter solves: - Each location has its own operating conditions. → Model branch hours, menus, fulfillment options and availability so that the ordering experience follows the actual operation. - Rewards and payments cross channels and markets. → Connect member identity, transaction events and program rules while allowing the local differences the business requires. - Campaign ideas take too many handoffs to implement. → Give teams tools to prepare and review offers against audience, consent and budget rules, with an explicit approval step. Published project results: Starbucks (project-specific) - 50K+ daily transactions - 65% lower cloud cost - 10x faster development FAQ: **Q: Can Retter build mobile ordering and loyalty together?** Yes. They can share customer identity and transaction events while connecting to store, payment and customer systems. Retter scopes the journey and integrations with your team. **Q: Can one platform support multiple brands or countries?** Yes, with shared and local rules designed explicitly. Our published Starbucks and PAUL stories describe multi-country engagements; Emirates Leisure Retail covers CRM, loyalty and wallet modernization across 300+ outlets. **Q: Can you build a tool for our operations team?** Yes. Retter can build internal applications and workflow tools quickly. Start with the task, the people involved and the information they need, even when the requirement is outside customer ordering or loyalty. ## Customers ### Starbucks Source: https://www.retter.io/work/starbucks Sector: Food & beverage · Markets: Türkiye, Kazakhstan & Azerbaijan Scope: Mobile app · CRM · Loyalty · Backend · Infrastructure A connected digital experience for Starbucks, bringing the customer app, CRM, loyalty, backend and infrastructure into one platform that serves three markets. - Customer app: The mobile experience through which customers interact with the brand. - CRM: The customer data and business workflows behind the experience. - Loyalty: The rewards and engagement systems that connect customers to the business. - Backend & integrations: The services and connections that bring the platform together, including local payment partners in each market. - Infrastructure: The AWS foundation for deployment and ongoing operation. ### Gratis Source: https://www.retter.io/work/gratis Sector: Retail & commerce · Markets: Türkiye Scope: Commerce · App & web · Backoffice · Compliance · Store integrations Retter builds and runs the platform behind Gratis: the web store and app, the backoffice the business works in, and the backend that connects them. Work is planned with Gratis and released to production weekly. - Digital commerce: The web store and application foundation: shopping, returns with an intermediate return status and updated return conditions, product reviews, blog and SEO improvements, and the product feed used by partner channels. - Customer segments: A customer segment structure across backend, storefront and backoffice. The backend is live; customers will see their own segment in the storefront once Gratis approves the release. - Backoffice & permissions: A comprehensive permission-management screen for backoffice users, automatic removal of access when staff leave, order-management filters, banner management and customer-service tooling. - Compliance & audit: Audit findings turned into prioritised changes and reports: contract and consent fields, data handling and access control across storefront, backend and backoffice. - Weekly delivery: A steady cadence agreed with Gratis: work moves from open to test to production every Tuesday, with backend, storefront and backoffice teams releasing together. - Migration & infrastructure: The transition of a live commerce operation onto infrastructure that responds to demand, and the foundation for continuing development. ### MMI Source: https://www.retter.io/work/mmi Sector: Retail & commerce · Markets: Dubai & Ras Al Khaimah Scope: Web · App · Loyalty · Home delivery · Dubai & Ras Al Khaimah Web, app, loyalty and home delivery for MMI in Dubai and Ras Al Khaimah, on a shared backend that serves every storefront and region. - Web store: The online shopping experience for MMI customers. - Customer app: The MMI app, with shopping, preferences and engagement in one place. - Loyalty: The rewards programme that connects purchases across web, app and store. - Home delivery: Delivery ordering and fulfilment connected to the store operation. - Shared backend: A common foundation for MMI brands and regional platforms, including MMI RAK. ### CarrefourSA (engagement in progress) Source: https://www.retter.io/work/carrefour Sector: Retail & commerce · Markets: Türkiye Scope: Backoffice · Loyalty · Web & mobile backend An engagement in progress for CarrefourSA: Retter is building the backoffice front end and back end, the loyalty programme, and the backend services behind the web and mobile channels. - Backoffice: Front end and back end of the tools the CarrefourSA business operates from. - Loyalty: The loyalty programme and its integration with the backoffice. - Web & mobile backend: The backend services that power the web store and the mobile app. ### A101 Source: https://www.retter.io/work/a101 Sector: Retail & commerce · Markets: Türkiye Scope: Web backend · Kapıda · Ekstra · Pet Web backend development for A101’s digital brands: A101 Kapıda for grocery delivery, A101 Ekstra for the wider online range and A101 Pet. - A101 Kapıda: Backend services for the grocery delivery storefront. - A101 Ekstra: Backend services for the extended online range. - A101 Pet: Backend services for the pet-care storefront. - Web backend: Shared services, integrations and the operational logic behind all three. ### istegelsin Source: https://www.retter.io/work/istegelsin Sector: Retail & commerce Scope: Commerce · Inventory · Delivery · Infrastructure A grocery commerce platform connecting customer shopping, inventory and delivery operations. - Commerce: The customer shopping experience. - Inventory: Live stock information connected to ordering. - Delivery: Order and delivery coordination. - Infrastructure: The platform supporting demand through peak periods. ### Emirates Leisure Retail Source: https://www.retter.io/work/emirates-leisure-retail Sector: Food & beverage Scope: CRM · Loyalty · Wallet · Infrastructure CRM, loyalty and wallet modernisation across the Emirates Leisure Retail operation. - Customer systems: CRM, loyalty and wallet brought onto a connected platform. - Payments: Digital wallet, Apple Pay and Apple Watch support within the customer journey. - Infrastructure: Cloud infrastructure and the ongoing operating foundation. ### Costa Coffee Source: https://www.retter.io/work/costa Sector: Food & beverage Scope: Customer app · Loyalty The Costa Coffee customer app and the loyalty programme behind it. - Customer app: The mobile app through which customers engage with Costa. - Loyalty: The rewards programme, member journeys and engagement built into the app. ### PAUL Source: https://www.retter.io/work/paul Sector: Food & beverage Scope: Customer app · Backend & front end · Azadea Group The PAUL customer app for Azadea Group, with Retter responsible for both the backend and the front end, and the regional needs of each market built into the experience. - App front end: The customer-facing mobile experience. - App backend: The services behind ordering, accounts and engagement. - Ordering & loyalty: Mobile ordering and customer loyalty in one journey. - Multi-market delivery: Local menus, pricing and the systems supporting regional operations. ### Pret A Manger Source: https://www.retter.io/work/pret-a-manger Sector: Food & beverage Scope: Catering web A catering web platform for Pret A Manger, bringing group and business orders online. - Catering web: The web experience for browsing the catering range and placing orders. - Order journey: Order capture, scheduling and hand-off to the operation. ### Shake Shack (engagement in progress) Source: https://www.retter.io/work/shake-shack Sector: Food & beverage Scope: Backoffice · App & web (in design) An engagement in progress with Shake Shack. The backoffice is being built and reviewed with the customer module by module, while the app and web flows move into build once their designs are approved. - Backoffice: Operational screens built module by module and walked through with the Shake Shack team. - Design: App and web experience design, presented to the customer for approval before build. - App & web flows: Customer-facing ordering flows, scheduled to follow design approval. ### Spinneys Abu Dhabi (engagement in progress) Source: https://www.retter.io/work/spinneys Sector: Retail & commerce · Markets: Abu Dhabi Scope: Web · App An engagement in progress for Spinneys in Abu Dhabi, covering the web store and the customer app. - Web: The online grocery shopping experience. - App: The customer mobile app. ### Lululemon Source: https://www.retter.io/work/lululemon Sector: Retail & commerce Scope: Web & app · Backend & front end Web and app development with Retter responsible for both backend and front end on each channel. - Web: Backend and front end of the online store. - App: Backend and front end of the customer app. ### Unifree Source: https://www.retter.io/work/unifree Sector: Retail & commerce · Markets: Türkiye Scope: Backend · Purchase-limit control · Stock control Backend services for Unifree duty-free retail. Purchase-limit control runs on the customer’s on-premises Kubernetes; stock control runs on AWS on Rio, Retter’s serverless foundation. - Purchase-limit control: Backend enforcement of duty-free purchase limits, deployed on on-premises Kubernetes. - Stock control: Stock services running on AWS on Rio, connected to the retail operation. - Hybrid deployment: One backend team across on-premises and cloud, chosen per workload rather than one stack for everything. ### İstanbul Sabiha Gökçen Airport Source: https://www.retter.io/work/isg Sector: Travel & airports · Markets: İstanbul Scope: Fast track integrations · Car park · Mobile apps · Backoffice Backend integrations, mobile apps and backoffice for İstanbul Sabiha Gökçen Airport, connecting fast-track services with banks and airlines and keeping the passenger apps and operational tools moving. - Fast track integrations: Backend integrations with banks and airlines so passengers can access fast-track services through their partners. Existing integrations are maintained and extended. - Car park: The car park integration, with a service change under way. - Mobile apps: Android and iOS passenger apps, including Netmera engagement integration and App Store releases. - Backoffice: Operational and reporting screens, including code reporting currently in testing. ### Emirates Source: https://www.retter.io/work/emirates Sector: Travel & airports Scope: Customer partnership ### Medisa Sigorta Source: https://www.retter.io/work/medisa Sector: Insurance · Markets: Türkiye Scope: Web platform Web development for Medisa Sigorta. The engagement covers the web channel. - Web platform: The customer-facing web experience and the requests it serves. ## Case Studies ### Starbucks — One loyalty platform. Three countries. Millions of members. Source: https://www.retter.io/work/starbucks Industry: QSR & Food & Beverage Challenge: Loyalty across three countries usually means three platforms. Every change ships three times, and the experience drifts apart. Starbucks needed one platform that still feels local: one brain, with local payments, partners, and languages in every market. What Retter built — One loyalty platform, built to carry millions of members: - One member and rewards engine for all three countries - Mobile ordering connected to store systems in each market - Local payments and partners per country, without copies of the platform - Infrastructure that scales itself through campaigns and rush hours Outcome: Today the platform serves 750+ stores and 2M+ app users, with 50,000+ transactions a day and zero downtime. Cloud costs are down about 65%. New features ship about 10x faster, and one change reaches all three countries at once. Metrics: - 50K+ daily transactions - 65% lower cloud cost - 10x faster development ### Emirates Leisure Retail — CRM, loyalty, and wallet — modernized across 300+ outlets. Source: https://www.retter.io/work/emirates-leisure-retail Industry: QSR & Food & Beverage Challenge: 300+ outlets ran on an old, closed system. It was expensive, and every change was a fight. They needed a modern platform, and a live move that wouldn't disrupt hundreds of stores. What Retter built — A full move to AWS, on infrastructure that scales itself: - CRM, loyalty, and wallet rebuilt on AWS - Apple Pay and Apple Watch built in, end to end - Customer history moved live, nothing lost - Infrastructure sized by real demand, not worst-case guesses Outcome: Costs fell about 70%, and new features ship about 10x faster. Since launch, the team has spent nothing on DevOps. The platform runs itself across 300+ outlets. Metrics: - 300+ F&B outlets - 70% lower cost - 10x faster development ### PAUL — Digital F&B across nine countries. Source: https://www.retter.io/work/paul Industry: QSR & Food & Beverage Challenge: Nine countries means nine menus, currencies, and partner sets. And every channel must feel like the same premium brand. PAUL needed one platform that grows across markets without multiplying systems. What Retter built — One digital platform for ordering, loyalty, and engagement: - Mobile and web ordering in nine countries, with local menus and pricing - One loyalty program that follows the customer across channels and borders - Engagement that fits a premium brand - New markets launch in weeks on the same core Outcome: PAUL's digital experience runs on one platform across nine countries. New markets launch without rebuilding anything. Metrics: - 9 countries - Multi channels - End-to-end platform ### istegelsin — National-scale grocery commerce, end to end. Source: https://www.retter.io/work/istegelsin Industry: Grocery & Quick Commerce Challenge: Grocery is brutal: thousands of products, stock that changes by the minute, and a 6 p.m. rush that breaks normal systems. istegelsin needed live stock counts, fast delivery at national scale, and easy search for shoppers on phones. What Retter built — A national grocery platform built for real-time scale: - Live stock counts across stores. The app never sells what isn't there - Orders and deliveries planned against live courier capacity - Mobile-first shopping built for quick, frequent baskets - Infrastructure that absorbs the rush and bills for use, not idle servers Outcome: Millions of weekly shoppers order through the platform. Stock counts and delivery promises hold through peak hours, with a lean team running it all. Metrics: - Millions weekly shoppers - Real-time inventory - 100k/s request capacity ### Gratis — Omnichannel beauty retail, unified on one platform. Source: https://www.retter.io/work/gratis Industry: Marketplace & Omnichannel Challenge: Every peak season was a capacity project. Every channel was a separate integration. The goal: move a busy, live store onto a modern platform without disrupting the business. What Retter built — A full move of Gratis' web store onto the Rio platform: - Web store moved live in under five months - One backbone connecting online and store operations - Infrastructure sized by real demand, not peak guesses - New channels plug in instead of starting over Outcome: The move finished in under five months with zero disruption. Gratis ran a nationwide campaign just three days after go-live, on the same foundation that already powered its app for two years. Metrics: - <5 mo live migration - 3 days to first campaign - Zero disruption ### MMI — Award-winning beverage commerce on one backend. Source: https://www.retter.io/work/mmi Industry: Marketplace & Omnichannel Challenge: Multiple brands and storefronts usually mean a backend for each one. Experiences drift apart, and every new launch takes quarters. MMI needed one backend for every brand and channel, so new storefronts launch fast. What Retter built — One backend for every MMI brand and channel: - One backend for MMI e-commerce, apps, and regional platforms like MMI RAK - Personal taste profiles that tailor shopping to each customer - Fulfillment connecting online and in-store - Mircate's engagement engine built into the shopping flow - New storefronts, including Spinneys, launch on it in weeks Outcome: MMI was named Most Admired E-Commerce Retailer of the Year at the 2025 IMAGES RetailME Awards. Every brand runs on one backend, so a new storefront is a launch, not a rebuild. Metrics: - Winner RetailME 2025 - One backend, every brand - Omnichannel commerce ## Blog ### Why AI-Native Commerce Platforms Win Source: https://www.retter.io/blog/why-ai-native-commerce-platforms-win Published: 2026-05-28 · Updated: 2026-09-17 · Author: Retter · Category: AI Commerce Strategy Every commerce platform now claims to “have AI.” A chatbot here, a recommendations widget there. But there’s a structural difference between a platform with AI features and an AI-native platform — and that difference compounds. ### Features vs. foundations An AI feature is limited by the information it can access. Search, loyalty and pricing may use different sources and update schedules. Connecting the relevant context, with appropriate permissions, can make a feature more useful without requiring every system to be replaced. An AI-native platform inverts this. Customer events — searches, orders, redemptions, abandonments — flow into one substrate that every capability reads from: - Search understands intent because it sees purchase history, not just keywords. - Recommendations adapt in real time because they share the same event stream. - Loyalty triggers the right offer because it knows the member’s actual behavior. - Pricing moves with demand because it isn’t waiting for a nightly batch job. ### Why this shows up in revenue The metrics that matter in commerce — conversion, basket size, repeat rate — are all functions of relevance. Relevance is a function of context. And context is exactly what seams destroy. A grocery search experience, for example, can depend on catalog descriptions, current availability and the customer’s intent. Connecting those signals gives a team a more useful basis for testing relevance. Any effect on conversion or basket size still needs to be measured in the actual customer journey. ### You don’t need to rebuild everything Retter can connect AI to an existing commerce, ERP or loyalty platform. Available interfaces, data quality and access rules determine the scope. Retter develops and iterates rapidly, while the production rollout is agreed around the systems and workflow involved. Start with one useful workflow, define how its results will be checked and expand from the evidence. ### Serverless Loyalty at Enterprise Scale: Practical Lessons Source: https://www.retter.io/blog/serverless-loyalty-at-enterprise-scale Published: 2026-04-15 · Updated: 2026-09-17 · Author: Retter · Category: Serverless Architecture Loyalty workloads can change sharply when a campaign launches. Capacity planning needs to account for peaks as well as normal traffic, and the cost of idle capacity needs to be weighed against the requirements of the customer experience. Retter brings years of AWS serverless experience to loyalty platforms. The published Starbucks and Emirates Leisure Retail stories describe concrete examples of the systems, integrations and operating requirements involved. ### What serverless actually buys you Managed scaling can help applications respond to variable demand. Service limits, data stores and downstream dependencies still need attention: a scalable entry point does not make every part of a transaction flow unlimited. Usage-based pricing can align some costs with demand, but savings depend on the workload and architecture. Retter’s published Emirates Leisure Retail story reports about 70% lower costs for that engagement. It is a project result, not a forecast for every serverless application. Managed services reduce some infrastructure tasks. Application monitoring, access control, failure recovery and cost management still require ownership. Teams can spend more attention on the program while maintaining a deliberate operating model. ### The patterns that matter A few hard-won architectural rules from running these systems in production: - Keep transaction history traceable. Choose a data model that supports reconciliation, reversals and investigation; event sourcing is one option, with its own trade-offs. - Idempotency at the edge. Mobile clients retry. Networks duplicate. Every write path needs an idempotency key before it needs anything else. - Design data location and identity around the project’s requirements. Assess the customer journey, access rules and applicable obligations before choosing where information is stored. - Design for the campaign, not the steady state. If your architecture review doesn’t include “what happens when 5 million push notifications land,” it isn’t finished. ### Proven, not theoretical Retter’s published work includes Starbucks loyalty across three countries, Emirates Leisure Retail’s CRM, loyalty and wallet across 300+ outlets, and PAUL’s ordering platform across nine countries. Each customer story describes its own scope and results. If you’re building — or rescuing — a loyalty platform, this is the architecture conversation to have first. ### Agentic Reporting: Ask Your Business Anything Source: https://www.retter.io/blog/agentic-reporting-ask-your-business-anything Published: 2026-03-10 · Updated: 2026-09-17 · Author: Retter · Category: Agentic Analytics A new business question may not fit an existing dashboard. “Why did basket size change last weekend?” can require a different comparison, data source or definition. An analytics assistant can help explore the question when access and validation are designed carefully. ### From dashboards to agents Agentic reporting replaces the dashboard-request cycle with an agent that has governed access to your data and the ability to do the work itself: - You ask in plain language. “Compare loyalty redemption rates across markets since the campaign launched.” - The agent plans the analysis. It decides which sources to query, joins what needs joining, and checks its own numbers against known totals. - You get an answer, not a chart dump. A direct response, the supporting figures, and the queries it ran — so analysts can verify instead of reconstruct. The difference from “chat with your data” demos is reliability. An enterprise reporting agent needs governed access controls, a semantic layer so revenue means the same thing in every answer, and an audit trail for every figure it produces. ### What this looks like in practice For commerce operators, the highest-value questions are operational and time-sensitive: - “Which stores will miss their delivery SLA this week at current courier capacity?” - “What did the price change on our top 50 SKUs do to margin, by market?” - “Which loyalty segments are quietly churning?” These questions may be supported by dashboards, analysts or an assistant. The right interface depends on the question and the data available; an agent still needs its reasoning and queries checked. ### What to establish before rollout An analytics assistant can connect to the warehouse, ERP or commerce systems already in use. First establish the data sources, definitions and permission model. Then test reference questions and ambiguous cases alongside the people who own the data before agreeing the rollout. Delivery timing depends on access, data quality, metric definitions and validation needs. A first demonstration and a production reporting tool are different milestones. Retter agrees scope and timing around the actual business requirements.