How to Compare Product Records Before Checking Price

Manchester United Kingdom Sapphire Blue Cigarettes - 1 Carton (10 Packs)
Catalogue reference: Manchester United Kingdom Sapphire Blue Cigarettes - 1 Carton (10 Packs) (SKU SS-232)

Before comparing two Azenlyx listings, confirm four stable fields: the complete product name, SKU, sale unit and live product URL. Only after those fields match the intended record should you review the current AUD price or stock status. This identity-first order prevents similar names, equal prices or saved screenshots from being treated as proof that two listings describe the same product.

What makes a catalogue record identifiable

A useful product record separates stable identity fields from information that can change. On Azenlyx, the stable reference starts with the complete product name and SKU. The canonical product URL provides the live source, while the sale unit confirms what the listing represents. Each published product listing represents one carton containing 10 individual packs.

Current AUD price and stock status belong to a second group. They are important at the time of viewing, but they can change and should not replace the identity fields. Two different products can display the same price, and one product can display a different price on a later date.

The identity-first comparison method

1. Open the live product pages

Start from the brand catalogue or complete shop. Keep the live pages open while recording details. Do not rely on a search-result snippet, cropped screenshot or shortened product nickname.

2. Copy the complete product names

Record each name exactly as shown. Words that appear minor can distinguish separate catalogue records. Preserve brand, range, variant, strength wording where present, and the stated carton quantity.

3. Match each name to its SKU

Place the SKU beside the complete name. If the name and SKU do not form the expected pair, stop and reopen the source page. Do not continue by guessing from colour, price or a similar family name.

4. Confirm the sale unit and URL

Check that the listing states one carton containing 10 packs, then save the canonical product URL. A comparison without a confirmed unit can mistake a quantity difference for a price difference. The URL makes the record repeatable for another reader.

5. Review current fields separately

After identity is confirmed, record the current AUD price, stock status and date checked. The AUD listing-price guide provides a consistent format for those observations.

Why the field order matters

A price is not a product identifier. Stock status is not a product identifier. A product image is also insufficient when the visible packaging has not been verified against the exact record. Starting with these changeable or ambiguous fields can produce a clean-looking comparison that refers to the wrong listings.

The correct order creates a simple boundary: complete name, SKU, sale unit and URL establish which record is being reviewed; price, stock and check date describe its current condition. If a current field changes later, the identity record remains understandable.

A concise MEVIUS example

The Azenlyx catalogue contains three records with similar MEVIUS Option Purple 8 wording. They are separated by their complete names and SKUs: Premium Menthol Option Purple 8 is SS-339, Option Purple 8 is SS-355, and Premium Blueberry Blast Menthol Option Purple 8 is SS-366. The MEVIUS Option Purple 8 support guide shows the three verified catalogue pairs.

This example does not identify packaging appearance or make claims about the products. It demonstrates why shortened names are inadequate when several records share part of the same wording.

Common comparison errors

  • Using only part of the name: shared words can hide a different range or variant.
  • Comparing price first: equal prices do not prove equal products, and prices can change.
  • Omitting the SKU: a complete name without its code is harder to verify when several browser tabs are open.
  • Ignoring the sale unit: a price has little comparison value until the represented quantity is confirmed.
  • Saving only a screenshot: a screenshot can lose its page URL and observation date.
  • Treating similar records as duplicates: similar wording alone is not evidence that pages should be merged.

Reusable record checklist

For every listing in a comparison, save:

  • complete recorded product name;
  • SKU;
  • canonical product URL;
  • sale unit of one carton containing 10 packs;
  • current AUD price and date checked;
  • current stock status.

If any stable identity field is missing or inconsistent, stop before comparing current values. Reopen the live record and resolve the mismatch first.

Next step

Use this method whenever you move between a category page, product page, saved note or order enquiry. For current catalogue records, browse products by brand. For changing commercial fields, continue with How to Check AUD Prices on Product Listings.

Catalogue scope: This factual guide is for adults aged 18 or older. It explains how Azenlyx catalogue records are checked and does not make health, safety, authenticity or product-quality claims. Current price and stock information should always be read from the live product page.