ecomcloser.com

Interior designer sorting material samples on a desk

Prepare WooCommerce variable products for guided selling

In WooCommerce, variable product attributes define the choices a shopper can make, such as Finish and Width. Add those attributes to the parent product, mark them for use in variations, and create a variation for each combination you actually sell. Each variation can have its own price, image, and stock settings. For a desk offered in oak and ash at 100, 120, and 140 cm, that means up to six variations, not six separate parent products.

For guided selling, the attributes help interpret a request like “the 120 cm desk in ash,” but the matching variation determines what the shopper can buy. Use consistent labels and one width unit, resolve the request to a specific variation, and check its availability before offering to add it to the cart. If 140 cm ash was never made, leave that combination out. If it exists but is temporarily out of stock, keep the variation and represent its availability accurately.

Build the desk variation matrix before configuring the selector

Start with what the desk can actually be ordered as, not what the attribute menus make possible. Write the combinations down where the catalog owner can review them. A grid is particularly useful when each attribute value is valid on its own but not every pairing is sold. The presence of Ash in one dropdown and 140 cm in another does not prove there is a 140 cm ash desk.

Illustrative example: This first matrix assumes all six specifications exist. The identifiers below are example SKUs, not WooCommerce variation IDs. Record the actual variation ID alongside each SKU in your working sheet once the records exist. The shopper-facing labels are examples of how to read back a selection, not a requirement to create six separate product titles.

Example desk matrix with all six specifications offered
Example SKU Finish Width Selection label
DESK-OAK-100 Oak 100 cm 100 cm desk in oak
DESK-OAK-120 Oak 120 cm 120 cm desk in oak
DESK-OAK-140 Oak 140 cm 140 cm desk in oak
DESK-ASH-100 Ash 100 cm 100 cm desk in ash
DESK-ASH-120 Ash 120 cm 120 cm desk in ash
DESK-ASH-140 Ash 140 cm 140 cm desk in ash

In the variable product editor, add Finish and Width, select their values, and enable them for variations. When all six pairings are real, generating combinations gives you a starting point; it does not tell you which configurations your business sells. For a five-variation assortment, create only those five or remove the extra pairing before publishing. Assign each variation its intended price and verify that each deliberately offered combination can be selected and purchased under the right stock conditions.

For those checks, work from both directions. Starting with a row, find the storefront selection and confirm which record it resolves to. Then start with a natural request and find the row it ought to resolve to. The second check catches errors a tidy matrix can hide, such as a selector that recognizes “140 in ash” but chooses the first ash variation instead of matching both attributes.

Choose names people can say and units the catalog can compare

Use labels that describe the choice, not the team’s internal shorthand. In this example, Finish has the values Oak and Ash. If those terms describe a surface finish rather than the desk’s construction, keep that distinction in the product copy and in spoken answers. Selecting Oak does not justify calling the desk solid oak. Likewise, if shoppers call the longest edge the desk’s length but the selector calls it Width, explain which dimension the options refer to instead of treating width and depth as interchangeable.

Store and display the three widths consistently as 100 cm, 120 cm, and 140 cm. The conversation can accept equivalent expressions without adding duplicate catalog options. “One metre twenty” and “1,200 millimetres” can both map to 120 cm when they clearly refer to the desk width. A bare “120” can be understood in context after the shopper has been offered widths in centimetres. If the unit is unclear, ask. Do not round a requested measurement to the nearest offered width without telling the shopper.

Separate equivalent requests from buying constraints. “Around 120 cm” invites a discussion of available sizes; “no wider than 120 cm” rules out 140 cm. If an ash variation at exactly 120 cm is unavailable, a 100 cm ash desk might satisfy the second request but should still be offered as an alternative, never substituted. A depth question is different again: answer it only from a recorded dimension, not from the value of the width attribute.

Define aliases narrowly. “Ash finish” can map to Ash, but “the lighter one” should not automatically do so: the phrase may refer to colour, weight, or a photo the shopper just saw. Keep a short list of expressions that can be normalized directly and examples that require clarification. If you publish a Merchant Center feed, reconcile its item IDs and group IDs with the catalog, and check that each submitted variant describes the same item as its landing-page selection. Conversational aliases do not need to become feed values.

Decide who owns the stock count: parent or variation

Stock should follow the inventory the business can actually fulfil. With parent-level stock management, variations that draw from the parent use a shared quantity. Variation-level management gives a specific combination its own quantity. Neither choice is automatically right for every desk. Ask the person who counts the stock what one unit represents and whether selling one finish reduces the number of units available in the other.

Example: independently stocked finished desks. Suppose the 120 cm ash desk has sold out, but the 120 cm oak desk has not. If the warehouse counts those as distinct finished goods, manage stock on the respective variations. The shared parent quantity would not, by itself, represent that difference. A shopper asking for 120 cm ash should be told that specific version is out of stock, not that the entire desk range is unavailable or that their ash desk can be added.

Example: a genuinely shared pool. If every offered configuration draws on the same finite pool, parent stock can represent that shared limit. Before using it, check for a constraint the shared number would hide. A shared supply of base components, for example, does not establish that each top is available at every width and in both finishes. The stock setup should not let the guide promise combinations the fulfilment team cannot make.

Check the settings variation by variation rather than assuming that turning on stock management once settles the whole family. WooCommerce can use parent stock for some variations while others manage stock separately. If the family uses both, document which records draw from the shared count and which have their own. Then test a zero-stock variation next to an available sibling. If the store permits backorders for the requested option, communicate that state instead of describing the desk as in stock or making up a dispatch date.

Finally, check what shoppers can see when an option sells out. An out-of-stock variation can remain a real specification in the catalog even if the storefront hides it under the store’s stock display settings. For guided selling, keep the distinction clear: a pairing that exists but cannot be bought now should not be described as a size or finish the business never offers.

Match variation photos to finish, and verify what the photo shows

Use the parent image to introduce the desk range and variation images to show the selected version. Attach the appropriate oak image to the oak variations and the ash image to the ash variations. If the same ash photo is used for all three widths, make sure it is suitable as a finish reference. Do not let a representative photo imply that the exact 100 cm desk has the proportions or extras shown on a photographed 140 cm model.

This matters when buyers ask about a visible feature. Consider an illustrative drawer example: the ash photo shows a 140 cm desk with a drawer, but the 120 cm model has none. The photo cannot establish that a “120 ash desk with a drawer” is available. Use a better-matched photo where possible, or identify the photo as representative where it is shown. The selection summary should state whether the drawer is included based on the matched record and its verified specifications.

Test images by changing one attribute at a time. Hold width at 120 cm and switch from oak to ash: the finish reference should change accordingly. Then hold ash and switch to 100 cm: verify that any reused photo does not misrepresent included features. Also test a variation with no assigned image. Check what the storefront displays in that case and whether the result could be mistaken for confirmation of a different finish.

A mock preview of a conversation or product card can show how a label and photo might appear together. Treat it as illustrative. It does not establish that a live product was matched, that the image belongs to the current variation record, or that a cart accepted the item. Check those separately on the configured store.

Handle incomplete requests without changing the order

There are two kinds of incompleteness: the shopper has not given enough information to select a variation, or the shopper has specified a pairing missing from the assortment. They need different replies. For “I’d like an ash desk,” ask which width the shopper wants, using widths that actually exist in ash. For “140 cm in ash,” both attributes are known; asking for the finish again would miss the problem. Look up the exact pair and explain the result.

When the pairing does not exist

Suppose the example assortment excludes 140 cm ash, while 120 cm ash and 140 cm oak are both available. A useful reply is: “This desk doesn’t come in ash at 140 cm. I can offer 120 cm in ash if you want to keep the finish, or 140 cm in oak if the width matters more.” The reply identifies what each alternative changes. If the buyer says 140 cm is a minimum, drop the shorter suggestion rather than repeating it as an equivalent.

When the pairing exists but cannot be bought now

If 140 cm ash exists but is out of stock and cannot be backordered, say so before offering a different variation. Do not imply the shop has discontinued it or promise when it will return. Check that each suggested alternative is currently orderable. If the buyer wants neither, leave the selection unresolved rather than turning their interest in the original version into agreement to buy another.

When the request includes a feature outside the selector

Test “120 ash desk with a drawer.” First resolve 120 cm and Ash, then check the drawer specification. If the matched desk has no drawer, say: “The 120 cm ash desk does not include a drawer.” If a drawer-equipped alternative is recorded and available, name it and spell out the changes in width or finish. If the record is silent, say you cannot confirm the drawer. Missing information is not proof that the feature is either included or absent.

A fixed feature can be recorded for the relevant configuration without becoming a third shopper choice. If the drawer is determined by width, making Drawer a freely selectable attribute can suggest combinations the business does not sell. If buyers really can choose with or without a drawer at a given finish and width, the matrix needs to represent those distinct configurations. Either way, avoid a default or broadly matching variation that can turn an unsupported request into a different, purchasable desk.

Separate voice selection, an accepted cart action, and payment

A voice interaction can identify the right desk and read back the choice. That is selection, not a completed cart action. A reply like “I found the 120 cm ash desk” is appropriate once the exact variation is resolved. Before adding anything, confirm the combination and quantity if either is uncertain. If oak was offered as an alternative a moment ago, make sure a brief “yes” clearly refers to the item being added rather than to a request for more information.

When the shopper asks to add the selected item, send the resolved variation information and quantity through the store’s cart flow. The WooCommerce Store API cart item reference distinguishes product or variation identifiers, quantity, and variation attribute data. Validate the cart result rather than treating a submitted request as success. In a test cart, check the resulting item against the intended variation and quantity. If the item is already in the cart, check the resulting quantity, not merely whether the desk name appears somewhere in the cart.

If the cart rejects the request, report that it was not added. Stock may have changed after the spoken recommendation, or the submitted selection may not match a buyable configuration. Recheck the variation before offering another action. Do not silently retry with a different finish or width. If the cart accepts the item, describe what actually happened: “One 120 cm desk in ash is in your cart.” Do not say that the desk has been paid for. Payment is a separate checkout outcome and should be reported only when confirmed by the store.

Apply the same evidence standard to Senoji BaldinÄ—

Present the owner-described Senoji Baldinė workflow as the owner’s account, not as an independently verified transaction. Use the public product listing only for facts that can be checked there, such as the product name or a specification explicitly displayed. A listing is not evidence that a voice selection resolved to a particular internal variation, that a cart action was accepted, or that payment took place. Likewise, a mock preview illustrates an interaction; it does not verify any of those outcomes. The oak-and-ash matrix in this guide is an example, not a description of Senoji Baldinė’s assortment.

Run a catalog-to-cart acceptance test

Give the tester the approved matrix and the expected behaviour for each unavailable combination. Run the checks from a shopper’s starting point, not only from the product editor. Where practical, use a test setup to exercise stock failures without changing what live shoppers can buy. For each prompt, record the expected variation, the actual match, what the guide told the shopper, and what the cart returned if an add was requested. Keep the expected outcome explicit even when it is “no variation should be selected.”

  1. Exact match: Ask for the 120 cm ash desk. Check the variation identifier, price, photo, and stock state against the intended record. Add one and verify the cart item.
  2. Equivalent measurement: Ask for one metre twenty in ash. Expect the same variation as for 120 cm. Then ask for a desk no wider than 120 cm and check that 140 cm is not offered as a fit.
  3. Missing specification: Test 140 cm ash in a matrix where it is not made. Expect an explanation and clearly identified alternatives, with no item added.
  4. Temporary unavailability: Test a real but out-of-stock 140 cm ash variation with backorders off. Expect an availability explanation, not a claim that the pairing does not exist.
  5. Feature mismatch: Request the 120 cm ash desk with a drawer. Check the reply against the feature specification and confirm it does not use the photo to fill a gap in the record.
  6. Stock changes before the add: Select a variation while it is available, then test an add after it becomes unavailable. Expect a truthful failure message and no silent replacement.
  7. Cart is not checkout: After a successful add, stop before payment. The guide should confirm the cart contents without saying the order has been paid for.

Measure exact-match accuracy on requests that specify a valid variation, and track clarification separately for requests that leave a choice open. On orders that proceed to an add, compare the intended variation and quantity with the accepted cart item. Count rejected adds separately from wrong-item adds: the former can happen even after a correct match, while the latter means the shopper may proceed with something they did not choose. Review unsupported or out-of-stock requests for whether the reply distinguished those two states and whether each offered alternative was valid.

Make the matrix part of ordinary catalog maintenance. When a width is introduced, a finish photo changes, or stock management moves from the parent to individual variations, rerun the affected rows and one neighbouring row that should remain unchanged. That gives the catalog owner a way to trace a spoken answer through the product or variation record to the cart, without relying on a plausible label or a convincing preview.

Try the EcomCloser demo

Related guides

Sources