The GoBasic blog
How to cut an assortment without removing the useful choices

A smaller catalog is only useful if customers can still find what they need. Cutting half the products may simplify a warehouse list while making the shopping decision worse. Start by asking which customer jobs the assortment covers and which differences help someone choose. Product count comes later.
Begin with a candidate catalog rather than a target number of items. You might have twelve products you are considering for a launch, or a larger collection that has become hard to maintain. Put each product on its own row and leave enough space for evidence. A picture and a supplier price will not tell you whether an item belongs in the offer.
Name the purchase situation
Describe the customer and the moment they need the product. “People who like simple design” is too broad to guide a cut. “Someone replacing an everyday work bag that no longer fits their laptop” gives you compatibility, carrying, and storage questions to investigate. The same person may buy a weekend bag for an entirely different reason.
For each candidate item, finish this sentence: a customer would choose this when they need to do a particular thing under these conditions. If two rows produce the same sentence, examine whether their differences matter. If you cannot write the sentence at all, move that product into a research pile instead of treating its attractive photo as sufficient justification.
Keep the source of each assumption visible. A supplier description, a customer interview, and a founder’s preference are different kinds of evidence. All can belong in an early worksheet, but they should not receive the same confidence. Mark unknowns plainly so an empty evidence column does not quietly become agreement.
Separate a useful difference from a duplicate
A variant can serve an important need even when it adds operational work. Size, reach, capacity, handedness, or compatibility may determine whether a customer can use the product. A decorative variation can matter too, but it needs a different evaluation. Ask how someone would decide between the alternatives and whether the current product information helps them make that decision.
Consider an illustrative bag launch with three models: a compact daily bag, a larger version for a bigger laptop, and a similar large bag with different trim. The second model may cover a physical requirement the first cannot. The third might express a style preference, but it does not automatically deserve the same priority. Confirm the laptop dimensions and usable interior measurements before deciding which distinction is real.
Useful choice and clear presentation work together. Nielsen Norman Group’s discussion of feature richness and user engagement describes the learning and navigation burdens that additional interface features can introduce, while also recognizing that added features sometimes help. That is a useful caution for catalog presentation, not proof that a specific number of products maximizes sales. Test your own shopping task rather than borrowing a universal limit.
Give each product a role
Use plain roles such as core item, needed alternative, experiment, or duplicate candidate. A core item serves the central purchase situation. A needed alternative covers a meaningful requirement the core item misses. An experiment has a specific uncertainty and a limited test. A duplicate candidate appears to serve the same job without a confirmed customer advantage.
These labels should reflect the evidence you have, not become permanent rankings. The supposedly central product may perform poorly in a fitting session, while an overlooked alternative fits the audience much better. A role makes the discussion clearer because it gives the team something concrete to challenge.
Write the decision rule before reviewing your favorites. For example, every launch item must have a clear customer job, confirmed specifications, a supplier plan, and an understandable product page. A candidate can pass the first requirement and still fail the others. Keep those reasons separate; a missing specification is a repair task, while a missing customer need may justify removing the item entirely.
Count the work behind the product
Add columns for minimum order quantity, storage needs, packaging, preparation, and likely support questions. Use actual quotes and measurements when available. Mark estimates as estimates and record the date. An item that appears inexpensive from a supplier may need a different box, extra inspection, or a fragile-parts replacement process.
The shipping column should use a packed sample. UPS’s package measurement guidance explains why both size and weight matter, including dimensional weight for packages large relative to their weight. The practical step is to measure the finished carton and obtain a quote for the intended service. Do not decide which item is cheaper to ship from the product’s weight alone.
Support burden is worth describing even before you can put a reliable number on it. “Customers may need help” is too vague. “The buyer must check the width of their shelf before ordering” identifies a question you can address on the product page. “Replacement parts require three supplier emails” points to an operating problem that better copy cannot solve.
Work through a small example
Imagine a proposed desk essentials collection with a tray, two organizers, a lamp, a cable holder, and a notebook. The intended customer is setting up a compact desk for routine home administration. This example is a planning exercise, not sales data from an existing collection.
The tray holds loose documents that would otherwise spread across the desk. One organizer stores small items upright; the second has nearly the same capacity with a different finish. The lamp introduces electrical specifications and a separate support process. The cable holder solves a distinct problem if the customer uses a wired charger. The notebook may be useful, but it does not become a core item merely because it photographs well beside the tray.
A first decision could keep the tray, one organizer, and the cable holder for a test. Put the alternative organizer into a preference comparison. Defer the lamp until its requirements and support plan are understood. Ask customers about the notebook in the context of their actual paper habits. The result is a smaller initial offer with recorded reasons, rather than a visual edit disguised as customer research.
Let people try to choose
Show prospective customers the proposed products with the information you expect to publish. Give them a realistic task and ask them to select what they would need. Watch for comparisons that require information you have not provided. A customer who cannot choose may need clearer dimensions, rather than fewer options.
Ask what they would leave out and what they would have to buy elsewhere. Those questions expose unnecessary additions and missing coverage. Avoid introducing the test by praising the assortment as carefully curated. That frames agreement as the polite answer and makes it harder to learn why an item does not belong.
Record observed behavior separately from opinions. “Selected the larger organizer after checking drawer depth” tells you something about a useful difference. “Liked the collection” gives less direction. Keep the test modest enough that you can inspect each decision rather than treating a handful of reactions as a market forecast.
Make the cut reversible where possible
Before placing an order, write the proposed launch list, the deferred list, and the question that would bring each deferred item back. A removed color might return after repeated requests from the intended audience. A bulky product might return after a packaging redesign. An item with no clear role can remain off the list until new evidence supplies one.
Set a review date that matches the next real decision, such as the second purchase order. Bring customer questions, returns, stock availability, and support work to that review. A small assortment needs maintenance because the products, suppliers, and customer needs can change. The worksheet gives that maintenance a practical structure.
For your next session, score one candidate catalog on customer job, meaningful difference, information readiness, and operating work. Choose the least certain decision and test it with prospective buyers. A focused launch begins with useful coverage and understandable choices; the final item count is the result of those decisions.
Make an inquiry about the domain.
Discuss acquiring GoBasic.com.