WhatsApp Business API Account Setup: Registration, Verification, and Number Checklist
TL;DRWhatsApp Business API account setup is easier when you treat it as an operating launch, not a form to finish. The account, business verification, WhatsApp Business Account, phone number, templates, customer opt-ins, and first automation all need to fit together.
For an ecommerce team, the goal is not merely to make a test message appear. The goal is to launch a trusted business number that can send the right Shopify message, stop when it should, route replies, and produce a measurable result.
This checklist takes you from account readiness to a tested first workflow without turning the setup into a developer-only guide.
First, Confirm You Need The API Account
The WhatsApp Business app and WhatsApp Business Platform solve different problems. The Business app is useful for manual one-to-one conversations, a simple profile, quick replies, and a small team. The platform, often called the WhatsApp Business API, is built for programmatic messaging, integrations, templates, automation, and messaging at scale.
Choose an API-backed setup when your store needs one or more of these:
Shopify-triggered messages such as abandoned checkout, COD confirmation, order updates, review requests, or winback.
Business-initiated messages sent through approved templates.
A shared team workflow for replies and customer context.
Delivery events, automation controls, or revenue reporting.
A provider, platform, or app connected to the same WhatsApp business identity.
If you only need a chat link and a person will answer every conversation manually, the Business app may be enough. If you need store events to trigger consistent messages, start planning the API account.
WhatsApp Business API Account Setup At A Glance
The setup has five practical stages.
| Stage | What you prepare or complete | Exit check |
|---|---|---|
| Prepare | Owner, business details, website, use case, phone-number plan | One person owns the setup and every business detail is consistent |
| Register | Meta business portfolio, WhatsApp Business Account, profile, provider or app connection | The WABA and business number remain under the correct business |
| Verify | Business identity, phone ownership, display name, two-step verification | The account can move beyond temporary testing safely |
| Test | Template, opt-in, test contact, Shopify event, reply route, stop rule | One end-to-end test succeeds without manual repair |
| Launch | First workflow, audience, timing, fallback, metric | The team knows what success and failure look like |
Do not start by creating assets in several employees' Meta accounts. Decide ownership first. Account recovery and vendor changes become much harder when the business does not control its own portfolio, WABA, number, or administrator access.
What To Prepare Before Registration
Collect the following before opening an onboarding wizard.
| Requirement | What to have ready | Common mistake |
|---|---|---|
| Meta access | A real employee or owner with full control of the correct Meta business portfolio | Using an agency employee as the only administrator |
| Legal business identity | Registered name, address, phone, and supporting records | Entering a brand name where legal records use another entity name |
| Public business presence | A working website with the brand, contact details, and domain-based email where possible | Submitting a placeholder site or conflicting business details |
| WhatsApp identity | Intended display name, category, description, logo, website, and support contact | Choosing a display name that is not clearly connected to the brand |
| Phone-number path | Fresh number, migration, or eligible coexistence path | Assuming an active WhatsApp number can always be reused unchanged |
| First use case | One workflow with audience, trigger, timing, copy, reply owner, and metric | Applying for the API without knowing what will send first |
| Consent plan | Where WhatsApp opt-in is collected and how opt-outs are recorded | Treating any checkout phone number as marketing consent |
| Setup route | Direct Cloud API, broad platform, or Shopify automation app | Choosing a provider before deciding who should own the workflows |
Keep the business name and address consistent across the website, Meta business portfolio, and supporting documents. Small differences such as an old address, abbreviated entity name, or missing legal suffix can create avoidable review loops.
Understand The Account Structure
Three names appear repeatedly during registration:
The Meta business portfolio owns and manages business assets and permissions.
The WhatsApp Business Account, usually shortened to WABA, contains WhatsApp phone numbers, message templates, Flows, and related assets.
The business phone number is the customer-facing sender registered under the WABA.
Your provider or Shopify app may guide the setup through Meta's embedded signup flow, but guided onboarding should not blur ownership. Confirm which business owns the WABA, which people have administrator access, and what happens to the phone number and templates if you later change software.
The provider is the operating layer. The business identity and number should remain durable business assets.
Step 1: Choose Direct, Platform, Or App-Led Setup
Your setup path determines who handles the technical work after registration.
| Route | Best fit | Your team still owns |
|---|---|---|
| Direct Cloud API | Engineering teams building custom messaging infrastructure | App setup, access tokens, webhooks, retries, templates, data sync, security, reporting |
| Broad WhatsApp platform | Teams combining marketing, sales, support, campaigns, and inbox operations | Platform configuration, agent processes, contact governance, add-ons, workflow design |
| Shopify automation app | Stores prioritizing ready-to-launch retention workflows | Flow choice, consent, template approval, timing, reply ownership, performance review |
Direct access is valid when you need custom infrastructure and have developers to maintain it. A broad platform is useful when WhatsApp is a workspace for several departments. A Shopify automation app is usually the cleaner route when store events and retention workflows are the main job.
For a fuller decision framework, read WhatsApp Business API Solution: BSP, Platform, or Automation App?.
Step 2: Create Or Select The Correct Meta Business Portfolio
Use the business portfolio that should own the WhatsApp assets long term. Give full control to at least two trusted internal administrators so one lost account does not block the business.
Before continuing, check:
Legal name, address, website, and contact details are accurate.
The website clearly connects the public brand to the business.
Only the necessary people and partners have access.
Two-factor authentication is enabled for administrators.
The employee leading onboarding can complete security prompts during the session.
If an agency or provider assists, add it through the appropriate partner or asset access instead of transferring the entire business identity to an outside login.
Step 3: Create Or Select The WABA And Business Profile
The embedded signup or direct setup flow will ask you to create or connect a WhatsApp Business Account. Choose a clear WABA name your team will recognize, then complete the business profile.
Prepare a display name that customers already associate with your store. The display name should have a clear relationship to the brand shown on your website and business records. Also prepare the business category, description, website, support email, and logo.
Do not confuse three separate checks:
Business Verification confirms the business portfolio belongs to a legitimate organization.
Phone verification confirms control of the number by SMS or voice code.
Meta Verified or an official badge is a separate trust or subscription program; it is not the same as completing basic API onboarding.
Treat those as different workstreams. Buying a badge does not replace clean account ownership, phone registration, policy compliance, or a working automation.
Step 4: Complete Business Verification
Business Verification may ask you to confirm the legal organization, address, phone number, website domain, or connection to the business. The exact method depends on the account and market.
Prepare clear, current documents that match the details entered in Meta. Depending on the business, that can include a certificate of incorporation or registration, tax document, licence, bank document, or utility record. Submit only what the live flow requests.
Use this verification checklist:
Match the legal name character for character where practical.
Use the current registered address.
Make sure uploaded documents are complete, readable, unexpired, and unaltered.
Use an email address or website domain controlled by the business when offered.
Record who submitted the verification and where replies will arrive.
Do not submit repeated variants while a review is still active.
Some test capabilities can appear before full verification, but a production plan should not depend on remaining in a temporary or restricted state. Complete verification early so it does not become the last blocker before launch or scaling.
Step 5: Choose The Phone-Number Path Carefully
The phone number is the decision most likely to create rework. Choose one path before onboarding.
| Number path | When it fits | What to verify first |
|---|---|---|
| Fresh dedicated number | You want the cleanest API-only setup | It can receive SMS or voice calls and is not tied to an unwanted WhatsApp account |
| Migrate an existing number | Customers already know the number and continuity matters | Migration requirements, downtime, chat-history implications, backups, and provider steps |
| Eligible coexistence | You want to keep using the WhatsApp Business app while adding platform capabilities | Whether Meta and the chosen provider offer coexistence for this account, region, and app version |
Do not publish a new number before it is stable, but do not hide a migration decision until onboarding day either. If the number sits behind an IVR, landline, toll-free service, or call forwarding, confirm that the verification call can reach a person or deliver the code.
Before requesting the code:
Confirm the full international number and country code.
Pause systems that may intercept the SMS or verification call.
Make sure a staff member can answer immediately.
Document whether the old app account must be migrated, removed, or retained through coexistence.
Decide how customer replies will be handled after the switch.
The safest rule is simple: let the live Meta and provider onboarding flow determine whether the number is eligible for migration or coexistence. Do not rely on an older guide that says every active number must be deleted, and do not assume every active number can coexist.
Step 6: Verify Ownership And Secure Registration
Meta verifies number ownership through an SMS or voice code. Direct Cloud API implementations also register the phone number and set a six-digit two-step verification PIN. Partner-led onboarding may handle technical API calls behind the interface, but the business should still retain the PIN and recovery details securely.
After verification:
Store the six-digit PIN in the company's password manager.
Record the WABA ID and phone-number ID if your implementation exposes them.
Confirm at least two internal admins can reach the relevant WhatsApp settings.
Remove temporary access that is no longer needed.
Note any deadline shown by embedded signup for completing registration.
Never place access tokens, verification codes, or the two-step PIN in a shared project document or chat channel.
Step 7: Prepare Templates, Opt-In, And Reply Ownership
Account registration is not launch readiness. Business-initiated messages require templates, and customers should have agreed to receive the relevant communication on WhatsApp.
For the first workflow, define:
| Control | Example for abandoned checkout | Why it matters |
|---|---|---|
| Trigger | Checkout starts but no order is created | Prevents unrelated contacts entering the flow |
| Audience | Customer supplied a valid number and relevant WhatsApp opt-in | Protects trust and message quality |
| Timing | First reminder after an intentional delay | Avoids interrupting an active purchase |
| Template | One clear reminder with a checkout link | Makes template review and customer intent clear |
| Stop rule | Stop after purchase, opt-out, invalid number, or manual suppression | Prevents embarrassing or unwanted messages |
| Reply owner | Named support queue or person | Ensures automation does not create ignored conversations |
| Metric | Recovered checkouts and revenue, plus replies and opt-outs | Shows whether the flow helps the business and customer |
Keep the first template narrow. Do not mix an order update, promotion, survey, and upsell into one message. A template with one customer reason and one next action is easier to approve, operate, and improve.
Step 8: Run One End-To-End Test
Do not call the account ready after an API sample or provider test message succeeds. Test the real business path.
For a Shopify workflow, verify all of the following:
Create a controlled checkout or order using a permitted test number.
Confirm the correct Shopify event reaches the automation.
Check that the intended customer enters the right audience.
Verify the delay and template variables.
Receive the message from the correct business number and profile.
Open every link and confirm it returns to the correct store or order.
Reply to the message and confirm the assigned person can see the conversation.
Complete the purchase or trigger the stop condition.
Confirm the next message does not send.
Check delivery, failure, reply, and conversion reporting.
That test proves more than connectivity. It proves the account, number, template, integration, customer experience, team handoff, and measurement work as one system.
Common Setup Failures And What They Usually Mean
| Symptom | Likely cause | Next check |
|---|---|---|
| Business Verification stalls | Business details and supporting evidence do not match | Compare legal name, address, website, and document freshness |
| Display name is rejected | The public brand connection is unclear or the name breaks display-name rules | Align the name with the website, profile, and business identity |
| Verification code never arrives | Wrong number, IVR interception, unsupported routing, or an existing account path was not handled | Recheck country code, SMS/voice access, migration, and coexistence eligibility |
| Test message works but automation does not | The API is connected but the Shopify trigger, audience, or template mapping is incomplete | Trace one event from Shopify to the final send decision |
| Customers reply but nobody sees it | Inbox, webhook, notification, or assignment ownership is missing | Test the reply route before launch |
| Messages send after purchase | The flow lacks a purchase stop rule or event reconciliation | Add and test suppression against the real order event |
| Account ownership is unclear | Assets were created under an employee, agency, or provider-controlled business | Audit portfolio, WABA, number, and admin ownership before scaling |
Fix the exact layer that failed. Recreating the entire WABA or switching providers is rarely the first move.
Launch The First Shopify Workflow
Start with one customer journey, not a full channel calendar. Good first workflows have a clear trigger and a result you can verify.
| First workflow | Trigger | Primary metric |
|---|---|---|
| Abandoned checkout | Checkout remains incomplete after the chosen delay | Recovered checkouts and revenue |
| COD confirmation | New cash-on-delivery order | Confirmed, cancelled, and no-response orders |
| Order update | Order or fulfillment status changes | Delivery rate and support-ticket reduction |
| Review request | Delivery is confirmed and the review delay passes | Review clicks and completed reviews |
For each flow, write down the trigger, timing, segment, message, fallback, and metric. Keep a person responsible for replies and exceptions during the first days. Review failures and opt-outs before increasing volume.
Where Retentionly Fits
Retentionly is for Shopify and D2C teams that want the WhatsApp account to power retention workflows without building the operating layer around a raw API.
The account setup establishes the business identity and sender. Retentionly connects that foundation to practical Shopify journeys such as abandoned checkout recovery, COD confirmation, order updates, review requests, winback, reorder reminders, welcome flows, and post-purchase upsells.
That makes Retentionly a strong fit when your main question is not "How do we maintain WhatsApp API infrastructure?" but "How do we launch and measure the right Shopify workflow?"
Final Account Setup Checklist
Confirm the Business app is no longer enough for the workflow you need.
Name an internal owner and backup administrator.
Clean up the Meta business portfolio details and access.
Prepare consistent legal records, website, business email, and public brand details.
Choose direct API, broad platform, or Shopify app-led onboarding.
Create or select the correct WABA under the correct business.
Prepare a supportable display name and complete business profile.
Complete Business Verification without confusing it with Meta Verified.
Choose a fresh, migrated, or eligible coexistence phone-number path.
Verify phone ownership and secure the two-step PIN.
Create one focused template and document customer opt-in.
Connect one Shopify trigger with timing, stop rules, reply ownership, and a metric.
Run the full journey from store event to message, reply, stop condition, and report.
Launch to a controlled audience before scaling.
Quick FAQs
What do I need to set up a WhatsApp Business API account?
Prepare a Meta business portfolio, consistent business identity, WhatsApp Business Account, customer-facing profile, supportable display name, eligible phone number, phone-verification access, a setup route, message templates, customer opt-in, and a first workflow to test.
Is Business Verification the same as Meta Verified?
No. Business Verification confirms the organization behind a Meta business portfolio. Meta Verified and official badge programs are separate trust products. Neither replaces phone registration, template rules, customer consent, or a working integration.
Can I use my existing WhatsApp Business app number?
Possibly. Some setups require migration, while eligible businesses may be offered a coexistence path that keeps the Business app connected. Availability varies by account, region, provider, and current Meta eligibility, so check the live onboarding flow before changing or deleting the account.
Does the phone number have to receive an SMS?
The number must complete an ownership verification step, commonly by SMS or voice call. Make sure the chosen method can reach you, especially when the number uses a landline, IVR, call forwarding, or virtual phone service.
Do I need a developer for account setup?
You need developer resources if you are implementing Cloud API infrastructure directly. A business messaging platform or Shopify automation app can guide onboarding and handle much of the technical layer, but your business still owns identity, access, consent, templates, reply processes, and workflow decisions.
What should I test before going live?
Test one real store event end to end: audience qualification, timing, approved template, business number and profile, links, customer reply, stop rule, delivery status, and conversion or operational reporting.
