Something new at SumUp

Prove what owners pay for POS Plus while card fees rise

Published Oct 23, 2026

You’re the finance & operations lead. Your team is in the room.

The setting

's combines in-store hardware with cloud software. Cafes, shops, bars and hair salons use it to take payments and manage orders, inventory and staff.

POS Plus pricing must stay simple for restaurant owners while preserving the economics behind each offer.

Restaurant owners need a clear monthly cost, while subscription and payment revenue must cover hardware and servicing exposure.

Who you’d be doing this for

“My manager asked what the new setup costs after fees, and I still had three different numbers on my desk.”

Anwar Santoso · Restaurant Owner · a character in this brief

Runs an independent restaurant evaluating POS Plus for a multi-station dining room.

What is at stake

Eligible restaurant offers lack one reviewed view of subscription, hardware and payment economics. You must weigh a simple owner-facing cost view against assumptions that protect contribution margin.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • owner clarity vs. contribution margin protection
  • fast pilot scope vs. reconciled financial inputs
  • standardized offers vs. merchant-specific economics
  • subscription growth vs. servicing exposure

Why SumUp

POS Plus connects restaurant ordering, staff access and multi-station service to payment acceptance, making each subscription offer a combined hardware, software and transaction decision.

Written with these in mind

unit economics builderfinancial operations strategistcommercial finance operator

Not your kind of problem? 38 more at SumUp, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at SumUp. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • ​​Senior Financial Analyst – Revenue Streams (opens in a new tab)
    • Post complex accrual, impairment and revenue recognition entries, and support month-end close within tight deadlines
    • Take ownership of complex reconciliations within one of SumUp's revenue streams such as lending, e-money or merchant banking
  • CoreOps Manager · no longer posted
    • Partner closely with Finance and Accounting to ensure operational costs, settlements, and reconciliation are accurately reflected in financial reporting and P&L.
    • This includes the end-to-end transaction lifecycle, non-transactional products that complement the core payments offering, and the onboarding and risk processes that enable sustainable growth.
  • Junior Credit Management Analyst w/ Italian (opens in a new tab)
    • In Italy, growth in subscription sales and the launch of "Installment from the Shop", our new self financing option for hardware purchases, has significantly increased the number of open payments that need active follow up.
    • 🏖 Generous time off: enjoy 22 days of annual paid leave, 32 hours of Ex Festivita (Personal Hours), plus public holidays and special leave days
  • Junior Credit Management Analyst w/ French (opens in a new tab)

Reporting read before this brief was written

The pieces closest to the situation in this brief.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on committing to a deal before it checks out.

The same setting, from another role

Each is set around SumUp’s Point-of-sale systems, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make complex payment systems feel dependable in the exact real-world moment someone needs to complete one.