Basiq360 Line Gateway

Connect the line. Preserve its control.

The factory needs reliable physical execution—not a web request in the middle of a print cycle. Basiq360 Line Gateway coordinates serial supply, printing, camera checks and packing locally, while AIQR provides the broader identity, traceability and engagement platform.

Discuss your implementation Try the free GS1 generator

Existing capability

The documented fragrance-manufacturing line implementation includes D365 serial retrieval, local SQLite storage, printer/camera integration, carton workflows and a persistent ERP registration outbox. AIQR separately has gateway authentication, production-line and print-job services.

Integration & roadmap

The two systems’ API contracts and lifecycle events are being aligned. End-to-end Gateway-to-AIQR EPCIS synchronisation is planned, not presented as an already completed production connection.

From enterprise serial to verified package

The line implementation takes ERP-supplied serials into a local pool, queues the print, compares camera reads with expected identity and controls eligibility for carton aggregation. ERP serial values remain authoritative. Printer, camera and label-printer compatibility must be validated for the actual line.

Recovery is part of the workflow

Local serial and carton records survive restarts. Registration uses a persistent outbox and reconciles ERP state before retrying uncertain work. Permanent business rejections are distinguished from transient connectivity failures, giving operators a recoverable exception rather than repeated blind submissions.

Local-first does not mean unlimited offline operation

Cloud event delivery must not become a dependency of a production cycle. Continued operation still depends on locally available serials, healthy storage and the existing line and ERP safety rules. Each deployment needs capacity limits, recovery procedures and an agreed offline operating window.

Respect what the hardware actually proves

A printer acknowledgement, a matching camera decode, an accepted weight and a physically confirmed reject are different facts. A camera identity match is not an ISO barcode-quality grade. Weight and PLC eject confirmation must be established on site before relying on them as evidence.

Bridge existing printing to the digital platform

The evaluated line code path constructs a GS1 element string. A phone-openable Digital Link is a different payload. The integration starts by preserving the installed printing behaviour; any format change needs separate printer, reader and packing validation. ERP-sourced and AIQR-sourced identity workflows must coexist without silently reassigning serials.

Common questions

Does the Gateway replace the ERP?

No. The ERP supplies enterprise context and, in the evaluated implementation, serials. The Gateway executes line-side work and reconciles carton registration.

Is every printer supported?

No universal compatibility is claimed. Protocol, model, firmware, substrate, line speed and reader behaviour require a deployment-specific assessment.

What connects this to AIQR’s loyalty and product pages?

A shared product identity can connect production history to configured cloud experiences. Reliable event ingestion and identity mapping are the next integration work; a printed serial alone does not activate loyalty.

Production. Identity. History. Engagement.

A connected-product platform. Not just a QR code.

AIQR brings tenant administration, product identity, verification, traceability, loyalty and branded experiences into one modular platform. Gateway, EPCIS and Resolver capabilities connect the factory story to the digital services around each product.

Each capability page distinguishes existing functionality from integration work and planned standards support.

Explore the whole AIQR platform →