Integration of AmoCRM and Tilda.

Experience with Baselinker (mandatory) We are looking for a specialist to set up the Baselinker system for integration with Polish marketplaces and CMS. Connecting marketplace accounts to Baselinker, synchronizing stocks and orders, setting up automatic processing of orders, import/export of product items, configuring templates, labels, automatic notifications, testing and troubleshooting possible errors. Accounting for expenses, maintaining cost price, reporting on orders, etc. Experience with Baselinker (mandatory) The platform is already registered; it only needs to set up and optimize the processes.

It is necessary to set up a CRM system and end-to-end analytics for a service company specializing in appliance repair (Appliance Repair, USA).Current Situation Company website SEO Google Ads Google Business Profile (Google Maps) Facebook / Instagram Ads Ringostat Google Analytics 4 CRM Workiz External online booking system Setmore.com Important: we are not looking for an advertising or SEO specialist. All advertising channels are already operational. It is essential to correctly link all systems together.What Needs to Be Done Analyze the current operation scheme of Workiz and existing integrations. Set up or suggest a CRM (if Workiz does not allow for the necessary functionality). Set up end-to-end analytics between advertising sources, Ringostat, CRM, and Google Analytics. Set up automatic lead creation in CRM from all possible sources. Transfer the source of the inquiry to CRM (Google Ads, Organic, Google Maps, Facebook/Instagram, Direct, Referral, etc.). Check the possibility of integrating the external booking system Setmore.com with CRM. Set up reports or a dashboard where you can see: the number of leads from each source; the status of each lead; conversions; the effectiveness of each advertising channel.Expected Result Ultimately, we want to see a complete picture for each inquiry: where the client came from; through which advertising source; whether a lead was automatically created in CRM; the further status of the lead; statistics and conversions for each channel. If Workiz is not suitable for implementing these tasks, we are open to considering a transition to another CRM if the contractor can offer a more suitable solution and carry out its implementation.When Responding, Please Indicate experience in setting up Workiz (or similar CRMs); experience in implementing end-to-end analytics; experience in integrating Ringostat, Google Analytics, Google Ads, and CRM; which CRMs you would recommend for this task (if not Workiz); estimated cost and time for completion.

Homepage - dashboard. Statistics - Tasks, payments, clients BASE 1: "Clients" (Table view) Properties: - Name (Title) - Company (Text) - Phone (Phone) - Address (Text) - Email (Email) - Notes (Text) - Files (attachment) - Regular client (checkbox) - Service (Multi-select: Bookkeeping, Payroll, Accounting, Business formation, Taxes, Support, Other) - Tasks (Relation → base "Tasks", bidirectional link, shows related tasks directly in the client card) with current status - Payments (Relation → base "Payments", bidirectional link) with current status - Meetings (Relation → base "Meetings", bidirectional link) BASE 2: "Payments" (Table view, separate base for payment history) Properties: - Amount (Number, format — currency) - Client (Relation → base "Clients") - Date (Date) - Status (Future, Invoice, paid). - Notes (Text) Add quick filters with statuses and date ranges. Button to download csv. Add to the client card Rollup "Total of all payments" (sum) and a table of related payments for viewing history. Dashboard for payments. Total money paid for the week, month. Total future payments BASE 3: "Tasks" (Board/Kanban view) Properties: - Task name (Title) - Client (Relation → base "Clients"). Allow new value for leads, or Text, if not yet a client - Task date (Date, ability to add exact time) - Date (Date, current default) - Timetracker (automation - integrate a button for tracking time spent on each task) - Description (Text) - Estimate (Number, optional, format — currency) - Task type (Select: Sale, Bookkeeping, Accounting, Payroll, Business Formation, Taxes, Other) Set up Board view with grouping by status (new, today, tomorrow, future, on hold, archive). Separately display a table of all archived tasks with a button to download a csv file sorted by parameters BASE 4: "Meetings" (Calendar view) Properties: - Date (Date) - Start time (include time in the same Date property) - Client (Relation → base "Clients", allow new value for leads, or Text, if not yet a client) - Notes (Text) Display as Calendar view by property "Date". BASE 5. Regular clients - Name (Relation - Base Clients Name) - Company (Relation - Base Clients Company) - Amount (Number, format — currency) - Period (Select: Month, quarter, year) - Service (Relation - Base Clients Service (Multi-select: Bookkeeping, Payroll, Accounting, Business formation, Taxes, Support, Other)) - Notes (Text) - Dept (Relation - Base Payments - status Invoice)

Set up marketing trigger emails. It's better to discuss the details and the cost of the services as well. Thank you.

There is a ready web tool for the sewing industry — the interface is made, part of the logic is there, but real integrations are not connected. It needs to be brought to a working state. Demo: https://prognoz.rich2222shop.site/Goal The system must accurately show how many and what positions (size/color) need to be cut, see the total remaining (stock + in cutting + returns), and reduce re-sewing by accounting for the statistics of refusals.Tasks Integration with LP CRM — connect via API (key/subdomain fields are already available), pull in stock, orders, returns. Bypass CORS through a proxy on Render.com. Cutting calculation logic — finalize the formula Plan − Stock CRM − In cutting + Returns to work with real data, calculate based on the size×color matrix. Accounting for refusals in the forecast — the % of refusals by size/color should reduce the cutting plan for that position, not just be displayed. Unified total stock — consolidate stock + in cutting + returns into one table. Workshops and cutting history — distribution by workshops, acceptance of returns, history of transfers. Bug fixes — some buttons are currently placeholders, they need to be brought to a working appearance.Stack HTML/JS single-page, localStorage, integration with LP CRM API, proxy on Render.com.Requirements Experience integrating CRM via REST API (plus — experience with retailCRM/LP CRM) Experience with proxy/CORS Understanding of warehouse/manufacturing logic Willingness to improve existing code without rewriting from scratchWork format Communication in writing (chat/messenger) → phased delivery (CRM → calculation logic → stock/workshops → polishing) → demo at each stage. It is important to understand the essence of the task, not just to formally execute the terms of reference — it is welcomed if you propose your own solutions or improvements where you see that it can be made more convenient or reliable.Budget / Timeline Budget: 6000 UAH (negotiable depending on the scope and phased delivery)