Serial Supply of 1,000 PCs: BOM, Testing, and Shipment

Why a large PC batch needs one overall plan

A serial supply of 1,000 PCs is not just a matter of assembling identical systems and sending them to a warehouse. Replacing an SSD, memory module, or power supply affects procurement, the reference configuration, test results, serial number tracking, and acceptance documents. If a change is approved after production starts, some of the equipment may no longer match the contractual specification.

An overall plan establishes one specification version and a clear process for handling deviations. Suppose the approved SSD model is unavailable. The supplier proposes a replacement, the customer checks its capacity, interface, speed, and warranty, and then approves it in writing before installation. This prevents unexplained differences between PCs in different waves.

Before production starts, the parties agree on the BOM, technical specification, test scenarios, labeling rules, serial number register format, shipment schedule, and acceptance procedure. The documents should name the responsible people and specify the deadlines for their decisions.

The production schedule must be linked to site readiness. If the equipment arrives before the network, workstations, or receiving area are ready, it takes up warehouse space and increases the risk of lost boxes. For branches in different cities across Kazakhstan, it makes sense to divide the batch into waves. For each wave, record the date, quantity, address, contact person, and deadline for signing the documents.

For example, 1,000 PCs can be shipped in four batches of 250 units. Before assembling each batch, the customer confirms that the rooms are ready, while the supplier confirms component availability and the date when testing will be complete. This makes transportation and acceptance easier to manage.

GSE handles assembly, testing, and service within one production chain, so it can compare the BOM with the actual output. However, an overall plan is useful with any supply model. It turns verbal agreements into verifiable deadlines, configurations, and documents.

How to approve the BOM before production starts

A BOM, or bill of materials, records the computer’s components before procurement and assembly. For a supply of 1,000 PCs, it is not enough to specify “Intel processor” or “512 GB SSD.” Such wording leaves too many options, and differences may only be discovered during acceptance.

Specify the PC model and the parameters of every item: processor, memory capacity and type, storage, motherboard, power supply, case, and port set. If specific connectors are required, such as two DisplayPort connectors or a COM port, list them separately in the document. The phrase “required interfaces” is almost certain to cause a dispute.

A typical office specification might look like this: GSE L200 Series PC, processor with four or more cores, 16 GB DDR4, 512 GB NVMe SSD, Ethernet, at least six USB ports, HDMI, and DisplayPort. If the procurement requires exact part numbers, add the manufacturer and part number for each component.

Agree on replacements in advance

Components may go out of stock or be changed by the manufacturer. Approve replacement rules together with the main BOM. They should specify acceptable equivalents and the supplier’s required actions.

• Prohibit replacements without written approval for the processor, memory capacity, storage, port set, and operating system.
• For approved replacements, define minimum specifications and compatibility requirements.
• Appoint representatives for both parties and set a response deadline, such as two business days.
• Issue a new BOM version after every change.

Storage devices with the same capacity are not always equivalent. Replacing a SATA SSD with an NVMe drive requires checking motherboard compatibility, the operating system image, and warranty terms. The reverse replacement may violate the specification.

Record the software and document version

The BOM should include the operating system, edition, language, activation method, and preinstalled software. List the settings required before the equipment is sent to the sites separately: device name, user accounts, network settings, disk encryption, or the customer’s system image. Without this information, the assembly team may prepare working PCs that the IT department cannot accept.

Assign the specification a version number, date, and approval status: “BOM-1000PC, version 1.2, approved 15 May 2025.” The supplier should assemble the equipment only according to this version, while the customer should keep it with the contract and acceptance documents.

How to control components and replacements

The supplier should check the availability of parts for the entire order, not just the first shipment: processors, memory, SSDs, power supplies, cases, cables, and packaging. Otherwise, the first 200 PCs may ship on time while the next wave stops because of one missing item.

The dated and numbered BOM version should record exact models, acceptable parameters, and replacement rules. For example, the customer may allow an SSD from another brand only if it has the same capacity, interface, write endurance, and warranty period. The wording “equivalent SSD” is too vague.

Divide items by risk

Each BOM line can be assigned a status: available, in short supply, or eligible for replacement. For scarce parts, the procurement specialist checks stock, reservations, and delivery dates every week. Alternatives should be approved in advance for items that allow replacements.

The supplier should reserve components not only for assembly, but also for defects, service, and delays. This is especially important for memory, storage, motherboards, and power supplies. If a problem is found in a component batch at one of GSE’s production sites, the reserve can prevent the entire wave from stopping.

How to document a replacement

Every change must be approved before the affected batch is assembled. The supplier’s manager sends the customer the reason for the replacement, the original and new models, a comparison of specifications, the number of PCs affected, and the impact on the schedule. After the written decision, the team updates the BOM, test plan, and labeling documents.

Do not change parts in an already assembled wave without separate tracking. PCs that look identical may contain different SSD or memory versions, making warranty repairs more difficult. The serial number of every device must be linked to its actual component list.

Before launching each wave, the supplier checks BOM stock levels, confirmed deliveries, reserves of critical parts, and approved replacements.

How to create a wave-based delivery schedule

For a branch network, it is better to divide the batch by address, site readiness, and the local team’s ability to receive the equipment. The customer has time to prepare the workstations, and the supplier does not have to store assembled computers longer than necessary.

For each wave, specify the readiness date, departure date, address, site contact, unloading window, number of workstations, and shipment contents. “100 computers for a branch” is not enough. The receiving employee should know the number of boxes, monitors, cable sets, keyboards, mice, and other peripherals.

The batch can be divided into five waves of 200 PCs. Send the first devices to locations where power, network access, and temporary storage are ready. After the first wave is accepted, the team estimates the time needed for unloading and serial number checks, then adjusts the following shipments.

What to include in the wave plan

• Address, date, delivery window, and backup day.
• Number of PCs and related equipment.
• Order and delivery note numbers, plus serial number ranges.
• Time required for packing, loading, transportation, unloading, and acceptance.
• Supplier, carrier, and site contacts.

Consider more than transportation time. Include palletizing, documents, vehicle access permits, and access to the unloading area. If the warehouse accepts deliveries until 4:00 p.m., a truck arriving at 3:30 p.m. can still disrupt acceptance, even on a short route.

Several days before shipment, the site confirms the storage area, unloading access, and receiving contact. The supplier confirms that the equipment sets and documents are ready. A small reserve of devices and cables outside the main allocation can quickly cover a shortage or damaged item without moving the remaining shipments.

Which tests to run before packing

Every computer should undergo the same checks. Sample testing is risky for a batch of 1,000 units: an unnoticed defect at the site can lead to a lengthy replacement and delay the work.

Approve the test scenario together with the BOM and apply it to every unit. It should confirm that the PC was assembled according to the specification and is ready for use.

What to check on every PC

The specialist verifies the serial number and installed components against the production order, then runs functional tests:

• power-on, system startup, and the absence of startup errors;
• memory capacity, storage model, and storage capacity;
• storage health and read or write errors;
• USB ports, video outputs, audio connectors, and other specified interfaces;
• Ethernet and, when a Wi-Fi module is installed, wireless connectivity.

A short load test is also useful. It can reveal overheating, unstable memory, or a power problem that is not visible during a normal startup.

How to record the results

Create a record for each device using its serial number: test date, test scenario version, configuration parameters, test results, and employee name. An internal identifier can be linked to the serial number and added to the batch register. The customer can then quickly find information about a specific PC, while the supplier can confirm its configuration and testing status.

If a test identifies a problem, move the device to a separate area. Do not label it as ready or include it in shipping documents. After the repair or component replacement, run the full test scenario again.

How to prepare labeling and tracking

Labeling links a specific computer to its box, batch, documents, and installation site. If the data does not match, acceptance takes longer because employees have to open boxes and search for the right device manually.

Put the manufacturer’s serial number, the customer’s inventory number, and the batch number on every PC. The serial number is needed for production and warranty service, the inventory number for asset registration, and the batch number for identifying the delivery wave.

Use one number everywhere

The information must match on the PC case, the box, and the packing list. For an all-in-one computer or a set containing a monitor, keyboard, and mouse, list the contents separately. For example: INV-0472 | SN: GSE-L200-02472 | batch 3 | Karaganda branch.

Prepare a tracking file that the customer can upload to its system or open in a spreadsheet. Each row should include the inventory and serial numbers, batch, model, configuration, MAC addresses if needed, site address, box number, shipment date, handover status, package contents, and installed software.

Send the file before the next wave leaves. The customer can check the data structure and match the equipment to the deployment plan before unloading.

The label must withstand delivery

A paper label quickly wears off from friction, moisture, and cleaning. Use a durable material with a protective layer and adhesive suitable for plastic and metal. Place the label on an accessible part of the case without covering ventilation openings, ports, or the factory nameplate.

Before packing, an employee scans or checks every number and confirms that it matches the packing list.

Mistakes that delay acceptance

Acceptance is often stopped not by a hardware failure, but by discrepancies between documents, boxes, and the actual configuration. In a supply of 1,000 PCs, this can quickly turn into several days of downtime.

Replacements without agreed rules

If the BOM lists only component names without replacement conditions, every unavailable SSD or memory model will require a separate decision. Production and shipping will wait for an answer.

Define minimum specifications, compatibility, approved manufacturers, and the notification procedure. Record every replacement in the actual configuration list before the batch is shipped.

Boxes, versions, and documents do not match

Do not ship pallets until employees have checked the boxes against the packing list and serial numbers. One error can cast doubt on the entire shipment.

Do not mix different configuration versions in one wave without clear identification. Even a difference between 8 and 16 GB of memory requires a separate code and list. Before release, check that the actual equipment matches the BOM or approved replacements, that the register numbers match the devices and boxes, and that the number of packages in the delivery note matches the number of boxes and pallets.

Unloading without a confirmed contact

A delivery can fail when the truck arrives at a site where no one is ready to receive it. The cause may be a missing storage area, trolley, driver access permit, or access to the loading entrance.

One or two days before shipment, confirm the time, address, responsible person’s phone number, and unloading conditions. Agree on who will sign the delivery notes and how shortages or damaged packaging will be recorded.

Example of a delivery for a branch network

An organization is purchasing 1,000 PCs for ten branches. The head office receives 280 computers, large branches receive 120 each, and the remaining branches receive between 40 and 90. The parties divide the order into five waves so that the IT department has time to accept the equipment, register it, and prepare the workstations.

Before assembly, they approve one BOM covering the processor, memory, storage, network interfaces, case, and operating system. A week before launch, the supplier discovers a shortage of the approved SSD for 180 PCs. It checks an alternative with the same capacity, interface, reliability class, and motherboard compatibility, then sends the customer a comparison and updated BOM.

The customer approves the replacement in writing for the specified quantity only. The supplier records the new BOM version in the production order. The first two waves follow the original specification, while the agreed revision applies to the following waves.

Before every shipment, the supplier prepares a register with the receiving branch, PC model, serial and inventory numbers, MAC address when needed, and package number. The customer receives it two business days in advance and uploads the data to its tracking system.

At handover, the parties sign the delivery note, the acceptance and handover certificate for the wave, the serial and inventory number register, the packing list, and, if required by the contract, the acceptance test report. The branch representative immediately checks the number of boxes, packaging condition, and register numbers.

Checks before every shipment

Every wave requires a separate check. Approval of the first batch does not confirm the second one: the address, recipients, unloading window, or equipment list may have changed.

The supplier’s employee checks the BOM version in the order, production order, and batch documents. If the versions differ, the shipment is stopped until the customer provides a written decision.

The quality control team checks the test results for the serial numbers included in the wave. The register must show matching model, serial number, configuration, MAC address when needed, and box number.

Before loading, check the BOM, the test status of every device, the serial numbers in the packing list, box labels, number of packages, and packaging condition. Keep boxes from one wave separate from the next, especially when they are intended for different cities.

One day before shipment, confirm the address, date, time, contact person, phone number, and unloading rules. Attach the acceptance and handover certificate, packing list, serial number register, and procedure for recording remarks to the batch.

Next steps for the customer and supplier

Start with one document set: the approved specification, the number of PCs by site, and the wave schedule. Include the model, BOM, required software, label type, package contents, and readiness date for each batch. The number of devices must match in the production plan, delivery note, and acceptance plan.

Assign people responsible for specification changes, logistics, and on-site acceptance. Agree on the change process: the customer sends a request with the BOM version number, the supplier assesses stock and lead times, the parties make a written decision, and the supplier then updates the documents for the specific wave.

GSE can prepare a plan for serial assembly, testing, and delivery to each site. It should define component reservations, test dates, serial numbers for each batch, and delivery deadlines. For 1,000 devices, it is better to use several checkpoints rather than wait until the entire volume is ready.

Before the first shipment, jointly compare the BOM with the actual configuration, check label samples, package contents, and certificate forms. Then confirm the address, unloading time, receiving contact, and storage conditions.

Keep approved specification versions, replacement records, serial number registers, test results, delivery notes, and certificates until acceptance of the final wave is complete. If a dispute arises over a specific PC, these documents will show the approved configuration and shipment contents.