MILabs
Integrations

Ordering app with SumUp: how the build works

How a custom ordering app works alongside SumUp payments, what AI can help with around the sales records, and where the limits sit.

Updated 2026-01-15

Ordering app with SumUp

If your café, restaurant or catering business takes orders outside the counter, the order itself and the payment are separate jobs. An ordering app can collect what a customer wants, when they want it and where it should go, while SumUp handles the card or contactless payment and records the sale. MILabs builds the ordering layer so that each order can be matched to its transaction in SumUp afterwards. That match matters because the till record is what a bookkeeper checks against bank deposits. A model can read a weekly export and show which items sell in which hours, draft the message a customer receives after collection, and sort notes that staff add to an order. It should not decide refunds or change prices on its own. Anything involving card data stays out of the model's inputs. The owner keeps control of the menu and every payment decision.

How it works

  1. Map the order fields the customer enters, such as items, collection time and notes, to the fields SumUp records for each sale.

  2. Confirm the current SumUp API scopes for transactions before building, since the developer documentation sets what a custom tool can read.

  3. Store each order with a reference that can be matched to the corresponding SumUp transaction once payment completes.

  4. Set up a scheduled read of transaction records so the order log and the till record can be compared on a regular basis.

  5. Route orders to the kitchen or counter screen, and keep card numbers and personal details out of any text sent to a model.

  6. Test with a day of exported records and have a person check the first matches before the app goes live.

good questions, straight answers

Frequently asked questions

Is an ordering app safe with SumUp data?
Card payments stay with SumUp and the bank, and the ordering app should never hold card numbers. Card data falls under payment card industry rules, so the build keeps card numbers and personal details out of anything sent to a model. Access to SumUp should use the narrowest scopes that the transaction reads require, and any stored order should hold only what the kitchen or bookkeeper needs.
What happens if SumUp changes?
The build is ready for it. SumUp can change its dashboard, export columns, plan features or API scopes, so the ordering app checks the export columns on each run and records which API version it was written against. When a change appears, the affected step is updated and tried out on a day of past records before live orders carry on.
Who owns an ordering app built around SumUp data?
The business owns the ordering app, its code and the order records it creates, and it holds the SumUp account and its transaction records. The build should be documented so that the owner can hand the app to another developer or move it to a different platform. Source code, configuration and access credentials should sit in accounts the owner controls. Keep separate exports of the SumUp records as well.
How does an ordering app hand work to a person in SumUp?
Orders that fail a match, carry a refund note or show a payment gap go to a staff queue rather than being resolved by the app. The person checks the order against the SumUp record and then marks it complete or sends it to the bookkeeper. Refunds and disputes stay inside SumUp's own tools, so the app only flags them and a person acts.
Can an ordering app work with SumUp data exports?
Yes, for reading and reporting. A model can read a downloaded transaction file and check it against the orders the app stored, listing orders with no matching sale or sales with no order. The export shows only what was recorded, so sales taken on a different till will not appear. A file is only as current as its pull, so a live link needs a connection someone maintains.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.