Start with the sample that changes the fewest unknowns. Use an existing hardware platform to learn how your material and filling process behave, add branding only after the product direction is stable, and request structural customization only when you can name the problem it must solve.
That sequence is not a rule that stock hardware is always faster, cheaper, or better. It is a way to make each sample answer one useful question. A branding supplier also recommends testing stock hardware with the intended formulation and filling workflow before confirming the product, branding, quantity, and artwork.[1]
Name the one unknown your first sample must answer
Before you choose stock or custom empty vape hardware, write down the uncertainty that could stop the project. It may be hardware fit with the material, the filling and closing routine, the physical format, the user experience, the package layout, or a visual requirement. Pick the uncertainty that matters most now.
A first sample becomes difficult to interpret when hardware structure, surface finish, logo, package, filling steps, and test conditions all change at once. A problem may appear, but the team will not know which change produced it. Keep an unknown-variable list with three columns: what stays fixed, what changes in this sample, and what you will observe.
Use the same material, fill routine, storage plan, and review record when you compare two hardware options. Record the model name or number, sample ID, date, supplier, and the version of any artwork used. Use those details to compare the same version later. Do not assume the record predicts the result of a future order.
If you are still deciding what empty hardware format belongs in the project, review the empty vape hardware guide before requesting decorative changes. Compare the current hardware options first, then choose how much the next sample should change.
Establish a stock-hardware baseline
“Stock” should mean an existing supplier platform you can identify clearly, not an assumption about current inventory or delivery. Confirm the actual model, configuration, quantity, packaging need, ship-from location, and timing with the supplier for the order being discussed. Do not carry a price, availability statement, or delivery estimate from one conversation into another without a fresh confirmation.
The purpose of the stock sample is to establish a baseline. Can the team fill, close, handle, store, and review this known platform under the intended process? Does the format meet the physical and operating requirements you wrote before the sample arrived? The answer may be yes, no, or “not enough evidence yet.” All three outcomes are useful when the changed variables are clear.
Do not treat a passed sample as proof about every later batch. Keep the accepted unit or a clearly documented reference. Compare future order details and receiving checks with that reference, while keeping the later order subject to its own review.
Add branding without hiding a product change
Branding an existing platform may sound like a simple middle step, but “logo only” needs a written definition. Ask where the mark appears, how the artwork is supplied, whether the surface treatment changes, whether packaging is included, and whether any color, material, dimension, or structural detail changes with the branded version.
If the only intended change is artwork, keep the hardware platform and operating conditions fixed. The sample can then answer a focused question: does the branded execution meet the visual and handling requirement without introducing an unrecorded product change?
A new color, surface, material, structure, dimension, stated capacity, or filling step can justify a fresh sample. Treat this as operating discipline rather than a universal legal requirement. The practical reason is simple: the earlier sample no longer represents every important detail of the new version.
Use the sample-to-reorder guide when the team needs a clean reference from an accepted sample to the next order. Keep the accepted sample details clear before discussing the later order.
Request custom engineering only for a named need
Custom work should begin with a problem statement, not the word “premium.” Common supplier language separates adapting or branding an existing platform from co-developing a new or substantially changed platform.[2] The labels OEM and ODM can vary between suppliers, so describe the actual change instead of relying on the label alone.
Write the need in a sentence a supplier can test: “The current candidate does not fit this package dimension,” or “The closing step cannot be completed with the equipment we plan to use.” Then list the features that must remain unchanged. This prevents the custom discussion from expanding into a complete redesign without a reason.
Ask what will be newly developed, what existing platform remains underneath, what files or samples are required, what parts of the product may still change, and how a new sample will be identified. Also state when the product needs to be ready for market. Timing matters, but no route is automatically faster or available on a fixed schedule.
If the custom request changes structure, material, dimension, capacity, or the way the team fills and caps the hardware, plan a fresh sample round. The old result describes a different version.
Reset the sample when a meaningful variable changes
Use a simple reset rule: when a change could affect the product requirement, operating process, or interpretation of the earlier result, stop and confirm a new reference sample. This includes changes to material, structure, dimensions, filling steps, or the material being filled. It can also include branding changes when they alter more than artwork.
Do not reset blindly for every administrative edit. A corrected filename does not automatically make the physical sample obsolete. Compare the before and after versions, name the changed variable, and ask whether the old sample still represents the product being considered.
The team can record each change in a short sample log: sample ID, known platform, changed detail, fixed conditions, observations, open questions, and next action. For a fuller record, use how to record empty AIO sample test results.
Compare the three routes without false precision
Put the three routes on one sheet, but do not invent a score that hides uncertainty. For each route, write what is already known, what the next sample will change, what the team must supply, what the supplier must confirm, and what decision becomes possible after the result.
For an existing platform, the next decision may be whether to continue with the hardware format. For a branded version, it may be whether the artwork and surface execution are ready for the planned package. For a custom request, it may be whether the changed structure actually addresses the named requirement and whether another revision is needed.
Keep time and commercial questions in the sheet, but mark them “confirm for this order.” Ask about the current quantity, packaging, stock position, ship-from location, and timing instead of carrying forward an old answer. Do the same with any development step: ask what the supplier expects from the buyer, what the supplier will return, and how each new sample will be identified.
The sheet should end with one of four plain outcomes: continue with this version, revise one named detail, compare a second candidate, or stop the route. That is more useful than a total score whose inputs cannot be verified.
Send a decision-ready supplier message
After this work, your supplier message can be short and specific:
- Name the hardware format and any known model.
- State whether you want an existing platform, branding on an existing platform, or a structural change.
- List the quantity you want discussed without assuming it is available.
- State packaging or logo needs and attach the current artwork version when relevant.
- Name the ship-from location and the date the project needs to be ready.
- Identify the one question this sample must answer.
- Ask the supplier to point out any material, structure, dimension, or process change that would require another sample.
Choose stock first when the team still needs a hardware-and-process baseline. Choose branding on an existing platform when that baseline is stable and the next uncertainty is visual execution. Discuss custom hardware when a stable requirement cannot be met by the existing candidate and the team can name what must change. The goal is not to minimize the number of samples. It is to give the team a clearer next question after each round.
References
- Hamilton Devices, “Custom Branding,” captured August 20, 2026: https://hamiltondevices.com/custom-branding/
- HTR, “OEM and ODM,” captured August 20, 2026: https://www.htrvape.com/ODM