I'm a procurement manager at a 32-person robotics integration firm. For the past six years, I've managed our motor and drive budget—roughly $180,000 a year—and I've documented every single order in our cost tracking system. That habit is probably why I now have a strong, stubborn opinion about small orders.

I do not think small orders deserve second-class service. That's not a feel-good customer-service slogan. It's a financial conclusion based on real invoices, real engineering hours, and a few painful mistakes. At least, that's been my experience in the small-batch robotics world.

The TCO Wake-Up Call

Earlier this year, we needed a few high-torque gearmotors for a conveyor application. I was comparing an established maxon-motor option against a significantly cheaper no-name gearmotor from an online distributor. The cheap option was nearly 40% less on unit price. On paper, that seemed like the responsible budget move, especially for a small prototype run.

I went back and forth between the two for two weeks. The maxon gearmotor offered reliability and documented performance; the cheap one offered undeniable savings. My gut said the savings were a trap, but I'm a numbers person, so I built a total-cost-of-ownership spreadsheet. That spreadsheet ended up being the reason I now preach the "small order is not an inconvenience" gospel.

The surprise wasn't the price difference. It was the pile of hidden costs sitting under the cheap quote. The no-name motor needed a custom adapter plate because the shaft was 2mm shorter—$90 in machine-shop time per unit. It didn't come with a load curve or thermal derating data, so our engineers lost an entire day tracking down information. And when one unit arrived with shaft runout out of spec, the distributor asked us to pay return shipping and a restocking fee.

When I added it all up—and I remember the number without even opening the spreadsheet—the "cheap" motor was 22% more expensive than the maxon motor. Maybe 18%, if I'm being generous about our internal labor cost. Either way, it was way more than we would have paid if we'd gone with the known-quantity supplier from the start. We eventually chose maxon for the final design, not because of brand loyalty, but because the real price was lower.

This is exactly the kind of hidden setup fee problem you see in other industries, like commercial printing. A quote might say $30 for a setup fee, but by the time you add plate changes, color matching, and rush handling, you've spent $300. Same principle: the unit price is the least important number on the quote.

Small Orders, Real Engineering Support

The second reason I defend small orders is that the treatment you get during a low-volume purchase tells you everything about a supplier's future behavior.

Take our e-bike powertrain project. We needed to bench-test a handful of maxon ebike motor units before committing to a production run. Honest? I was expecting the classic "minimum order quantity: 500 units" routine. When your company is as compact as ours, you get used to being screened out at the door.

Instead, maxon motor ag gave us the same documentation library a tier-one customer would receive: wiring diagrams, thermal data, and even a sample drive system for testing. We got through the feasibility study in about three weeks. That kind of help saves real money because it shortens the design cycle, and a shorter design cycle means fewer paid engineering hours.

That wasn't the only surprise. The most valuable part was the applications engineering call we got when a question came up about voltage handling. No one charged us a consultation fee, and no one asked if we were going to order thousands of units. That's the level of support you normally only get after you've shown your PO history. But they did it for a one-unit sample.

I'll say this plainly: the difference between a supplier that treats a $300 order seriously and one that treats it like a nuisance can easily be a month of engineering time. And engineering time is the most expensive line item on any product build.

Prototyping, Arduino, and the VFD Question

These same principles show up in smaller-scale projects too. A while ago, I was helping a startup friend source components for a stepper motor Arduino prototype. He wanted to order a handful of cheap stepper drivers, and he didn't care which one. I convinced him to pick an A4988 stepper motor driver that actually had a datasheet and a support forum. Same price, but one had documentation and one didn't.

You'd be surprised how many "budget" components fail because the info is missing. We literally saved a weekend by buying the driver with a clear pinout diagram. That wasn't a big order—it was five drivers—but the documentation made all the difference.

The same goes for industrial VFD compatibility. I've spent more hours than I'd like searching for the answer to "what motors are compatible with VFD?" The short answer: it's not just the motor type; it's the insulation rating, frequency range, and whether the motor is rated for inverter duty. You can't get that from a shelf price. You need motor manufacturers to provide technical specifications even for sample orders.

When we were testing VFD compatibility for a custom automation line, we needed three different motor samples from different manufacturers. The one supplier that refused to provide insulation class data until we sent a large PO? We crossed them off the list. The suppliers that helped us evaluate a single unit? They got the production order. It's that simple.

Wait—Am I Just Asking for Lower Prices?

Let me anticipate the pushback. Some readers will say: "Of course you, as a buyer, want premium support at low volume. But that's not how economies of scale work." I agree completely. I don't expect a ten-unit order to get a thousand-unit price. That would be delusional.

What I'm pushing back against is dismissiveness. The "you're too small" attitude isn't a pricing issue; it's a communication issue. When a supplier hides minimum order quantities until the last minute, charges extra for standard technical drawings, or refuses to answer a basic application question because they don't see a big enough purchase order, they're adding artificial friction. Artificial friction is a cost, even if it never appears on an invoice.

I also get that supporting small customers can eat into margins. But good suppliers treat it as customer acquisition. Every large account started as a small account. The maxon rep we worked with didn't know our future order volume, and yet he spent an hour on the phone with me about thermal properties. That investment is why we're now recommending maxon-motor to our partners.

Bottom Line

So here's my final stance. Small orders are the way most relationships and most products begin. They are not a nuisance to be tolerated. If you're a supplier, be the one that gives small customers real support. It pays off. If you're a buyer, don't accept a vendor that makes you feel like a problem for wanting to test before you commit.

I've got the invoices to prove it. The "cheap" motor was 20% more expensive, and the "expensive" motor saved us time, headaches, and rework. Run the numbers. Demand documentation. And whatever you do, never let a supplier convince you that a small order makes you a small customer.