30.03.2026

How to Pass the Application Readiness Check on the SAP Store

Mateusz

Software Architect & Developer, SAP S/4HANA Consultant

This article was last updated on 30th March 2026.

If you’ve ever tried to bring a new SaaS or ISV product into the SAP ecosystem, you already know: SAP doesn’t just open its doors to any solution. To be listed on the SAP Store, your app must meet SAP’s high standards for security, performance, integration, and customer value.

That’s exactly what the Application Readiness Check (ARC) ensures.

Think of the ARC as SAP’s quality gate: the mandatory process that ensures every solution listed on the SAP Store meets the same global standards that SAP itself follows. It’s a mix of a technical review, compliance validation, and business readiness assessment rolled into one.

For many solution partners, this step is the most misunderstood part of the journey. You might already have a great product, but if it doesn’t align with SAP’s architectural, security, and governance expectations, it won’t make it to the store.

In this guide, you’ll walk through everything you need to know to pass the Application Readiness Check with confidence.

By the end of this guide, you’ll know exactly how to:

Prepare your app for ARC submission.
Understand what SAP reviewers look for.
Avoid the top mistakes that get apps rejected.
Confidently move from ARC approval to listing on the SAP Store.

And if you think you’d like expert support along the way, you can book a meeting with one of our consultants to discuss the process. We can help with strategy, development, governance and compliance steps.

What the ARC Really Is

The ARC is SAP’s internal vetting process for partner-built solutions, whether they’re integrations, extensions, or stand-alone SaaS applications that connect to SAP systems. If you’re building on SAP BTP or integrating with core SAP applications (like S/4HANA, Ariba, or SuccessFactors), ARC is mandatory.

It’s not a deep technical certification (like the ICC certification); it’s a comprehensive readiness review focused on ensuring your product meets SAP’s baseline standards in four key areas:

Technical Compatibility. Does your app work seamlessly with SAP technologies (e.g., SAP S/4HANA, SuccessFactors, Ariba, BTP)?
Security & Compliance. Are data handling, authentication, and encryption aligned with SAP and industry requirements (GDPR, SOC 2, ISO 27001)?
User Experience & Documentation. Does your solution offer a professional, SAP-aligned experience and proper user support?
Operational Readiness. Is your product fully functional, supported, and ready for enterprise adoption?

In short, the ARC is SAP’s way of saying:

“Yes, this solution meets the quality, security, and integration standards we expect in our ecosystem.”

What Happens If You Skip or Fail the ARC

You cannot publish your solution on the SAP Store without passing the Application Readiness Check. It’s mandatory. And, if your solution fails ARC, SAP provides detailed feedback for resubmission, which can delay your go-live by weeks or months.

Most failures stem from:

Missing documentation (especially architecture and security details).
Incomplete or vague responses in the ARC questionnaire.
Lack of integration evidence or unclear use of SAP technologies.
Submitting before the app is fully stable or market-ready.

Gather Core Documentation Before You Begin

The ARC process is heavily documentation-driven. Prepare these materials in advance; you’ll need to upload or reference them in the ARC questionnaire.

Solution Architecture Diagram showing how your app integrates or extends SAP components.
Security Documentation covering authentication, data protection, encryption, and compliance standards (e.g., GDPR, SOC 2).
Technical Stack Summary: programming languages, runtimes, services, APIs used.
Functional Overview describing your app’s purpose, key features, and value proposition.
Localisation & Globalisation Info, including supported languages, data residency, and compliance in target regions.
User Assistance: help guides, onboarding materials, and support documentation.
Lifecycle Management Plan: how you handle updates, maintenance, and version control.

Treat documentation as part of your product’s “enterprise readiness.” The more clearly you can communicate your architecture and governance practices, the faster SAP reviewers can approve your submission.

Quick Readiness Checklist Before Starting ARC

Steps	Description	Status
PartnerEdge Build or ISV Contract	Active and valid	☐
S-User Access	Verified and functional	☐
Solution Technically Ready	Fully built and tested	☐
Licensing & IP Rights	Verified	☐
Documentation Set	Architecture, security, support	☐
Solution Registered	In Partner Portal	☐
Roles & Access	Proper submission rights	☐

Once every box is checked, you’re ready to begin the ARC process.

The ARC Process (Step-by-Step)

The ARC process may appear intimidating at first glance, but once you understand how it flows, it becomes a predictable and manageable sequence. Let’s go through the process, step by step.

1. Register Your Solution

Everything starts in the SAP Partner Portal, specifically in Manage My Apps (sometimes listed as Manage My Solutions). This portal is your control centre for listing and managing your SAP Store apps.

When registering your solution, you’ll provide:

Solution name and short description. Keep it professional and descriptive. Avoid using “SAP” in your app name unless explicitly authorised.
Solution type. Choose whether it’s an extension, integration, or standalone app.
Supported SAP products. Specify which SAP systems your app connects to (e.g., S/4HANA, SuccessFactors, Ariba).
Deployment environment. Indicate if it runs on SAP BTP, private cloud, or hybrid infrastructure.
Technical and business contacts. These will be your ARC communication points.

Double-check your solution type and naming. SAP is strict about naming conventions and solution categorisation. Mislabeling these can delay your ARC start.

Once your solution is registered, you can initiate the Application Readiness Check for that app.

2. Complete the ARC Form

This is the core of your submission, the structured form that SAP reviewers will evaluate. It’s divided into several sections, each targeting a different readiness dimension.

Here’s what the ARC form typically covers (based on SAP documentation and partner experiences):

Section	What It Evaluates	What You’ll Provide
Application Platform & Architecture	Whether your solution is technically compatible with SAP systems.	Architecture diagram, BTP services used, and integration flows.
Integration / Extension Scope	How your app connects with SAP systems or extends their functionality. If you’re extending SAP functionality, reviewers want to see that you do it in a compliant and future-proof way.	Reference to SAP-certified APIs or standard interfaces, data exchange models, clear explanation of integration points, integration scenarios, and statement on version compatibility, e.g., “Supports SAP S/4HANA Cloud 2308 and higher.”
Functional Correctness	Whether your app actually solves the problem it claims to, and does so with an enterprise-grade user experience.	A brief overview of key features (one-page summary), a role-based access table (showing which user types can do what), and a QA/testing summary showing stability across test cases.
Security & Compliance	Security is the most heavily weighted area of the ARC review. SAP evaluates how your app handles data protection, authentication, and security audits.	Security documentation covering Identity management, authentication flow, encryption standards, and incident response process. Mention if your organisation is certified (e.g., ISO 27001, SOC 2, GDPR). Include data flow diagrams showing where and how SAP data is stored or transferred.
Software Lifecycle Management	How you manage releases, patches, and support.	Provide a short “Software Lifecycle Plan” PDF or document. Mention versioning strategy (e.g., semantic versioning). Describe how customers receive updates (automatic, manual). And service-level expectations, even basic ones (e.g., “Response within 24 hours for high-severity tickets”).
Operations & Support	Whether you have a customer support model and escalation process.	Support plan, contact process, ticketing overview.
Globalisation & Localisation	Multi-language and compliance readiness for target markets.	Provide a list of supported languages, localisation details, and compliance notes on how you handle localisation in architecture (e.g., via i18n files)
Branding, IP, and Documentation	Whether your app meets SAP’s brand and documentation standards	Provide user guides, logos, and proper trademark usage.

Pro Tip:

SAP reviewers look for clarity, completeness, and evidence. Don’t write vague answers like “Yes, our app is secure.”

Attach real artefacts like diagrams, policies, architecture files, or URLs to demonstrate compliance.

We have created a template with clear instructions on how to fill out the ARC form.
Download Template.

3. Submit Your Application

Once you’ve completed the form and uploaded all required documents, review all fields for completeness. Confirm that the right solution type and SAP product connections are selected. Ensure your documentation files are properly labelled (e.g., Security_Overview_v1.0.pdf). And then submit your ARC request for review.

After submission, your solution enters the SAP Review Queue.

Timeline & Effort Expectations

The Application Readiness Check (ARC) and SAP Store listing process is a structured journey.
While SAP provides a standardised workflow, timelines can vary depending on your solution maturity, documentation quality, and responsiveness during review.

On average, the full ARC and publishing process takes 6 to 10 weeks from preparation to listing.

However, durations can differ based on partner experience and solution complexity:

Experienced SAP partners with all documentation ready typically complete the process in 4 to 6 weeks.
First-time partners (standard ISVs) with moderate solution complexity usually take 6 to 8 weeks.
Complex enterprise solutions involving multiple integrations or hybrid deployments may require 8 to 12 weeks.
Submissions with multiple feedback cycles or missing documentation can extend beyond 12 weeks.

Partners who prepare their documentation before starting the ARC generally finish the process 30–40% faster.

Once submitted, SAP’s Application Review Team evaluates your solution across all readiness dimensions. The SAP review phase typically takes 2 to 4 weeks, depending on submission volume and the complexity of your app.

Also, add buffer time around SAP’s internal fiscal quarters, as review queues tend to grow near major SAP events such as SAPPHIRE and TechEd.

SAP reviewers may contact you via email if they require clarification, additional details, or supporting evidence. Be responsive and reply within 24–48 hours. Make sure your technical lead replies to the queries, as reviewers often ask specific architecture questions. Clear and concise responses speed up the approval process.

Key Factors That Influence Your Timeline

1. Solution Complexity

Simple SaaS extensions (1–2 SAP integrations) can clear ARC in ~4 weeks. While enterprise-grade apps with multiple integrations or on-premise components often take 8–10 weeks.

2. Documentation Readiness

Incomplete or inconsistent documentation is the #1 delay driver. SAP reviewers cannot proceed until all required evidence is uploaded. Make sure your architecture, security, and lifecycle docs are finalised before submission.

3. Internal Team Bandwidth

You’ll need time from your Technical architect (for integration details), Security/compliance officer (for data handling), and Product manager (for business value documentation). If these roles are overbooked, plan a staggered submission timeline.

Here’s an optimal setup for small-to-mid ISVs going through the process for the first time:

Role	Responsibility	Typical Time Allocation
Project Owner / Product Manager	Oversees overall ARC readiness, communication, and submission	~20 hours
Technical Architect	Prepares architecture diagrams, integration flows, and technical details	~25–30 hours
Security Officer / IT Lead	Prepares compliance, authentication, and data protection documentation	~10–15 hours
Operations / Support Lead	Drafts lifecycle management and support plans	~8–10 hours
Marketing Manager	Prepares SAP Store content (copy, visuals, pricing)	~10–15 hours
Executive Sign-off	Final review and submission approval	~2–3 hours

Assign a single ARC coordinator; someone who keeps track of every document, version, and communication thread with SAP. This dramatically reduces confusion.

ARC Outcomes: Pass, Conditional, or Rework

Once your submission has been reviewed, SAP will send you an official notification outlining the result of your Application Readiness Check.

There are three possible outcomes you can expect:

Approved (Pass)
This is the ideal outcome. It means your solution has successfully met all technical, security, and operational requirements. You can now move forward with creating and publishing your listing on the SAP Store.

Conditionally Approved
In some cases, SAP may grant a conditional pass. This means your solution meets most of the criteria, but there are a few minor updates or clarifications required, for example, adjusting documentation, refining your architecture diagram, or providing additional test evidence. Once those adjustments are complete, you can quickly resubmit for final approval.

Returned for Rework
If your submission has significant gaps, SAP will return it with detailed feedback. You’ll need to address the identified issues before reapplying. This doesn’t mean your product isn’t valuable; it simply means key readiness elements need to be strengthened before SAP can approve it for listing.

SAP provides clear, structured feedback explaining where your submission fell short. In most cases, these fall into a few common categories:

Missing or unclear architecture documentation
Insufficient security explanation or compliance detail
Incomplete or confusing integration flow
Missing lifecycle management plan or unclear support structure

Treat your first submission as a baseline validation round. Take that feedback seriously. It’s not a rejection, but a roadmap for improvement. Most partners who carefully address SAP’s comments successfully pass their second attempt.

Next Steps After ARC Approval

Once you receive approval, your solution moves into publishing readiness. You’ll now work within the SAP Store publishing cockpit.

Inside the cockpit, you’ll define:

Solution overview & description: a concise explanation of your product’s purpose and business value.
Target industries and use cases: clearly identify which SAP customers benefit most from your app.
Supported SAP products: specify exactly which SAP environments your solution integrates with.
Deployment & pricing model: one-time, subscription, freemium, or quote-based.
Visual assets: logos, banners, screenshots, and demo videos.

Pro Tip: Keep your listing customer-centric, write for business decision-makers, not developers. SAP customers browse for outcomes (“automate invoice approvals”) more than for technical specs.

Add Marketing & Commercial Details

Your listing is both a technical summary and a sales page. SAP provides multiple fields for partners to position their apps effectively.

Here’s what to focus on:

Element	Purpose	Best Practice
Short Description (Up to 150 characters)	Quick snapshot of value	“Automate vendor invoice approvals directly from SAP S/4HANA.”
Long Description	Deeper business and technical overview	Focus on problem → solution → benefit → proof.
Key Features	Highlight capabilities	Use bullets, each starting with an action verb.
Customer Benefits	State business outcomes	Quantify results (“Reduce manual processing by 40%”).
Trial Option	Let customers test your app	Offer a 14-day trial or sandbox access if possible.
Contact Info	Customer outreach	Add dedicated SAP Store support email.

Pro Tip: Add a demo video or animated walkthrough. Listings with videos consistently get higher engagement.

Configure Pricing and Commercial Models

Decide how customers will interact with your solution financially. SAP supports several transaction models, such as,

Get It Now (Self-Service Purchase): Customers can buy or start a subscription immediately through the SAP Store. It’s best for lightweight SaaS or integrations with standard pricing.

Request a Quote: Ideal for enterprise or industry-specific solutions that require tailored pricing. This model triggers lead notifications to your sales team.

Free Trial: Offers short-term access for evaluation. Builds trust and accelerates adoption.

Pro Tip: If you’re a new partner, start with a Request a Quote model. It allows you to qualify leads directly and control pricing flexibility.

From there, your app goes through a final content review before going live. And just like that, your product becomes officially visible on the SAP Store, joining thousands of other enterprise-ready apps.

Best Practices to Expedite Your ARC Approval

SAP’s Application Readiness Check (ARC) is thorough by design. But that doesn’t mean it has to be slow or painful. The difference between a partner who clears ARC in 2 weeks and one who gets stuck for 2 months usually comes down to preparation, documentation quality, and communication.

Below are the best practices distilled from our past clients and lessons shared by experts in the SAP Community who’ve done it multiple times.

1. Don’t Submit Until You’re Truly Ready

It’s tempting to submit as soon as your app works, but readiness is about enterprise stability. Before submission, make sure you’ve:

Completed internal testing across all supported SAP systems.
Finalised your integration flows and error handling.
Reviewed every section of the ARC questionnaire with technical and compliance teams.
Validated your documentation set; no placeholders, no “TBDs.”

Pro Tip:

Run a mock review internally. Have someone outside your core team go through your ARC answers and documentation. If they can’t easily understand how your app works, SAP reviewers won’t either.

2. Provide Organised, Professional Documentation

SAP reviewers appreciate clarity and completeness more than volume. A clean, structured submission shows that your team is mature and process-oriented.

Name all files consistently, e.g., Solution_Architecture_v1.2.pdf, Security_Overview_vFinal.pdf.

Keep your architecture diagram and security documentation separate; don’t bury them in one giant file.

Avoid screenshots of text; use readable PDFs or diagrams. If you reference a document in the questionnaire, ensure the file name matches exactly.

Pro Tip:

Create a submission folder structure like this:

/ARC_Submission/

├── 01_Architecture/

├── 02_Security/

├── 03_Functionality/

├── 04_Lifecycle/

├── 05_Localisation/

└── 06_AdditionalEvidence/

It not only helps reviewers but also becomes your internal compliance asset for future submissions.

3. Leverage SAP Guidelines and Templates

SAP provides various templates and readiness documents through the PartnerEdge portal and BTP documentation.

Before writing from scratch:

Check the official ARC Guidelines PDF
Review the SAP Store FAQ for the latest submission policies.
Look up SAP Community posts from SAP employees explaining submission examples.
Use existing partner case studies as formatting references.

Pro Tip:

Always align your answers with SAP’s terminology; using SAP’s own language (“tenant isolation,” “BTP subaccount,” “OData integration”) instantly builds credibility.

4. Use Visuals and Evidence. Don’t Just Tell, Show

SAP reviewers are engineers at heart. They love visuals that communicate complex architectures or processes quickly.

Enhance your submission with:

Clear diagrams for integration and data flow.
Screenshots or videos of critical workflows (especially if your app integrates with SAP UI).
Short summaries at the start of each document (“Purpose / Scope / Architecture Overview”).

Include a 2-page executive summary up front. It helps reviewers quickly understand your solution before diving into technical details.

5. Involve Both Technical and Compliance Stakeholders Early

The ARC covers multiple domains: technical, security, legal, and operational. Don’t let one team handle it alone; missing perspectives lead to rework.

Recommended contributors:

Technical Lead: Architecture, integration, APIs.
Security Officer: Data protection, encryption, compliance.
Product Manager: Functional correctness, roadmap, business context.
Operations Lead: Lifecycle management, support.

Set up a short internal “ARC Review Board” meeting before submission to ensure all domains are signed off.

6. Conduct a Pre-Submission Quality Review

Before hitting Submit, take time to conduct a thorough pre-submission quality review of your entire ARC package. This step is your final safeguard to ensure every document, response, and attachment aligns with SAP’s expectations before the review begins.

Use this mini checklist to make sure your submission is complete and consistent:

Checkpoint	Verified?
Solution name, type, and SAP product association are correct	☐
Architecture diagram uploaded and legible	☐
Security and data protection documentation completed	☐
Integration and API details are clearly explained	☐
Lifecycle and support plans attached	☐
All questionnaire responses have correct evidence	☐
File names are consistent and professional	☐
Internal review completed	☐

Is there a Cost for the ARC Submission?

The ARC process itself typically doesn’t have a direct fee. However, you must be part of SAP PartnerEdge (Build) or an equivalent program, which comes with its own annual partner membership cost. Additional expenses may include internal resource time, documentation preparation, or consulting support if you choose external help (like readiness assessments).

Can We Submit Our Solution for ARC Before It’s Fully Built?

Technically, yes, but not recommended. SAP reviewers expect your product to be feature-complete, tested, and supported. Submitting a half-finished product almost always leads to rejection or lengthy clarification cycles.

Submit when you have full integration working with SAP systems, a stable production or demo environment, and security documentation finalised.

Does Passing ARC Guarantee Sales on the SAP Store?

No, ARC validates readiness, not market traction. Sales depend on your product’s positioning, pricing, visibility, and SAP alignment. However, ARC approval dramatically increases buyer confidence and qualifies your app for SAP co-marketing opportunities, which can lead to stronger pipeline generation.

Can You Help Us Prepare or Submit the ARC?

Well, certainly! AvoTechs specialises in helping SaaS vendors navigate SAP’s certification journey, from market research, build, and validation to ARC success.

Our team supports you in:

Market research
Building your integrations/extensions
Governance and Licensing Alignment: Making sure your product and partner setup comply with SAP’s legal and operational frameworks.
Security & Compliance Review: Guiding you through GDPR, ISO, and SOC standards aligned with SAP’s requirements.

If you’re preparing your first ARC submission or if you’ve struggled with rejections or unclear feedback, let’s simplify it together.

Our team has guided multiple SaaS vendors through the process, helping them launch faster and with a stronger compliance posture.

Schedule a Free SAP Product Readiness Consultation
We’ll review your current stage, identify readiness gaps, and outline a clear path to ARC approval and SAP Store success.

Resources:

ARC approval tips

Saas listing on SAP Store guide

SAP ARC