Integrations
How Food-Ordering.com connects to the systems a restaurant already uses: POS, kitchen printers, payment providers and delivery marketplaces.
POS systems
Integration options depend on the POS vendor and model. Typical patterns are:
- Direct API integration — orders pushed into the POS in real time where the vendor supports it.
- Middleware — a third-party connector translates between the ordering system and the POS.
- File-based exchange — a scheduled export/import, used where API integration is not available.
Confirm your POS model during scoping so the integration route can be confirmed rather than assumed.
Kitchen printers and KDS
Epson ePOS, Star WebPRNT, generic ESC/POS and Windows printers are supported. Station routing sends drinks to the bar and food to the kitchen. See the printer setup guide.
Payment providers
Payment processing depends on deployment. Card, wallet and local payment methods can be configured. Payout timing and refund handling should be confirmed before launch.
Delivery marketplaces
Marketplace integration, where required, is handled through middleware so direct and marketplace orders flow into a single kitchen queue.
White-label and reseller deployments
For agencies and resellers, the platform can be deployed as a white-label product with the reseller's branding.
Related
Frequently asked questions
Does Food-Ordering.com work with my existing POS?
Integration options depend on the POS. Some systems connect directly, others via middleware or file-based exchange. Confirm your POS model during scoping.
Can it connect to delivery marketplaces?
Yes, via marketplace middleware where required, so marketplace and direct orders flow into a single kitchen queue.
Which printers are supported?
Epson ePOS, Star WebPRNT, generic ESC/POS and Windows printers are supported. The connection method depends on the printer and device.