🖨️ BizPrint to Smartender Integration Flow
📋 Summary Flow
- OAuth / Token Authentication
- API Polling or Webhook Events
- Agnostic to Windows Updates
- Managed by POS Vendor
- OAuth / Token Auth
- API Polling or Webhook Listener
- Secure, Non-PI Data Bridge
- Centralized Audit & Visibility
- Convert incoming payload into Smartender schema
- Validate and clean fields
- Map: order_id, customer_id, server_id, table_number, order_type, status, timestamps, item details
- Pipe-delimited .txt file
- Filename: TicketNumber + MMDDYYYYHHMMSS
- Example: 39234004222025172205.txt
- Fields: order_id, customer_id, server_id, table_number, order_type, status, created_at, completed_at, order_item_id, item_id, quantity, unit_price, modifiers, notes
- Push files to Smartender endpoint via SFTP
- SSH key-based authentication
- Include retry logic, logging, and rate limits
- Audit trail for file creation and delivery
- Queue unsent files with timestamped logs
- Receives & processes files from SFTP
- Ingests file to complete beverage dispensing journey
- Triggers dispense flow
📊 Performance Targets
🎯 Integration Approach
Selected Path: API Extraction (Cloud-Enabled) – This provides a scalable, secure, and maintainable solution with centralized visibility and audit control.
Why Not Printer Emulation? Local/sniffer-based approaches require privileged OS access, break with Windows updates, create unmonitored attack surfaces, and aren’t scalable. They remove centralized audit control and may violate POS vendor terms.
Security & Compliance: Cloud-based solution ensures secure non-PI data bridge, SSH key-based SFTP authentication, and comprehensive audit trails. All processing timing and volume targets can be guaranteed with SLA support.
Executive Value: No-hands solution where BizPrint develops the API integration and FTPs files to Smartender units, which then complete the beverage dispensing journey.