Name the seller
Capture the seller name shown for the exact offer. Record a legal entity only when the retailer or marketplace identifies it.

DEEP DIVE · SELLER ROUTE
The same marketplace product page can host multiple sellers, fulfilment methods and return responsibilities. A comparison must identify the actual commercial route rather than borrowing trust from the platform name.
Capture the seller name shown for the exact offer. Record a legal entity only when the retailer or marketplace identifies it.
Record who stores and ships the item when that differs from the seller.
Identify who handles returns, refunds, delivery issues and product questions for the destination.
Keep the seller or offer identifier shown in retailer data so a seller change does not silently inherit the old evidence.
MARKETPLACE BOUNDARY
A marketplace may change the default seller according to price, stock, location or account. A product-level link alone may not reproduce the route that was reviewed.
Seller ratings, platform badges and fulfilment labels can be useful context, but they do not replace the exact price, shipping and return details for the selected offer.
A comparison should name the seller and fulfiller shown for the route. It should not infer reliability or authenticity from the marketplace name alone.
The seller shown for the item must remain attached to the observed price.
Warehouse and delivery responsibility can affect timing, fees and support.
Cross-border return costs and windows may differ by seller route.
A new seller requires new evidence instead of inheriting the previous record.
COMPARABLE ROUTE
The record should bind product identity, seller, fulfilment, destination, price and check time. If any binding changes, the offer returns to review.
A route tied to one named seller is easier to reproduce than a marketplace page that can rotate sellers between visits.