Skip to main content

Common Issues

This page covers common issues merchants may experience while setting up or using CartWisp. Most issues are related to rule configuration, customer eligibility, shipping/payment settings, product conditions, or overlapping checkout rules.

If CartWisp does not behave as expected, first review the rule setup, active conditions, customer status, and Shopify configuration. In many cases, checkout behavior is caused by a rule applying correctly, but under conditions that were not expected during setup.

Rule Not Triggering​

Issue​

A CartWisp rule has been created, but checkout is not blocked or restricted when the expected condition is met.

Possible Causes​

The rule may be inactive, the condition may not match the cart scenario, the wrong product, SKU, collection, tag, or customer segment may have been selected, or the customer may not match the required eligibility condition. In some cases, the rule may depend on shipping or payment information that has not yet been entered during checkout.

How to Fix​

Check that the rule is active and saved properly. Review each condition carefully and confirm that the product, SKU, tag, collection, customer category, shipping region, or payment method matches the test checkout scenario. If the rule depends on customer information, make sure the customer is logged in with the correct account.

If available, use the Rule Simulator to test the rule before activating it on the live store.

Rule Triggering Unexpectedly​

Issue​

A rule is blocking checkout or restricting options when it should not apply.

Possible Causes​

The rule condition may be too broad. For example, a rule intended for one product may be applied to an entire collection, or a customer rule may apply to all customers instead of a specific segment. Another active rule may also be triggering at the same time.

How to Fix​

Review the rule conditions and narrow them if needed. Confirm whether the rule should apply to all products, selected SKUs, selected collections, selected customer groups, or selected regions. Also check whether any other rule is active and affecting the same checkout scenario.

A good practice is to test the same rule with both valid and invalid carts to confirm it behaves correctly.

Checkout Blocked but Customer Does Not Understand Why​

Issue​

Checkout is blocked, but the customer is confused about what caused the issue or what they should do next.

Possible Causes​

The validation message may be too vague, too technical, or missing a clear next step.

For example: Checkout validation failed.

This does not help the customer understand the problem.

How to Fix​

Update the checkout message so it clearly explains the issue and the next action.

Better message examples:

  • Minimum order value is $40. Please add more items to continue.
  • This product cannot be shipped to your selected state. Please remove it from your cart or choose another address.
  • This product requires verification before purchase. Please submit a verification request to continue.

A useful checkout message should explain what happened, why checkout is blocked, and how the customer can fix it.

Customer Verification Not Applying​

Issue​

A customer has been approved for a verification category, but they are still blocked at checkout.

Possible Causes​

The customer may not be logged into the correct account, the verification request may not actually be approved, the wrong category may have been assigned, or the checkout rule may be checking a different category than the one assigned to the customer.

There may also be another rule blocking checkout, such as a shipping restriction, payment restriction, product restriction, or regional restriction.

How to Fix​

Confirm that the customer’s verification status is approved. Check that the correct category is assigned to the customer. Ask the customer to log in using the same email address used for verification.

Then review the rule condition and confirm it references the correct customer category.

If the customer is still blocked, check whether another active rule is causing the restriction.

Verification Request Not Appearing in Admin​

Issue​

A customer says they submitted a verification request, but the request is not visible in the CartWisp admin.

Possible Causes​

The customer may not have completed the form submission, the upload may have failed, the customer may have submitted from a different account, or the request may be filtered under a different status such as Pending, Rejected, Approved, or Revoked.

How to Fix​

Ask the customer to confirm the email address used for submission. Review all verification request status filters in CartWisp. If the request is still missing, ask the customer to resubmit the verification form and ensure the document upload completes successfully before submission.

Uploaded Verification Document Not Opening​

Issue​

The merchant cannot open or view the document uploaded by a customer.

Possible Causes​

The upload may be incomplete, the file type may not be supported, the file may be corrupted, or access permissions may have failed.

How to Fix​

Ask the customer to upload the document again in a supported format. Recommended formats are usually PDF, JPG, or PNG, depending on your store configuration.

If the document still cannot be viewed, reject the request with a clear reason and ask the customer to submit a new request with a readable file.

Shipping Method Not Showing​

Issue​

A shipping method that should appear during checkout is missing.

Possible Causes​

The shipping method may be hidden by a CartWisp rule, unavailable in Shopify shipping settings, unsupported for the customer’s address, or blocked because of cart weight, product type, P.O. Box address, or regional restrictions.

How to Fix​

First check Shopify shipping settings to confirm the method is available for the customer’s shipping destination. Then review active CartWisp shipping rules to see whether the method is being hidden.

Check for rules such as:

  • Ground-only shipping enforcement
  • Oversize or weight restrictions
  • Pickup requirement by region
  • Disable P.O. Box shipping
  • Country/state restrictions
  • SKU-level shipping restrictions

Test with different products, addresses, and shipping methods to confirm the exact trigger.

P.O. Box Address Is Being Blocked​

Issue​

A customer cannot checkout using a P.O. Box address.

Possible Causes​

A CartWisp rule may be configured to disable P.O. Box shipping. This is often intentional for products that require street delivery, signature confirmation, oversized handling, or restricted shipping.

How to Fix​

Review the P.O. Box shipping rule and confirm whether it should apply to the customer’s cart. If the rule is correct, advise the customer to use a valid street address.

If the rule is too broad, adjust it so it only applies to specific products, regions, or shipping methods.

Payment Method Not Showing​

Issue​

A payment method such as Cash on Delivery, BNPL, invoice payment, or another gateway is not visible during checkout.

Possible Causes​

The payment method may be hidden by a CartWisp payment rule, unavailable in Shopify payment settings, unsupported in the customer’s region, or restricted based on cart value, product type, customer category, or order risk.

How to Fix​

First confirm that the payment method is enabled in Shopify. Then review CartWisp payment rules that may hide or restrict the method.

Common rules include:​

  • Disable COD for international orders
  • Hide COD above a threshold
  • Disable COD for specific products
  • Block BNPL for high-risk SKUs
  • Restrict invoice payment to B2B customers
  • Region-based payment rules

Test the checkout again with different cart values, products, customers, and regions.

COD Is Disabled for Some Orders​

Issue​

Cash on Delivery is available for some customers or carts but not others.

Possible Causes​

A CartWisp rule may be configured to disable COD under specific conditions, such as international orders, high-value carts, restricted products, or selected customer groups.

How to Fix​

Review all active COD-related rules. Confirm whether the cart value, customer country, product type, or customer segment matches the rule conditions.

If COD should be available for the scenario, adjust the rule condition to make it more specific.

Customer Cannot Use Discount Code​

Issue​

A customer enters a discount code, but CartWisp blocks checkout or prevents the discount from being used.

Possible Causes​

A discount validation rule may be active. The rule may restrict coupons for specific products, block coupon usage on sale items, limit one coupon per order, or prevent discount usage for restricted SKUs.

How to Fix​

Review discount validation rules and confirm whether the discount code should apply to the customer’s cart. If the restriction is correct, update the message to explain why the discount cannot be used.

Example message:

This discount code cannot be used with the selected product.

Minimum Order Value Rule Not Working Correctly​

Issue​

A minimum order value rule is not blocking checkout as expected, or it blocks checkout when the cart appears to meet the threshold.

Possible Causes​

The rule may calculate subtotal differently than expected. For example, the rule may exclude discounts, taxes, shipping fees, gift cards, or certain products depending on configuration.

How to Fix​

Review how the minimum order value is configured. Confirm whether the threshold is based on subtotal before discounts, subtotal after discounts, total quantity, product-specific value, or customer segment.

Test the rule with multiple carts to confirm calculation behavior.

Maximum Quantity Rule Blocks the Wrong Product​

Issue​

A maximum quantity rule is blocking checkout for a product that should not be restricted.

Possible Causes​

The rule may be applied to a product collection, product tag, or SKU group that includes unintended products.

How to Fix​

Review the selected products, SKUs, tags, or collections in the rule. If the rule should apply only to a specific SKU, avoid using broad product tags or collections.

Bundle Rule Blocking Checkout​

Issue​

A customer cannot checkout because CartWisp says a required bundle item or accessory is missing.

Possible Causes​

A required bundle item rule may be active. The customer may have added the main product but not the required accessory, warranty, battery, installation kit, or companion product.

How to Fix​

Review the bundle rule and confirm the required dependency. If the rule is correct, update the message so the customer knows exactly which item must be added.

Example message:

  • This product requires a compatible warranty. Please add the warranty item to continue.

If the rule is too strict, consider applying it only to specific variants or product types.

Subscription and One-Time Products Cannot Be Purchased Together​

Issue​

A customer cannot checkout with both subscription products and one-time products in the same cart.

Possible Causes​

A rule may be configured to prevent subscription and one-time product mixing.

This is usually done to simplify billing, fulfillment, or customer experience.

How to Fix​

If this behavior is intentional, update the checkout message so customers understand they need to place separate orders.

Example:

  • Subscription products and one-time products must be purchased separately. Please remove one product type to continue.

If the rule is no longer needed, disable or update it.

Country or State Restriction Blocking Checkout​

Issue​

Checkout is blocked after the customer enters a shipping address.

Possible Causes​

A country/state blocking rule or SKU-level regional restriction may apply to the cart. This is common for alcohol, CBD, supplements, hazmat products, or other restricted items.

How to Fix​

Check which product is triggering the restriction and review the shipping destination. If the restriction is correct, the customer should remove the product or use an eligible address if allowed.

If the restriction is too broad, update the rule to apply only to the intended SKUs, product tags, or regions.

Rule Simulator Result Differs from Live Checkout​

Issue​

A rule behaves one way in the simulator but differently in live checkout.

Possible Causes​

The simulator inputs may not match the live checkout scenario. Differences may include customer login status, customer tags, product variants, shipping address, payment method, market, currency, or active Shopify settings.

How to Fix​

Compare the simulator configuration with the live checkout carefully. Make sure the same customer type, product, quantity, shipping address, market, and payment method are being tested.

If differences continue, capture screenshots or a screen recording and contact support.

Multiple Rules Trigger at the Same Time​

Issue​

The customer sees multiple checkout messages or the merchant is unsure which rule is responsible for blocking checkout.

Possible Causes​

Several active rules may apply to the same cart or customer scenario.

For example, an alcohol product may trigger:

  • Age verification rule
  • State restriction rule
  • Payment restriction rule
  • Shipping restriction rule

How to Fix​

Review the rule priority and simplify overlapping rules where possible. Critical compliance rules should usually have higher priority than promotional or operational rules.

If messages are confusing, rewrite them so the most important action is clear.

Rule Conflict Detected​

Issue​

CartWisp detects conflicting rules or the merchant notices contradictory checkout behavior.

Possible Causes​

Two or more rules may be trying to enforce opposite outcomes.

Examples:

  • One rule allows a payment method while another hides it
  • One rule requires a product while another blocks the same product
  • One rule allows a shipping method while another disables it
  • One rule applies broadly while another applies narrowly

How to Fix​

Review the affected rules and determine which policy should take priority. Disable duplicate or outdated rules and make rule conditions more specific.

Use conflict detection or simulation tools when configuring advanced rule sets.

Analytics Showing High Rule Triggers​

Issue​

Analytics show that a rule is triggering more often than expected.

Possible Causes​

The rule may be too broad, customers may not understand the requirement, product pages may not explain restrictions clearly, or the message may not give enough guidance.

How to Fix​

Review the rule, customer message, and affected products. Consider adding information earlier in the shopping journey, such as on product pages, cart pages, or verification prompts.

If the rule is blocking too many valid customers, narrow the conditions.

Customers Abandon Checkout After Rule Message​

Issue​

Customers see a CartWisp message and do not complete checkout.

Possible Causes​

The message may not be actionable, the rule may be too restrictive, customers may not know how to resolve the issue, or the restriction may appear too late in the buying journey.

How to Fix​

Improve the customer message and provide a clear next step. Consider using smart suggestions or auto-fix mode where available.

Examples:

  • Please reduce this product quantity to 1 to continue.
  • This product requires age verification. Submit your verification request to continue.
  • This product cannot ship to your selected state. Please remove it or choose another eligible address.

App Installed but Rules Are Not Applying​

Issue​

CartWisp has been installed, but checkout behavior has not changed.

Possible Causes​

No active rules may have been created, rules may still be in testing mode, or rules may not match the checkout scenario being tested.

How to Fix​

Create and activate at least one rule. Confirm the rule is not only in preview or testing mode. Test with a checkout scenario that matches the rule conditions.

App Uninstalled but Previous Behavior Seems to Continue​

Issue​

After uninstalling CartWisp, the merchant still notices restrictions or checkout behavior that seems similar.

Possible Causes​

The behavior may be caused by Shopify settings, another installed app, theme customizations, shipping profiles, payment settings, or manual Shopify configurations rather than CartWisp.

How to Fix​

Review other apps, Shopify shipping settings, payment settings, discount rules, and theme customizations. If needed, contact CartWisp support to confirm whether any CartWisp configuration remains active.