Presell to product page: keep the right variant and offer
A presell handoff must keep the same item, option, offer and next step. Check the final store page, not just the button URL. This guide helps you record the expected state, find a broken link and test the route on mobile before you send paid traffic to it.
On this page 13 sections
- How should a campaign-tag issue be recorded?
- What is a presell-to-product handoff?
- How do you open the intended Shopify variant?
- What if an option was removed or is unavailable?
- Does the link preserve the offer and quantity?
- How do you record a stockout at the handoff?
- Which price and language checks belong to this route?
- What should the button and nearby text promise?
- How do you test redirects and the return route?
- What should a reusable handoff record contain?
- How do you measure a handoff without inventing a result?
- When is the route ready for a launch decision?
- When a presell exit is part of the intended route
| Expected state | What to observe at the destination | A reason to stop |
|---|---|---|
| Product and option | The named item and selected color, size or model | Another option appears without explanation |
| Offer contents | The included items, quantities and purchase type | A pair is promised but one item is selected |
| Price context | Currency and conditions visible for that market | A discount is implied but its condition is missing |
| Next action | The step described by the presell button | “View options” silently skips selection |
| Return route | The reader can return to the explanation | A normal return loses a necessary result |
How should a campaign-tag issue be recorded?
The offer and the measurement trail answer different questions. A product page may show the intended item while a tagged entry link changes on an earlier redirect. Conversely, a campaign field in a URL does not show that the right option or promotion reached the store.
Record the starting address with dummy values, the first changed redirect and the product destination as separate observations. Do not add customer details or private tokens to the record. If the route changes domains, document the actual session-linking setup instead of assuming that copying UTMs provides continuity.
Use the campaign-parameter redirect check to find the first changed hop. Keep this offer-state checklist as a separate decision: the route can pass one check and fail the other.
What is a presell-to-product handoff?
A presell-to-product handoff is the transition from the editorial explanation to the store step it promises. Its useful unit is the received offer state, not an isolated button click.
Consider a fictional travel-mug brand. The presell compares lids and recommends a blue mug. Its button says “View the blue mug.” The store opens with the cream model selected. The link works technically, but the route has lost a choice the reader already made. A stronger button color would leave that defect intact.
Write a short expectation before testing: blue mug, one item, one-time purchase, the market's displayed currency, product details before any purchase. That note gives two coworkers the same thing to check. It also prevents a reviewer from accepting whatever the default page happens to show.
If the page's role is still unclear, start with the presell-page primer. Use the CTA placement worksheet for where the action belongs. This guide concerns what survives after the action is taken.
How do you open the intended Shopify variant?
Shopify documents product variant deep links using the product URL with a variant query parameter and the selected variant's ID.1 Obtain the real ID from the merchant's own product data, then test the resulting URL in the current theme.
A schematic example is /products/travel-mug?variant=VARIANT_ID. VARIANT_ID is a placeholder, not a working option. Do not guess an ID from a color name or treat a product ID as a variant ID. Keep the real product route and the option it identifies in the same record.
The theme still has work to do: its displayed selection, media and price must reflect the selected variant. A URL containing the right parameter can therefore be a useful starting point without being sufficient proof. Check what the visitor sees after the page has initialized, including any theme or localization behavior.
Avoid putting customer names, email addresses or other personal information in this worksheet or its URLs. Nonpersonal product labels and authorized store routes are enough to describe the check. Do not test by placing a real order.
What if an option was removed or is unavailable?
An old deep link needs a fresh destination check after product changes. A visitor should not have to infer that a different selection replaced the option described in the presell.
Separate three observations: whether the URL loads, whether the expected variant is selected and whether that option is currently available. A product page may answer one question without settling the other two. Record each state rather than writing “link OK” after the first successful load.
For a removed option, pause the route or revise the recommendation and destination together with the merchant. For a temporarily unavailable option, verify the store's actual explanation and available next step. Do not silently move the reader to another color, size or purchase arrangement merely because it remains in stock.
Use the selector to decide which check comes first. It follows your observation; it does not inspect the store, detect inventory or authorize a launch.
Interactive
Choose the first handoff check
Select the first mismatch you observed. This selector does not inspect a store or predict sales.
Without JavaScript: wrong option → variant; wrong contents → offer; redirected market → final route; lost context → return path.
Does the link preserve the offer and quantity?
A product link does not establish every part of an offer. Item selection, quantity, discount eligibility and purchase type need their own visible checks.
In the fictional mug example, “the blue mug” and “the blue mug pair” are different promises. If the destination selects one item, an image of two mugs in the presell does not make the offer a pair. Likewise, choosing a variant does not prove a promotion applies. Record what the merchant actually sells in that route.
Check the conditions alongside the headline price: which item qualifies, whether a code or purchase condition is required, and whether the displayed arrangement is a one-time purchase or something else. Do not invent store rules to fill a gap. Ask the merchant's documented offer to resolve it before sending traffic.
The bundle landing-page guide covers the argument for buying items together. The handoff record below covers a narrower question: does the destination actually contain the described offer? Keep copy decisions and store-state checks connected without treating them as the same test.

How do you record a stockout at the handoff?
Record the option named on the presell, then check whether that exact option can be ordered at the destination. A page that loads successfully can still present an unavailable size, scent or quantity. Note the market and time because availability may differ between checks.
If the advertised option is unavailable, coordinate the ad and the presell with the store owner before sending traffic again. The stockout handoff guide separates an unavailable offer from a genuine backorder or a clearly described alternative.
Which price and language checks belong to this route?
Check the currency, language and offer shown in the intended market after any redirect or market selector. Start with the market you plan to target, then document what the destination actually returns.
Google Merchant Center's landing-page requirements address consistency between submitted product data and the landing page, including the intended variant and price context.2 Those are requirements for that program. They do not certify a Meta campaign or establish that a presell is approved by another platform.
For a separate editorial presell, use a practical comparison: the reader's described item and offer on one side, the received store page on the other. If a regional choice changes the available product, currency or shipping explanation, the presell may need a market-specific route. A translated button alone does not settle those differences.
Avoid asserting that a displayed price is permanent. Note when and where you checked it, preserve any relevant conditions and repeat the check when the offer changes. The record is an observation of a version, not a guarantee about every visitor's future session.
What should the button and nearby text promise?
Describe the destination step accurately and give enough surrounding context to explain its value. A label such as “Compare lid options” should not open an unrelated offer or skip the comparison it names.
Nielsen Norman Group describes information scent as the cues people use to judge whether a link will help meet their goal.3 Its English explanation below considers link wording, surrounding context and prior knowledge. It explains expectations around navigation; it is not a Shopify setup tutorial or a measured sales result.
For the fictional mug, “View the blue mug” and “Build your mug pair” imply different next steps. Use the wording the actual route supports. A clear nearby sentence can name a choice or condition before the button without hiding it inside an ambiguous action label.
The message-match guide connects the ad promise to the first screen. Extend that review to the product destination so a consistent opening does not end in an inconsistent offer.
How do you test redirects and the return route?
Test the full published route, including redirects, selection and a normal return to the presell. Record the final destination and the received state, not merely the href in the editor.
Open the presell in the intended layout, follow its product action, observe the selected option and use the browser's ordinary Back action. If the route begins with a quiz, check whether the explanation needed to understand its result remains available. Do not describe a reset as a purchase failure unless you observed that consequence.
Repeat with a keyboard and a narrow viewport. Can you reach the action, identify its focus and continue without an overlay hiding an essential control? On a real device when available, also check the on-screen keyboard and the browser's return behavior. A desktop viewport simulation should be labeled as such.
Keep each observation specific: final URL, selected blue option, quantity shown, return state, page version and test environment. “Works on mobile” loses too much information to reproduce a defect. The mobile presell QA workflow covers the broader layout review.

What should a reusable handoff record contain?
A useful record states the expectation, the observed route and the unresolved difference. Keep nonpersonal project labels so the note can be shared without collecting customer information.
Complete the fields with observations from your authorized store test. The generator assembles those fields locally; it does not open a URL or inspect the merchant's setup. Without JavaScript, copy the field labels into a document and make the same record manually.
Interactive
Write a product-handoff QA record
Use nonpersonal labels. This local draft does not visit or validate the store.
- Expectation and routeExpected: Fictional blue mug, one item, one-time purchase. Authorized route and version: Merchant product route, reviewed page version. Received state: Observed option, quantity and price context.
- Conditions and follow-upEnvironment: Intended market, browser and viewport. Return observation: Relevant explanation still available, or actual reset. Unknowns and next action: Unknown availability; verify with merchant before launch. This is a recorded observation, not a sales forecast or launch approval.
Without JavaScript, copy these six labels into a document. Keep untested states marked unknown.
Use “unknown” when a check has not run. A blank stock observation should not become “available,” and an untested market should not inherit the result from another. Keep the old note when retesting so a later reviewer can distinguish a new observation from an edited recollection.
How do you measure a handoff without inventing a result?
Separate action clicks, arrivals at the intended route and completed orders. They describe successive observations, and none alone proves why a visitor bought or left.
A click can be recorded before the destination finishes loading. An arrival can reach the wrong option. An order may have several paths and attribution rules behind it. Define the denominator and reporting window before comparing routes; keep missing outcomes unknown rather than substituting an intermediate action.
If a wrong variant was reproducible and the revised link now opens the intended one under the same test conditions, report that defect and verification. A claim about revenue needs separate outcome evidence. For experiments, the A/B testing guide covers the comparison design and uncertainty.
When is the route ready for a launch decision?
The route is ready for review when its observed state matches the recorded promise and unresolved issues are explicit. This checklist records your confirmations; it does not automatically approve the campaign or store.
Review the received offer
9 items
A presell-to-product handoff should carry the choice the reader just made into the store. Fix an observable mismatch before spending effort on another button variation. Keep the expectation, received state and next verification in one record, then repeat the check when the product or offer changes.
When a presell exit is part of the intended route
Keep the handoff check and the exit report on separate lines. Google Analytics defines Exits using the page or screen of the last event in a session.4 If the next step crosses the measured boundary, a last event on the presell can accompany the intended onward route. That possibility does not prove the store was received, and it does not prove that an order was lost.
For a fictional review, write the expected product and option before following the published link. Record the received destination after redirects, then name any separate click or outcome evidence. A manual route check supports an observation about that test. It is not a distribution of real visitor experiences. An analytics click record, similarly, does not guarantee that the destination completed loading or displayed the intended option.
The presell exit-rate guide adds the measurement boundary and denominator to that review. Check the actual outbound-link configuration too: Google excludes domains configured for cross-domain measurement from its enhanced-measurement outbound-click behavior.5 Keep a missing event as an uncertainty until the setup is understood. Do not alter tab behavior or a report filter just to make a departure count smaller.
| Record | What it supports | What it does not prove |
|---|---|---|
| Link action | Configured click evidence | Received product state |
| Manual destination test | Observed route in that test | Outcome for every visitor |
| Last measured step | Reporting boundary | Reason for leaving |
Before repeating a savings claim, separate a successful destination from an eligible cart. The presell discount-link review helps record which result is still missing.
Frequently asked questions
How do I link a presell to a specific Shopify variant?
Use the product URL with ?variant= followed by the actual variant ID. Verify the selected option, image and price in the published theme. A copied URL alone does not prove the received state.
Does a variant link apply the advertised discount?
A selected variant and a discount are separate states. Check the current promotion conditions and displayed offer. Do not describe an ordinary product link as a discount mechanism.
Can one product link create a bundle?
A product link alone does not prove a bundle is selected. Confirm which items and quantities the destination includes. If a specific bundle flow is needed, verify that flow with the merchant before publishing.
What should I do when the linked option is unavailable?
Stop the route or update the promise and link together after checking the store. A different default option is not an acceptable silent substitute for an advertised choice.
Should every presell button go to checkout?
Choose the step the label promises. Product inspection, option selection and checkout are different actions. Keep the necessary explanation available and test the actual destination.
Do more product-page arrivals prove the handoff sells more?
Arrivals show that the route was reached under the recorded definition. Orders, refunds and attribution require separate observations. A route improvement and a causal sales effect are different findings.
Sources
- Product variants, Shopify developer documentation. Opened October 25, 2026; variant deep links and theme state.
- Landing page requirements, Google Merchant Center Help. Opened October 25, 2026; requirements apply to Merchant Center destinations.
- Information Scent, Nielsen Norman Group. Opened October 25, 2026; link expectations and surrounding context.
- [GA4] Entrances and exits, Google Analytics Help
- Enhanced measurement events, Google Analytics Help



