D-U-N-S number for Apple Developer and Google Play accounts

A D-U-N-S number is a nine-digit business identifier issued by Dun & Bradstreet, and both app stores require one before a company can publish an app. Apple requires it for an Apple Developer Program organization account. Google requires it for a Google Play organization developer account. Requesting one is free.

This is usually the first hard blocker in a Shopify mobile app launch, and it is the one brands miss, because it is the only step that depends on a third party neither store controls. Getting it wrong costs days. Getting it wrong twice costs weeks.

This guide covers what the number is, whether you need one, how to request it, how long each party says it takes, and the mismatches that cause an account to fail verification after it has already been approved.

Scope. Account prerequisites only. This is not a guide to the full enrollment flow, App Review, or Play Console release management. Requirements, fees, and timelines below are quoted from Apple, Google, and Dun & Bradstreet and were checked on September 14, 2026. All three change them without notice, so confirm the live values at the linked sources before you plan a launch date. This is not legal advice.

What a D-U-N-S number is

A D-U-N-S number is a unique nine-digit identifier that Dun & Bradstreet assigns to a business location. Banks, governments, and large buyers use it to confirm that a company exists as a registered legal entity at a stated address.

Apple and Google use it for one purpose: identity. In Apple's own words, your organization "must have a D-U-N-S Number so that we can verify your organization's identity, legal entity status, and address." The number is not a credit score, it does not cost anything to request, and having one grants you nothing on its own.

Two consequences follow. Your company probably already has a number, because D&B assigns them to businesses that never requested one. And the record behind it has to match your company documents exactly, because both stores compare the two.

Do you need one?

You need a D-U-N-S number if you publish as a company. You do not need one if you publish as an individual.

For a Shopify brand, the organization account is the right choice, and the reason is on the store listing rather than in the paperwork. Apple displays your organization's name as the seller name of your apps. An individual account publishes under a person's name, which reads as a side project next to the brands you compete with.

Apple is strict about what counts as an organization. It states plainly: "We do not accept DBAs, fictitious business names, trade names, or branches." If your store trades under a name that differs from the registered entity, enroll the registered entity and set the customer-facing app name separately.

How to request one

Request the number through the store's own enrollment flow, not through a search result. Both routes reach the same D&B database, and paid intermediaries resell a free service.

1. Look your company up before you apply. Apple hosts a D-U-N-S lookup inside its enrollment flow, and D&B runs a public lookup. You need your legal entity name, headquarters address, mailing address, and your work contact details. If a number already exists, you are finished with this step.
2. Request one if the lookup finds nothing. Apple's lookup requests the number for you at no cost. Outside that flow, use D&B's own free application. D&B states: "There is no cost to request and receive a D-U-N-S Number."
3. Use the exact registered details. Legal name, legal structure, registered address, and the name of the owner, president, or CEO. Copy them from your incorporation documents rather than from your website footer.
4. Reuse the same number for both stores. One number covers Apple and Google. A second location or a second legal entity needs its own application.
5. Match the number to your Google payments profile. Google reads your organization name and address from the linked Google Payments profile, then checks them against your D&B record. Fix the payments profile before you submit, not after.

How long it takes

Plan for 30 days. That is what Google tells developers to expect, and D&B's free application quotes 30 business days, which is longer still.

Apple and D&B publish different waits for the same request, and neither explains the gap. Treat the short figure as the best case and the long one as the number you build the launch calendar around.

What we see in practice is faster than either upper bound. Across NAPPS onboardings for brands in the US, UK, Europe, and Australia, most D-U-N-S requests come back within a few business days. Some run past the 5 business days Apple quotes. None has reached the 30 days Google and D&B publish. We have not onboarded a brand outside those markets, so we cannot tell you what the wait looks like elsewhere, and the published figure is still the one that belongs in your plan.

Paying D&B to rush the number does not rush Apple's step after it. Apple states that "expediting your D-U-N-S Number creation process will not shorten this waiting period." If you are already behind schedule, the expedited fee buys less than it appears to.

The wait does not have to be idle. Design, build, and content all continue while the number is pending. Store submission is the only step that cannot start without it.

Where brands get stuck

Every common failure in this step is a mismatch between three records that should say the same thing: your incorporation documents, your D&B record, and what you typed into the store.

The lookup returns a stale address. D&B records go out of date when a company moves and never files an update. Correct the record with D&B before you enroll. An application filed against a stale record fails verification and restarts the wait.

The lookup returns two records. Companies that changed name or registered a second location end up with duplicates. Ask D&B to consolidate them and confirm which number survives.

The entity is not an entity. Apple rejects DBAs, trading names, and branches. A brand operating under a trading name has to enroll the parent company.

The work email is on a free domain. Apple requires the account's work email address to use your organization's own domain name. A Gmail address fails.

The website is a placeholder. Apple requires a public, working website on your own domain, and states that "links to social media webpages or websites that contain minimal content or display a message from a domain registrar won't be accepted." A Shopify store on your own domain satisfies this comfortably. A parked domain does not.

Google adds a failure mode the others do not have, and it does not stop at approval. Google re-checks your organization name and address against D&B for the life of the account. Its documentation is explicit about the consequence: "If Google detects any mismatches, you'll receive an email and see a banner in Play Console saying 'Your organization name or address is no longer verified.' You must fix this by the deadline provided to avoid your developer account being restricted, which would remove all of your apps from Google Play."

Treat that as a standing obligation. If you move offices or change your registered name two years after launch, update D&B and the Google payments profile in the same week. A company that misses the deadline loses its listing, its ratings, and its install base.

Register both accounts in your own name

Open the Apple and Google accounts under your company, with your work email, and keep the credentials. Your app platform should build and ship into those accounts, not into its own.

The cost only shows up when you leave. If a vendor publishes your app from the vendor's developer account, you cannot take the listing with you. Moving providers means a new listing, which starts at zero ratings, zero reviews, and no install history. Every customer who already has the app has to find and install a different one. For a Tapcart-specific migration example, see the NAPPS vs Tapcart comparison.

The D-U-N-S number is the piece you own outright. It belongs to your legal entity, it does not expire, and no app vendor can hold it. Use it to open both accounts in your own name from the start, and the ownership question never comes up again.

How NAPPS fits in

NAPPS, a native mobile app builder for Shopify and Shopify Plus brands, publishes every app from the brand's own Apple Developer and Google Play accounts. We ask for the D-U-N-S number in the pre-kickoff checklist for that reason: it is the one item with an external dependency, and it sets the floor on the launch date.

Our onboarding runs from kickoff to both apps live in 30 to 45 days. That schedule assumes the developer accounts exist on day one. When the D-U-N-S request starts at kickoff instead, the 30-day D&B wait lands on top of the build, and the launch moves. The Shopify mobile app launch checklist lists everything else worth having ready before that call, and the app store listing guide covers the submission step that comes after the accounts exist.

The bottom line

Both stores require a D-U-N-S number for an organization account, it is free, and it can take up to 30 days. Request it in the week you decide to build, not in the week you plan to submit. Open both developer accounts in your company's name while you wait, keep the D&B record matching your incorporation documents, and the only thing left between a finished build and a live app is store review.

If you are working out whether an app is worth building at all, start with how to turn a Shopify store into a mobile app.