Upgrades on OpenCart

It is necessary to migrate a custom project from CodeIgniter 2 to Laravel 12. I will provide details in private messages.

A full diagnosis is needed and the issue with the transmission of the Purchase event in Meta Events Manager should be resolved. The site runs on OpenCart 3.x. The module SP SEO REMARKETING ALL IN ONE PRO 9.2 is installed. Meta Pixel and Conversions API are configured. Meta support reported an incorrect transmission of the Purchase event, which may lead to improper optimization of advertising campaigns.Tasks to be completed Audit the configuration of Meta Pixel. Check the functionality of the Conversions API. Verify the transmission of all main events: PageView ViewContent AddToCart InitiateCheckout Purchase Identify the cause of the incorrect transmission of Purchase. Fix all errors. Ensure that Purchase triggers only once after a successful order placement. Set up deduplication between browser and server events (event_id). Check the transmission of the following parameters: value; currency; content_ids; contents; num_items; event_id; customer_data (if possible, according to Meta's recommendations). In summary - correct transmission of events to the Meta cabinet.

Вітаю! Шановні фрілансери. Необхідно налаштувати передачу товарів з сайту на OpenCart на сайт Пром. Зі збереженням знижки на кількість. При цьому щоб мати можливість зробити націнку на товари, які передаються. Дякую. Прошу звертатися тільки тим, хто не "зникає". Працюю виключно через Сейф

Mockups of new pages, design mockups, and a detailed technical task will be provided in Figma (link attached). A link to the current version of the website will also be provided for familiarization with the existing implementation. Please note that we are not technical specialists. During the testing period, we were able to identify a significant number of errors and incorrectly implemented scenarios; however, we cannot guarantee that this is a complete list of shortcomings. There may be other technical errors or incorrect settings that can only be discovered during a professional code audit and comprehensive functionality testing. That is why, before starting work, we expect the contractor to conduct a technical audit of the current state of the website, check the functionality of all implemented features, and identify any additional issues that may need correction. The ultimate goal of the project is to obtain a fully ready-to-launch online store, in which all functions specified in the technical task work correctly, integrations are properly configured, there are no critical technical errors, and all functionality has undergone comprehensive testing and is ready for real-world use.Humanize 152 words You have a free plan The current state of the website: https://beautylady.ua/ Mockups of the cart/checkout: https://www.figma.com/design/MLJeIwBRcMqJC7PweBuORm/Cart-checkout?node-id=0-1&t=3OFCn9AlmvGDEEPW-1

Development of a SaaS platform and software for self-service kiosks. 1. General project description Development of a B2B SaaS platform based on the HaaS/RaaS model (Hardware/Retail as a Service) for automating sales in barbershops and beauty salons. The product consists of a cloud management panel (Web Admin Panel) and a client web application (Kiosk Frontend) operating on 24-inch vertical touch screens in a secure mode. 2. System architecture Backend (Cloud server): Data storage (PostgreSQL/Supabase), subscription management for owners, processing API requests. Web Admin Panel: Owner's personal account. Kiosk Application: Terminal interface. Hardware Bridge: Local wrapper program (Electron.js or Python) for connecting the web tab of the browser with the physical ports (USB/COM) of the payment terminal and receipt printer. 3. Owner's personal account (Web Admin Panel) Access is provided by subscription. The panel should be as intuitive as possible, without complex drag-and-drop mechanics. Module "Constructor" (CMS) • Uploading the salon logo. • Choosing a visual theme from 3 presets (Light Minimalistic, Dark, Branded). • Tabular input: adding masters (photo + name), service categories, and price list. • "Publish / Launch" button: saves settings and generates a unique secure link. When this link is opened on the kiosk, a ready-to-use interface is launched. Module "Marketing and Upsell" • Adding complementary products (cosmetics) for additional sales. • Setting up automatic discounts ("Happy Hours"). Module "Analytics and AI" • Dashboard: revenue, number of transactions, statistics for each master (including collected tips). • AI Assistant (based on LLM), which summarizes the week's results in text and gives sales advice. 4. Kiosk application (Kiosk Frontend) Vertical interface (aspect ratio 9:16), operating in full-screen Kiosk Mode (strict lockout of access to the operating system). Main navigation and multilingual support • A language selector is located in the corner of the screen. • Localization (i18n): English and Polish languages are hardcoded in the code for instant loading. Other languages (Spanish, French) are translated dynamically via API (DeepL/Google) with mandatory caching of translations in the salon's database to save requests. • Three main buttons on the start screen: "New Visit," "Repeat Visit," "Purchase Products." Scenario "Repeat Visit" and loyalty program • The client enters their phone number for identification. • Hidden loyalty: the system checks the visit counter in the database. If the condition set by the owner is met (for example, "6th haircut"), an animation of a gift is displayed, and a 100% discount is automatically applied. • An offer to repeat the last service with the same master in one click. Scenario "New Visit" and payment • Choosing a master. • Choosing a service. • Upsell screen (offering to add shampoo, paste, or an additional service). • "Smart Tips" screen: a pop-up before the final amount — "Will you leave a tip for the barber [Name]?" Action buttons: "No, thank you," quick denominations (e.g., 5 zł, 10 zł, 20 zł), and "Other Amount" button (calls the numeric keypad). • Payment: transferring the final amount (service + tips + products) through the Hardware Bridge to the bank terminal. Payment waiting animation. Transaction completion and marketing • SMS receipts and Google Maps: an offer to send the receipt via SMS. The SMS integrates a link to the electronic receipt and a request to leave a review on Google Maps (the link to the maps is set in the admin panel). • Quality assessment: the last screen with a photo of the master and 5 stars — "Rate the work." One touch sends the rating to the owner's admin panel and returns the kiosk to the main screen. 5. Hardware and stability requirements Integration with acquiring • Direct API integration with Polish terminals (Polcard, eService). • The system must correctly handle errors: insufficient funds, cancellation by the client, timeout. Integration with printer • Automatic printing of fiscal receipts. Offline resilience • In the event of a short-term Wi-Fi network drop, the kiosk saves visit data locally and synchronizes it with the server when the connection is restored. 6. Recommended technology stack Frontend (Admin Panel + Kiosk) • React • Next.js • TailwindCSS Backend & Database • Supabase (PostgreSQL) • Node.js Hardware Bridge • Electron.js (for packaging the web version into a desktop application with access to USB/COM ports of the hardware) AI & External API • OpenAI API (AI analytics) • Twilio or SMSAPI (sending SMS receipts)