Dealing with Guideline 4.3(a) on a Legitimate B2B Legacy App Migration (Unable to redesign)

Hello everyone,

I am hoping to get some advice or hear from anyone who has successfully navigated a similar situation with App Review. We are currently stuck in a review cycle regarding Guideline 4.3(a) - Design - Spam, and the goalposts seem to be shifting.

The Context: Our company recently acquired a B2B application (a utility app used by regional cable operators in India for payment collection). The app was originally built by an independent developer whose Apple Developer account was subsequently terminated. We legally acquired the complete intellectual property, source code, and distribution rights.

The Review Timeline:

  • Submission 1: Flagged under 4.3(a). App Review stated the app was associated with a terminated account. We replied via the Resolution Center, attaching the fully executed IP Assignment Agreement and proving we are a distinct, compliant corporate entity. We also updated the Bundle ID and backend infrastructure.
  • Submission 2 (Current): Apple reviewed the IP documentation but rejected it again under 4.3(a). This time, the reason shifted entirely. The message stated: "Specifically, this app appears to be identical to apps already submitted to the App Store from other developers." They suggested revising the app to provide a unique experience or restricting storefronts.

Our Constraints & Actions Taken:

  • No Redesign Possible: Because this is a legacy B2B app actively used by our clients' operational staff, we cannot arbitrarily alter the UI/UX, widget tree, or navigation flows just to change the binary footprint. Doing so would break existing business processes and invalidate staff training.

  • Current Status: We have escalated this to the App Review Board, explicitly stating that this is a 1-to-1 migration of an active B2B ecosystem tool, not a generic consumer template aimed at spamming the store. We are currently waiting for their response.

My Questions for the Community:

  1. Has anyone successfully pushed through a 4.3(a) "clone" rejection by arguing the B2B/Enterprise legacy angle with the App Review Board?
  2. If the appeal fails and we absolutely cannot change the source code or UI due to client constraints, is moving this to Apple Business Manager (Custom Apps/Unlisted) our only viable path forward?
  3. Does App Review treat Unlisted Apps differently regarding 4.3(a) Design Spam?

Any insights, workarounds, or shared experiences would be greatly appreciated. Thank you!

Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences.

If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select "App Review Appointment." A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.

Dealing with Guideline 4.3(a) on a Legitimate B2B Legacy App Migration (Unable to redesign)
 
 
Q