Current location:
Home
> News > Product News > Query machine
Release date: 2026-09-03
Clicks:0
When the brand is planning the deployment of multinational self-service ordering machines, most of the internal discussions focus on the software-which ordering system to choose, which POS to connect with, and which membership system to use. Hardware is often treated as a purchase item that is resolved after the software solution is finalized. This order is actually the opposite.
The software can be switched within a weekend, but a self-service machine body designed around the specifications of a certain country's payment terminal cannot be modified overnight when the certification requirements or terminal sizes in the next market are different-and when this mismatch is exposed, the corresponding purchase orders are often hundreds of units, not several prototypes.
Qunmao focuses on building self-service ordering machine hardware for global chain brands. This guide reflects our actual experience and position-including being honest about where our solution is not appropriate. Please use it as a starting point for your own due diligence, not as a substitute.
Next, this guide will disassemble the six links of self-service ordering machine hardware procurement in the order that most brand procurement teams actually advance: hardware architecture selection, supplier due diligence, regional adaptation, pits that are easy to step on after scale, delivery methods, and acceptance criteria before shipment.
What global chain brands need is never just a self-service ordering machine with stacked functions, but a hardware architecture that is scalable, risk-controlled, and not tied to a certain software ecology.
At present, there are only two mainstream practices for self-service ordering machines with payment terminals, and none of them is the optimal solution that is universally applicable. The real decision is the size of your deployment, the compliance requirements of your target market, and how long it is expected to take for the next round of hardware iterations-not simply which architecture is inherently better.
Compliance has nothing to do with whether the payment terminal is connected with Bluetooth. The key lies in whether the terminal has been effectively authenticated by the local market and whether the transaction link has been encrypted end-to-end. In fact, many large chain brands can still achieve full compliance with the modification scheme in small-scale pilot stores with small passenger flow.
Problems often arise after scaling. According to our project experience, once the device density and network load in the same store increase, the Bluetooth pairing stability of multiple devices will obviously decrease, and the reconciliation errors will also increase. The failure rate of exposed cables and split fuselage will also be significantly higher in the catering environment with heavy oil pollution and frequent touch-this part of the cost will eventually be reflected in the higher single-store maintenance expenditure during the life cycle of the equipment, which is often the part that the brand operation team did not budget in the pilot phase.
Suitable scenarios:Single-store testing, small-scale regional pilots, pop-up shops, stores with low passenger flow.Not suitable for the scene:Large-scale multinational standardization deployments, or flagship stores with high compliance requirements.
The value of this scheme is not really reflected until it is large-scale: the certified payment hardware can be replaced one by one according to the market, and there is no need to re-open the mold to change the body, nor do you need to re-certify the whole machine. Built-in wiring plus independent hardware positions, rather than exposed cables, is the real reason why the failure rate and reconciliation accuracy can be improved. And because the hardware baseline remains the same, multinational compliance audits are simplified to audit only the local payment module, rather than the entire device.
If you only plan to do a pilot in one or two stores with small passenger flow, the modification scheme may enable you to go online faster instead-modular hardware is prepared for the large-scale expansion stage, not necessarily the best solution for the first round of pilot.
| Dimension | Retrofit (Bluetooth) | Modular integration |
|---|---|---|
| The most suitable size | Small-scale pilot, pop-up shop | Transnational standardized scale deployment |
| Prophase investment | Lower | Higher |
| Costs that grow with scale | tend to go higher | Gradual dilution |
| Compliance audit workload | Equipment-by-equipment verification | Unified baseline, only need to replace the certification module |
Parameters and quotations hardly indicate whether a supplier has the ability to deliver on its promises at scale. The following six checks are materials that we believe any serious brand procurement or IT team should request in writing before arranging factory visits.
The equipment should reserve independent and standardized positions for payment, printing and code scanning hardware, and be able to adapt to the terminal specifications of multiple regions.
Hardware should not be bound to any specific software or payment channels, but should open standard interfaces to facilitate docking with self-research systems or third-party POS.
The hardware baseline itself should not carry compliance restrictions, but should be able to carry payment terminals that have received valid local certification. This typically includes PCI PTS terminal authentication, EMV chip transaction specifications, and if the transaction takes place in the EU, the authentication process for strong customer authentication (SCA) under PSD2 is also required. The main body responsible for compliance is the payment terminal and transaction link, not the body itself.
The equipment shall be capable of continuous and uninterrupted operation and shall be dust-proof, splash-proof and high-temperature resistant to high passenger flow catering environment.
For white-brand projects, suppliers should support customization of appearance, structure adjustment and boot interface, and can be realized in both finished product delivery and semi-bulk delivery modes.
The supplier should have stable mass production capacity and be able to make a commitment for the supply of spare parts for 3-5 years. This 1.1 has to fall into a written agreement-a promise of supply in a sales call does not constitute a real guarantee of purchase.
The following is based on observed experience with regularity in our own programs and is not a substitute for verifying the latest regulatory requirements with your local attorney, acquiring agency or compliance team in each market.
These two markets usually have the most mature compliance systems-there are clear requirements for payment terminal authentication, transaction encryption, and barrier-free hardware deployment. Selection priority: certified EMV/NFC terminals, integrated body without exposed accessories, and equipment placement height that meets local accessibility standards. This reduces risk exposure during the compliance audit, which is where the retrofit program is most likely to go wrong after it is scaled up.
The dusty and hot environment and the fact that local e-wallets are the mainstream payment method are the two most important factors to consider here. Selection priority: dust-proof body, and a module position that can replace the cost-compliant two-dimensional code/e-wallet payment terminal without redesigning the whole machine, while also supporting multi-language interface.
Network stability in many of these markets is uneven, and cash transactions still account for a significant proportion. Selection priority: hardware that supports offline order caching, and module positions that can be equipped with cash storage equipment and support multi-currency cash processing as needed.
The shape of stores in this area varies greatly and is sensitive to cost. Selection priority: the same set of modular design can support the standardized hardware baseline of floor, wall-mounted and table-top forms at the same time, so that the iteration cost can be controlled when the store form is adjusted.
The following three cases document the three most representative problem patterns we have observed in the deployment of multinational self-service ordering machines. One of them comes from a real project and has hidden identifiable information. The other two are composite scenarios sorted out by combining common problems of multiple projects, not the original data of a certain customer. The numbers are presented in the form of intervals to match the desensitization treatment.
A local coffee chain, headquartered in Vietnam and with about 260 stores, has previously used fixed open-hole self-service machine bodies to initiate expansion into Thailand, the Philippines and Malaysia.
The existing fuselage is designed around Vietnam's local payment terminal specifications. Thailand and Malaysia require the use of a new generation of certified terminals of different sizes, and there is no room for modification in the body of the network equipment-this possibility has not been considered from the beginning of the design. Brands had to re-purchase complete machines for these markets and go through the compliance certification process again instead of reusing existing inventory.
The cost of replacing equipment fell in the middle of the range of hundreds of thousands of dollars, and Thailand's launch was delayed by several weeks. Even if the brand switched to modular hardware in the subsequent stages, Malaysia's first batch of replacement equipment was still behind schedule-the training of the installation team did not keep pace with the design of the new position. This also reminds us that hardware architecture can solve the compatibility problem, but it cannot solve the problem of deployment execution itself.
Lessons learned: For multinational deployments, a modular, replaceable hardware structure is almost a prerequisite-a fixed-structure fuselage is suitable for a single, short-term market and cannot support expansion plans that span several years.
A fast-food chain based in Spain first piloted a modified Bluetooth payment scheme on about 60 devices in the local market without any problems. However, when the same scheme was extended to more than 450 terminals in new stores in Italy and Portugal, the stability of parallel Bluetooth pairing of multiple devices in the same store was significantly reduced, and this modification mode of store-by-store deployment and separation also made it difficult for compliance documents to be consistent across the entire device group.
A quarterly compliance audit found that the traceability of the transaction link of some Italian store equipment was incomplete, and the brand was required to suspend the new terminal until the rectification was completed-the rectification process took about a month, during which it also significantly slowed down the store checkout efficiency.
Experience summary: the performance of the modification scheme in the local small-scale pilot phase is completely no problem, the problem is that the same set of scheme is copied to the new EU market on a large scale before it is revealed-this is worth being included in the planning in advance before the success of the pilot is announced.
A Saudi Arabian retail chain has deployed hundreds of self-service machines from a smaller manufacturer without a written long-term spare parts supply agreement. When the manufacturer introduced a new generation of models, the core components of the old models were discontinued without advance notice and no stock plan.
As a result, a considerable part of the brand's equipment in Saudi stores has completely lost its maintenance channels and can only be left idle, and there is no feasible replacement plan in the short term.
Lessons learned: For large-volume purchases, written multi-year spare parts agreements and supporting materials for stable capacity are as important as the stand-alone price itself-verbal commitments cannot replace these.
Once the scale of the project and the supply chain constraints are clear, the decision is actually not complicated-the core is to match the delivery method with the project structure, rather than wrestling with which method is inherently better.
| Delivery method | Best Type of Project | Optimization objectives |
|---|---|---|
| Finished complete machine | Small-scale pilot, short-term project, pop-up shop | Plug-and-play speed, lower upfront coordination costs |
| SKD (Semi-Knocked Down) | Large multinational deployments with local assembly capabilities | Tariffs and logistics costs, moderate lead times |
| CKD (Full Parts) | Overseas owned factories, bonded area projects, large-scale supply chain | Maximize tariff/logistics optimization, in line with local assembly policy |
This link determines whether the whole process really stands up after the purchase contract is signed-the following criteria should be written into the supply agreement, not just verbally.
Each batch of equipment should undergo a long period of continuous aging test before shipment-usually between 48 and 72 hours, which is also a common practice in the industrial hardware industry-and also do batch-level parameter consistency verification, and issue a complete functional test report for each equipment.
Spare parts should be shipped with the lot, and equipped with a local replacement mechanism. If the equipment is faulty after reaching the local market, remote technical support should be available for troubleshooting.
Hardware interfaces should remain open at the basic level, and there should be no forced version locks or continued use tied to paid upgrades.
When conditions permit, the new generation of hardware should try to remain compatible with the older model structure so that existing equipment assets can continue to be used instead of becoming idle inventory in the next iteration.
The starting point for a good purchasing decision is to match the hardware solution to your true size and risk tolerance-not to go after the parameter list with the longest function list.
If you are evaluating suppliers or planning a multinational self-ordering machine deployment, the Qunmao team is happy to talk to you in detail about specific requirements-if our hardware is not suitable for your project, we will tell you directly.
No need. Standard modular positions support third-party, locally certified payment modules, and the choice of supply chain is entirely in your hands.
The hardware itself has nothing to do with the software, provides an open SDK and standard interface, and will not be bound to any specific ordering system or POS system.
Sure. For large-scale projects, we offer both finished and semi-bulk deliveries, depending on your supply chain and tariff strategy.
Not natural non-compliance. Compliance depends on the authentication of the payment terminal itself and the encryption of the transaction link, not the connection itself. The modification scheme can be used normally in the small-scale pilot phase, but it will often encounter more resistance after large-scale deployment-for specific comparison, please refer to the content of the first part.
Previous: Not yet.
Return to list
Next article:Guide to the Full Product Line of Self-Service Terminals (Kiosk) -7 Category Selection and Procurement Strategies 
Partner Links:
en
中文 
