Cartsaver Troubleshooting Guide: OTP, WhatsApp and Verification Fixes

Symptoms, causes and fixes for the most common Cartsaver issues: codes not arriving, codes rejected, missing checkout blocks, unconfirmed orders and quota limits.

11 minutes Updated Nov 2, 2026

The Cartsaver troubleshooting guide is a symptom-by-symptom checklist for the cash on delivery verification problems Shopify merchants report most: codes that never arrive, correct codes rejected, a missing thank-you page block, and orders that stay unconfirmed. Each section names the likely causes in order of frequency, then the fix.

Cartsaver is a Built for Shopify app by Xtnd that confirms cash on delivery orders on WhatsApp or SMS before you ship, through the official WhatsApp Business API. Almost every issue below can be diagnosed in two places: the order itself in Shopify, and the Logs page in Cartsaver.

Start here: read the logs before changing settings

Before you change anything, open Cartsaver's Logs page, pick the right tab (OTP Verification, Order Notification, Abandoned Messages or Order Follow-Ups) and find the customer's phone number. For a long list, export the tab to CSV and search it in a spreadsheet. The log tells you whether a message was sent at all, on which channel, and what happened to it. That one check usually splits the problem in three:

  • No log entry for the order. Cartsaver never tried to send. The cause is a setting, the plan's message allowance, or the order itself (for example, it was not a COD order).
  • A failed entry, or an error message in place of the status. Cartsaver tried and the channel refused. When the provider returns an error, the log shows that error instead of the status badge, and it usually names the cause, such as a number that is not on WhatsApp.
  • An entry marked sent (or verified, once the customer entered the code or tapped the WhatsApp confirmation button). The message left Cartsaver. The issue is on the customer's side: the wrong number, a blocked business chat, or a phone without signal.
Cartsaver OTP verification logs showing channel, country and verification status

The guide to reading Cartsaver logs explains every log type and how to export them.

What if the customer did not receive the code or WhatsApp message?

When a customer did not receive the code or WhatsApp message, the cause is usually a mistyped phone number, a used-up monthly message allowance, a customer who is not on WhatsApp, a country you have not allowed, a confirmation delay still running, or a blocked number. Check them in that order.

This is the most common report. Work through the causes in this order.

1. The phone number is wrong

Customers mistype numbers or leave out digits. Cartsaver adds the country code for you, based on the country in the shipping address, so a local Egyptian number such as 010… is fine. A typo is not: open the order and compare the phone number with what the customer says. If many orders arrive without a phone number, make the phone field required in your Shopify checkout settings so every COD order carries one.

2. The plan's monthly message allowance is used up

Each plan includes a set number of messages a month (10 on Free, up to 60,000 on Elite for stores in Egypt, India and Pakistan, and up to 8,000 for stores elsewhere), shared by WhatsApp and SMS, and cross-sell messages use them too. When the allowance runs out, new messages stop, with no automatic fallback, until the next 30-day cycle or until you upgrade. The dashboard shows the credits left this cycle. If codes stopped arriving for everyone at once, check this first. Plans and limits are on the pricing table.

3. The customer is not on WhatsApp or blocks business messages

A WhatsApp message cannot reach a number that does not use WhatsApp, and some customers turn off business messages in their WhatsApp privacy settings. The log shows a failed entry with the reason. WhatsApp order confirmation is sent on WhatsApp only, so these customers cannot confirm that way. If many of your customers are not on WhatsApp, use the pre-checkout pop-up or Fast Checkout instead, which can send the code by SMS to Egyptian numbers.

4. The customer's country is not allowed for WhatsApp, or SMS cannot reach it

You can accept WhatsApp verification from every country or only the countries you select. If you restricted the list, a customer from another country will not get a WhatsApp message. SMS codes on Cartsaver's default sender reach numbers in Egypt; for other countries rely on WhatsApp, or connect your own SMS provider (available from the Scale plan).

Cartsaver settings for choosing SMS, email or WhatsApp as the OTP channel

5. The confirmation message delay is still running

With WhatsApp order confirmation you can send the message right away or up to 48 hours after the order. If the delay is set to several hours, "I did not get anything" may simply mean "not yet". Check the delay setting before treating it as a failure.

6. The number is on your blocked list

Cartsaver does not send codes to blocked phone numbers. If a real customer was blocked by mistake, unblock the number on the Blocked Contacts page (Block Contacts in the Cartsaver menu).

The docs keep a step-by-step ladder for this symptom: customer didn't receive the OTP.

Why is the customer's code rejected?

A code the customer believes is right is usually rejected because they typed an older code after asking for a new one, tried too many times within a minute, used a different phone number, or pasted extra spaces. Cartsaver codes are 4 digits, and a new one can be requested after 60 seconds.

Cartsaver codes are 4 digits, and a customer can ask for a new one 60 seconds after the last. When a customer insists the code was right, the cause is almost always one of these:

  • An older code was used. After the customer asks for a new code, only the newest one should be entered. Customers who tap resend several times often type the first code they see.
  • Too many tries in a row. Cartsaver accepts 5 code attempts per 60 seconds for the same phone number and blocks further tries until that minute is up, to stop guessing. Ask the customer to wait a minute and try again.
  • A different phone or number. The code belongs to the phone number on the order. A customer reading WhatsApp on one number and typing on another device may mix them up.
  • Extra spaces from copy and paste. Ask the customer to type the code by hand, or tap the one-click verify link instead.

With one-tap WhatsApp confirmation there is no code to type: the customer taps Confirm on the order summary. If many of your customers struggle with codes, switching to one-tap WhatsApp order confirmation removes this whole class of problem.

The confirmation block or pop-up does not appear on the store

Cartsaver adds a confirmation block on the thank-you and order status pages, and the pre-checkout pop-up and Fast Checkout run on your storefront. If customers do not see them:

  • The app embed is off. In Shopify, open Online Store, Themes, Customize, then App embeds, and turn Cartsaver on. Save.
  • The checkout block was never added. The thank-you and order status block is a checkout extension and is not added automatically. Use the Add Widgets button in Cartsaver, which opens the Shopify checkout editor, place the block on both the Thank you and Order status pages, and save. The WhatsApp confirmation message is still sent without the block; the block just shows the status on those pages.
  • The pre-checkout pop-up does not open. It needs Cartsaver's app embed switched on in your theme. The Cartsaver dashboard shows whether the theme extension is active.
  • The theme is not Online Store 2.0. Theme app extensions need a 2.0 theme. Older vintage themes do not show app blocks.
  • Another app owns the same spot. Post-purchase upsell, loyalty or review apps that also use the thank-you page can push the block out of view. Reorder or disable them to test.
  • Browser cache. Test in a private window before assuming it is broken.

Fast Checkout has its own checks: it must be switched on in Cartsaver, the Fast Checkout card must show Ready (not Action Required, which means the theme extension is off), and the plan's Fast Checkout allowance must not be used up (10 orders on Free, 450 on Advanced, 2,500 on Unlimited, unlimited on Scale, Ultra and Elite). The Fast Checkout guide covers the setup.

Why do orders stay unconfirmed, or good orders get cancelled?

Orders stay unconfirmed or good orders get cancelled when your settings are stricter than your customers' habits: the wait before acting is too short, auto-cancel was switched on before you reviewed flagged orders, or the Cancel button cancels instead of flagging. Lengthen the wait and start with mark as high risk.

If too many orders end up high risk or cancelled, the settings are usually stricter than your customers' habits:

  • The wait is too short. Unconfirmed orders are marked high risk or cancelled after a wait you set, from 30 minutes to 24 hours. A 30-minute wait catches customers who order and then go to sleep. Try 12 hours.
  • Auto-cancel was switched on too early. Start with mark as high risk, review what lands there for a week, then move to auto-cancel.
  • Customers tap Cancel by mistake. If that happens, set the Cancel button to flag the order for review instead of cancelling it.

Cross-sell or order update messages are not sending

  • Cross-sell runs only on WhatsApp and only after the customer confirms. Check that it is switched on, that its products are in stock, and that the customer confirmed on WhatsApp rather than by SMS.
  • Order updates are switched on one by one (created, fulfilled, cancelled). Check that the trigger you expected is on.
  • Any message that needs Meta's approval, such as a custom note in the order created message, waits until it is approved.
  • Customers message back asking about their order. Replies to your order messages are not order updates. To answer "where is my order?" automatically with the status and tracking, turn on WhatsApp order auto-reply.

Your own WhatsApp number or sender name is not being used

On the Scale plan and up you can send from your own WhatsApp number and use a branded SMS sender name. If messages arrive from the default sender instead, your setup may still be waiting for approval, or Meta may be rejecting your number's messages because of an unpaid Meta balance. In that case order confirmations and notifications go out from the default sender until you pay it and reactivate your number; campaigns stop until then. A number Meta restricts for quality or policy reasons does not switch to the default sender. See the sender ID guide for the requirements.

When to contact support, and what to send

If the logs and the checks above do not explain it, contact Cartsaver support on WhatsApp at +20 102 222 3633. Send these details so the team can look it up straight away:

  • Your store's myshopify.com address.
  • The order number.
  • The customer's phone number in international format.
  • The channel (WhatsApp or SMS) and the status shown in the log.
  • Roughly when it happened, and what you have already tried.

If several customers report the same problem within a short time, say so: it can point to an issue with a provider rather than your settings.

Frequently asked questions

Why didn't my customer receive the OTP?

The most common reasons are a wrong or incomplete phone number, a used-up monthly message allowance, or a customer who is not on WhatsApp. Search the order in Cartsaver's logs: if there is no entry, check settings and your allowance; if the entry failed, read the reason shown with it.

What happens when I run out of WhatsApp messages?

New messages stop until the next 30-day cycle starts or you upgrade your plan. The Cartsaver dashboard shows the message credits left this cycle, so check it before big sales.

Why doesn't the Cartsaver block show on my thank-you page?

The block is not added automatically. Use Add Widgets in Cartsaver to open the Shopify checkout editor, add the block to both the Thank you and Order status pages, and save. The WhatsApp confirmation message is sent even without the block.

Why are real orders being cancelled?

The wait before unconfirmed orders are cancelled is probably too short, or the Cancel button is set to cancel instead of flag. Lengthen the wait, or switch to mark as high risk while you review.

Still need help?

Our support team is always ready to assist you with any questions.

Before you contact us