Start with one empty AIO hardware SKU when your team still needs a clean sample baseline. Add a second only when it solves a different, documented buyer or operating need. Keep expansion on hold when the reason is vague or when no one owns every added workstream.
AIO means all-in-one empty hardware with the reservoir, heating system, and battery in one device. A SKU, or stock keeping unit, is an internal code used to track a product in inventory and sales records.[1]
For this decision, the important question is not how many choices look good in a catalog. It is whether every hardware SKU has a clear job and can be managed as a separate item.
Begin with the problem, not the product
Write down the reason you are considering another SKU before choosing a device. Name a real difference that is not available in the current configuration. It might be a requested fill capacity, a different body shape for a confirmed retail setup, a dual-reservoir use case, or a fixed-output test that removes mode selection.
Avoid broad reasons such as “customers want options” or “competitors carry more devices.” Those statements do not tell your team what to test or what evidence would justify a launch. A stronger note identifies who raised the need, what the current product cannot do for that case, and what the next sample should answer.
The first SKU does not have to serve every buyer. It needs to serve one defined starting use well enough for the team to learn from samples, filling work, buyer questions, support requests, and reorders. A second SKU should create new information instead of dividing the same information between two similar items.
Know when a difference needs its own SKU
Shopify describes SKUs as internal codes used to track inventory and report on sales.[1] In practice, a separate hardware configuration usually needs a separate SKU when receiving, production, sales, or support must distinguish it from the current item.
Capacity, body format, reservoir layout, activation method, and output controls can all change the work around a product. A packaging-only variation may also need its own finished-goods SKU even when the empty hardware is unchanged. Your internal code should make the meaningful difference clear enough that staff can identify the correct item without relying on a vague label such as “white AIO.”
Use the supplier name, model name or number, capacity, and version information that your team can verify. If two items require different filling instructions, packaging, training, or reorder notes, treating them as the same SKU can hide useful differences.
Look for evidence that the second job is real
Before adding a product, review the evidence already created by the first one. List completed sample requests, buyer questions, fill records, service cases, repeat orders, inventory movement, and requests that the current configuration could not answer.
Label the source of each signal. A buyer request, a sales record, and an internal idea do not carry the same weight. An idea may justify ordering a small sample. It does not automatically justify packaging inventory, training, photography, sales copy, and a launch.
Ask these questions:
- Who has requested the difference, and how often has it appeared?
- What part of the current hardware or process does not answer the need?
- Could a setting, instruction, package, or clearer product description solve it without another hardware SKU?
- What will the new sample teach that the current sample cannot?
- What result would make the team stop or postpone the addition?
Do not invent a universal threshold. Set one that belongs to your business and can be checked later. List qualified requests, a completed process review, finished packaging work, and a named person who can manage the additional work.
Compare four different sample questions
GreenDeagle's current product pages describe four hardware paths. The differences below can help a buyer choose what to sample. They do not prove that a device fits a particular oil, filling process, or future production run.
| Hardware | Public difference | What changes in the sample review | Operating effect to plan for |
|---|---|---|---|
| Briar | A 1.0mL glass AIO with Soft, Balanced, and Strong output modes.[2] | Record the selected mode beside every observation. Results from one mode do not describe the other two. | One hardware item creates three setting conditions, but the settings remain part of the same named product. |
| Nook | A 2.0mL[3] reservoir in a compact 58 × 32 × 15mm body with fixed 2.8V output.[3] | Record the actual oil, fill process, capacity, and handling of the short, wide format. Fixed output removes the need to choose a mode. | The capacity and package footprint differ from a slim 1.0mL AIO, so receiving, packaging, and stock records must stay separate. |
| Lumen | Two independent 1.0mL reservoirs with Left, Right, and Both selections.[4] | Identify the fill on each side. Record Left, Right, and Both as separate observations. | Two fill identities and three selection states add instructions, review steps, and support questions that do not exist on a single-reservoir device. |
| Wisp | A slim 1.0mL format specified for rosin sample programs, with fixed 1.8V output and a 97 × 19 × 10mm body.[5] | Record the actual rosin and filling conditions. The page's rosin positioning is a starting point for testing, not a compatibility promise. | Its narrow body needs a different packaging footprint and its own inventory record. |
These are not four automatic additions to a lineup. They are four different questions a sample program can answer. Choose the question that matches the documented need, and confirm current order details on the relevant product page before buying.
Count the work around a second product, not only the device itself.
Count the work that arrives with another SKU
The purchase price is only one part of the decision. A second SKU can require a separate sample plan, fill instructions, package fit, product page, photography, inventory location, staff training, service notes, and reorder check. Similar-looking items also need clear receiving and storage labels.
Write down the additional work before approving the item. Name the person responsible for each part and the evidence they need. If the work has no owner, the product is not ready to enter the lineup even if the sample itself looks promising.
Make a one-page work list. Put the proposed SKU at the top, then add one line for receiving, filling, packaging, inventory, sales copy, staff instructions, buyer service, and reordering. Each line needs an owner, a due date, and the record that completes the work. Leave the status open when evidence is missing.
Use the check to expose work that sits in another department. It also gives the team a review point before launch inventory is ordered. If one person cannot explain which record closes a line, keep that line open and return to the sample question.
This step also reveals when one product can answer the question without another SKU. Briar's three output modes, for example, are settings inside one 1.0mL product.[2] If the unmet need is a different output condition, the team may be able to compare those settings while keeping one hardware SKU. A setting cannot change capacity, body shape, or create two independent reservoirs.
Choose one of three decisions
Test one first
Choose one first when your team needs a clear baseline, when demand for another format is weak, or when staff cannot yet keep separate records. State what you will measure and what new evidence would reopen the lineup decision.
The first sample should match the question you need to answer. Briar is GreenDeagle's main product focus, but no product should be selected on the assumption that it fits every oil or process.
Add a second
Add a second when a different capacity, format, output method, or reservoir task solves a named need and the sample plan is ready. Write down the buyer problem, the candidate item, the work owner, and the evidence required for a limited launch.
Also write the stop condition. Stop before adding inventory if any named stop condition remains open.
Hold expansion
Hold when the request is vague, the first sample is incomplete, or the proposed item repeats the same job. Keep the candidate in a research list with the next question and review date. That preserves the idea without creating a live SKU too early.
Choose the current decision; do not turn an unfinished sample into a launch.
Finish with a decision your team can review
Record the unsolved problem and who reported it. State why the current SKU cannot answer it. Add the candidate item, extra work, and decision conditions.
Give each open item an owner and a review date. Keep the decision in the same file as the records used to make it. Review the file again when a new buyer request, completed sample, or reorder changes the evidence. Review it once more before any inventory commitment or public launch.
There is no universal ideal number of empty AIO SKUs. One is not automatically better, and several do not automatically create more sales or less risk. The useful lineup is the smallest set of separately tested products that each solves a clear problem your team can operate and support.
References
- Shopify Help Center: Using SKUs to manage your inventory.
- Briar Glass AIO, current public product page reviewed 2026-09-03.
- Nook 2mL Empty Disposable Vape Hardware, current public product page reviewed 2026-09-03.
- Lumen Dual-Chamber Empty Disposable Vape Hardware, current public product page reviewed 2026-09-03.
- Wisp Empty Rosin Disposable Vape Hardware, current public product page reviewed 2026-09-03.