Your product runs outside ServiceNow: build a minimum certifiable app

• Your product is SaaS or on-premises, with an API.
• Customers’ ServiceNow teams want a Store app they can install and govern, not a script.
• The integration is simple: create or update records, show status, keep tickets in sync.

• List it as type Integration and keep it free if you can: the Store says free apps of type Integration “are exempted from the custom table count and do not require custom table entitlement.”
• If the app writes to ITSM or CSM records, customers need those products.

• Build Program membership. ServiceNow announced in January 2026 that “all global partners will move to a streamlined single annual membership fee”, and it quotes the fee when you apply.
• One use case worth installing: usually keeping the records your customers care about in sync.
• A dedicated integration user and a role design, never an admin account.

Certification reviews your documents as well as your app, and in our experience it’s the part most teams miss. ServiceNow’s certification guide says “Certification has two tracks”: an app review and a listing review.

• For the app review, ServiceNow asks for a “Design Document (for certification team only)”, a “Test Plan with results (for certification team only)” and an “Installation Guide (customer facing)”. Write the design document and test plan on ServiceNow’s templates; it provides a recommended template for the installation guide too.
• For the listing review, your Store listing “consists of marketing documentation, demo videos, and other resources”, and the team inspects it for “Accuracy” and “Adherence to branding guidelines”.

ServiceNow lists “How well you documented your architecture in your Design Documentation” among the things that decide how long certification takes. The calendar gives the documents a week of their own.

Plan on roughly 6–9 weeks from the start of design to a Store listing.

Not in ServiceNow’s Build Program yet? Add admission first: in our experience it takes 2–6 weeks, because ServiceNow reviews each application.

Weeks for design, build, documents and any programme steps come from our own projects. The review range is ServiceNow’s: certification “typically requires 3-5 weeks”, and no service level is published.

• An app with no real logic, which ServiceNow says isn’t recommended.
• Credentials stored in properties or scripts instead of credential records.
• An admin-level service account.
• No Contact Support module, one of ServiceNow’s ten most-failed checks.

• Maintenance is a release certification for each family release: retest on the new release and submit a revised test plan. ServiceNow’s Upgrade Policy says it “generally releases two new release families per year”. Any change to the app is a recertification, planned as new work.
• Grow the app from the use cases customers actually ask for.

• Whether it’s certified, and what that covers. Certification is strict on most security and performance issues, but it isn’t a full security audit, and the Store’s terms still leave use at the customer’s own risk. Have your own security answers ready.
• What data leaves their instance, and where it goes.
• Which user the app runs as, and what that user can touch.
• How you handle vulnerabilities and updates.