App marketplace
POS apps that show every permission first
Add apps from outside developers to Esplanda, and read every permission each one asks for, in plain words, before you install.
What you pay Esplanda is the same with no apps or ten: see Esplanda pricing.
- Read your product list
- See your sales, item by item
- Create purchase orders to your suppliers
Never your bank details, tender types or tax settings
Illustrative example
In short
The Esplanda app marketplace lists POS apps built by outside developers that plug into your Esplanda account and work on the same catalog as your register, purchasing and profit reports.
Every permission is shown in plain language before you install, only merchants who installed an app can review it, and uninstalling ends the app's access that moment.
- Permissions in plain words
- Verified-install reviews
- One store or all of them
- Uninstall ends access
- No paid placement
What apps are for
The one or two things only your store runs
Every store runs something particular to it. The marketplace is where those things live, working on your catalog without anything keyed twice.
A route sheet for the van
Deliveries planned from the orders already in Esplanda.
A label your state requires
Printed from the product details you already keep.
The local association's loyalty scheme
Run on the customers and sales your register records.
One catalog, never a copy
Apps read the same records as your POS system with inventory management, so none needs a separate copy of your products or prices.
Private apps, just for you
A developer you hire can build an app for your own stores without listing it publicly.
Built on the public Esplanda API
Developers see the terms on the POS partner program page.
Permissions
Every permission, in sentences
The install screen lists every permission an app requests before you approve anything. A permission that is not on that screen, the app never gets, and asking for more means showing you a new screen.
| Developer shorthand | What you see | What it leaves alone |
|---|---|---|
catalog:read | Read your product list | Prices and items stay as they are |
catalog:write | Change your prices and product details | Your customers and your bank details |
orders:read | See your sales, item by item | Refunds, voids and re-rings |
purchase_orders:write | Create purchase orders to your suppliers | Sending them: that waits for your approval |
customers:read | Read your customer names and email addresses | Emailing them, unless it also asks to |
inventory:write | Adjust your stock counts | Tender types and tax settings |
An app that wants to reprice bottles has no business reading customer email addresses, and on this screen you see that for yourself in about four seconds. The wider rules on your data are on why Esplanda is safe to trust.
Reviews
Reviewed only by stores that ran the app
Reviews are tied to a verified install, by a merchant who ran the app in a real store.
No seeded praise
A developer cannot fill a listing with five-star reviews from accounts that never used the app.
No drive-by one-stars
A rival cannot post a review from the outside. Three reviews from stores that ran the app for a month tell you more than ninety from people who never installed it.
Placement is never for sale
When one app sits above another, it is not because it bought the slot. Read the reviews, then ask the developer for a reference.
Installing an app
What happens when you install
Five steps, and you can stop at step three. Nothing reaches your data until you approve the permission screen.
Want an online store rather than an add-on? That is part of Esplanda itself: POS with online ordering. To reach nearby shoppers, see how to sell locally online.
Open the app's listing
What it does, who built it, what it costs, and reviews from merchants who installed it.
Press install
That shows the permission screen; nothing starts yet.
Read the permissions, then approve or walk away
Walking away costs nothing and leaves no trace on your account.
The app connects with exactly what you approved
At the locations you chose: one store or all of them.
Uninstall whenever you like
Its access ends at that moment, not at the end of a billing period.
Your store, your call
How you stay in control of every app
Full disclosure up front and a clean yes or no, so an app either does its whole job or never starts.
What you decide
- One set of permissions, all shown. An app requests the set it needs; you accept the set or decline it.
- Which stores it reaches. One location or all of them.
- When it goes. Uninstall cuts its access straight away.
Works with what you have
- Your store keeps running. Your register, catalog and reports keep working whatever an app does.
- App support from its developer. The people who wrote the app fix it; Esplanda cuts its access in one step.
- Your current register, too. Keeping another register? Connect it with POS integration.
Questions
POS app questions owners ask
What are POS apps in the Esplanda app marketplace?
They are third-party applications, built by outside developers, that extend what Esplanda does for your store. You install them yourself from inside Esplanda, and they work on the same catalog your register, purchasing and reporting already use. Nothing is installed for you and nothing runs until you approve it.
How do I know what an app can see about my business?
The install screen lists every permission the app is asking for, written the way you would say it out loud: read your product list, see your daily sales totals, create purchase orders. You see plain sentences, not developer shorthand like catalog:read. A permission that is not on that screen, the app does not have.
Can I stop an app from reading my customer list?
You can decline the install. Permissions come as one set that the app needs to do its job, so the decision is take it or leave it rather than a row of toggles. That is why the list is shown in full, in plain language, before you commit: an app asking to read customer names and email addresses in order to reprice bottles is telling you something, and you should be able to see it.
What happens to my data when I uninstall an app?
Uninstalling removes the app's access immediately. Its permission to read or change anything in your Esplanda account ends at that moment, not at the end of a billing period. Any copy of your data already held on the developer's own systems is governed by that developer's terms, so if that matters to you, ask them directly before you install.
Who can write a review on a marketplace app?
Only a merchant who actually installed the app and ran it. Reviews are tied to a verified install, so a developer cannot seed praise from accounts that never used the app and a rival cannot post a one-star review from the outside. A new app may carry fewer reviews, and each one comes from a store that ran it.
Do marketplace apps cost extra on top of Esplanda?
What you pay Esplanda stays the same whether you run no apps or ten; every price is on Esplanda pricing. The apps themselves are priced by the developers who build them, some free and some paid, and that price is shown before you install.
Is a marketplace app the same thing as a POS integration?
No. A marketplace app adds a capability on top of Esplanda. A POS integration connects Esplanda to a register you already own and are keeping: Square, Clover, Lightspeed or KORONA. One extends the system; the other bridges to the register you have.
What if an app breaks something in my store?
Uninstall it, which cuts its access straight away, and report it. Support for the app itself sits with the developer who wrote it, because they are the people who can fix their own code. Your register, catalog and reporting keep running regardless: an app cannot take the store down with it.
Start with the store, then add apps
Start free today, or book a demo and we'll show you the install screen and what an app sees before you approve it.
Esplanda POS and your website are free to start, with no card needed. Add paid tools only when you want them.
