Spur caught a price sorting using original prices instead of actual sale prices

Bug Book — Murad
When sorting by "Price, Low to High," sale items were being ordered by their original price, not what customers actually pay. The result: a $14.40 item appearing after a $15 one, because it was originally $16.
TYPE OF TEST
Pricing
SEVERITY
Medium

What this run

has verified.

Spur's Functional Testing agent opened the shop-all page, chose "Price, Low to High" from the sort dropdown, and checked that products reloaded correctly. The grid loaded and the sort label updated, but the prices were out of order.

Sort accuracy

Products reordering by the price customers actually pay.

Sale price handling

Discounted items slotting into the correct position in a price-sorted grid.

Filter logic

The sort function reading current sale prices.

Browse experience

Shoppers seeing a genuinely ascending price order when asked.

Compare

The customer's live site,

captured by

Spur

during the run.

Before

After

Spur Agent Analysis

Failure reason: When sorting a collection by "Price, Low to High," sale items were ordered by their original price rather than the actual sale price, so a $14.40 item appeared after a $15 one because it had originally been $16, quietly breaking the sort for exactly the shoppers hunting for the best deal.

5 - Step failed

What this

one catch saved.

5hrs

Dev time saved

Shipped, this one is subtle enough that it takes a focused investigation, someone has to work out whether the sort is pulling from the wrong price field, confirm it only affects sale items, and test the fix.

Misleading

User experience

A shopper sorting by price lowest first is trying to find the best deal. Showing them a $15 item before a $14.40 one because the cheaper item used to cost more quietly undermines the whole experience.

3hrs

Manual QA time

Catching this manually means sorting by price and then reading every product card carefully enough to notice the sequence is off, and knowing enough about the catalogue to spot.

The actual test

in

Incorrect price sorting

A 5-step functional test of the sort functionality on a collection page. Spur opened the sort dropdown, selected the price ascending option, waited for the grid to reload, confirmed the sort label updated correctly, then verified the actual product order. Four steps passed, the one that checked the numbers didn't.

Click the SORT BY dropdown

Select [Sort_label:Price, low to high] from the dropdown options

Wait for the product grid to reload

Verify the SORT BY dropdown now shows [Sort_label:Price, low to high] as the current selection

Validate that [Sort_label:Price, low to high] the first several product prices are in ascending order (lowest first)

Incorrect price order

CASE FILES

More bugs, same playbook.

Site Merchandising

Mild
Spur spotted a shoe page recommending backpacks, hats and travel bags instead of shoes

Site Merchandising

Medium
Spur found a "Fit" accordion filled with materials and sustainability info

Checkout Interactions

High
Spur caught a product page displaying tote bag reviews instead of hat reviews

Accessibility

Mild
Spur noticed the cart image for a women's sock was labelled as a men's product in the alt text

Payment

Medium
Spur spotted a $100 e-gift card showing Afterpay installments of $250 each instead of $25!

Checkout

Mild
Spur spotted a pickup-only item sitting under the "Items to be Shipped" header in the cart

UI/UX

Mild
Spur flagged three subtle issues on product pages

Checkout

Critical
Spur caught an Add to Cart button blocking every purchase