Système de borne libre-service vs Système de point de vente (PDV)

1. Overview (System-Level Definition)

In commercial automation environments, Kiosk Systems et Systèmes de caisse (POS) are two core transactional subsystems designed for different interaction models within a retail or service workflow.

• A Kiosk System is a customer-operated self-service terminal
• A POS System is a staff-operated transaction control system

In modern architectures, both systems typically connect to a shared backend service layer, enabling unified order, payment, and data management.

Chez Aonkiosk, kiosk hardware is designed to integrate with mainstream POS ecosystems via API, middleware, or cloud-based order routing systems.

2. System Classification (Functional Layering Model)

From a system architecture perspective:

2.1 Kiosk System (Front-End Self-Service Node)

A kiosk is classified as a:

• Human-machine interaction (HMI) terminal
• Front-end order capture device
• Automated payment initiation unit

It operates in a customer-driven input model (CDI – Customer Driven Interface).

2.2 POS System (Transaction Control Node)

A POS is classified as:

• Staff-operated transaction controller
• Order validation and modification system
• Operational management terminal

It operates in a staff-driven input model (SDI – Staff Driven Interface).

3. Core Functional Difference (System Behavior Model)

4. Workflow Engineering Comparison

4.1 POS-Centric Workflow (Traditional Model)

This model follows a linear human-operated process:

1. Customer places request verbally
2. Staff enters order into POS
3. System calculates total amount
4. Payment is processed via POS terminal
5. Order is transmitted to backend/KDS
6. Receipt is generated

Key characteristic: Human-dependent bottleneck at order entry stage

4.2 Kiosk-Centric Workflow (Self-Service Model)

This model follows a user-driven automated flow:

1. Customer interacts with kiosk UI
2. Product selection is completed independently
3. System performs automatic pricing calculation
4. Payment is executed via integrated gateway
5. Order is pushed to backend system (POS/KDS/ERP)
6. Digital or printed confirmation is generated

Key characteristic: Order entry bottleneck is eliminated

5. System Architecture Integration Model (Aonkiosk Standard)

In enterprise deployment, kiosk and POS are not independent systems—they operate as part of a unified architecture:

5.1 Front-End Layer

• Kiosk terminal (customer interface)
• POS terminal (staff interface)

5.2 Integration Layer

• Order routing API
• Payment gateway interface
• Middleware synchronization service

5.3 Backend Layer

• Système de gestion des commandes (OMS)
• Inventory system
• Analytics & reporting system
• ERP/CRM integration layer

6. Data Flow Logic (Unified Transaction Model)

Both systems eventually converge into a single data pipeline:

Kiosk Input → API Gateway → Order Management System → Kitchen/Service System
POS Input   → API Gateway → Order Management System → Kitchen/Service System

Key Principle:

The difference is not in the backend, but in the data entry origin layer

7. Deployment Scenarios (System Selection Logic)

7.1 When Kiosk is Primary System

• High customer throughput environments
• Labor cost optimization required
• Queue reduction is critical KPI
• Standardized product catalog
• Fast service environments (QSR, retail, transport)

7.2 When POS is Primary System

• Complex order customization required
• Staff-guided service model
• High-touch hospitality environments
• Internal inventory-heavy operations
• Manual override requirement is frequent

7.3 Hybrid Architecture (Recommended Standard)

Most enterprise deployments use:

POS + Kiosk + Unified Backend

Benefits:

• Redundancy in transaction processing
• Load balancing between staff and self-service
• Higher peak-hour scalability
• Reduced operational bottleneck risk

8. Technical Integration Considerations

8.1 API Compatibility

Kiosk systems must support:

• RESTful API / JSON communication
• POS vendor protocol mapping
• Order synchronization endpoints

8.2 Payment System Integration

Supported models:

• Card payment (EMV/NFC)
• QR payment (Alipay / WeChat Pay / local wallets)
• Tokenized payment gateway integration

8.3 Real-Time Synchronization

Critical requirement:

• Order status must sync within <1–3 seconds latency
• Failure recovery mechanism required (retry queue)

9. Operational Troubleshooting (Support Reference)

Issue 1: Order mismatch between Kiosk and POS

Cause:

• API desync
• Middleware delay
• Duplicate request handling failure

Resolution:

• Check order ID mapping logic
• Validate API logs
• Enable retry queue mechanism

Issue 2: Kiosk payment success but POS not updated

Cause:

• Payment webhook failure
• Network interruption

Resolution:

• Verify payment gateway callback URL
• Check firewall or server timeout settings

Issue 3: POS overrides kiosk orders incorrectly

Cause:

• Role conflict in system permissions

Resolution:

• Define system hierarchy rules (POS override vs kiosk lock)
• Enable audit logging

10. System Design Principle (Aonkiosk Engineering Standard)

The correct design principle is:

POS = Control Layer
Kiosk = Interaction Layer
Backend = Source of Truth

This separation ensures:

• System stability
• Data consistency
• Scalable architecture
• Multi-channel ordering capability