Guide

How to plan a laptop rollout before you order

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.

4decisions that shape a rollout
24months of platform stability
12month limited warranty from shipment
1,000units per model for a custom build

Plan a rollout with us

Start from the deployment, not the device

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.

  • When do the users need a working device, not when do you need a delivery. Work back from the deployment date, because commissioning, imaging and asset tagging all sit after arrival.
  • How many units will be out of service at any time. A rollout needs a spares position, and the spares position depends on the failure and repair path rather than on the order size.
  • Whether one configuration covers the whole estate. A single specification simplifies the spares list, the support script and the replacement process. A mixed estate multiplies all three.
  • Who supports the fleet after handover. If the answer is your own team, the repair and RMA path has to be agreed with the supplier before the rollout, not after the first failure.
  • What evidence you need before committing the budget. That is what a sample is for, and it is the stage most often compressed to save two weeks.

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.

What decides each part of a rollout

Part of the rolloutWhat it depends onSettled when
Quantity1,000 units per model for a custom build, about 100 units as a first stocking batch, or from one unit on in-stock configurationsWith the quotation
StagingWhether the first delivery is a sample, a pilot batch or the whole orderBefore production is booked
SpecificationPlatform, configuration, keyboard language, labelling and packagingAt specification freeze
DocumentationThe compliance set for the destination market, plus battery transport documents for the freight modeDuring quotation
Spares and serviceabilitySpare parts supply, the warranty process and how RMA is handledAgreed with your account
Supply continuityHow long the platform is held stable, so a replacement matches the original deployment24 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.

Sequencing a rollout

Decide the deployment, the estate and the support model

The date the users need working devices, whether one configuration covers everyone, and who supports the fleet afterwards.

Fix the specification and prove it with a sample

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.

Agree the commercial terms in writing

Configuration, customisation scope, tooling or artwork cost where it applies, lead time, the production window and the last-order date.

Stage the delivery against the deployment 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.

What support looks like after the rollout

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.

  • A 12-month limited warranty from the shipment date applies to ODM/OEM laptop products, with spare parts supply and online technical support.
  • Remote diagnosis first. Support starts with diagnosis, which is why the process is agreed with your account rather than handled case by case.
  • RMA authorization before return. Handling is defined in advance, so a faulty unit follows an agreed path instead of an improvised one.
  • Long-term repair support can continue beyond the warranty period, with replacement parts, labour and logistics charged according to the work required.
  • Replacements match what you deployed. Platforms are held stable for 24 months, so a unit supplied in the second year is the configuration you originally rolled out.

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.

Rollout planning questions

  • How far ahead should a rollout be planned?

    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.

  • Should we order a sample before the volume order?

    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.

  • What quantity should a first order be?

    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.

  • How do we handle replacement units mid-rollout?

    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.

  • What support applies after delivery?

    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.

  • What documentation should the rollout budget for?

    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.

  • What should be in writing before the first order?

    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.

The platforms a rollout can be built on

Every platform below is held on the same commercial terms, and the product pages carry the published specification for each one.

Plan the rollout, then place the order

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.

Plan a rollout with us