Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

E-commerce Marketing › E-commerce Acquisition

Launching a New Product in an Online Store

How to launch a new product in an online store: page and feed ready first, an honest pre-order or waitlist, launch day in order, and the first weeks read.
Tutorialintermediate10 min readUpdated

What a store launch has to get right

The launch planning and tiers guide and the product launch playbook cover any launch: how much a release deserves, the plan from goals to channels, who owns each part, and the gates that decide go or no-go. They are written mostly from a product marketing team's side. A store launching one new product has narrower and more concrete work: a page, a feed entry, a decision about pre-orders, the first reviews, a sequence of messages and the weeks of stock, returns and questions that follow. Whether to launch at all is a separate question, answered before this tutorial starts by testing demand before a launch.

Most store launches that disappoint fail on one of four things, and each maps to a step below.

What goes wrongWhat the shopper seesWhere this tutorial fixes it
The announcement goes out before the page is readyThin copy, missing sizes, no delivery dateStep 2
The ad promises what the store cannot deliver"In stock" for a product that ships in weeksSteps 3 and 4
Early reviews look arrangedGlowing reviews with no disclosureStep 5
Everyone hears at onceWaitlist members find the product already sold outSteps 6 and 7

When a launch has already underperformed, the product launch underperformed diagnosis works backwards from the symptoms. This tutorial is the forward version for a store. A launch is the introduction stage of the product life cycle, and the graduation rule in step 9 marks where the product's next marketing job begins.

Before you start

  • A decision to launch. The product is going ahead, from a demand test or from the business's own judgement.
  • Stock and fulfilment dates you trust. When the stock arrives, how many units, and how fast the store can pack and ship them.
  • A working product page template that already meets the product page optimisation guide, the prerequisite for this tutorial.
  • Access to the product feed and the site's markup, or to whoever maintains them.
  • The list and its consent records, so the store knows who agreed to marketing and who only asked about this product.
  • A place to write the launch plan, including the graduation rule in step 9, before launch day.

The steps

  1. Set the launch tier and a date the stock allows

    Decide how much the launch deserves using the tiers in the launch planning guide: a major launch gets the list, ads, partners and the homepage; a minor one may get a mention in the next newsletter and a place in the category. The tier sets the effort, not the date. The date is the one the stock and fulfilment allow, as the guide to planning marketing around capacity and stock frames any campaign: demand the store cannot serve is wasted or harmful. If the stock lands on a given day, the launch is after it has been checked and booked in, with time for the first orders to be packed. Treat the date and the tier as one of the gates in the phase-gate reviews framework, so a slipped delivery moves the launch rather than the promise.

  2. Build the product page before the announcement

    Nothing announces the product until its page is complete. That means the title, a description that answers the questions a buyer of this kind of product asks, every variant with its own availability, the price, the delivery estimate and the returns summary near the button, and photographs that show scale, detail and use, all as the product page optimisation guide sets out. Commission the photographs early from a shot list built on buyers' questions, as the guide to briefing product photography describes. A new page also starts with no links and no history; the category and product page SEO guide lists in its section on launching new products how to link it from the category and related products and get it crawled quickly. Check the page on a phone before anything else goes live, because most launch traffic from email and social arrives there.

  3. Get the feed and markup ready

    The product feed entry and the page's structured data should be ready on day one, not added after the first ads run. Google's Merchant Center product data specification, as the product lifecycle guide states, requires the preorder availability value with an availability_date for preorder items, so that the ad does not promise immediate delivery; when the stock arrives, availability changes to in stock in the feed and on the page together. Product markup on the page has to agree with both, which the product structured data tutorial covers in its checks against the feed. The Merchant Center feed setup checklist is the gate for the feed itself; run its product lines for the new item rather than rebuilding them here. In Shopping, give the new product a listing group of its own so its results can be seen apart, as the lifecycle guide's section on new products without history recommends.

  4. Choose pre-order, waitlist or neither and write honest terms

    Three options exist. A pre-order takes payment before the stock is ready; a waitlist collects interest without payment; a straight launch puts the product on sale when the stock is in. Choose from the stock and the promise the store can keep, not from what sounds most exciting. Whichever is chosen, write the terms the demand test guide asks of any commitment page: what the buyer is committing to, when they will hear next, when the product will be dispatched and what happens to their money or their place if the date slips. Rules on taking payment for goods not yet available differ by country; take advice before taking pre-order payments, and treat nothing here as legal advice.

    A waitlist sign-up is a request about that product. The back-in-stock and price-drop alerts tutorial treats such a request as a request for that message and not as consent to the newsletter, as the list building and consent guide does for downloads, following the direction of the ICO's direct marketing guidance. Put any newsletter choice next to the form, unticked, as a separate decision.

  5. Seed early reviews and creator content honestly

    A new product has no reviews, and the temptation is to manufacture some. Reviews are never bought, written by the business or filtered to hide negative ones, as the e-commerce industry guide states and the reviews and social proof guide explains in its section on incentives and fake reviews. Sending product free to reviewers, customers or creators is allowed, but the free product is a material connection that has to be disclosed clearly, as the FTC's Endorsement Guides Q&A states. The disclosure travels with the review or the post, and creator agreements carry it as a term, as the influencer contracts and disclosure guide sets out. Any incentive for a review is offered whatever the reviewer writes. Plan this before launch, so honest early opinions exist by the time paid traffic arrives.

  6. Plan the launch order across waitlist, list, site and ads

    Write down who hears first, second and third, and on which day. The usual order is the waitlist, because those people asked to be told; then the engaged part of the list; then the site itself (homepage, category, navigation); then paid ads and the rest of the list. The sale and launch email tutorial sequences the emails inside that order: who hears first, staging by engagement, removing buyers before follow-ups and sending a last call only when a deadline is real. For limited stock, decide in advance what the waitlist is promised: first access for a period, or simply first notice. Do not promise first access and then open the product to everyone at the same hour.

  7. Run launch day in that order

    On the day, follow the written order and check each stage before the next. Before the first send, place a test order on the live page and check that the price, availability and delivery estimate match the feed and the ads. Send the waitlist message, watch the first orders arrive, then move to the list. Turn on the homepage and category placements, then the ads, starting with the new product's listing group. Keep one person watching stock and the inbox: an urgency or low-stock message on the page must be true at the moment it is shown, and a product that sells out mid-launch needs its availability updated in the feed and its back-in-stock alert switched on straight away.

  8. Read stock, returns and questions in the first weeks

    The first weeks show whether the product matches its page. Read four things together: sell-through against stock, add-to-cart rate and conversion rate on the product page, the return rate and its reasons, and the questions customers send or ask on the page. Volumes are small at this stage, so read them as the guide to reading small numbers advises: counts beside every rate, ranges rather than single figures, and no decision from a handful of orders. Look for clusters. Several questions or returns about the same point usually mean the page is missing a fact or a photograph, and the fix is on the page before it is in the ads.

  9. Graduate the product into the core range

    A launch ends on a rule the store chose before launch day: a date, a sales level or a count of reviews. When the rule is met, the product leaves its launch listing group and joins the core or long-tail group that fits its margin and history, as the product lifecycle guide sets out for Shopping. The launch emails stop, the homepage placement moves on, and the product's page and copy carry what was learned in the first weeks. If the rule is not met by the date the store set, that is a decision point too: change the page, the price or the audience, or let the product sit in the range without launch spend. Where shoppers hesitate over committing to a full size, the trial size product test is a design for checking whether a paid trial size beside it adds margin per first-time visitor before one is stocked for good.

A teaware shop launches a new pot (illustrative)

Illustrative example — not a real result

Teacaddle Teaware takes pre-orders for a cast-iron teapot

Teacaddle Teaware is an invented online teaware shop. Its new cast-iron teapot is due from the foundry in five weeks, in a first batch of 300. The shop treats it as a mid-tier launch: the waitlist, the list, the homepage and a Shopping listing group of its own, but no paid social.

Three weeks before stock arrives, the product page goes live with pre-orders open and a stated dispatch week. The feed carries the preorder availability value with an availability date in that week, and the page's markup matches. The pre-order terms say that if the batch is late, buyers are emailed within two days of the store hearing, and can cancel for a full refund. Six tea writers receive a pot each; the shop's covering note asks them to disclose that the pot was free, and the reviews section labels their reviews accordingly.

The 410 people on the waitlist hear first, by a day, followed by the engaged list and then the homepage and Shopping. Pre-orders take 180 of the 300 pots before the stock lands. In week two after dispatch, the shop sees 14 questions and 5 returns, and 11 of the questions are about whether the lid sits loose. It adds a close-up photograph of the lid seated and one line of copy explaining the deliberate gap that lets steam out; lid questions drop to 2 in the following fortnight. The shop's graduation rule was 40 sales a week for three weeks running; the pot reaches it in week seven and moves into the core listing group.

Once a product has graduated and later sells out, the troubleshooting page for sales not recovering after a restock covers what the gap can cost and how waitlists and honest dates protect the return.

Common mistakes

  • Announcing before the page is ready. The first visitors are the most interested ones; a thin page wastes them.
  • Letting the feed say in stock. A pre-order item needs the preorder value and an availability date, and the page has to say the same.
  • Treating the waitlist as newsletter consent. A request about one product is a request for that message.
  • Arranging early reviews. Free product to reviewers is fine only with clear disclosure; bought, written or filtered reviews are not.
  • Telling everyone at once. The waitlist was promised something; give it a head start the store can honour.
  • Setting the launch date from the calendar, not the stock. A launch that runs ahead of delivery creates refunds and complaints instead of customers.
  • Never ending the launch. Without a graduation rule, a product stays new in name and budget long after it has history.

Frequently asked questions

Should a store take pre-orders for a new product?

Only when it can state honestly when the product will be dispatched and what happens to the buyer's money if that date slips. A pre-order turns interest into a commitment and funds part of the first batch, but it also creates a promise to every buyer. In Google Shopping, Google's product data specification requires the preorder availability value with an availability date, so the ad does not suggest immediate delivery. Rules on taking payment for goods not yet available differ by country, so take advice before taking money; nothing here is legal advice.

Can a waitlist for a new product be used for the newsletter afterwards?

Not on the strength of the waitlist sign-up alone. The site's back-in-stock tutorial and list building guide treat a request about one product as a request for that message, not a newsletter subscription, following the direction of the ICO's direct marketing guidance. Offer the newsletter as a separate, unticked choice next to the waitlist form, and send people who only joined the waitlist the launch message they asked for.

How soon should a new product move out of its launch campaign?

When it reaches the level the store chose before launch, not when the launch feels over. Write a graduation rule in advance: a date, a sales level or a number of reviews, whichever the store can read reliably with its own volumes. The product lifecycle guide recommends the same for Shopping, so a product does not stay labelled new indefinitely and the launch group does not keep a budget it no longer needs.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Product data specification — Google Merchant Center Help
  2. FTC Endorsement Guides: What People Are Asking — Federal Trade Commission
  3. Direct marketing guidance — Information Commissioner's Office (UK)

Related