Quality control

Quality you can check, step by step.

Before you order, before it ships and when it arrives, we check your robot against what you agreed. You keep every record, and every issue gets a next step.

Shipment check recordSample layout
Model and edition
Booster K1 · Education
Serial number
Recorded for each unit
Firmware and SDK
Version numbers recorded
Packing list
Every item checked
Power-on and remote
Tested
Stop method
Tested
Video
Date, serial number, human input

Each check names who ran it.

01 · Before you orderConfiguration sheet and acceptance criteria
02 · Before it shipsProgress updates and a shipment check record
03 · When it arrivesDelivery check, acceptance record and handover
04 · After handoverIssue log with a next step
What we control

Four risks we manage for you.

Control is step three of how we work: we flag quality, compliance, supply and delivery risks early, and manage them. Here is what that means for you.

01

Quality

The robot arrives incomplete, or not as ordered.

We arrange a check of each unit against your order before it ships, and send you the record.

02

Compliance

A CE mark on a web page, but no documents for your exact model.

We request documents for your exact model and configuration, and flag any gaps before you order.

03

Supply chain

Same model name, different edition, battery or hands, or a delay nobody explains.

Every item goes into a sheet you confirm, and we update you at each stage until it ships.

04

Delivery

Damage in transit, missing paperwork, nobody to help at start-up.

We handle packing, shipping and battery documents, then go through start-up and acceptance with you.

Checkpoint 1 · Before you order

Your robot, written down.

Robots that share a name can differ in computing, battery, hands and software. Before you order, we write down what is ready today, what depends on configuration and what needs development, and how we will check it.

Why it matters
  1. K1 comes in Geek, Education and Professional editions. Height and weight are the same. Computing, storage and battery are not.

    Booster §04
  2. On T1, the version with 7-DoF arms does not support the Soccer, Teach or Dance skills.

    Booster §04、§06
  3. Some SDK features need a minimum firmware version, and running several robots together needs matching versions on every unit.

    Booster §10、§16
Configuration sheetSample layout · K1 Education
Built-in skills
Walking, football, dance and TeachReady today
Developer access
Python and C++ SDKReady today
Hi Chat conversation
Needs an internet connectionConfigure
Computing and battery
Jetson Orin NX 8GB · 5AhConfigure
Magnetic charging
Confirmed with your orderConfigure
Your own lesson routines
Built by you, or quoted separatelyDevelop
Acceptance criteriaWritten from your own tasks
Task
What the robot must do for your class or lab
Setting
Floor, space, network and who operates it
Pass mark
What counts as done, and how many times
How it runs
On its own, remote-controlled or assisted, recorded separately
Versions
Firmware and SDK used for each test
Checkpoint 2 · Before it ships

Checked against your order before it ships.

While your robot is prepared, we update you at each stage. Before it leaves, we arrange a check of each unit against the agreed list; anything that fails is fixed and checked again.

  1. 01Serial number and model
  2. 02Every item on the packing list
  3. 03Firmware and SDK versions
  4. 04Power-on and remote control
  5. 05Stop method
  6. 06Cameras and purchased interfaces

You receive the record with photos and a video marked with the date, serial number and any human input. Each check names who ran it, and packing photos come too.

Need an independent inspection? We agree the inspector, scope and cost with you first.

Manufacturer visual
Checkpoint 3 · When it arrives

Checked again, then put to work.

Delivery is not the finish line. Acceptance is.

  1. 01/04

    Check the delivery

    Before you unpack further, use our checklist to record boxes, seals, serial numbers and items. If anything looks damaged, keep the packaging and tell us.

  2. 02/04

    First start-up

    Follow the manual’s set-up steps on flat, open floor: at least 2 m × 2 m for K1 and T2. We go through it with you, as agreed.

  3. 03/04

    Run your tests

    We run the acceptance criteria you agreed before ordering, and record each result, the versions used and any human help.

  4. 04/04

    Hand over

    Your team practises the everyday steps: start, stop, charge and report a problem. You keep every record, with the manuals and version list.

What you keepConfiguration sheetShipment check recordPacking and shipping documentsAcceptance recordManuals and quick-start guidesSoftware version listWarranty terms for your orderSupport contact
Checkpoint 4 · After handover

Every problem gets a next step.

Tell us what you see. We record it, bring in the right people and tell you what happens next, and when you will next hear from us.

Something is missing or damaged on arrival

Keep the boxes and packaging, send us photos and don’t start it if anything looks unsafe. We notify the carrier and insurer, and follow up the claim.

What has been submitted, and what happens next

It doesn’t match your configuration sheet

We compare the unit with your order record and agree a fix and a recheck with you.

The differences, the fix and the recheck result

It won’t start, or an interface doesn’t work

We collect the status, versions and steps that led to it, and bring in technical support.

What has been checked, and the next step

An update breaks something that worked

We record the versions before and after, and hold further changes until a fix is confirmed.

What changed, and how to work in the meantime

It needs a repair

We confirm the return route, packing, data backup and any cost before anything ships. After the repair, the original problem is checked again.

The repair route, quote and return plan

Questions

Evidence, documents and data.

Straight answers to the questions schools and labs ask before they buy.

Do the robots come with CE or UKCA documents?

We don’t issue certificates ourselves. We request the declaration of conformity and other documents for your exact model and configuration, and tell you before you order if anything you need is missing. A mark on a web page is not enough.

Are the photos on this website from your checks?

No. They are manufacturer visuals and illustrations. The photos and video in your shipment check record show your own unit.

Will a software update break our lessons or code?

It can. We record your firmware and SDK versions at handover. Check with us before updating: we confirm compatibility first, and if something stops working, we follow it up and retest your tasks.

Does the robot send data online?

Some features do: Hi Chat conversation needs an internet connection. Before you order, we confirm which features need a connection and what can be switched off, so you can check it against your data rules.

Is damage from our own code covered by warranty?

Not always. Warranty terms can exclude falls or collisions caused by custom code, and unauthorised repairs. We set out what your order’s warranty covers before you buy, and how a repair would be handled.

Can we arrange an independent inspection?

Yes. Tell us what you want checked. We agree the inspector, scope, cost and the record you receive before anything is arranged.

MANUFACTURER PRODUCT IMAGE

Manufacturer product material; not a FARSEN customer project or inspection record.