Factory app vs. localized platform: what actually matters

The Chinese hardware factory will sell you the station. They'll also offer to license you their app. The pitch is reasonable — same vendor, one relationship, integrated software. So why would an operator pay a separate platform partner instead?

Because the factory's app and a localized platform are not the same product, and the difference shows up where it costs you most: at the moment of the rental.

Let's go through what actually matters.

What the factory app is built for

The factory's app is built for the factory. Specifically: to ship one product that runs on every box they sell to operators around the world, without bespoke engineering per market.

That's a sensible product strategy for the factory. It's a problem for the operator, because the operator's market is not generic.

What "localized" actually means

When we use the word "localized," we mean four specific, expensive things:

1. Payment rails per market

The factory app typically integrates a single global processor. That single processor doesn't natively handle:

• Pix in Brazil
• OXXO or SPEI in Mexico
• Mercado Pago across the southern cone
• iDEAL in the Netherlands
• Bancontact in Belgium
• SEPA-style flows across European countries
• Local credit / debit card behaviors specific to each country

Each of those is the actual rail your customer wants to use. If your payment screen doesn't show their preferred method, they bounce. The rental is gone.

A localized platform integrates these per market. That's not a feature add; it's months of work per region, and it's the work the factory isn't doing.

2. Customer-facing UI in the local language

Your end customer scans the QR code and hits a web app. That web app needs to:

• Be in the customer's language by default
• Use the vocabulary that reads natively in that language (not Google-translated English)
• Show the right currency, the right time format, the right number format
• Render correctly on the phone OS distribution of that market

The factory app is often English-or-Chinese-only with mediocre translations to anything else. A localized platform ships native UI per region.

3. Settlement in the operator's currency

The factory app typically settles in a single currency. The operator absorbs the FX. In high-inflation or weak-currency markets, this is painful — the operator is silently underwriting currency risk on every rental.

A localized platform settles to the operator in the operator's chosen currency, with the FX exposure handled at the platform level.

4. Support in the operator's language and timezone

When something breaks — a payment failure, a station offline, a dashboard question — you need to reach a real human in a reasonable time. The factory's support is sized for global, often async, often with a language gap and a 12-hour timezone delay.

A localized platform staffs support in the operator's region or at least at a timezone overlap with reasonable working hours.

What the operator dashboard difference looks like

The factory app's dashboard, if it has one, is built for the factory's reporting needs. You typically get:

• Basic station status
• Limited per-rental detail
• Limited or no payout reporting
• No real operator-facing analytics

A platform-grade dashboard, built for operators, shows:

• Real-time station status, battery levels, alerts
• Per-rental detail with full fee breakdown
• Payout statements that tie to bank deposits
• Per-venue / per-station / per-day analytics
• Exportable reporting for taxes and accounting

The dashboard is the difference between running a business and owning one.

What "ongoing platform updates" actually means

The factory ships hardware. They are not a software company. App updates happen on their cadence, when they have to, often skipping features that don't matter to their hardware sales.

A platform company's product is the software. Updates happen continuously. New payment methods get added when a market needs them. Bugs get fixed quickly. New analytics get added. The platform improves under you while you operate.

This compounds. A year into operating, your platform-licensed operation has measurably better software than the factory-app-licensed operation next door. Not because the factory is bad — because their incentives point at hardware sales, not platform feature velocity.

The cost question

The factory app license is not actually free. There's typically a per-device fee or a transaction percentage. Once you factor that in, the cost gap between factory app and localized platform is smaller than it looks — and the value gap is significantly larger.

We're transparent about platform fees in the operator agreement. They're structured so we and you both win when transactions grow.

When the factory app is the right choice

There is one scenario where the factory app might genuinely be the right call: you're operating in a market that's culturally and linguistically similar to the factory's home market, your payment behavior matches the rails the factory integrates, and you don't need a real dashboard.

For operators in most of the rest of the world, those conditions don't hold.

What we'd actually rather you do

Before you commit to either path:

1. Get a real demo of the factory's actual current app (not the brochure version). Look at the customer-facing flow in your country's primary language.
2. Try a test transaction with your country's most common payment method. See if it works.
3. Look at the dashboard. Ask whether you can build a real business on that surface area.
4. Then talk to a platform partner and compare.

We're happy to walk you through ours on a demo. Apply to become an operator.