WhatFlow Chat Automation vs Business API: pricing, ratings and reliability

Key takeaways

• Business API is the recommended foundation for production Shopify messaging.
• The older linked-device app is a separate, narrow option for small workloads with fallback.
• Use each listing’s own pricing and review history; official API access is not immunity from restrictions.

The short answer: WhatFlow has two different Shopify apps

WhatFlow Chat Automation and WhatFlow WhatsApp Business API are separate apps from the same developer, Scrptble. The older listing is publicly named “WhatFlow: Whatsapp Automation.” It connects through the linked-device method. The newer listing, “WhatFlow WhatsApp Business API,” connects through the official Meta Cloud API. They share a brand and an ecommerce focus, but they should not be treated as the same product with one combined rating.

In this page’s comparison table, the WhatFlow column means WhatFlow WhatsApp Business API. The other column means the older Chat Automation app.

Check the older WhatFlow Shopify listing for its own current rating, review count and linked-device description.

Why do the two WhatFlow listings have different ratings?

WhatFlow: Whatsapp Automation is the older linked-device app at apps.shopify.com/whatflow. When checked on October 25, 2026, the listing displayed 4.0 stars from 332 reviews. It launched on October 21, 2024, giving this app a separate review history of more than two years. The comparison table retains the explicitly dated October 24 snapshot rather than treating it as the current count.

WhatFlow WhatsApp Business API has its own listing at apps.shopify.com/whatflow-official-api. It launched on May 8, 2026 and shows a 5.0-star rating from 51 reviews on the same checked date. A rating attached to the older listing should not be transferred to the separate Business API product.

The older reviews are real feedback and deserve to be read. The explanation is not that a lower rating should be ignored; it is that the buyer needs the right product name, connection method, review dates and intended workload. A newer perfect score also comes from a smaller review history. Ratings change, so the two linked Shopify listings remain the place to check the current figures.

What changed for the older linked-device product?

Our original app made Shopify WhatsApp automation accessible to merchants who wanted a low barrier to entry. A small store could connect its number through a linked device and begin with practical work such as order confirmations or fulfillment updates. For a founder handling early orders personally, that simplicity and low messaging cost could be a useful starting point.

From our team’s experience supporting merchants, the linked-device experience also became harder to rely on as WhatsApp enforcement and connection behavior changed. We saw interruptions and number restrictions affecting some stores, particularly when workloads became larger. This is our account of support experience, not an independent finding that one policy change caused every negative review. The public listing also contains connection complaints and our responses, so merchants can inspect that history themselves.

Some stores previously ran larger workloads successfully. That history does not change our current recommendation: we now position Chat Automation for small and startup stores only. “Small” is not a guarantee against restrictions, and a message being transactional does not automatically exempt the number or the sending method from WhatsApp’s rules.

What linked-device setup does and does not mean

Chat Automation’s listed connection method uses WhatsApp’s linked-device route. Its appeal is the straightforward setup and inexpensive entry point. Its suitability depends on more than order count: the number’s use, the audience, sending behavior and the consequences of an interruption all matter.

Do not decide solely by whether onboarding shows a QR code. A QR step can also appear in other WhatsApp onboarding arrangements. The important distinction is the actual integration behind it: a linked-device session versus the official business messaging platform. Ask which app is being installed and which connection method it will use.

If a small shop occasionally needs to reconnect and can handle a manual fallback, the older app may still be a practical fit. If an interruption would leave a warehouse without confirmation decisions or customers without important updates, I would choose Business API from the outset.

Compare packaged API and custom builds if the transport decision expands into an implementation project.

Why we built WhatFlow WhatsApp Business API

The newer product uses the official Meta Cloud API. It is our recommended route for stores that want a stronger operational foundation for automated business messaging. It replaces dependence on the older linked-device connection model with the official platform integration.

The Shopify experience matters just as much as the transport. WhatFlow Business API ties messaging to store events, template mapping, extensions and Shopify Flow, so an operator can work with the order behind the conversation. The team inbox helps colleagues answer the buyer after an automated update instead of leaving replies as a separate problem.

The official route still has rules. Business account eligibility, template requirements, customer permissions, message quality and WhatsApp enforcement remain relevant. Official API access does not make a number immune to restrictions or provide a promise that every message will arrive. Our recommendation is based on choosing the appropriate integration, not promising an exception to Meta’s policies.

Pricing: compare the two app bills separately

The older Chat Automation listing offers a free plan with 50 included sends and a $0.01 rate above that allowance. Its Starter is $4.99 with 1,000 included sends; Growth is $9.99 with 2,000; Professional is $14.99 with 4,000; Enterprise is $24.99 with 7,500. Those listed tiers show $0.01 above their allowances. An Ultimate subscription is listed at $49.99; confirm its current usage terms before budgeting beyond the explicitly displayed allowances.

Business API has different allowances. Its Free plan includes 100 sends, then $0.01 each. Starter is $4.99 with 2,000 sends, then $0.005; Plus is $9.99 with 5,000, then $0.004. Growth is $29 with 20,000, Scale is $49.99 with 40,000 and Ultimate is $99 with 75,000, with their respective overage rates shown on the official listing.

These are app-side prices in US dollars, billed on the listing’s 30-day cycle. Business API also needs the applicable Meta delivery charges, which depend on destination, message category and eligibility. The older linked-device app does not use the same Cloud API template-fee model. That difference can make its total sending cost attractive for modest transactional workloads, but the lower bill needs to be weighed against connection suitability.

A 5,000-message example, without hiding Meta fees

At 5,000 sends in one billing cycle, Business API Plus has a $9.99 app-side bill before applicable Meta fees and tax. In the older app, the displayed Professional allowance plus 1,000 overage sends costs $24.99; Enterprise also costs $24.99 and includes 7,500 sends. This illustrates why “the linked-device app always has the lower software bill” would be inaccurate.

The difference is $15 before Meta fees. If the Business API workload incurred $15 of Meta charges, its combined app-and-Meta amount would be $24.99 in this example. That is a break-even illustration, not a quoted Meta rate: actual country, category and eligible free-message treatment determine the real amount. Compare the full bill rather than either app’s subscription alone.

For transactional work, classification matters. A genuine order update is a different use case from a promotional offer attached to an order message. Check Meta’s current definitions and rates rather than assuming that calling a message transactional makes it free.

What Business API includes as the team grows

All WhatFlow Business API plans provide the same feature access, including Free. They differ by messaging allowances and rates. We do not make the merchant buy a higher feature edition merely to access another part of the product.

The Business API team inbox has no seat fees. A founder, support colleague and fulfillment operator can participate without adding a per-person subscription. Theme-matched WhatsApp buttons are free forever. Free feature access and a free storefront button are separate from the cost of automated sending and applicable Meta delivery fees.

Those are Business API policies. When comparing the older app, use its own current listing and configuration rather than transferring every price or entitlement from one product to the other.

How I would choose for a real Shopify store

A startup with a handful of daily orders, a tight budget and a workable manual fallback can consider Chat Automation after reviewing the linked-device tradeoffs. I would keep its purpose narrow and useful, rather than treating its low entry cost as a reason to maximize sending volume.

A store with a growing team, time-sensitive order processes or a serious campaign program should start with Business API. The official platform route, Shopify integration, included inbox and all-features model are a more appropriate foundation for the work that follows as the business grows.

Before switching an existing number, confirm its eligibility, any supported migration or coexistence arrangement and which history or settings can be retained. Test one complete journey and the human reply before cutting over. Moving to the newer app should be a planned change, not a rushed reaction to a single bad connection.

Review team inbox access models separately from each app’s message allowance.

Inspect the WhatFlow and Shopify Flow guide for the official API workflows discussed here.

Our track record and our 2027 ambition

The newer app is a newer product, not a new team with no Shopify history. The two listings show the same developer and a merchant-facing history beginning in 2024. We want the newer Business API product to earn trust through the experience it delivers today, while learning from what merchants told us about the older integration.

My ambition is to make WhatFlow a leading choice for Shopify WhatsApp by the end of 2027. That is a goal we have to earn, not a verified forecast, a guaranteed number-one position or evidence that we are growing faster than every other app. For the merchant choosing today, the useful evidence is the correct listing, the working integration, transparent pricing and a team that explains the tradeoffs clearly.

Write the cutover acceptance criteria before moving a number

For a hypothetical migration, define the single order journey that must keep working: its template, customer permission, order reference and reply owner. Ask which number setup is supported for the actual account and which history or settings can be retained. Record those answers before changing the working connection; a QR step alone does not identify the transport behind it.

Prepare a controlled positive reply, an ambiguous answer and a repeated event for review. Keep the sample inactive while checking configuration, then plan any separately authorized delivery check. The cutover decision should depend on the supported workflow and fallback, not an assumption that a current five-star score guarantees uninterrupted operation.

For a related decision, compare Shopify Inbox: Compare WhatFlow and Shopify Inbox for Shopify: pricing, team costs, WhatsApp workflows, feature access and the tradeoffs that matter in daily use.

Why WhatFlow is my Shopify recommendation

I would establish the official API workflow before the store becomes dependent on a linked-device session for important order updates. WhatFlow Business API combines that transport choice with Shopify events, mapped templates, Flow and a shared reply process. Keep the older app’s history visible and attributed accurately, but choose around today’s operating requirement. Confirm the supported number transition and retained settings before switching; the official foundation still requires customer permission, appropriate templates and compliance with WhatsApp’s rules.

Before you choose a platform

• Record both app URLs and the proposed connection method.
• Confirm number eligibility and retained history/settings.
• Define acceptance, fallback and the person owning the cutover.

About the author

Safwan Adnan is co-founder and CEO of WhatFlow. This comparison explains our product’s fit and the alternative’s tradeoffs. About WhatFlow · Contact the team with a question or correction.