FAQ

General Questions

What is Cart Guard?

Cart Guard is a WooCommerce plugin that validates shopping carts against custom rules. Enforce bundles, minimum quantities, category restrictions, and more using a server-first architecture that prevents rule bypass.

Key Features:
– ✅ Bundle enforcement (BOGO, product + accessory, etc.)
– ✅ Minimum order quantities and cart values
– ✅ Category restrictions (e.g., “No mixing wholesale + retail”)
– ✅ Stock validation (ensure bundles have sufficient inventory)
– ✅ Quantity synchronization (lock bundle item quantities)
– ✅ Automatic discounts (percentage, fixed amount, free shipping)
– ✅ Soft-fail mode (never lose sales during API downtime)
– ✅ Full analytics (violation tracking, revenue impact, trends)

How is Cart Guard different from Force Sells or WPC Bundles?

Key Differences:

Why Server-Side Matters:
– Customers can’t bypass rules by editing browser code
– Disabling JavaScript won’t skip validation
– Admin-level security for critical business rules

Is Cart Guard more expensive because it uses an API?

No. Cart Guard PRO is $49/yr ($10 cheaper than Force Sells $59/yr) and includes 100,000 API calls per month. That’s enough for 1,100+ orders per day — more than 99% of WooCommerce stores ever need.

Will Cart Guard slow down my WooCommerce store?

No. Cart Guard is actually faster than traditional client-side validation plugins (including Force Sells) on the vast majority of WooCommerce sites.
Here’s why:

• Cart validation happens via a lightweight AJAX call to our Cloud API (average response time < 50 ms worldwide).
• Your shared/discount webhost does almost zero PHP work we don’t loop through the cart, run complex conditionals, or query stock on every page load.
• Force Sells and similar plugins run all logic directly on your server in PHP on every cart/update action. On cheap shared hosts (SiteGround, Hostinger, Bluehost, GoDaddy, etc.) this quickly adds 150–400 ms of PHP processing time per cart update — exactly what kills conversion rates.

Result:
Most stores using Cart Guard see faster cart & checkout load times than before they installed it, especially on budget hosting.
Real-world numbers from live stores (Nov 2025):

• Average Cart Guard API response: 38 ms
• Average PHP execution time saved per cart update: 220 ms
• Net improvement on shared hosting: +182 ms faster cart updates

Even on Black Friday with 1,000+ concurrent visitors, the API stays under 80 ms.
If the API were ever unreachable (hasn’t happened yet), soft-fail mode instantly disables rules and lets customers check out — zero blocked sales.
Bottom line: Cart Guard is the only validation plugin that gets faster the cheaper your hosting is.
Everyone else slows you down the moment your store grows.
(Yes, that includes Chained Products, Force Sells, WPC Force Sells, YITH Bundle, etc. They all run heavy PHP on your server. We don’t.)

What happens if I go over 100,000 API calls in a month?

Your checkout keeps working 100% of the time. Rules and discounts simply pause until the next month (soft-fail mode). There are no overage fees and no surprise charges. Only massive stores (thousands of orders/day) ever need to upgrade to Agency.

Does Cart Guard slow down my store?

No. Validation is fast and optimized.

Performance Metrics:
– API validation: 50-100ms typical response time
– Object caching (Redis): Reduces load to <10ms
– Only runs when cart changes (not on every page load)
– Average impact: <0.2 seconds on cart page

Optimization Available:
– Skip validation for empty carts (saves 20-30% API calls)
– Disable AJAX validation for guests (saves 40-60% API calls)
– Batch requests for high-traffic stores (saves 50% API calls)

What happens if the API goes down?

Soft-fail mode activates automatically (configurable):

What Happens:
1. ✅ Cart validations pass (no revenue lost)
2. ✅ Checkouts allowed (customers don’t see errors)
3. ⚠️ Violations logged for manager review (yellow badges)
4. ✅ You review orders later, approve/reject with notes

API Reliability:
– Uptime SLA: 99.9%
– Average outage: <1 hour/year
– Status page: status.paretoedge.com

Configuration:
– Go to Settings → Enable/disable soft-fail mode
– Default: Enabled (protect revenue)
– Can disable for strict enforcement (regulatory compliance)

Can customers bypass rules by editing browser code?

No. All rule logic runs on our secure API server, not in the browser.

What Happens if Customer Tries to Bypass:

Scenario 1: Disable JavaScript

Customer action: Disables JavaScript in browser
Cart Guard response: Checkout still validates server-side
Result: Invalid order blocked at checkout

Scenario 2: Edit Browser Console

Customer action: Manipulates HTML/CSS to hide error message
Cart Guard response: API server rejects invalid cart
Result: Checkout blocked with server error

Scenario 3: Re-enable Checkout Button

Customer action: Uses browser dev tools to enable disabled button
Cart Guard response: Server validates every checkout attempt
Result: Order blocked OR logged as soft-fail violation for review

This is why Cart Guard uses server-first architecture. Even if customers hide error messages or manipulate browser code, the API server catches violations and either blocks checkout or logs for manager review.

Licensing & Pricing

What’s included in the FREE tier?

FREE Tier Includes:
– ✅ 1 active rule
– ✅ 100 API calls/month
– ✅ Basic analytics (dashboard widget only)
– ✅ Community support (forum)
– ✅ Soft-fail mode
– ✅ All rule types (bundle, BOGO, minimum order, etc.)
– ✅ HPOS compatible

Perfect For:
– Testing Cart Guard before committing
– Small stores (<5 orders/day)
– Single bundle enforcement
– Seasonal promotions

Limitations:
– Only 1 rule active at a time (can create more, toggle active/inactive)
– 100 API calls = ~50 orders/month
– No priority support (community forum only)

How many API calls will I use per month?

Estimate: [Daily Orders] × 2 × 30 days

Why 2x? One call when adding to cart, one at checkout.

Examples:

Actual Usage:
– View in Settings → “API Usage” section
– Shows: Calls used this month / Total allocation
– Resets: First day of each month (12:00 AM UTC)

What happens if I exceed my API call limit?

Soft-fail mode activates automatically:

What Happens:
1. ✅ Cart validations still work (checkouts allowed)
2. ❌ Violations not logged (no analytics until reset)
3. 📧 Email notification sent to admin
4. 📅 Limit resets: First day of next month

No sales lost, no downtime.

Options:
1. Upgrade tier (instant activation, prorated billing)
2. Wait for reset (first of next month)
3. Optimize usage (reduce active rules, skip empty carts)

Example:

Date: Nov 28, 2025
Tier: PRO (100,000 calls/month)
Usage: 100,347 calls (exceeded by 347)
Action: Soft-fail activated until Dec 1 reset
Revenue: No lost sales (checkouts allowed)

Can I upgrade/downgrade mid-month?

Yes.

Upgrade Process (Instant):

1. Go to Cart Guard → Settings → "Upgrade" button
2. Pay prorated difference (e.g., $25 for 6 months remaining)
3. New limits active immediately
4. API calls reset to 0 for new tier

Downgrade Process (At Renewal):

1. Contact [email protected]
2. Request downgrade to [FREE/PRO/AGENCY]
3. Downgrade effective at next renewal date
4. Keep current tier until then (no refund for partial month)

Example:

Current: AGENCY ($499/year, 1M calls/month)
Renewal: May 1, 2026
Action: Request downgrade to PRO on Nov 14, 2025
Result: Stays AGENCY until May 1, then downgrades to PRO
New price: $49/year (charged May 1)

Do you offer refunds?

Yes. 14-day money-back guarantee.

Conditions:
– ✅ Within 14 days of purchase date
– ✅ Used <10% of monthly API call allocation
– ✅ Email [email protected] with reason
– ✅ Refund processed in 5-10 business days

Non-Refundable Scenarios:
– ❌ After 14 days from purchase
– ❌ Used >10% of API calls (actively using service)
– ❌ Downgrade requests (wait for renewal instead)

Refund Process:

1. Email: [email protected]
2. Subject: "Refund request - Order #12345"
3. Include: Purchase date, reason, license key
4. Response: Within 24 hours (business days)
5. Refund: 5-10 business days to original payment method

Technical Questions

Is Cart Guard compatible with HPOS (High-Performance Order Storage)?

Yes. Cart Guard v3.1.0+ fully supports HPOS.

What is HPOS?
– WooCommerce 8.2+ feature
– Stores orders in custom database tables (faster than WordPress posts)
– Required for stores with 1,000+ orders/month

Cart Guard Auto-Detects:
– Classic mode (post-based orders): Uses legacy WooCommerce hooks
– HPOS mode (custom tables): Uses HPOS-specific hooks
– No configuration needed (works automatically)

Upgrade Path:

1. Update WooCommerce to 8.2+
2. WooCommerce → Settings → Advanced → Features
3. Enable "High-Performance Order Storage"
4. Update Cart Guard to v3.1.0+
5. Test order creation (badges should appear)

Troubleshooting:
– If badges missing after HPOS migration, update Cart Guard
– If still broken, contact support (likely plugin conflict)

Can I use Cart Guard with AJAX cart plugins?

Yes. Cart Guard includes AJAX endpoints for real-time validation.

Compatible Plugins:
– ✅ WooCommerce AJAX Cart
– ✅ Side Cart WooCommerce (Pro)
– ✅ Fly Cart for WooCommerce
– ✅ Mini Cart for WooCommerce
– ✅ WooCommerce Menu Cart

How It Works:
1. Customer adds product to cart (AJAX request)
2. AJAX cart plugin triggers Cart Guard validation
3. Cart Guard returns validation result (50-100ms)
4. AJAX cart updates with error message or success

Troubleshooting:
– If validation not triggering, disable AJAX cart plugin temporarily
– Test with standard WooCommerce cart
– If works, contact AJAX cart plugin developer for integration help
– Send them: docs.paretoedge.com/cart-guard/developers/

Does Cart Guard work with subscription products?

Yes. Cart Guard works with WooCommerce Subscriptions.

Example Rules:

Rule 1: Subscription + Upfront Supply

Trigger: Coffee Subscription (monthly)
Required: 3-Month Coffee Supply (one-time purchase)
Message: "Get 3 months upfront with your subscription!"
Discount: 15% off upfront supply

Rule 2: Subscription + Membership

Trigger: Software Subscription
Required: Premium Membership (annual)
Message: "Unlock premium features with annual membership"
Action: Block checkout (hard-fail)

Rule 3: Bundle Subscription + Physical Product

Trigger: Monthly Box Subscription
Required: Reusable Tote Bag (first order only)
Message: "Your first box includes a free tote!"
Discount: Free shipping on first order

Limitations:
– Renewal orders bypass validation (subscription already active)
– Can’t enforce rules on renewal charges (WooCommerce limitation)
– Manual subscription changes skip validation (admin override)

Can I create rules based on customer purchase history?

Not yet (planned for v1.2).

Coming Soon:
– ✅ “First-time customers only” rules
– ✅ “Must have purchased X before buying Y” rules
– ✅ “VIP customers (5+ orders) get special bundles”
– ✅ “Repeat customers unlock exclusive products”

Current Workaround: Use WordPress User Roles

Example:

1. Install "Auto Assign User Roles" plugin
2. Create user role: "VIP Customer" (5+ orders)
3. Cart Guard rule:
   - Condition: User role = VIP Customer
   - Action: Unlock VIP product category
   - Message: "VIP-only products now available!"

Roadmap:
– Submit feature requests: roadmap.paretoedge.com
– Vote on existing requests
– Get notified when feature launches

How do I migrate from Force Sells / WPC Bundles to Cart Guard?

One-click import available.

Migration Process (10 minutes):

Step 1: Keep Source Plugin Active

Do NOT deactivate Force Sells / WPC Bundles yet
Cart Guard reads rules from source plugin database

Step 2: Run Import

1. Go to Cart Guard → Rules
2. Click "Import" button (top right)
3. Select source plugin:
   - Force Sells for WooCommerce
   - WPC Product Bundles
   - Chained Products for WooCommerce
4. Click "Import All Rules"
5. Wait for progress bar (30-60 seconds)

Step 3: Review Imported Rules

1. Check imported rules count (should match source)
2. Preview 2-3 rules (verify accuracy):
   - Product selections correct?
   - Messages make sense?
   - Discount amounts accurate?
3. Mark all rules as "Inactive" initially (safe testing)

Step 4: Test

1. Activate 1 imported rule
2. Test cart validation (add products, check behavior)
3. If works correctly, activate next rule
4. Repeat for all rules (activate 5-10 at a time)

Step 5: Deactivate Source Plugin

Once all rules tested and working:
1. Plugins → Deactivate Force Sells (or source plugin)
2. Keep plugin installed for 7 days (rollback option)
3. After 7 days, delete source plugin (optional)

Troubleshooting:
– If import fails, see Troubleshooting → Import Failed
– If rules incorrect, edit in Cart Guard (don’t re-import)
– If rules missing, check source plugin has configured rules

Best Practices

How many rules should I have active?

Recommendation: 10-30 rules for most stores

Too Few (<5):
– Missing enforcement opportunities
– Not maximizing Cart Guard value
– Consider adding seasonal rules, category restrictions

Too Many (>50):
– Slower validation (more API processing time)
– Higher API call usage (approaching tier limits)
– Harder to manage (cluttered rules list)
– Customer confusion (too many error messages)

Sweet Spot: 15-25 rules covering:
– 5-10 bundle rules (BOGO, product + accessory)
– 3-5 minimum order rules (wholesale, cart value)
– 2-5 category restrictions (don’t mix X + Y)
– 3-5 seasonal/promotional rules (holiday bundles)
– 2-5 stock/quantity rules (prevent overselling)

Review Quarterly:

1. Go to Cart Guard → Analytics
2. Sort rules by "Trigger Count" (last 90 days)
3. Deactivate rules with <10 triggers (unused)
4. Archive seasonal rules (activate when needed)

Should I use soft-fail or hard-fail mode?

Depends on business requirements.

Use HARD-FAIL (Block Checkout):

When Enforcement is Critical:
– ✅ Safety compliance (can’t ship incompatible products)
– ✅ Legal/regulatory rules (age verification, licensing)
– ✅ Stock management (prevent overselling limited inventory)
– ✅ Policy must be enforced (no exceptions, no manual review)
– ✅ Revenue protection (prevent abuse, fraud)

Example Scenarios:

Rule: "Laptop + Warranty bundle required"
Reason: Company policy, no exceptions
Mode: HARD-FAIL (block checkout, show error)

Rule: "Chemical products require safety certification"
Reason: Legal compliance, liability risk
Mode: HARD-FAIL (cannot ship without cert)

Use SOFT-FAIL (Log but Allow):

When Flexibility Matters:
– ✅ Promotional bundles (suggestions, not requirements)
– ✅ High-traffic periods (Black Friday, avoid blocking valid orders)
– ✅ New rules (test before strict enforcement)
– ✅ Revenue priority over enforcement (don’t lose sales)
– ✅ Manual review preferred (yellow badge workflow)

Example Scenarios:

Rule: "Coffee + Mug BOGO promotion"
Reason: Marketing campaign, not policy
Mode: SOFT-FAIL (allow checkout, review later)

Rule: "Wholesale minimum 10 units"
Reason: Guideline, exceptions granted for VIP customers
Mode: SOFT-FAIL (log violations, manager reviews)

How to Configure:

Global Setting:

Cart Guard → Settings → "Enable Soft-Fail Mode" checkbox
- Checked: All rules soft-fail (log violations, allow checkout)
- Unchecked: All rules hard-fail (block checkout on violation)

Per-Rule Setting (Coming in v1.2):

Future feature:
Edit rule → "Enforcement Mode" dropdown
- Hard-fail (block checkout)
- Soft-fail (log and allow)
- Conditional (hard-fail for guests, soft-fail for registered customers)

How often should I review analytics?

Recommended schedule:

Daily (5 minutes):

1. Check Dashboard → "Orders Needing Review" widget
2. Review yellow badge orders (pending manager approval)
3. Monitor API usage (approaching limit?)
4. Check "Recent Violations" widget (any unusual spikes?)

Best time: Morning before processing orders

Weekly (15 minutes):

1. Go to Cart Guard → Analytics
2. Review "Violation Timeline" chart (last 7 days)
3. Identify trends:
   - Are violations increasing? (rule too strict?)
   - Are specific rules triggering too often? (need adjustment?)
4. Export violations CSV (archive for records)
5. Check "Top Violating Rules" (optimize underperformers)

Best time: Friday afternoon (wrap up week)

Monthly (1 hour):

1. Full analytics deep dive (30-day review)
2. Revenue impact analysis:
   - Total revenue saved (blocked invalid orders)
   - Soft-fail ROI (prevented lost sales during API issues)
3. Rule optimization:
   - Deactivate unused rules (<10 triggers/month)
   - Archive seasonal rules not currently active
4. Tier evaluation:
   - If usage >80%, plan upgrade
   - If usage <20%, consider downgrade at renewal
5. Export rule performance CSV (management reports)

Best time: First Monday of each month

What’s the best way to write customer messages?

Follow these guidelines:

✅ BE SPECIFIC

Bad:

"Error: Missing item"

Good:

"Add {product_name} to complete your bundle and save 20%!"

Why: Customer knows exactly what to do.

✅ BE HELPFUL

Bad:

"Cart invalid"

Good:

"Laptop bundle requires Charger. Click here to add →"

Why: Message guides customer to solution.

✅ USE VARIABLES

Available variables:
– {product_name} – Links to required product page
– {min_qty} – Shows minimum quantity required
– {quantity} – Shows current quantity in cart
– {cart_total} – Shows current cart total
– {min_total} – Shows minimum cart total required

Example:

"Add {min_qty} more {product_name} to reach wholesale minimum"

Renders as:
"Add 7 more Coffee Beans (1lb) to reach wholesale minimum"

✅ BE POSITIVE

Bad:

"You can't checkout without adding X"

Good:

"Complete your bundle to unlock checkout!"

Why: Positive framing reduces customer frustration.

✅ TEST THOROUGHLY

Process:

1. Create rule with custom message
2. Open store in incognito window (act as customer)
3. Add products to cart
4. Read message as if you're customer
5. Ask: Does it make sense? Is action clear?
6. If confusing, revise and test again

Next Steps

New Users:
1. ✅ Complete Quick Start → Getting Started
2. ✅ Create your first rule → Creating Rules
3. ✅ Test validation → Creating Rules: Testing
4. ✅ Review analytics daily → Analytics

Existing Users:
1. ✅ Import rules from plugins → Getting Started: Migration
2. ✅ Enable advanced features → Advanced Features
3. ✅ Set up review workflow → Managing Orders
4. ✅ Optimize performance → Troubleshooting: Performance

Need Help?
– 📧 Email: [email protected]
– 💬 Forum: community.paretoedge.com
– 📚 Docs: docs.paretoedge.com
– 🎥 Videos: youtube.com/@paretoedge

Feature Requests:
– Submit ideas: roadmap.paretoedge.com
– Vote on existing requests
– Get notified when features launch

Last Updated: November 14, 2025
Plugin Version: 1.0

← Back: Troubleshooting | Home: Documentation