Budget: 30 USD Deadline: 1 day
Good evening!
Feel free to reach out, I will help as I receive information.
Thank you.
Hello, I have a project on the stack Laravel + Vue 3 + Inertia + MySQL
I request a call, during which I will consult on the following issue:
It will be very vague now, but I will try to avoid "names"
There was one large CRM database with one database
Then a separate franchise1 was created and a completely different database
Then also a separate franchise2
they did not depend on each other
These CRMs are scattered across 3 cities
And then, a separate franchise4 was separated, but it was simply copied from the main CRM
And now the most interesting part:
up to a certain ID, clients, sales history, etc. are fully duplicated.
and after June, the databases go in 2 streams (because they are copied) …. well, let's say everything would be fine, but clients in the CRM are duplicated in almost all franchises ….
The unique field is the phone number
Up to a certain "day" this is normal… but when a new sale is created in the CRM, it is no longer in one of the franchises (accordingly)… what to do? continue to duplicate (as now), and the API request information from other databases?
And when a new client buys at the franchise, he is not in the main CRM and then this client is created again in the main CRM, a sale is created for him with a cost of 0… so that the profit does not get distorted, and only then he appears in the search, horror! What can be done?
With all this, the same situation may repeat in other cities ….
Is there an option to merge the client database of the city? also some nomenclatures...
Or the client database of the country?
That is, a common one.... as well as other dependent databases, etc.?
And many questions about MySQL, I did not create dependencies there, etc.
Approximately such questions
Please write your experience and proposal regarding time and cost
Budget: 30 USD Deadline: 1 day
Good evening!
Feel free to reach out, I will help as I receive information.
Thank you.
Budget: 35 USD Deadline: 1 day
Good day. I am interested in your order. I have been working in the web sphere since 2014, and I have been writing in Laravel for over 6 years. Please message me for discussing the details.
Приветствую!
вариантов не так много:
костыльный (короткосрок): оставить базы раздельно, но сделать API-шину, которая синхронизирует клиентов между ними (например, при создании клиента в франшизе — пуш в мастер БД).
оптимальный: выделить централизованную клиентскую базу (страны/всей сети). Франшизы работают с локальными продажами, но клиентская часть общая.
идеальный (но долгий): мульти-тенант архитектура (merchant_id/tenant_id), где у вас одна БД, и все франшизы различаются по
merchant_id. Тогда клиенты единые, продажи/номенклатура/отчётность разделяются по франшизам
Тем более на что обратить внимание в первую очередь:
Нормализация данных клиентов
сейчас у вас клиенты дублируются во всех базах, а уникальный ключ — телефон.
правильнее сделать единый справочник клиентов (master DB), где каждому клиенту соответствует уникальный
client_id.остальные базы (франшизы) должны ссылаться на этот master через
client_id, а не хранить копии.Проблема дубликатов
нужно провести процедуру дедупликации (по телефону, email, паспорту, комбинации полей).
разрулить «исторические» данные: до определённого ID они дубль → связать. после — найти пересечения и почистить.
Продажи, заказы, история
продажи и история не должны дублироваться в разных CRM. они должны «привязываться» к
client_idиmerchant_id(франшиза/город).тогда один клиент может иметь заказы в разных франшизах -> но в единой аналитике это видно как одна сущность.
Эта информация вам на подумать!
It is required to refine a WordPress plugin that performs analytics functions. The plugin scans data and displays it on its website. The work can be divided into stages. Main tasks: Analysis and optimization of the current architecture of the plugin. Enhancement of the module for collecting and processing data from external sources. Improvement of performance when working with large volumes of information. Implementation of additional settings in the admin panel. Optimization of storage and display of results on the website. Correction of identified errors and increasing stability of operation. Requirements: Experience working with WordPress. Confident knowledge of PHP, MySQL, JavaScript. Understanding of working with APIs and automated data processing. Ability to understand someone else's code. A detailed technical assignment will be provided to the selected performer after preliminary discussion.
We need a Laravel Backend Developer for the development and maintenance of server logic, databases, and core APIs for our web application. Responsibilities include developing and maintaining server logic and databases for our web application based on Laravel. The work involves integrating frontend frameworks with our server infrastructure and includes designing database architecture and executing queries on relational databases such as MySQL. Professional experience in Laravel development with at least three years of work in this field is required. Experience with integrating frontend frameworks with server infrastructure is also preferred.
We are looking for support for a project based on Yii , we need to make edits and improvements to the database, there is partially a connection with the previous contractor .....................
A virus has currently infiltrated the website. The site is not functioning properly. In particular, the main page is not working correctly. We need a developer who can fix this error as soon as possible.
A developer is needed with experience specifically in CS-Cart Multivendor for two related modifications on an existing online store. Task 1 - broken product photos. On the pages of some products, they do not display. Some photos show a "broken" image icon. Self-diagnosis revealed two different types of causes: The original photo exists on the server, but a specific non-standard (non-square) size needed for full-screen viewing of the photo is not generated (this function is from the third-party module "AB: Advanced Image Viewers," AlexBranding). Square sizes of the same photos are generated without problems. The original photo is completely absent on the server - a specific example and link will be provided upon response. Task 2 - warming up the cache of new products. The site automatically parses and adds new products every night (a separate cron script). Page caching is already set up and working, the warming of the main page and categories has already been done - but the pages of the new products themselves are still not warmed up immediately after import, so the first real buyer who opens a new product directly experiences slow "cold" loading. It is necessary to add automatic warming (curl/wget for the list of new products) immediately after the completion of the nightly import. All necessary access will be provided to you after selection. Work format: two separate stages with separate or joint payment for each task. First, diagnostics/analysis with written confirmation of the approach for each task, then implementation. Respond if you have relevant experience with CS-Cart Multivendor - details and a test task will be provided in personal correspondence.