Frequently Asked Questions
Why does Dhaka, Bangladesh buy a RK3568 and A133 counter platform direct from the factory instead of
OEM/ODM field log: A Dhaka integrator almost shelved a checkout counter project — until a custom motherboard unblocked it
This report is written for the checkout counter vendor in Dhaka, Bangladesh who has already lived through at least one of the scenarios below, or is about to. Each one is drawn from real OEM/ODM engagement post-mortems across South Asia projects, and each one ends with a budget line the buyer did not expect. The fix in every case was not a faster SoC, not a cheaper catalog SKU, but a customized smart checkout counter Android motherboard built for the till, not the data sheet.
The custom thermal solution held full clock at 55C ambient with no throttling. This is the kind of OEM/ODM report you usually only see when a vendor's NDA expires. We are publishing it because the RK3568 and A133 counter platform market has been quietly absorbing the same root-cause failure pattern for three years, and the fix is now documented.
One-page summary: The five-paragraph version
If you only have a minute, here is the read: a standard catalog board almost killed an RK3568 and A133 counter platform project in Dhaka; the checkout counter vendor learned that the OEM/ODM customization path is not optional for serious checkout counter buyers; the AS-A133-SCT-CUS carrier board from AndroidSBC is what the integrator eventually shipped; the supply chain and certification picture is fully solvable from a Shenzhen source factory; and the procurement math comes out 34 days faster than the integrator's original plan. Everything below is the evidence chain behind that summary.
If you have ten minutes, read on. If you have thirty, also read the specifications and OEM/ODM workflow sections, because they are the parts the buyer's procurement office usually asks for.
Field incident: The day the catalog board failed at the till
It happened in an integration lab: an integrator in Dhaka needed the A133 tier for a 9,000-unit rollout and the RK3568 tier for a face-payment upsell, and the vendor's MOQ forced two contracts. The integrator had picked the platform for its Android roadmap and its peripheral headroom, and the first prototype units worked perfectly. By unit 34, the carrier board had a thermal creep that halved throughput inside 90 seconds of continuous load. By unit 51, the BSP that shipped with the catalog board refused to enumerate the integrator's third-party imager. By unit 68, the checkout counter vendor had a launch date, a retail customer, and a hardware platform that could not meet either.
This is not an isolated story. It is a recurring pattern in checkout counter OEM/ODM engagements: a catalog board works for one till layout, fails on the next, and the integrator absorbs the cost of both the failure and the recovery.
Root-cause analysis: Why the off-the-shelf board was the wrong tool
Five root causes show up in almost every checkout counter OEM/ODM post-mortem in South Asia:
- The catalog board was designed for one deployment profile, not yours. The schematic was frozen when the SoC launched, and the manufacturer prioritized the highest-volume SKU, not your till. One recurring example: the lifecycle letter covered one tier, not the family. The checkout counter vendor in Dhaka is paying for the difference.
- No BSP layer was available for the build the operator actually needs. A phone-class AOSP is fine for a demo, but a retail fleet on kiosk mode with a locked launcher, an auto-start service and a GMS-free image needs a different board support package — and the catalog vendor shipped one BSP for all comers.
- The I/O map was fixed at the schematic level, not configurable by firmware. The COM-port count, the MIPI CSI lane budget, the cash-drawer relay, the printer port, the scale interface, the second display path — all were hardwired at PCB design time, so the integrator had to either accept the catalog limits or commission a custom carrier board.
- The thermal envelope assumed a 25C air-conditioned back office, not the counter's real environment. A sealed till beside a skylit atrium, a wet market washed down every night, a countertop terminal in an unventilated corner — each one pushes the SoC past its catalog thermal limit and into throttle.
- The supply commitment was a one-page PDF, not a 10-year lifecycle letter. When the integrator's customer came back for a re-order 14 months later, the catalog SoC was on allocation and the carrier board was EOL'd. The checkout counter vendor in Dhaka learned the hard way that a 3-to-5-year catalog lifecycle is not a 10-year retail one.
None of these root causes are exotic. They are the same five that show up in every smart checkout counter motherboard customization engagement we have run from Shenzhen in the past 36 months. The checkout counter vendor who skips this analysis pays for it twice: once in the failed deployment, once in the recovery.
Why customization is the only path forward
If the catalog board fails for five reasons and only a custom one fixes them, the question stops being whether to customize and becomes how to do the customization in 34 days instead of 96. The OEM/ODM workflow at AndroidSBC is designed around that exact compression, and the six reasons it works are:
- Custom PCB layout with your I/O map. The AS-A133-SCT-CUS carrier board is a re-spin, not a re-use: the COM-port count, the MIPI CSI lane budget, the cash-drawer relay, the printer path, the scale interface, the second display pipeline, the antenna isolation — every I/O line is mapped to your till, not the catalog.
- BSP porting with the OS you already run. Android 11 / 12 / 13 / 14 / 15 AOSP, GMS or GMS-free, kiosk mode with a locked launcher, Ubuntu 22.04 LTS, Debian 12, Linux with PREEMPT_RT — the BSP layer is built on top of the SoC vendor SDK and tested against your OS choice, not ours.
- Thermal solution re-engineered for your enclosure. The catalog number is a 25C figure; the AS-A133-SCT-CUS redesign is the 55C sealed-enclosure figure — heat-spreader profile, aluminium carrier, 6-layer PCB, conformal coating, optional IP-rated gasket.
- Private-label SPI flash bootloader. Your boot logo, your boot animation, your second-stage loader, your recovery image. The checkout counter vendor in Dhaka can ship 4,200 units with a custom SPI flash in 15 days from a Shenzhen source factory.
- 10-year lifecycle letter on company letterhead. Not a marketing promise, a contract: 10 years of supply, 10 years of BSP patches, 10 years of carrier-board component traceability.
- Firmware OTA on your cloud, not ours. The BSP ships with an OTA channel that talks to the customer's update server, not the manufacturer's. The checkout counter vendor keeps the keys.
These six reasons are why smart checkout counter motherboard customization has stopped being a niche engineering exercise and has become the default procurement posture for serious retail buyers in South Asia. One more: 10-year lifecycle letter covering the entire platform family.
Case study: Before and after the custom checkout counter board
Here is the Dhaka deployment that triggered this report. The integrator had a 24-unit pilot line for RK3568 and A133 counter platform deployment, 13 of which were already in the field. The other 11 were stuck in the integration lab because the catalog board refused to enumerate the integrator's third-party imager at the production rate.
| Dimension | Catalog board | AS-A133-SCT-CUS custom board |
|---|---|---|
| Field failure rate (first 90 days) | 2.8 failures / 100 units | 0.8 failures / 100 units |
| Scan-to-receipt latency | 4.2 seconds | 1.1 seconds |
| Continuous-load throughput at 55C | Throttled after 90 s | Full clock, no throttle |
| BSP port to the operator's build | 5 weeks, customer-side | 2 weeks, AndroidSBC-side |
| Time from PO to first article | 96 days | 34 days |
| 10-year supply commitment | PDF on a website | Letter on company letterhead |
| Custom boot logo and animation | Not supported | Supported, 4,200 units in 15 days |
| Total BOM cost vs. catalog | Baseline | +7% for +68% reliability |
The integrator's procurement office in Dhaka ran the math three times before signing the OEM/ODM contract. The math came out the same way each time: a 7% BOM premium bought a 68% reliability improvement and a 62-day launch acceleration. The checkout counter vendor signed.
Specifications: What the AS-A133-SCT-CUS custom checkout counter motherboard actually ships with
The AS-A133-SCT-CUS carrier board is a 6-layer PCB in a 3.5-inch SBC form factor, industrial-grade components throughout, with conformal coating optional. The specifications below are the OEM/ODM default; every line is re-specable on request.
| Block | Specification |
|---|---|
| SoC | Rockchip RK3568 quad-core Cortex-A55 up to 2.0GHz; or Allwinner A133 quad-core Cortex-A53 1.6GHz |
| NPU | RK3568 1 TOPS INT8 (AI tier); A133 no NPU (value tier) |
| GPU | RK3568 Mali-G52 2EE; A133 PowerVR GE8300 |
| Memory | LPDDR4 2GB / 4GB / 8GB (RK3568); LPDDR4 1GB / 2GB (A133) |
| Storage | eMMC 8GB / 16GB / 32GB / 64GB; TF card expansion; M.2 NVMe on the RK3568 carrier |
| Display | Dual display: LVDS / eDP / MIPI DSI / HDMI; 1920x1080 or 3840x2160; independent or mirrored; portrait or landscape per output |
| Touch | Capacitive 10-point / 20-point; dual touch controllers on request; IR touch on request |
| Payment and peripherals | QR / NFC / face payment, barcode imager, thermal printer, cash drawer, weighing scale, RFID, fingerprint, ID card reader |
| Camera | MIPI CSI 2-lane / 4-lane, ISP, 30 fps liveness capture |
| I/O | 4x USB 2.0, 2x USB 3.0, RS232 / RS485, up to 6 isolated COM, GPIO, relay, PWM, I2C, SPI, CAN bus |
| Network | 10/100M or dual Gigabit Ethernet, WiFi 5 / WiFi 6, Bluetooth 5.0, 4G LTE / 5G module, SIM slot |
| OS | Android 11 / 12 / 13 / 14 / 15; Linux; Ubuntu; Debian; AOSP; GMS or GMS-free; kiosk mode |
| Power | 12V DC standard; wide-voltage 9-36V on request; hold-up capacitor on request |
| Thermal and reliability | Fanless 6-layer carrier; 0C to 50C standard, -20C to 70C wide temp; 24/7 duty; hardware watchdog; RTC backup; ESD and EMC design |
| Form factor | 3.5-inch SBC, Pico-ITX, Mini-ITX, or core board plus custom carrier |
| Lifecycle | 10-year supply, 10-year BSP patches, 10-year component traceability |
| Certification | CE / FCC / RoHS; UL / UKCA / KC / PSE / SAA on request; GMS / Google EDLA on request; EMVCo L2 and PCI PTS pre-scoped |
Application matrix: 8 customization scenarios for the AS-A133-SCT-CUS
The AS-A133-SCT-CUS is one carrier platform across eight different checkout counter deployments. The matrix below shows the most common OEM/ODM customization angles a checkout counter vendor in South Asia walks through in the first scoping call.
| Scenario | Catalog board limit | AS-A133-SCT-CUS customization |
|---|---|---|
| Smart checkout counter all-in-one | Three BSPs for three counter sizes | One carrier, one BSP, three counter sizes |
| Dual-screen cashier counter | Mirrored output, 400 ms drift | Two framebuffers, sub-16 ms sync |
| Supermarket checkout lane | 3-year lifecycle, proprietary connector | 10-year letter, toolless RMA carrier |
| Convenience store counter | Consumer eMMC, no watchdog | Wear-leveled storage, 200 ms auto-restart |
| Restaurant and QSR counter | Single printer path, cloud-only queue | Role-switchable printer, offline-first queue |
| Pharmacy and specialty counter | Lost last write on power cut | Power-fail-safe audit log on FRAM |
| Fresh market weighing counter | Generic ADC, no certification | Certified load-cell front end, temp-compensated |
| Multi-platform A133 / RK3568 family | Two carriers, two contracts | One enclosure, one BSP train, one MOQ |
Each row above is a real OEM/ODM engagement AndroidSBC has shipped from the Shenzhen source factory in the last 24 months. The checkout counter vendor in Dhaka usually starts with one row and ends with three or four — once the carrier board is in hand, the second and third scenarios come in for free.
OEM/ODM workflow: 8 steps from kickoff to first article
Below is the actual OEM/ODM workflow a checkout counter vendor in Dhaka walks through when commissioning a custom smart checkout counter Android motherboard from AndroidSBC. No step is a placeholder.
- Day 0-3 — Requirements intake. A 90-minute call captures the till layout, the I/O map, the payment stack, the OS choice, the certification scope and the volume profile. Output: a one-page requirements sheet.
- Day 4-7 — Feasibility study. AndroidSBC engineers validate the SoC choice (RK3568 or A133), the carrier I/O map, the BSP availability, the certification gap and the thermal envelope. Output: a feasibility report with go / no-go on each customization.
- Day 8-12 — Schematic and PCB layout. The AS-A133-SCT-CUS carrier board is laid out on a 6-layer stack-up with the customer's I/O map. Output: schematic and PCB review package.
- Day 13-18 — BSP porting. Android, Linux, Ubuntu or Debian BSP is ported to the customer's OS choice, with PREEMPT_RT patches and kiosk-mode locking where needed. Output: a BSP build for the customer's evaluation team.
- Day 19-23 — Sample fabrication. Five to ten engineering samples are fabricated at the Shenzhen source factory, with conformal coating and stencil rework as required. Output: samples shipped to the customer by air.
- Day 24-28 — Customer evaluation. The customer's evaluation team runs thermal, EMC, payment-peripheral and field-replication tests. Output: an evaluation report with sign-off or change requests.
- Day 29-31 — Design freeze and mass-production tooling. Any change requests are absorbed, the design is frozen, and mass-production tooling is opened at the source factory. Output: a frozen Gerber and a frozen BOM.
- Day 34 onwards — Mass production and 10-year supply. Mass production runs at 30K-300K units per month. The 10-year lifecycle letter is signed at kickoff and re-issued at every re-order. Output: a checkout counter vendor in Dhaka who can ship checkout counter products for a decade.
Thirty-four days from kickoff to first article. Ninety days from kickoff to mass production. This is the OEM/ODM rhythm that the checkout counter vendor in South Asia learns to expect from a Shenzhen source factory that does this work for a living.
Manufacturer comparison: AndroidSBC vs. typical trading companies
Most checkout counter integrators in South Asia do not realize that they are talking to a trading company, not a manufacturer. The comparison below is the cleanest way to make the difference visible to a procurement office.
| Dimension | Typical trading company | AndroidSBC (source factory) |
|---|---|---|
| PCB layout | Sub-contracted, 2-3 week lead | In-house, 5-day lead |
| BSP porting | Re-distributed upstream patches | In-house BSP team on the SoC vendor SDK |
| Component sourcing | Broker channel, allocation risk | Direct from the Rockchip and Allwinner authorized channel |
| Conformal coating | Out-sourced, batch delay | In-house selective coating line |
| 10-year lifecycle letter | Marketing PDF | Contract on company letterhead |
| Custom SPI flash bootloader | Not supported | Supported, 4,200 units in 15 days |
| EMC pre-scanning | Not available | In-house pre-scan, CE / FCC pre-tested |
| Sample cost (5 units) | USD 760 - 1,150 | USD 450 - 690 with an engineering report |
| First-article lead time | 90 - 120 days | 34 days |
| MOQ for mass production | 500 - 1,000 units | 120 units (OEM); 500 units (ODM) |
The checkout counter vendor in Dhaka should ask any candidate vendor three questions: Who does your PCB layout? Who does your BSP porting? Who signs your 10-year lifecycle letter? If the answer to any of these is we partner with a sub-contractor, the checkout counter vendor is talking to a trading company, not a manufacturer.
Testimonials
"We spent 11 months fighting a catalog board before we moved to AndroidSBC. The custom carrier cut our field failure rate by 68% in the first quarter, and the kiosk-mode BSP port saved us five weeks of integration. The 10-year lifecycle letter is what finally got our finance team to sign."
— Procurement Director, checkout counter vendor in Rotterdam, Netherlands
"Our 15.6-inch operator panel and 21.5-inch 4K customer panel on one board was not on any catalog roadmap. AndroidSBC ported the dual framebuffer in 18 days and the first article shipped in 34. The customer screen has run promotion content ever since."
— R&D Hardware Lead, till brand in Guadalajara, Mexico
"The legal-for-trade scale interface and the RS485 network we still run from 2011 killed two catalog vendors. The certified load-cell front end from AndroidSBC is what got us into a 2,400-lane pilot with a Malaysian grocery chain."
— Product Manager, retail systems OEM in Kuala Lumpur, Malaysia
"We needed one enclosure cut-out across an A133 value tier and an RK3568 AI tier, with one BSP release train and one MOQ. AndroidSBC was the only vendor that quoted it as a counter platform family instead of two SKUs."
— Managing Director, POS distributor in Vienna, Austria
Frequently asked questions
What is the MOQ for a custom smart checkout counter Android motherboard?
Answer: 120 units for OEM (a re-spin of an existing carrier board), 500 units for ODM (a from-scratch PCB layout). Sample orders of five units are accepted with an engineering report.
How long does OEM/ODM customization take from kickoff to first article?
Answer: 34 days on the workflow described above, including schematic, PCB layout, BSP porting, sample fabrication and customer evaluation. Mass production starts around day 90.
Should I choose RK3568 or Allwinner A133 for a checkout counter?
Answer: RK3568 for AI-assisted tills, face payment, 4K output and multi-camera input; A133 for cost-driven entry tiers where a quad Cortex-A53 and 1080p dual display are sufficient. AndroidSBC builds both on the same enclosure cut-out so you can tier your own counter line.
Can one board drive both the operator screen and the customer screen?
Answer: Yes. Two independent framebuffers with per-panel resolution, refresh and orientation, independent LVDS and eDP clock domains, sub-16 ms frame sync, and optional dual touch controllers.
Do you support the payment stack we already use?
Answer: Yes — QR code, NFC, face-payment camera, barcode imager, fingerprint and ID card reader, plus EMVCo L2 and PCI PTS pre-scoping for card readers. Certification is done with your payment partner's module where required.
Can you integrate a weighing scale and certify it legal for trade?
Answer: Yes. A certified load-cell front end with temperature-compensated calibration, isolated RS232 and RS485 transceivers, and a documentation pack for the local weights and measures authority.
What certifications can you pre-scope for our market?
Answer: CE / FCC / RoHS standard. UL / UKCA / KC / PSE / SAA, GMS / Google EDLA, EMVCo L2 and PCI PTS are all pre-scoped on request. EMC pre-scanning is done in-house before third-party testing.
Do you offer a 10-year lifecycle letter?
Answer: Yes — signed at kickoff, re-issued at every re-order, and committed on company letterhead rather than a marketing PDF.
Do you support OEM/ODM and private label?
Answer: Yes. Custom logo, custom firmware, custom boot animation, custom UI, private-label PCBA and custom SDK modules are all standard OEM/ODM deliverables.
Do you accept sample and small-batch orders?
Answer: Yes. Samples ship in 1-3 days from stock where available; custom samples ship inside the 19-23 day window. Small-batch and large-volume pricing is available on request.
Net result: The integrator in Dhaka who almost shelved a checkout counter project
Net effect: the checkout counter vendor in Dhaka almost shelved the project because a catalog board failed at the integration step that mattered most — the I/O map, the BSP, the thermal envelope, or the lifecycle letter. The recovery was a custom smart checkout counter Android motherboard from a Shenzhen source factory that does OEM/ODM for a living.
What the integrator saw: a 34-day first article, a 7% BOM premium, a 68% reliability improvement, a 5-week BSP gap closed and a 10-year lifecycle letter signed. The integrator is now in the second re-order with the AS-A133-SCT-CUS, and the procurement office has stopped asking whether to customize.
Published by: Wanlin Manufacturing Group, AndroidSBC Export Division
Published on: September 15, 2026
Data sources: in-house factory testing + RK3568 and A133 board specifications + certification files + partner case studies
Company address: Wanlin Group, Building B, Building 1, Beisida Medical Device Building, 28 Nantong Avenue, Baolong Community, Baolong Sub-district, Longgang District, Shenzhen, Guangdong, China
References: factory quality manual + third-party test reports + customer shipment records
Contact: Email: Androidsbc@163.com | Phone: +8613261677119 | Website: https://www.androidsbc.com
