Almost certainly the file system, and it's the field buyers forget most often because nothing in the quote mentions it. Your laptop reads everything; an older register, till or embedded player often reads only FAT32, sometimes only with an MBR partition. An exFAT drive simply doesn't appear. Two lines in your specification prevent it, and so does telling the factory which device the drive has to plug into.
When a drive works on a laptop but not in a till, kiosk or embedded player, the cause is almost always the file system or partition scheme, not the hardware. Laptops read FAT32, exFAT and NTFS; many embedded and legacy devices read only FAT32, sometimes only with an MBR partition, and will not mount an exFAT or GPT drive at all. Specify FAT32 (and MBR if the device is old) in the order, name the exact device the drive must plug into, and verify the label and contents on a host at final inspection.
The short answer
Almost certainly the file system — and it’s the field buyers forget most often, because nothing in a typical quote mentions it.
Your laptop reads every common format, so it hid the problem from you. The machine — a till, a kiosk, an embedded player, an older register — often reads only one, and a drive in the wrong format is simply invisible to it. Not slow. Not corrupted. Just not mounted.
Two lines in your specification prevent it. So does one question asked before the order.
Why the laptop lied to you
A laptop runs a full operating system with drivers for FAT32, exFAT and NTFS. It mounts almost anything.
An embedded device runs a minimal system built to read what its firmware was written for. That’s usually FAT32, sometimes only with an MBR partition. It has no exFAT driver, no NTFS driver, and no interest in your GPT table.
So the same drive:
| Environment | Reads | Result |
|---|---|---|
| Laptop | FAT32, exFAT, NTFS | Mounts everything |
| Embedded device (modern) | FAT32, maybe exFAT | Mounts FAT32 |
| Embedded device (older) | FAT32 + MBR only | Mounts only that |
When the drive “works on my laptop but not in my device,” the laptop proved the hardware is fine. The device proved the format isn’t the one it reads.
FAT32 vs exFAT: the wrong default
The tempting move is to format everything as exFAT, because exFAT allows files larger than 4GB and feels modern.
For device compatibility, that’s backwards.
- FAT32 is read by essentially everything, at the cost of a 4GB single-file limit that rarely matters for this use.
- exFAT allows large files but is not supported by many embedded and legacy devices, which then won’t mount the drive at all.
If you need exFAT for large files, confirm the device supports it first. Don’t assume — the laptop will let you assume, and the machine won’t.
MBR vs GPT (the part nobody mentions)
MBR and GPT are two ways of laying out partitions. MBR is older and read by everything; GPT is newer and not read by older embedded firmware.
For most small-capacity custom drives the factory defaults to MBR. But if your specification doesn’t say so, you don’t know — and “it doesn’t mount” is an expensive way to find out. If the device is more than a few years old, specify MBR explicitly.
The volume label (the easy one people also miss)
The volume label is the name the drive shows when mounted — “MYBRAND” or whatever you choose. On any device with a screen, or anywhere a user sees the drive name, a generic or blank label reads as unfinished, and can even read as the wrong product.
It’s one line in the spec and one line of checking at inspection. The difference between a drive that reads as yours and one that reads as “NO NAME” is that one line.
A scenario: the register that won’t see the drive
A buyer ordering drives to load software for a retail system specifies capacity and USB-A, receives the drives, tests one on a laptop — mounts, looks perfect — and ships 500 to stores. A week later, stores report the registers don’t see the drives.
The drives are fine. They were formatted exFAT, which the register’s embedded OS doesn’t support. The laptop test passed because the laptop reads exFAT. The fix is a re-format of 500 units and a specification line that should have said FAT32 from the start.
The one question that prevents this: which device must this plug into, and what does it read?
What to put in the specification
| Field | Wording | Why |
|---|---|---|
| File system | FAT32 (exFAT only if device confirmed) | Mounts on the device |
| Partition | MBR if device is older | Older firmware reads MBR only |
| Volume label | Exact string, case-sensitive | Shows as your brand, not “NO NAME” |
| Target device | Model the drive must plug into | Decides the above |
And at final inspection: plug the drive into the actual device, not a laptop, and confirm it mounts, shows the right label, and opens the expected content. A sample tested only on a laptop tells you nothing about the machine.
The thing to remember
Capacity and interface decide whether the drive exists. The device decides whether it mounts.
A factory that isn’t told the device will build a perfectly good drive in whatever format they default to — which may not be the one your machine reads. Ask which device the drive must plug into before the order, not after the return. That single question is worth more than any amount of incoming inspection afterwards.
Frequently asked questions
Why does it work on my computer but not in the machine?
Because your computer has drivers for every common file system and the machine often doesn't. A till or embedded player runs a minimal operating system that was built to read one format — usually FAT32, sometimes only with an MBR partition table. An exFAT or GPT drive is simply invisible to it: not slow, not corrupted, just not mounted. The laptop hid this from you because it reads everything.
Should I just format everything as exFAT to be safe?
No — the opposite. exFAT allows files larger than 4GB, which is useful, but many embedded and legacy devices have no exFAT driver at all and will not mount the drive. FAT32 is the safe universal choice for devices, at the cost of a 4GB single-file limit that rarely matters for this use. If you need exFAT for large files, confirm the device actually supports it first; don't assume.
What's the MBR vs GPT thing and do I need to care?
MBR and GPT are two ways of laying out partitions on a drive. MBR is older and read by essentially everything; GPT is newer and not read by older embedded firmware. If your device is more than a few years old, specify MBR. For most small-capacity custom drives the factory defaults to MBR anyway, but if the specification doesn't say it, you don't know — and 'it doesn't mount' is an expensive way to find out.
What is the volume label and why does it matter?
The volume label is the name the drive shows when mounted — 'MYDRIVE' or your brand. On a device with a screen, or anywhere a user sees the drive name, an unnamed or generic label looks unfinished and can even read as the wrong product. It's one line in the spec and one line of checking at inspection, and it's the difference between a drive that reads as yours and one that reads as 'NO NAME'.
I told the factory the capacity and interface but not the device. Is that the mistake?
Very likely. Capacity and interface decide whether the drive exists; the device decides whether it mounts. A factory that isn't told the device will build a perfectly good drive formatted in whatever they default to, which may not be what your machine reads. The one question that prevents this is 'which device must this plug into, and what does it read?' Ask it before the order, not after the return.
How do I check this before a full shipment?
Two steps. In the specification, state FAT32 (and MBR if old), the exact device model, and the volume label. At final inspection, plug the drive into the actual device — not a laptop — and confirm it mounts, shows the right label, and opens the expected content. A sample tested only on a laptop tells you nothing about the machine.