Top-ranked IT company building powerful #WordPress + #WooCommerce plugins that help businesses grow online. Founded by @IamYashKapoor.
India
- Tweets 814
- Following 98
- Followers 178
- Likes 2,526
Which pricing rule creates the most support questions in your store: quantity breaks, member prices, coupons, or tax display?
The confusing rule is a useful place to start your next checkout test.
2
13
4/ Repeat with a guest and a logged-in shopper. If their eligibility differs, the message should explain why.
2
3
3/ Add a second coupon if your store allows combinations. Check the displayed discount and the final order total against your written rule.
1
2
4
2/ Remove the qualifying product. Does the discount disappear? Reduce quantity below the threshold. Does the price reset?
1
2
10
1/ A cart discount test needs more than a successful coupon entry.
Start with the exact basket that should qualify. Then change one condition at a time:
1
2
19
Example: a $100 order uses $20 credit and $80 card payment.
Before enabling partial wallet payments, decide where a $30 refund should go. Then test that exact policy on staging.
2
25
A WooCommerce order ID is not a promise that order data lives in wp_posts.
For HPOS-compatible order access, start with wc_get_order() and the order object methods.
2
13
New free plugin "Prescription for WooCommerce" launched 🚀
Require a prescription at checkout for the products you pick. The order stays on hold until your pharmacist approves or rejects it.
No limit on orders or reviewers.
wordpress.org/plugins/devdig…
2
28
For a back-in-stock alert, test the whole path: join the waitlist, restore stock, receive the email, open its product link.
A visible signup button only proves the first step.
1
3
38
Bulk-price test: put 9 units in the cart, then 10, then return to 9.
Does the unit price change at the right boundary and reset correctly? Test a boundary in both directions.
3
20
Before adding a WooCommerce plugin, choose one page where it should do nothing.
Compare that page before and after activation on staging. It is a useful place to spot unnecessary scripts, styles or queries.
3
22
A test payment succeeded, but the WooCommerce order still says Pending.
Before asking the shopper to pay again, compare the gateway transaction with the order and inspect the payment notification.
3
26
For a share-for-discount offer, test eligibility, repeat use and combination with other coupons.
Then compare completed orders and margin. A higher share count alone does not establish that the offer paid for itself.
3
24
Before adding an installment option, check what the buyer sees before confirming: amount due now, later payment dates, fees and cancellation terms.
A payment button alone cannot explain the agreement.
3
24
3/ Fix one cause, then run the task again and inspect the result it was supposed to create. A cleared error message is not the same as a completed job.
2
11
2/ On staging, reproduce the task and inspect its error record. Note the plugin version and the last change before the failure.
1
3
17
1/ For a store task that stopped running, start with one failed action and its timestamp.
Changing several settings before reading the failure makes the trail harder to follow.
1
3
33
Price-drop notification workflow: devdiggers.com/product/wooco…
2
8