InnoSyncSystemsBook a demo
Field-proven pilot · Early access

// InnoTerminal

The warehouse terminal, reimagined.

A modern replacement for Microsoft Dynamics' legacy ADCS warehouse-terminal system. It keeps all your Business Central warehouse logic exactly as-is, but moves the handheld experience onto secure cloud connectivity and modern rugged Android handhelds — field-proven on Zebra, and built to run on Honeywell, Datalogic and other leading devices.

Book a demo See how it works
4:30▮ ▲ ⌁ ▮
IT-LOGIN−+↻⚙
Welcome
User ID:
Password:
Enter12345
User ID:|
◀●■
// THE PROBLEMLegacy ADCS

Legacy ADCS won't move to the cloud

Many Dynamics 365 Business Central and NAV warehouses still run handheld terminals over ADCS — the old Automated Data Collection System that speaks VT100 / Telnet. Companies moving BC to the cloud hit a wall: their warehouse terminals don't come with them.

Legacy transport

Plain Telnet, green-screen VT100, and aging Symbol/Motorola hardware.

On-premises-bound

The classic ADCS engine can't run on Business Central SaaS at all.

Hard to modernize

Upgrading usually means ripping out and rewriting the warehouse business logic.

// THE SOLUTIONSame logic, new front end

A modern front end. The same Business Central logic.

InnoTerminal replaces only the transport, session and presentation layer of ADCS — never the warehouse business logic. Business Central keeps owning every screen definition, function, and warehouse transaction: put-away, pick, movement, count, posting.

Open Telnet

OAuth 2.0

VT100 byte streams

WebSockets / OData V4

Legacy terminals

Rugged Android + scanner

On-prem only

Business Central SaaS + on-prem

A device shows the same warehouse workflows the operator already knows — but on a touch screen with a hardware scanner, over an encrypted connection. It runs against Business Central SaaS, where classic ADCS cannot go, as well as on-prem.

// CAPABILITIESFeatures

Everything the operator already knows — on modern hardware

Warehouse flows, label printing, and a resilient native device experience — on rugged Android handhelds from Zebra, Honeywell, Datalogic and beyond.

Warehouse workflows, driven by BC

  • Operator login by scanning a badge/QR — user and password in a single scan.
  • Main menu: Pick, Put-away, Movement, Count, and Print Label.
  • Work real Warehouse Activity documents: drill into lines, enter Qty to Handle, and Register back into BC — the real posting.
  • Line progress tracking with a live done-count (* marks completed lines).
  • Item and data lookups that read live BC data — description, on-hand, unit of measure.
  • Screens are configured in BC (the same Miniform model as standard ADCS), not hard-coded.

Label printing from the handheld

  • Scan an item on the device and a physical label prints on a networked label printer — Zebra or another ZPL/EPL-compatible model.
  • A cloud print service queues jobs; a tiny on-prem agent drains them to the printer — built in-house, no third-party print subscription.
  • Label layouts are defined in Business Central codeunits (EPL and ZPL).
  • Per-user printer selection — different operators, different printers and formats.

Modern device experience

  • A standard native Android app — runs on rugged Android handhelds from Zebra, Honeywell, Datalogic and other leading makers.
  • Status header, quick-select buttons, clear confirm/error banners, adjustable font, portrait-locked, auto-connect on launch.
  • Hardware-scanner integration (Zebra DataWedge today) feeds scanned barcodes straight into the app.
  • Resilient sessions survive Wi-Fi drops, device sleep and brief cloud outages.
  • Idempotent retries — a re-sent scan never double-posts.

The app, in the order an operator sees it

4:30▮ ▲ ⌁ ▮
IT-LOGIN−+↻⚙
Welcome
User ID:
Password:
Enter12345
User ID:|
◀●■
STEP 01Secure sign-inScan a badge or QR to sign in — user and password in a single scan.
4:30▮ ▲ ⌁ ▮
IT-MENU−+↻⚙
Main Menu
1=Pick 2=Put-away
3=Move 4=Count
5=Print Label
6=Logoff
Option:
BackEnter12345
Option:|
◀●■
STEP 02Warehouse menuEvery workflow is defined in Business Central — not hard-coded.
4:30▮ ▲ ⌁ ▮
IT-PUTLIST−+↻⚙
Put-Away Docs
1) PU000001 5
Choose:
Select #:
BackFunctionsEnter12345
Select #:|
◀●■
STEP 03Real documentsBrowse open put-away and pick documents straight from BC.
4:30▮ ▲ ⌁ ▮
IT-ACTLINE−+↻⚙
Lines (*=done)
1) W-08-0001 WRB-1000 2 *
2) W-05-0003 WRB-1000 1
3) W-05-0002 WRB-1000 1
4) W-08-0001 WRB-1001 8
Choose:
Select #:
BackFunctionsEnter12345
Select #:|
◀●■
STEP 04Progress at a glanceProcessed lines are marked done as you work the document.
4:30▮ ▲ ⌁ ▮
IT-ACTDET−+↻⚙
Line Detail
Item WRB-1000
Bin W-08-0001
Zone RECEIVE
UoM BAG
Qty to Handle2
Outstanding 2
BackFunctionsEnter12345
Qty to Handle|
◀●■
STEP 05Confirm & registerEnter quantities and register the document back to Business Central.
4:30▮ ▲ ⌁ ▮
IT-ACTFUNC−+↻⚙
Functions
1. Return
2. Register Doc
3. Header Info
Choose:
BackEnter12345
Choose:|
◀●■
STEP 06Document functionsRegister, header info and more — the classic ADCS function menu, modernized.
4:30▮ ▲ ⌁ ▮
IT-PRINT−+↻⚙
Print Item Label
Item No:
BackEnter12345
Item No:|
◀●■
STEP 07Print a labelScan an item — a label prints on the warehouse Zebra printer via the cloud print service.
POS
Techdeck 96mm Board Ast
$4.49
2000100013
0 12345 67891 2
OUTPUTThe printed labelItem label generated in Business Central (EPL / ZPL), printed on a networked Zebra.
// ARCHITECTUREHow it works

Four cooperating pieces, one shared protocol

The Connector exposes BC's warehouse screens as a clean, structured semantic screen model and does the real work in BC. The Gateway moves and renders screens but never interprets warehouse logic. The Android app renders natively and feeds scans in. The Print Service and Agent handle the cloud-to-printer hop.

SESSIONOAuth 2.0 · OData V4 · secure WebSocket

Rugged Android handheld

Native terminal renderer; the hardware scanner (Zebra DataWedge today) feeds barcodes straight in.

Gateway (Azure)

Manages device sessions and renders screens. Never interprets warehouse logic.

Business Central + Connector

Owns every screen, function and posting; exposes the semantic screen model.

← semantic screen model rendered back to the device as structured screens

LABEL PRINTINGcloud → on-prem printer · ZPL / EPL

Business Central

Builds the label from a BC label codeunit.

Print Service (Azure)

Durable in-house label queue with a per-printer registry.

On-prem Print Agent

Tiny always-on service that drains the queue.

Label printer (ZPL/EPL)

Zebra or ZPL/EPL-compatible printer on the warehouse LAN, over TCP.

Connector
App inside Business Central: a thin facade over the standard ADCS/Miniform model; cloud-native re-implementation of the warehouse flows, plus label generation.
AL / Business Central extension (BC 28)
Gateway
Device-facing session manager in the cloud; WebSocket plus legacy Telnet bridge; makes secure OAuth calls to BC. Never interprets warehouse logic.
ASP.NET Core / .NET 10 · Azure Container Apps
Android app
Universal handheld client; native terminal renderer; Zebra DataWedge scanning.
Kotlin / Jetpack Compose
Print Service
In-house cloud label queue with durable jobs and a printer registry.
.NET 10 · Azure Container Apps + Table Storage + Key Vault
Print Agent
Tiny on-prem program that pulls jobs and sends them to the printer.
.NET console (Windows service/task)

Roadmap: an on-prem Legacy Bridge (Telnet↔HTTPS) for old Symbol/Motorola terminals.

// IN BUSINESS CENTRALConfigured, not coded

The logic lives in Business Central — and it's yours to change

InnoTerminal doesn't hard-code your warehouse. Every terminal screen is a Miniform defined in BC — the same model as standard ADCS — so your team owns the flows, fields, and rules, and can customize the processing logic with standard Business Central development.

  • Every terminal screen is a Miniform record in BC — code, form type, and line-by-line field bindings.
  • Lines bind straight to BC tables and fields (e.g. Warehouse Activity Line 5766), so screens read and write live data.
  • Change the flow yourself: add or reorder screens, bind new fields and validations, or branch between forms with Next Miniform.
  • A Handling Codeunit hooks your own AL logic to a screen — customize the processing behaviour without forking the app.
  • Users, locations and per-user printers are configured in BC (InnoTerminal Setup, ADCS Users, Warehouse Employees, Locations).

Setup area

SetupSessions
  • InnoTerminal Setup
  • ADCS Users
  • Warehouse Employees
  • Locations
  • Miniforms
  • Miniform Functions
Business Central · Miniform

MiniformIT-MENU

General
CodeIT-MENU
Handling Codeunit0 ▾
DescriptionMain Menu
Next Miniform▾
Form TypeCard ▾
Start Miniform
No. of Records in List0
Lines+ New Line✕ Delete Line
AreaField TypeTable No.Field No.Field LengthText
HeaderText000Main Menu
BodyText0001=Pick 2=Put-away
BodyText0003=Move 4=Count
BodyText0005=Print Label
BodyText0006=Logoff
BodyInput001Option:
Business Central · Miniform

MiniformIT-PICKLIST

General
CodeIT-PICKLIST
Handling Codeunit0 ▾
DescriptionPick Docs
Next Miniform▾
Form TypeSelection List ▾
Start Miniform
No. of Records in List5
Lines+ New Line✕ Delete Line
AreaField TypeTable No.Field No.Field LengthText
HeaderText000Pick Docs
BodyOutput5766220No.
BodyOutput5766134Lns
FooterText000Choose:
Business Central · Miniform

MiniformIT-ACTFUNC

General
CodeIT-ACTFUNC
Handling Codeunit0 ▾
DescriptionFunctions
Next Miniform▾
Form TypeCard ▾
Start Miniform
No. of Records in List1
Lines+ New Line✕ Delete Line
AreaField TypeTable No.Field No.Field LengthText
HeaderText000Functions
BodyText0001. Return
BodyText0002. Register Doc
BodyText0003. Header Info
FooterInput003Choose:

Customize and extend the processing logic

Because InnoTerminal keeps every warehouse transaction in Business Central, you extend it the way you already extend BC — no separate runtime, no fork of the app, and nothing to re-certify on the device. Reshape a flow by editing Miniforms; bind new table fields, defaults and validations on a line; branch between screens with Next Miniform; and attach a Handling Codeunit to run your own AL when a step posts. Pick, put-away, movement, count and label printing stay yours to change — in the ERP your team already knows.

Edit MiniformsField & table bindingsNext Miniform branchingHandling Codeunit (custom AL)Label codeunits (EPL / ZPL)No app fork

Screens shown from a Business Central demo (CRONUS) environment. The same Miniform, user and printer setup applies in your tenant.

// WHYWhy InnoTerminal

A better foundation than legacy ADCS

Cloud-ready

Works with Business Central SaaS, which classic ADCS fundamentally cannot.

Keeps your logic

No re-writing warehouse processes — BC still owns every Miniform, function and posting.

Secure by default

OAuth 2.0 and encrypted WebSockets in place of open Telnet.

Modern hardware

Standard Zebra Android devices with touch and an integrated scanner.

Configurable, not coded

Terminal screens are configured in BC data — table and field bindings, like ADCS.

Resilient

Session resume and idempotent retries survive network blips.

Extensible label printing

In-house cloud print pipeline; label layouts are BC codeunits (EPL & ZPL), routed per user/printer.

// STACKBuilt on Microsoft, Azure & Zebra

Enterprise-grade building blocks

A Business Central / AL extension, .NET 10 microservices on Azure, and a Kotlin Android client — all with managed identities.

Dynamics 365 Business CentralMicrosoft AzureEntra ID · Zebra · Honeywell · Datalogic
Business Central / AL (SaaS + on-prem).NET 10 / ASP.NET CoreAzure Container AppsAzure Container RegistryAzure Table StorageAzure Key VaultLog AnalyticsMicrosoft Entra ID (OAuth 2.0)Kotlin + Jetpack ComposeZebra DataWedgeSecure WebSocketsOData V4ZPL / EPLRugged Android 10+ (Zebra · Honeywell · Datalogic)
// SECURITYSecurity & reliability

Secure by default, duplicate-proof by design

// PRICINGPackaging

Simple, per-device pricing — we run the cloud

A per-active-device monthly rate, InnoSync-managed on Azure. Start with your first device free for 180 days, quick onboarding, and early-access founding pricing while InnoTerminal is in pilot.

Available now

Early Access

For first pilot warehouses going live now.

from $25/device · mo

Founding pricing

First device free for 180 days
  • Single warehouse, field-proven on Zebra
  • Full warehouse flows: pick, put-away, move, count
  • Label printing included
  • InnoSync-managed on Azure
  • Quick onboarding & go-live support
  • Founding rate locked in exchange for feedback
Start a pilot

Standard

For live Business Central warehouses on SaaS.

from $39/device · mo

Per active device

  • Multiple warehouses
  • All terminal workflows, configured in BC
  • Label printing included (EPL / ZPL)
  • InnoSync-managed Azure — infrastructure bundled
  • Rugged Android devices (Zebra, Honeywell, Datalogic)
  • Standard support
Book a demo

Enterprise

For multi-site and regulated operations.

Custom

Volume per active device

  • Unlimited warehouses and devices
  • Priority SLA & dedicated onboarding
  • Optional customer-hosted (BYO) Azure
  • OAuth 2.0, Entra ID, Key Vault security posture
  • Roadmap access (e.g. Legacy Bridge)
Contact sales

Billed per active device — InnoSync manages the Azure infrastructure. Quick onboarding from $500 one-time, and your first device is free for 180 days. All prices in USD. Contact sales for a quote.

// FAQCommon questions

Do we have to change our warehouse setup?

No — Business Central keeps all warehouse logic; InnoTerminal only modernizes the terminal connection and device.

Does it work with Business Central in the cloud?

Yes — that's a core reason it exists; classic ADCS doesn't.

What devices?

Rugged Android handhelds with a built-in scanner — field-proven on Zebra (TC21), and built to run on Honeywell, Datalogic and other Android devices.

Can it print labels?

Yes — scan an item and a label prints on a networked Zebra printer, with layouts defined in Business Central (EPL and ZPL).

Is it secure?

OAuth 2.0, encrypted connections, Azure Key Vault, and duplicate-proof messaging.

// STATUSField-proven pilot

A working, demonstrated pilot

Real scans on real hardware posting to real Business Central, with a live label coming out of a real printer.

  • Connector. Built, running against a live Business Central sandbox; full warehouse flow working.
  • Gateway. Built and deployed to Azure; live device sessions.
  • Android app. Running on a physical Zebra TC21 — login → menu → pick/put-away → register; item lookup; print.
  • Print Service + Agent. Deployed to Azure and verified printing a physical label end-to-end on a networked Zebra printer.
Request early access

On the roadmap

  • Multi-profile device management, richer label templates, reprint and label preview.
  • Legacy Bridge for old Symbol/Motorola terminals.
  • Agent self-registration with tokenized auth; horizontal scale-out; deeper telemetry.
  • Biometric/PIN device unlock; encrypted on-device profile storage.