An app is something built by somebody else that you can add to Finocket — a connector to a service you already use, a report Finocket does not have, a workflow step. The directory is where you would find one and see, before you add it, exactly what it would be able to look at in your books.
What the screen tells you
Three things, and only the first one changes when apps arrive.
- What is listed. Nothing today. When there is something, each entry names what it does and which parts of your books it asks to see — your invoices, your customers, your baskets — before you decide.
- How an app gets listed. A developer writes it, submits it, and somebody at Finocket reviews it. A developer cannot list their own app. A listed app can be suspended, which stops new installs and leaves anyone already using it running.
- What is still missing. Four things, each saying who has to do it. Nothing is hidden behind “coming soon”.
Why you cannot add anything yet
The one that matters most to you is the permission notice. Adding an app means handing another company a look at your customers and what they buy, and the words you would be agreeing to when you do that have not been written or approved by anybody. Finocket will not put an Add button in front of you before that exists, because a button that always refuses is worse than no button.
What happens when you do add one
You see exactly what the app is asking for, grouped by what it covers, and you grant it or you do not. Ending it is always yours to do and never needs anyone’s agreement — removing an app cuts off every connection and every key it was given, immediately.
What an app can put on your shop pages
An app can offer a block — a small piece a shop or checkout page can show, like a delivery estimate under a price or a notice before payment. Two things are worth knowing about how these work, because both are deliberate.
Finocket draws every block itself. An app tells us what the block is called, which of a few shapes it should take and where it belongs; it never sends anything to a shopper’s browser. That is why an app cannot change how your shop looks beyond the slot you gave it, and cannot slip anything into a page a shopper loads.
A block only shows if the app is still added and holds the permission it needs. Your page stores the app’s name and the block’s name and nothing else, so the check happens every time the page is drawn rather than once when you placed it. Remove the app and its blocks stop appearing immediately, with nothing for you to undo. If a block cannot be shown for any reason, you are told which one and why — it never just leaves a gap you would have to notice.
You cannot see one today for the same reason there is nothing to add: no app can be published, so no workspace has one installed to contribute a block. Your shop pages do draw their sections — there is simply no app block to put in one yet.
Your marketplace and courier connections are not apps
This is the part worth being precise about, because the two sound alike and work in opposite directions. When you connect Amazon, Shopify or a courier, Finocket holds your key and calls them. An app is the reverse: somebody else holds a key and calls Finocket. That is why your existing connections do not appear in the directory, and why removing an app could never end one of them.
Nothing was added to your app list on your behalf when the directory arrived. An app you never agreed to is not something that should appear because a screen was built, so none did.
The directory lists those connections anyway, with what is actually known about each one — whether it has ever been used with a real account, or only with sample data. A name on its own would read as a promise about a service, and for several of these nobody has ever connected a real account to check.