Contact Azenlyx
Contact Azenlyx through the site contact form for order status, product identity, Australian delivery or returns questions. Include the order number or SKU when relevant so the request can be matched accurately.
Questions about same-unit carton comparisons are easiest to answer when they avoid comparing two amounts before confirming both listings represent one 10-pack carton. Use the complete live record instead of a shortened name or saved snippet.
Information to include
- Order enquiry: order number and the email used at checkout.
- Product enquiry: exact product name and SKU.
- Delivery enquiry: destination postcode and order number.
- Damaged item: order number and a concise description; support will request photographs when required.
Adult customers only. Support cannot process an order for anyone under 18.
Prepare a focused support enquiry
Stop the benchmark when one page describes a different sale unit or currency context. The bench result is reached whenever a required field conflicts. At that bench result, do not turn a nearby image, price or search result into an assumed replacement. Reopen the exact catalogue record and ask through the current contact form when the mismatch remains. This is how Carton Comparison Bench ends with a documented answer rather than an inference.
Close the bench note with the observed date and the exact field that differed. Finish with a price-date mark that states when the live value was observed. The price-date mark prevents an old amount, picture or availability state from becoming a permanent claim. Readers can return to the same Azenlyx URL, repeat the relevant checks and understand whether the product identity stayed constant while one store condition changed.
A compact evidence format
Write the check date beside each AUD figure so an older observation stays visibly historical. The alignment line answers one narrow question: does the visible page still describe SKU SS-302? A alignment line compares the complete title with the code and sale unit, then labels the observed price and stock as current conditions. That distinction reflects the Carton Comparison principle that Two prices are comparable only after the product identity, currency and carton quantity have all been aligned.
A comparison row is incomplete until name, code, carton quantity and live amount all align. A comparison checkpoint keeps stable fields away from temporary values. For Marlboro Red Cigarettes – 1 Carton (10 Packs), the title, SKU SS-302 and one-carton wording belong on the identity side. AUD price, availability, imagery and delivery eligibility belong beside the date checked. The comparison checkpoint therefore supports the outcome that A same-unit comparison prevents a quantity difference from being mistaken for a price difference.
Mobile and desktop review habits
Ask support to compare two explicit SKUs instead of describing the cheaper-looking package. A support message should use the review margin: exact title, SKU SS-302, the specific issue and an order number only when one exists. The review margin leaves out card details, identity documents and unrelated personal history. Support can then investigate same-unit carton comparisons from a defined record instead of reconstructing the product from a nickname.
A saved comparison should point back to both live records, never only to cropped screenshots. Test a saved result with the record boundary. The final address should still open Marlboro Red Cigarettes – 1 Carton (10 Packs) and display SKU SS-302 with the expected carton wording. If a category link or redirect lands elsewhere, the record boundary records that path problem separately from stock or price, preserving a clean diagnosis for same-unit carton comparisons.