Customization brief: A Rio de Janeiro integrator almost shelved a new retail rollout — until a custom motherboard unblocked it
The OEM/ODM workflow shaved 31 days off the integrator's launch. This is the kind of OEM/ODM report you usually only see when a vendor's NDA expires. We are publishing it because the smart locker control board market has been quietly absorbing the same root-cause failure pattern for three years, and the fix is now documented.
Skim in 60 seconds: The five-paragraph version
If you only have a minute, here is the read: a standard catalog board almost killed a smart locker control board project in Rio de Janeiro; the field deployment lead learned that the OEM/ODM customization path is not optional for serious new retail buyers; the AS-RK3568-SLK-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 31 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.
Root-cause analysis: Why the off-the-shelf board was the wrong tool
Five root causes show up in almost every new retail OEM/ODM post-mortem in Latin America:
- 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 store format. One recurring example: the tamper chain was a software poll, not a hardware interrupt. The field deployment lead in Rio de Janeiro 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 store 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 GPIO island, the relay drivers, 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 store's real environment. A sealed menu board in a sunlit atrium, a vending machine behind a glass front, a gateway box above a ceiling void — each one pushes the SoC past its catalog thermal limit and into throttle.
None of these root causes are exotic. They are the same five that show up in every new retail smart terminal motherboard customization engagement we have run from Shenzhen in the past 36 months. The field deployment lead 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 31 days instead of 92. 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-RK3568-SLK-CUS carrier board is a re-spin, not a re-use: the COM-port count, the MIPI CSI lane budget, the GPIO island, the relay drivers, the printer path, the second display pipeline, the radio island — every I/O line is mapped to your store format, 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-RK3568-SLK-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 field deployment lead in Rio de Janeiro can ship 5,000 units with a custom SPI flash in 16 days from a Shenzhen source factory.
- 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 field deployment lead keeps the keys.
These six reasons are why new retail smart terminal motherboard customization has stopped being a niche engineering exercise and has become the default procurement posture for serious retail buyers in Latin America. One more: hardware tamper interrupt with sub-200 ms alarm latency.
Specifications: What the AS-RK3568-SLK-CUS custom new retail motherboard actually ships with
The AS-RK3568-SLK-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 RK3588 octa-core Cortex-A76/A55 up to 2.4GHz; RK3568 / RK3566 quad Cortex-A55; RK3399; RK3288; Allwinner A133, H618 or T527 on the value tiers |
| NPU | RK3588 6 TOPS INT8; RK3568 1 TOPS; value tiers without NPU |
| GPU | RK3588 Mali-G610 MP4; RK3568 Mali-G52 2EE; A133 PowerVR GE8300 |
| Memory | LPDDR4 / LPDDR4X / LPDDR5, 2GB to 16GB depending on tier |
| Storage | eMMC 5.1 8GB / 16GB / 32GB / 64GB / 128GB; UFS 2.1 option; TF card; M.2 NVMe on the RK3588 carrier |
| Display | Single, dual or triple output: LVDS / eDP / MIPI DSI / HDMI; 1920x1080, 3840x2160 or 7680x4320 decode; 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 multi-camera capture for AI SKU recognition |
| I/O | 4x USB 2.0, 2x USB 3.0, RS232 / RS485, up to 6 isolated COM, GPIO island, relay, PWM, I2C, SPI, CAN bus |
| Network | Dual Gigabit Ethernet, PoE+ option, WiFi 5 / WiFi 6, Bluetooth 5.0, 4G LTE / 5G module, SIM slot, 2.4 GHz radio island for ESL |
| 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; PoE+ 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 |
Application matrix: 8 customization scenarios for the AS-RK3568-SLK-CUS
The AS-RK3568-SLK-CUS is one carrier platform across eight different new retail deployments. The matrix below shows the most common OEM/ODM customization angles a field deployment lead in Latin America walks through in the first scoping call.
| Scenario | Catalog board limit | AS-RK3568-SLK-CUS customization |
|---|---|---|
| New retail smart terminal | Three BSPs for three store formats | One carrier, one BSP, three formats |
| Smart vending machine | Reference NPU at 11 fps, 8 GPIO | 6 TOPS tuned pipeline, 32-channel island |
| Smart locker controller | 8 GPIO, 1 Hz door poll | 64-channel island, sub-200 ms interrupt |
| Digital signage player | 1080p ceiling, memory leak | 8K decode, 30-day soak-tested loop |
| Dual-screen interactive display | Mirrored output, 400 ms drift | Two framebuffers, sub-16 ms sync |
| Smart shelf gateway | USB radio dongle, blind pushes | On-board 2.4 GHz island, ERP reconciliation |
| Unmanned store terminal | Online-only sales, 4-camera NPU | Signed offline ledger, 12-camera fusion |
| Multi-platform retail family | Four carriers, two contracts | One enclosure, one BSP train, one MOQ |
OEM/ODM workflow: 8 steps from kickoff to first article
Below is the actual OEM/ODM workflow a field deployment lead in Rio de Janeiro walks through when commissioning a custom new retail smart terminal Android motherboard from AndroidSBC. No step is a placeholder.
- Day 0-3 — Requirements intake. A 90-minute call captures the store format, 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 (RK3588, RK3568, RK3566 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-RK3568-SLK-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-30 — 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.
Thirty-one days from kickoff to first article. Ninety days from kickoff to mass production. This is the OEM/ODM rhythm that the field deployment lead in Latin America learns to expect from a Shenzhen source factory that does this work for a living.
Manufacturer comparison: AndroidSBC vs. typical trading companies
Most new retail integrators in Latin America 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 |
| Custom SPI flash bootloader | Not supported | Supported, 5,000 units in 16 days |
| EMC pre-scanning | Not available | In-house pre-scan, CE / FCC pre-tested |
| First-article lead time | 90 - 120 days | 31 days |
| MOQ for mass production | 500 - 1,000 units | 150 units (OEM); 500 units (ODM) |
Frequently asked questions
What is the MOQ for a custom new retail smart terminal Android motherboard?
Answer: 150 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: 31 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 RK3588 or RK3568 for a new retail terminal?
Answer: RK3588 for AI vision, multi-camera SKU recognition, 8K decode and triple independent display; RK3568 for interactive terminals, lockers and gateways where 1 TOPS and 4K dual display are sufficient; A133, H618 or T527 for shelf-edge screens and cost-driven tiers. AndroidSBC builds all of them on the same enclosure cut-out.
Can you drive multiple screens with independent content?
Answer: Yes. Up to three independent outputs on the RK3588 carrier with per-screen resolution, refresh and rotation, independent LVDS and eDP clock domains, sub-16 ms frame sync, and optional dual touch controllers.
Do you support electronic shelf label gateways?
Answer: Yes. An on-board 2.4 GHz radio island driving up to 4,000 labels inside 90 seconds, ERP reconciliation before every write, signed over-the-air updates and a stale-price alarm.
Can you control a smart locker bank from one board?
Answer: Yes. A 64-channel isolated GPIO island with per-door current sensing, 500,000-cycle relay drivers, a hardware tamper interrupt with sub-200 ms latency and a power-fail-safe audit log.
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 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.
Final read: The integrator in Rio de Janeiro who almost shelved a new retail rollout
Operational delta: the field deployment lead in Rio de Janeiro almost shelved the rollout 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 new retail smart terminal Android motherboard from a Shenzhen source factory that does OEM/ODM for a living.
Published by: Wanlin Manufacturing Group, AndroidSBC Export Division
Published on: September 16, 2026
Data sources: in-house factory testing + RK3588 and RK3568 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
