Guide
A rollout goes wrong in the planning, not in the delivery. Four decisions carry almost all of the risk, and every one of them is cheaper to settle before the first order than after it.
The four are quantity, staging, spares and support. Quantity sets what is possible: 1,000 units per model for a custom build, about 100 units as a first stocking batch, or from a single unit on in-stock configurations. Staging decides whether the first delivery is a sample, a pilot batch or the whole order. Spares and support decide what happens in month nine, when a unit fails and the users still need a working device. Supply continuity decides whether a replacement in month nine is the same machine or a substitute build.
Buyers usually begin with a platform and then discover the operational questions late. Planning in the other order surfaces them while they are still cheap to answer.
If this is an education or campus deployment, the education page compares the volume platforms; if it covers desk-based or multi-window work, start from business or large screen. Where one device has to serve as both laptop and tablet, see convertible laptops.
| Part of the rollout | What it depends on | Settled when |
|---|---|---|
| Quantity | 1,000 units per model for a custom build, about 100 units as a first stocking batch, or from one unit on in-stock configurations | With the quotation |
| Staging | Whether the first delivery is a sample, a pilot batch or the whole order | Before production is booked |
| Specification | Platform, configuration, keyboard language, labelling and packaging | At specification freeze |
| Documentation | The compliance set for the destination market, plus battery transport documents for the freight mode | During quotation |
| Spares and serviceability | Spare parts supply, the warranty process and how RMA is handled | Agreed with your account |
| Supply continuity | How long the platform is held stable, so a replacement matches the original deployment | 24 months from launch |
The last two rows are the ones that get skipped, and the two that decide how the rollout feels in its second year. Both are covered in more detail on supply continuity and warranty and RMA.
The date the users need working devices, whether one configuration covers everyone, and who supports the fleet afterwards.
A sample is built within 7-10 days and becomes the production reference. Rushing this stage is the most common way a rollout loses time later.
Configuration, customisation scope, tooling or artwork cost where it applies, lead time, the production window and the last-order date.
Mass production runs 20-30 days once the specification is frozen. In-stock configurations dispatch in 2-3 business days and local stock arrives in 1-2 days.
The sample page covers the approval stage, the shipping page covers transit and landed cost, and the market compliance page covers what the document set depends on.
Support is where a rollout is judged, because a device that fails in month nine is a support question rather than a procurement one. The framework is standard, and it is worth reading before you sign rather than after a failure.
Final coverage follows the confirmed order terms, the signed commercial documents and the agreed after-sales process. The warranty and RMA page sets out the framework in full.
Work back from the date the users need working devices. In-stock configurations dispatch in 2-3 business days and local stock reaches United States and European addresses in 1-2 days. A produced order adds a sample at 7-10 days and mass production of 20-30 days once the specification is frozen.
Yes, and it is the stage most often rushed. The sample is how the specification gets frozen, and it becomes the production reference for every unit that follows. See the sample page.
1,000 units per model is the standard custom minimum, about 100 units is workable as a first stocking batch, and stock configurations start from one unit. A pilot is usually a sample plus a stocking batch rather than a full order. See how small a first order can be.
Platforms are held stable for 24 months, so a replacement matches the configuration you originally deployed rather than a substitute build. RMA is handled through the warranty process agreed with your account. See supply continuity.
A 12-month limited warranty from the shipment date for ODM/OEM products, remote diagnosis first, RMA authorization, and long-term repair support that can continue beyond the warranty period. See warranty and RMA.
The compliance document set for your destination market, agreed during quotation, plus lithium battery transport documents for the freight mode. Documentation follows the model and the market rather than the order size.
The production window and the last-order date, so your own stock position can be planned rather than reacted to. Both are confirmed in writing before production is booked.
Every platform below is held on the same commercial terms, and the product pages carry the published specification for each one.
Send the deployment date, the size of the estate, the market and whether you need branding. We will confirm the platform, the quantity that is workable, the documentation set and the timeline, and set out what a pilot would look like. If you are still comparing supply options, the sourcing guide covers what to verify first.