Інтеграція продукту в amocrm

It is necessary to set up a connection between the tables, delineate access rights, and automate the calculation of net profit and commissions. What needs to be done: Order database and auto-distribution: The manager enters orders into the Main Table. Order data is automatically transferred to the personal tab/table of the master (each sees only their own orders). Automatic saving of customer history by phone number. Master's report in the table: The master marks the order status and enters actual figures (work volume, total amount, material costs, parking, etc.) directly in their table/row. Status and data are automatically saved. Automatic financial calculations: Auto-calculation of net profit for each order. Critically: The manager's commission is calculated only from the net profit. Consolidated financial report: A separate tab with summaries for the period (revenue, payments to masters, manager commissions, net profit of the company).

We are looking for an experienced eSputnik expert for the online store Ahimsa. https://ahimsa.in.ua/ We are already using eSputnik PRO, KeyCRM, Google Analytics, and an online store on Khorosho. We need to conduct an audit of the current CRM system, evaluate existing automations, identify points of loss for repeat sales, and propose a CRM development plan. In the first stage, we expect: an audit of the current eSputnik settings; analysis of automatic scenarios; recommendations for increasing repeat sales; a CRM development plan with priorities. If the collaboration is successful, we are open to long-term work. Please include in your response: What experience do you have with eSputnik? What results have you achieved for online stores? What CRM projects have you personally implemented? How will you start the audit in our project?

Our old custom system has outlived its usefulness, we need to grow. We are looking for an experienced professional to implement ERPNext. Must have experience, our field is wholesale and retail trade. There will be a lot of different standard and non-standard solutions, as well as classic connections to PRRO, Bank Mono and Privat, Nova Poshta, marketplaces, and so on. Ready?! :) Then send your resume and let's get to know each other.

It is necessary to set up the logical operations for the online store. Set up funnels, automations, and all necessary functions.

The client database has been collected over several years from various sources, so the phone numbers are recorded in different formats, one client exists under multiple IDs, cities are entered manually in different languages, and the region is almost never filled in. Because of this, it is impossible to properly segment the database. What needs to be done: 1. Database audit (paid separately, first stage). How many cards, how many phone numbers are out of format, how many duplicates, how many unique city entries. Based on the results — a refined estimate of the remaining work. 2. Standardization of phone numbers. All numbers should be brought to the format +380XXXXXXXXX. Numbers that cannot be unambiguously recognized should not be deleted or guessed, but listed separately. 3. Merging duplicates. Rule: one phone number = one client ID. At the same time, one client can have an unlimited number of numbers. Order history, emails, addresses, tags, and custom fields must be preserved. 4. Parsing cards that have many numbers "attached" to them. 5. Cities and regions. Names of settlements — from a single directory in Ukrainian (API of Nova Poshta or KATOHTG). The region must always be filled in so that all clients from Kyiv and the region can be exported with one filter, not separately for Brovary, separately for Irpin, etc. 6. Protection against re-contamination: normalization of phone and city at the input (website forms, integrations, manual entry) + regular background checks of new entries. Requirements: — practical experience with the SIMLA / RetailCRM (v5) API: exporting, updating, merging cards, request limits; — experience with data deduplication tasks; — understanding of Ukrainian address directories. Working conditions: full backup before any changes; initially a dry-run with a report on planned changes for approval, and only then launch on the live database; log of all operations with the possibility of rollback. No irreversible deletions without approval. In your response, please include: — timelines and cost