Build Integration to send IONOS Web Orders to Kipos POS
Description
We run a food takeaway and need a developer to build an integration so that orders placed on our IONOS webstore are automatically sent into our Kipos account (https://app.kipos.uk/) and print straight to our kitchen/printer setup with no manual re-entry.
This must be production-ready: fast, reliable, and built to handle busy service periods.
What the integration must do
Capture new online orders from IONOS Detect new orders as soon as they’re paid/confirmed (or the correct “ready for kitchen” status) Pull all relevant order data: Order ID, timestamp Customer name + phone/email Delivery vs collection Address (delivery) / pickup details (collection) Requested time: ASAP vs scheduled (time slot if applicable) Customer notes (allergies, “no onions”, etc.) Items, quantities, variants Modifiers / add-ons / extras (e.g., “extra cheese”, “no sauce”, spice level) Discounts / delivery fee / tips (if present) Payment method/status
Create the order in Kipos exactly as the kitchen needs it Push the order into Kipos so it lands in the correct screen/queue as an online order Map all the required fields Ensure delivery/collection is correctly set and visible on print tickets Include requested time clearly (especially for scheduled orders)
Auto-printing to kitchen printers Orders arriving in Kipos should auto-print to our configured printer(s), or be inserted into the correct Kipos workflow/status that triggers printing.
Key requirements (takeaway-specific) Modifier & note handling (critical) Must support multiple modifiers per item, and multiple items each with their own notes Preserve formatting so the ticket is easy to read during service
Handle edge cases like: “No X” and allergy notes Duplicate prevention + reliability No duplicate tickets/orders if a webhook retries or the sync is re-run Retry + failure handling: Automatic retries Clear error logs Optional alert (email) if an order fails to sync Operational timing Webhook/event-driven preferred (near-instant) Polling acceptable only if webhooks aren’t available, but it must still be reliable and efficient
Security Secure credential storage (environment variables/secret store) HTTPS, least-privilege access
Preferred technical approach We’re open to the best implementation, but we expect this to be either: Middleware service (recommended): listens for IONOS orders and posts to Kipos or Direct plugin/integration if IONOS supports it.
Deliverables Working live integration: IONOS → Kipos order creation + printing workflow
Configuration options: Which order status triggers sending Item/modifier mapping method Logging dashboard or structured logs (success/failures, retries, duplicates)
Documentation: Setup steps How to update menu/mappings Troubleshooting guide
Test evidence: At least 10 varied test orders (modifiers, delivery/collection, scheduled/ASAP)
Source code + handover (Git repo or zip) Short post-launch support period (bug fixes)
Acceptance criteria A new IONOS order appears correctly in Kipos within an agreed time (e.g., under 60 seconds if webhook-based) Ticket prints automatically (or via correct Kipos status trigger) without staff interaction Items, modifiers, notes, times, and delivery/collection details are accurate and readable No duplicates under retries/network issues Clear logs for each order’s sync status
To include in your proposal Your recommended approach (webhooks vs polling, architecture, hosting) Relevant experience (POS integrations, online ordering, printers/kitchen workflows) Estimated cost + timeline (phased: build → test → deploy) What you need from us (API access, sample menu, Kipos printer workflow details)
Info we can provide to speed things up Sample orders (with modifiers/notes) Our current IONOS product list/menu structure Screenshot/video of our Kipos order screen + print output requirements Printer setup details inside Kipos (single printer or multiple stations)
Budget: GBP 250 (Fixed Price)
Proposals: 21 freelancers have applied