How to Set Up BotSpace on Shopify Without Getting Blocked

Most WhatsApp projects fail in week three, not week one. The account gets approved, the first broadcast goes out, and then the number picks up blocks, the quality rating drops, templates get reclassified as marketing, and the bill triples. This is the setup order that avoids that, using BotSpace on a Shopify store. Everything here is from Meta's developer documentation and BotSpace's own docs, checked on 18 September 2026.

If you have not decided on the platform yet, start with what BotSpace does and what it costs, then come back to this.

What do you need before you install anything?

Three things, and getting them wrong causes most of the delays.

• A phone number that is not already on WhatsApp. Meta's documentation is explicit: numbers already in use with WhatsApp cannot be registered unless they are deleted from WhatsApp first. Do not use the number your support team already uses on the WhatsApp app.
• A two-step verification PIN. This is required when registering the number, and losing it is a genuine nuisance later. Store it where your team can find it.
• A display name. You provide this at registration and it appears on your WhatsApp profile, so it should match the brand customers recognise from checkout.

Business verification through Meta matters more than people expect, and not only for trust. It is one of the routes to a higher messaging limit, which we come to below.

How do you connect BotSpace to Shopify?

The connection itself is the easy part. BotSpace's documentation gives six steps: open Integrations from the homepage, click Add integration, click Connect and then Install on Shopify, search BotSpace in the Shopify marketplace, click Install, and the integration is live.

One documented detail worth knowing if you set this up before: BotSpace notes that merchants with an existing Shopify integration have to reinstall the app in their store to access its newer triggers and actions. If your flows are running on an older install, reinstall before you build anything new.

Which Shopify events can BotSpace actually use?

This is the part that decides what you can automate, and it is worth checking against your plans before you design a flow around an event that does not exist. From BotSpace's documentation:

Two observations that matter in practice. First, the write-back actions are the useful half. Tagging an order as confirmed or cancelling it from inside a conversation is what turns messaging from a notification channel into an operations tool. Second, the documented trigger list names "Order paid" and "Checkout created" rather than a generic order created event, so check which event actually fires for your COD orders before assuming your flow will run.

How do you build a COD confirmation flow?

You assemble it from the pieces above. BotSpace markets COD verification as a capability, but its public documentation does not publish a step by step recipe for it, so treat any specific flow as something you design and test rather than switch on.

The shape that works:

1. Trigger on the Shopify event that fires for a new COD order in your setup. Verify this with a real test order rather than trusting the label.
2. Send a utility template that states the order number, items and amount, and asks the customer to confirm. Keep it factual. The moment it sells anything, it becomes a marketing template and the economics change.
3. On confirmation, add an order tag such as cod-confirmed, so your fulfilment team and your courier rules can act on it.
4. On cancellation or no reply, tag accordingly, and decide deliberately whether to cancel the order automatically. Automatic cancellation is available as an action, and it is also the fastest way to cancel orders customers actually wanted, so most stores should tag first and cancel manually until the flow is proven.
5. Offer prepayment in the confirmation message where you can. Converting a COD order to prepaid is worth more than confirming it.

The reason to bother is in the numbers. Unicommerce's India D2C Report, published April 2026 from 410 million shipments, found COD orders returned at 58% during the festive quarter against under 15% for prepaid, with RTO peaking at 39.2% in November and optimised brands reaching 21% by March. Our COD and RTO guide covers the operational side.

Why do templates get rejected or reclassified?

Because Meta decides the category, not you. Utility templates must be non-promotional, with no persuasive intent, and tied to something specific the customer asked for or a safety-critical update. Order management is explicitly listed as a utility use case.

Two rule changes are worth knowing. Since 9 April 2025, if you submit a template as utility and Meta decides it is marketing, it is approved as marketing rather than rejected, so you can end up paying marketing rates without noticing. Since 16 April 2025, businesses previously warned for miscategorisation get reclassified instantly with no 24 hour notice. Templates Meta thinks should be authentication are rejected outright on the first day of the following month.

You can request a review of a rejected utility or marketing template, or of a template approved as marketing, through WhatsApp Manager. Meta documents an outcome window of up to 60 days, which tells you how much this is worth planning around rather than appealing after the fact.

Practical rule: write confirmations and tracking updates with no offer, no discount and no persuasion in them. Put the selling in a separate marketing template you expect to pay for.

What are messaging limits and how do you raise them?

New business portfolios start at 250 messages, then step up through 2,000, 10,000, 100,000 and unlimited. Reaching 2,000 requires one of three things: verifying your business, having a partner verify it, or delivering 2,000 messages outside customer service windows to unique numbers within a 30 day period using templates with a high quality rating.

Above 2,000 the increases are automatic, on two conditions: you are sending high quality messages across all numbers and templates, and in the last seven days you have used at least half your current limit. When you qualify, the limit rises one level within six hours.

The planning consequence: get business verification done before your peak season, not during it. A store that hits festive volume on a 250 message limit has a problem that no amount of budget fixes quickly.

How do you keep your quality rating out of trouble?

Meta rates templates green, yellow and red. Green means little to no negative feedback. Yellow means negative feedback from multiple users or low read rates, and warns that the template may soon be paused or disabled. Red is the same signal, worse. New templates sit at unknown until enough data accumulates.

Read that carefully: low read rates hurt you, not just complaints. Sending marketing templates to people who never engage is not a neutral act with a wasted cost. It actively degrades the channel you depend on for order confirmations.

This is why the setup order in this article puts broadcasts last. Confirmations and tracking updates get read and replied to, which builds the rating that makes everything else deliverable.

What does opt-in actually require?

Meta's opt-in documentation requires that you clearly state a person is opting in to receive communication from your business, clearly state your business name, and comply with applicable law. Opt-in can be collected over SMS, on your website, by phone, or in person on paper. Since the November 2024 policy update, the opt-in does not have to mention WhatsApp specifically.

India adds its own layer. Under the DPDP framework, consent for marketing messages must be free, specific, informed and withdrawable, so a pre-ticked box at checkout or a purchased contact list will not do. The compliance answer and the deliverability answer point the same way here.

What goes wrong in the first month?

• Everything written as a marketing template. Confirmations get charged on every send when they could have been free inside an open service window.
• A broadcast to the entire customer list on day two. Blocks arrive, the rating falls, and templates start getting paused.
• Automatic cancellation switched on before testing. Real orders get cancelled because a customer was asleep.
• Nobody watching the inbox. Automated messages invite replies. Replies that go unanswered for a day cost more goodwill than the message earned.
• No baseline. Without your current RTO rate and tickets per 100 orders recorded before launch, you cannot prove the tool paid for itself, and it quietly gets cancelled at renewal.

For the account level background, template submission and approval mechanics, see our WhatsApp Business API guide for Shopify India.

Want the flows built and tested

Free review. Email hello@exactwhy.com with subject "WhatsApp setup" and tell us your store URL, your COD share of orders and whether your Meta business verification is done. We respond within 4 hours with the flow order we would build for your volume and which templates should be utility rather than marketing.

Prefer a form? Send it through the contact page instead. It reaches the same inbox.

A WhatsApp setup is not finished when the messages send. It is finished when a confirmed order is tagged in Shopify, the fulfilment team trusts the tag, and somebody is watching what the quality rating does next.

Verified on 18 September 2026 against Meta's WhatsApp Business Platform documentation for template categorisation, messaging limits, template quality and opt-in, BotSpace's own integration documentation, and the Unicommerce India D2C Report published April 2026.