Freelance Video Editor Jobs

opportunity

Build Integration to send IONOS Web Orders to Kipos POS

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 1) 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 2) 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) 3) 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)

Freelance Exhibition Booth Assistant (UK)

1. Engagement Overview We are seeking a UK-based freelance exhibition assistant to support our participation at a technology exhibition in London. This is a short-term, on-site freelance engagement covering booth setup, exhibition days, and post-event dismantling and packing. This role is strictly limited to exhibition support, marketing assistance, and lead generation. The freelancer will not be authorised to negotiate, sign contracts, or make binding commercial commitments on behalf of the company. 2. Engagement Period Setup Day: 1 day prior to exhibition opening Exhibition Days: 2 days (full show hours) Dismantling & Packing: End of final exhibition day (Exact dates and venue details will be provided upon engagement.) 3. Scope of Work A. Pre-Exhibition Setup (Day Before Exhibition) The freelancer will be responsible for: Receiving Exhibition Materials Receive pre-shipped materials at a UK address (provided in advance) Verify receipt against a checklist supplied by us Booth Setup Arrange product samples, demo units, and marketing materials inside provided cabinets and display units Place brochures, flyers, and giveaway items neatly and professionally Ensure booth presentation matches reference photos / setup guide provided Branding & Visuals Apply supplied self-adhesive vinyl banners / stickers onto booth wall panels Ensure stickers are applied straight, clean, and without damage to panels Follow positioning instructions provided by us B. Exhibition Attendance & Support (During Show Days) During exhibition opening hours, the freelancer will: Booth Presence Be present at the booth during agreed hours Maintain a professional, welcoming appearance and conduct Visitor Engagement Greet visitors Distribute brochures, flyers, and marketing material Provide high-level explanations of products using supplied talking points Demonstrate products at a basic, non-technical level (training material provided) Lead Collection Capture visitor details using: business cards QR forms lead capture sheets or apps (as instructed) Note visitor interests and questions for follow-up Escalation & Follow-ups For detailed technical or commercial queries, direct visitors to: a designated email address, or scheduled online follow-up meetings Facilitate remote introductions where required (e.g., video call with our team) C. Post-Exhibition Dismantling & Packing At the end of the exhibition, the freelancer will: Branding Removal Carefully remove all vinyl stickers / banners from wall panels Ensure panels are left clean and undamaged, as required by the organiser Packing & Logistics Pack all product samples, demo units, and remaining marketing materials securely Label items according to instructions provided Arrange shipment to a specified UK address (courier details provided or approved by us) Confirm dispatch and provide tracking details 4. Materials & Support Provided by Us We will provide: All exhibition furniture (via organiser) Product samples and demo units Marketing materials (brochures, flyers, giveaways) Branding stickers / banners Setup reference photos and written instructions Product overview document and FAQ Lead capture method and reporting template Remote support during the exhibition if required 5. Deliverables The freelancer is expected to deliver: Properly set up and presented booth Continuous booth coverage during exhibition hours Daily summary of leads collected Secure packing and confirmed shipment of materials post-event Final handover report (leads + shipment confirmation) 6. Skills & Requirements Must be legally allowed to work in the UK Prior experience in: exhibitions, trade shows, events, or brand promotions (preferred) Strong communication and interpersonal skills Comfortable applying/removing adhesive branding materials Reliable, punctual, and detail-oriented Able to follow instructions accurately 7. Authority & Limitations The freelancer: ❌ Is not authorised to sign contracts ❌ Is not authorised to negotiate pricing or commercial terms ❌ Is not authorised to represent the company as a legal or sales agent All commercial discussions must be referred back to our team. 8. Engagement Type & Payment Engagement type: Freelance / Independent Contractor Duration: Short-term (event-based) Payment structure: Fixed fee or hourly rate (to be agreed) No employment, visa sponsorship, or long-term commitment implied 9. Confidentiality The freelancer must treat all product information, pricing discussions, and business contacts as confidential, and may not use collected leads for any purpose other than this engagement.

Unreal Engine + Pixel Streaming + Full Platform Integration

We are a technical team and we handle all technical solutions and decisions ourselves. We are not looking for an architect, a planner, or someone else to define the system for us. What we need is an execution-focused engineer who can help implement the website strictly according to our requirements. This project has very strict verification requirements. There are eight platform development contracts based on the same principle; this is just the first one. We need to deliver a multi-role platform based on (state-machine driven + Stripe payments/escrow + ad bidding + 3D digital humans via pixel streaming).Using low-code + modular composition, we are building an international platform. It must be explicitly stated that this is not an MVP. A.Deployment & Infrastructure(Must be assembled and built on the Fly.io platform) 1) The platform must run on (frontend/backend, jobs/queues, WebSocket/WebRTC services as needed). 2) Proper logging/monitoring/alerting is required, including alerts for third-party integration failures and cost/usage anomalies. B.Core Requirements (Important) 1) Multi-role / four portals: end users, service providers, maintenance staff, and admin portal (different permissions and flows). 2) Critical business flows must be implemented using a state machine / state-driven architecture (no “skipping steps”): order → payment → escrow/split → fulfillment → acceptance → settlement → refund/dispute, with full traceability, rollback rules, and audit logs. 3) Payments: Stripe (payments, payouts, webhooks). Must handle idempotency, webhook replay protection, and concurrency-safe state transitions. 4) Automation / orchestration: n8n (or similar) as the workflow hub, connecting Supabase, payments, notifications, ads, and digital humans. 5) Conversational guidance: use Botpress (or similar tools) for conversations + next-step actions. 6) Advertising: creative management + delivery configuration + analytics; ad slot bidding/auction (e.g., Prebid.js / RTB model). Bidding logs must be retained and auditable. 7) Multilingual: UI/content must support multiple languages and integrate language detection and translation APIs. 8) External widgets / external entry systems：iframe / JS SDK / external components with controlled internal core logic. 9) Risk control mechanisms: rate limiting, switches, circuit breakers, fast shutdown without impacting payments) 10) 3D digital human system (Unreal Engine Pixel Streaming): 10.1.) MetaHuman + Unreal Engine for creating 3D digital humans. 10.2.) Pixel Streaming (WebRTC) to stream UE video to web/mobile clients. 10.3.) A unified control interface to switch avatars/actions and drive lip-sync via TTS audio, integrated with state-machine-driven guidance flows. C.Execution responsibility (mandatory) 1) This project must be completed independently by you personally. We do NOT accept teams, outsourcing, temporary staffing, or task splitting. 2) This requirement exists purely for commercial confidentiality reasons. 3) If the project cannot be completed by one individual, please do not proceed. D. Price and maintenance terms (fixed) Project delivery price: USD 3,000 (fixed) Post-launch maintenance: - USD 100 per month (fixed) - Includes system stability, critical bug fixes, security updates, and environment handling - No unilateral price increase is allowed - Any adjustment requires written mutual agreement If your pricing expectation is significantly higher, or if you cannot accept these terms, please do not contact us. E.Delivery time: 1) For an experienced and skilled engineer, under normal circumstances, the full project should be achievable within two months. 2) In addition, we have a clear requirement that within an earlier phase of the timeline, a runnable pilot version must be delivered. This pilot version is not the final completion, but it must already be in a stable, operable state and able to enter trial operation. 3) During the trial operation, we will identify issues, validate stability, and make necessary adjustments, so that the final delivery can meet the required quality standards. F. Please reply with: 1) Similar projects you have delivered (if possible, provide links/demos). 2) Recommended architecture and service decomposition. 3) What materials you need from me to proceed (execution step flows, required module list, etc.). 4)phased timeline, rough price range.