Skip to content

Publishing requirements

These requirements are a public app's: a private app is never reviewed, and its partner publishes each version. Every version of a public app submitted for review is checked by the platform team before it reaches merchants. The decision, approval or rejection with its reason, is emailed to the partner's contact address. A rejected version stays in the history; the first change after the rejection opens the next version, which is submitted again (versions). An app submits at most 5 versions for review per day.

Send to review is enabled only when the version holds everything below. The portal shows what is missing.

What Requirement
Name and icon Both.
Texts In one language at least (Romanian or English), all of them: the one-line pitch, the description and 3 to 5 key features.
Screenshots 3 to 5. The video is optional.
Store sections A primary one; optionally a secondary one, another than the primary. An open section (ERP, marketing, reports, customer service, other), or the section of an integration the app provides; for each integration it provides, that section is one of the two.
Support and privacy The support page's and the privacy policy's URLs.
Install URL Absolute, https (http only for localhost).
Languages At least one.
Scopes At least one.
Redirect URIs At least one.
  • The name of the app and of the partner: neither is nor holds as a word the platform's name, its assistant's or that of a vendor in the integration catalog. A public app's name is also its own: no other public app may hold it, in any case (a deleted app frees it). The listing uses no other company's name, marks or look in a way that may mislead.
  • Installing: the store's Install button opens the install URL, and the app sends the merchant to the consent screen (OAuth).
  • What the app provides: it does that integration's work as the listing describes, with the scope each one requires.
  • The scopes: the app asks only for the scopes it needs; each matches a feature the listing describes. The merchant reads each scope explained in one sentence, on the consent screen and in the store.
  • Privacy: the consent screen tells the merchant that the data leaves for the partner, with the privacy policy's link. The policy says which data the app uses and how it is deleted.
  • Support: the support URL leads to a page or a contact where the merchant gets help.
  • The listing says truthfully what the app does, which data it uses and what it costs; the screenshots show it as it works.
  • Data after an uninstall: the app handles app.uninstalled and deletes the merchant's data, as the Partner agreement requires.
  • The approved version becomes the published one: it shows in the store and on the consent screen, and applies to installations. The previous one stays in the history.
  • A later change to what a merchant sees or grants goes through review again; the published version stays in the store until the decision.
  • The partner's name, once the partner has a published app, also changes through review.