Amazon Listing Projects

Outbound Sales Development Representative (B2B) Part-Time Remote

Industry: Industrial & Consumer Gases (Helium & CO₂) Products: Disposable helium cylinders for balloon inflation + CO₂ cylinders for soda systems Markets: UK, Germany, France, Spain, USA Deal Size: €2,000 – €20,000 per order Schedule: 3 days per week (part-time, long-term) ⸻ About the Role We are looking for an experienced Outbound Sales Development Representative (SDR) to support our Sales Director and sales team by identifying, contacting, and qualifying new B2B prospects. This is a high-quality, relationship-focused outbound role, not high-volume spam. You will use LinkedIn Sales Navigator and selective follow-ups via WhatsApp and telephone to initiate conversations and pass qualified, interested leads to our English-speaking sales team (Jade & Ali). ⸻ Your Responsibilities Prospecting & Targeting • Build targeted prospect lists using LinkedIn Sales Navigator • Identify decision-makers in relevant B2B segments (events, retail, wholesale, hospitality, distributors, etc.) • Focus on quality and relevance over volume Outbound Outreach • Send personalised LinkedIn connection requests and first messages • Conduct structured follow-ups (LinkedIn → WhatsApp → phone where appropriate) • Communicate professionally and in line with brand guidelines Lead Qualification & Handover • Engage prospects and identify genuine interest • Capture context, needs, and next steps • Pass warm conversations to the Sales Director / Sales Team in English • Maintain clear tracking of outreach and responses ⸻ Ideal Candidate Profile Required • Proven experience as a B2B SDR / Lead Generation Specialist • Hands-on experience with LinkedIn Sales Navigator • Excellent written English • Comfortable with cold outreach (LinkedIn, WhatsApp, calls) • Organised, process-driven, and reliable • Understands professional outreach vs spam Nice to Have • Ability to message in German, French, or Spanish • Experience in industrial, consumer goods, gas, or technical products • Familiarity with multi-channel outbound strategies ⸻ What This Role Is NOT • Not social media management • Not mass automation or scraping • Not high-volume copy-paste outreach • Not closing sales (handover to Sales Team) ⸻ Tools Provided • LinkedIn Sales Navigator • Approved messaging templates & outreach framework • Shared CRM / tracking sheet • WhatsApp Business (web access) ⸻ KPIs (Weekly – 3 Days) • Quality connections sent & accepted • Meaningful replies • Qualified conversations handed to Sales Team ⸻ Compensation • Hourly or fixed monthly retainer (based on experience) • Long-term opportunity for the right person • Performance-based increases possible ⸻ How to Apply Please include: 1. Brief summary of relevant SDR / lead generation experience 2. Confirmation of Sales Navigator experience 3. Languages you can outreach in 4. One short example of a LinkedIn opening message you would use

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)

SportPress Customisation - Wordpress

Job Specification – SportPress Customisation Project: Manager & Referee Login Portals + Match Workflow Platform: WordPress (SportPress Plugin) Objective: Build simple, user-friendly login areas for team managers and referees, with a controlled workflow for adding players, submitting match scores, and completing match reports. ⸻ 1. Overview We need two new user login areas—Manager Portal and Referee Portal—integrated with the existing SportPress plugin. These portals must be extremely simple and intuitive, suitable for non-technical users. The system must allow managers to log in, and complete their portion of match reports. Referees must be able to log in to see their assigned fixtures, record the score, and record disciplinary actions. Notifications and approval flows must be integrated. ⸻ 2. User Types 2.1 Managers • Log in to a dedicated Manager Portal. • Add players to their team (pending approval by admin before visible/active). • Receive notifications when referee has completed match data. • Complete their portion of the match report: • Goalscorers • Yellow/red cards for their players (if applicable) 2.2 Referees • Log in to a dedicated Referee Portal. • Access a list of their assigned matches only. • After the match: • Enter the final score. • Enter yellow/red cards issued (per team & player). • Submitting this triggers notifications to both teams’ managers. 2.3 Admin (Me) • Approves new players added by managers. • Can override any match data. • Receives notifications when managers and referees complete their steps. ⸻ 3. Functional Requirements 3.1 Login Portals • Entry points: • /manager-login • /referee-login • Clean, mobile-friendly UI (these users will likely be on phones). • Custom role types: • manager • referee • Restrict backend access — portals must be front-end based only. ⸻ 3.2 Manager Portal Features 1. Dashboard • Upcoming fixtures • Completed fixtures requiring match reports • Team information 2. Player Management • Add player (form fields TBD – basic info only) • Status: Pending approval / Approved • Admin receives notification when new player is submitted 3. Match Report Completion Managers should only be able to edit the following: (once completed they cannot edit) • Goals scored (select players; number of goals) • Cards for their own players (yellow/red) Validation: • Manager cannot enter scores; only referee can. • Manager cannot edit other team’s data. 4. Notifications • Email/push notification when: • Referee submits match result • Admin approves/rejects a player ⸻ 3.3 Referee Portal Features 1. Dashboard • Assigned matches • Match status indicators (e.g., pending input / completed) 2. Match Submission Form After the match, the referee should be able to record: • Final score (home/away) • Yellow cards (team → player → minute) • Red cards (team → player → minute) • Any admin notes 3. Submission Workflow • When submitted: • Lock referee fields from further editing • Trigger notification to both managers to complete their match report ⸻ 3.4 Data Workflow Summary Step 1: Match Played • Referee logs into Referee Portal → selects the match → enters: • Score • Cards • Submits match result. Step 2: Managers Notified • Both team managers receive notification (email/SMS if possible). Step 3: Managers Complete Match Reports • Each manager logs into Manager Portal. • Completes: • Goals • Cards for their players • Submits. Step 4: Data Goes Live • Once both teams submit, or after admin approves: • Results appear publicly on the website via SportPress. ⸻ 4. User Experience Requirements • Extremely simplified front-end UI. • No WordPress backend exposure. • Mobile-first responsive design. • Minimal fields and clicks. • Use large buttons, clear icons, and straightforward navigation. ⸻ 5. Technical Requirements • Integrate fully with SportPress custom post types and match data structures. • Custom post status for “player pending approval”. • Custom notifications (email or integrated WP notifications). • Use WordPress user roles/capabilities for access control. • Ensure compatibility with existing SportPress widgets and shortcodes. ⸻ 6. Deliverables • Functional Manager Portal (frontend). • Functional Referee Portal (frontend). • End-to-end workflow for match submission. • Player approval workflow. • Notification system. • Documentation for: • Adding managers/referees • Assigning referees to matches • Approving players • Editing match data

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.

opportunity

Tidy the server from X-ransom attack

Hello, Our Wordpress website was attacked by x-ransom. We have a backup of the WP and the database dump. We have detected some corrupted files there but it seems that there are still some left that were not detected. It has to be tidy after the attack. It’s an internet shop with uploads files of around 100GB. It’s stored on a private hosting in LV. What is done do far: 1. Update WordPress Version 2. Use z’d updateSecure WP-Admin Login Credentials 3. Set Up Safelist and Blocklist for the Admin Page 4. Use Trusted WordPress Themes 5. Install SSL Certificate 6. Remove Unused WordPress Plugins and Themes 1. Enable Two-Factor Authentication for WP-Admin 2. Back Up WordPress 3. Limit Login Attempts 4. Change the WordPress Login Page URL 5. Log Idle Users Out Automatically 6. Monitor User Activity 7. Check for Malware - found several none-Wordpress specious files and plugins. Deleted them. 1. Disable PHP Error Reporting 3. Turn File Editing Off 4. Restrict Access Using the .htaccess File 5. Change the Default WordPress Database Prefix - not done 6. Disable XML-RPC 7. Hide the WordPress Version 8. Block Hotlinking - not done 9. Manage File Permissions not done After making the list, we received another x-ransome attack. I suspect he has a server level access not only wp level. If you apply, you need to be a server security and a Wordpress specialist. Please, quote for the job.