Budget: 6000 UAH Deadline: 4 days

Good day! I develop in Python, React/Node.js. I have extensive experience in the field and am ready for collaboration.

Budget: 6000 UAH Deadline: 5 days

Ready to finalize your clothing accounting system — I will connect LP CRM via REST API, set up CORS, and localStorage. I see the task — to link inventory with orders and display charts.

Connecting LP CRM — I will pull inventory for fabrics and finished clothing, and customer orders in real-time.
Cut accounting — I will calculate fabric costs per item and automatically deduct them with new orders.
CORS solution — I will set up a proxy on Render so that the browser can securely fetch data from CRM.
HTML/JS interface — I will refine the single-page application, caching data in localStorage for fast performance.

I have experience with such integrations: I have pulled inventory and orders from CRM via API, calculated production logic on real data, and handled CORS through a proxy on Render. So, I am familiar with the details and can start today.

After delivery, I won’t disappear — I will be available for any edits or updates. I will help without additional charges.

✅ I am currently completely free — I have no other projects in progress. Message me, and I will draft a brief plan for the first stage in 10 minutes. Expand

Budget: 6000 UAH Deadline: 7 days

Good day. I looked at the demo. Essentially, the task is not to "connect the CRM," but to ensure that the cutting calculation is accurate based on real data — and this depends on how the LP CRM provides the data. Therefore, the key question right away is: how are "in cutting" and "returns" represented in your LP CRM — are they separate order statuses, separate entities, or custom fields? The formula Plan − Stock − In Cutting + Returns will only work if these states are differentiated at the API level. The answer will determine whether the logic has already been implemented or if we first need to agree on the data model in the CRM.

Regarding experience: I have not worked specifically with LP CRM, but REST integrations with CRM are my main job (connecting via API, pulling orders/stock/returns, writing back). I typically set up a proxy to bypass CORS — I will deploy it on Render (keeping in mind that the free tier goes to sleep during inactivity, so the first synchronization after a pause may lag; I will implement keep-alive or we can discuss the plan). I am ready to refine the existing code without rewriting it.

I propose to work step by step, as you described:
Stage 1 — integration of LP CRM + proxy + one working cutting calculation based on the size×color matrix with real data. This is the most important and riskiest part: once the data flows correctly, the rest (single stock, accounting for refusals, workshops) will be an add-on to it. A demo at this stage will show that the foundation is working.

Next — single stock, reduction of the cutting plan by % of refusals, workshops/history, polishing stubs. The format of written communication and staged delivery works for me. I currently have no feedback here — so the step-by-step approach is convenient for you as well: you see the result of each stage before paying for the next.

I am ready to provide the cost and timeline for stage 1 after receiving a response about the data model in the CRM and a brief review of the current code.

Budget: 6000 UAH Deadline: 9 days

Hello! I have done exactly such connections — I pulled the leftovers and orders from the CRM via API and calculated the production logic on real data, I also handled CORS through a proxy on Render. I looked at your demo, the picture is clear. I am ready to prove the cutting formula (Plan − Stock − In cutting + Returns) and the accounting of refusals to a working state on live data. One question: is LP CRM lp-crm.pro? And do you already have the key with the subdomain at hand to connect right away?

Budget: 6000 UAH Deadline: 7 days

Good day.

The categories of web programming and client management are indicated absolutely correctly. Your task combines interface development and deep integration with the CRM system.

I am ready to bring your accounting system for the sewing production to a working state. I have experience working with REST API and bypassing CORS through a proxy on the Render platform.

I will connect LP CRM for automatic synchronization of stocks, orders, and returns. I will set up the exact logic for calculating the cut according to your formula, taking into account the size and color matrix. I will implement automatic reduction of the cutting plan based on refusal statistics. I will consolidate all data into a single general inventory table. I will add functionality for distribution across workshops and maintain a history of transfers. I will activate all non-working buttons and fix current bugs.

I guarantee work with the current stack of HTML and JS without rewriting the code from scratch. I will deliver the work in stages with mandatory demonstration of results. I always try to understand the logic of the business, so I will definitely suggest technical improvements for greater system reliability.

Budget: 6000 UAH Deadline: 7 days

Hello! I am ready to bring your cutting accounting system to a working state — specifically to finalize the existing HTML/JS single-page, without rewriting from scratch.

Regarding the task: I will connect LP CRM via REST API (stocks, orders, returns), bypass CORS with a proxy on Render.com — I have already worked with CRM integrations via API and proxy. Then I will adjust the formula Plan − Stock − In cutting + Returns to real data based on the size×color matrix, incorporate the % of refusals in such a way that it actually reduces the cutting plan for the position, rather than just displaying it; I will consolidate the total stock into one table and add distribution by workshops with acceptance and transfer history. I will bring the placeholder buttons to a working state.

The format will be written and step-by-step, as you requested: CRM → calculation → stock/workshops → polishing, with a demo at each stage so you can see the progress and pay for the result. Where I see that something can be made more reliable — I will suggest it, rather than silently doing it according to the specifications.

Clarification on integration: Does LP CRM provide stock and returns as separate methods, or is there a single endpoint for stock by SKU (size/color)? This will determine how accurately we can consolidate the "total stock" without desynchronization.

I will set the price within your budget, and we will agree on the timelines for phased delivery. I can share live examples of my API integrations in the chat so you can see the level of my work.

Petro Pankov, BotCraft Group Expand

Budget: 12000 UAH Deadline: 5 days

Доброго дня.
viacore.group
https://project-rework.packages.viacore.group/

Budget: 6000 UAH Deadline: 4 days

Katerina, I see that it's not just about "stretching" the interface, but about making a correct accounting of cutting and stock based on real data. I can gradually connect LP CRM via API, bypass CORS through a proxy, refine the Plan-Stock-Return formula in cutting + Returns to the working matrix size × color, and integrate the % of refusals into the calculation itself. I work with REST/API and warehouse logic, and I enjoy refining existing code without rewriting it. I can start with CRM integration and immediately show results in a demo.

Budget: 6000 UAH Deadline: 1 day

Hello! The task is clear: connect LP CRM via API, bypass CORS through a proxy on Render, and restore the formula Plan - Stock - Cutting + Returns to correct operation with real data, taking into account the percentage of refusals in the cutting forecast. Working with REST API, warehouse logic, and modifying someone else's code without rewriting from scratch is exactly what I do. I am happy to discuss the details and phased delivery in private messages.

Budget: 6000 UAH Deadline: 6 days

Hello, Katerina! I reviewed the demo. I am ready to bring the system to a working state - connect real integrations and consolidate stock/returns into a single balance considering the rejection statistics. The main stack for such tasks is Python/FastAPI or Node.js + Postgres, depending on what the backend of the current tool is written in (please clarify the stack). Similar experience: a consolidated inventory and batch system on an industrial project, batch data processing with validation (github.com/slonce70/promAI).

Budget: 6000 UAH Deadline: 4 days

Hello!

I see the task as follows: not just to "connect the API for the sake of it," but for KroyLab to honestly show, based on live data from LP CRM, how many and which positions (size × color) need to be cut — with the correct remainder and % of refusals that actually reduces the plan.

I will do the following:
1. Proxy on Render: CORS + LP CRM key on the server (not in the browser), taking into account the "sleeping" of the free instance.
2. Pulling in remainders/orders/returns and explicitly matching CRM fields → matrix cell.
3. Formula Plan − Stock − In cutting + Returns based on real examples; refusals — as a reducing coefficient per position.
4. Then according to your stages: single stock, workshops/history, stubs — after the demo of the foundation, without rewriting the SPA from scratch.
5. In writing, with a demo at each stage; I will propose improvements to reliability separately, without inflating the MVP.

I work on test accesses/copies; I will briefly document the calculation logic and technical notes for support; after launch, I am ready to remain for support.

In the form, I indicated the estimated cost for the first stage (proxy + LP CRM + working formula on real data with demo). Stock/workshops/polishing — the next stage after the demo, we will agree on the scope separately.

Questions:
1) In LP CRM, are "in cutting" and "returns" separate entities/methods, statuses, or custom fields? And is "+ Returns" in the formula the available remainder or a signal to recut?
2) Is KroyLab one person on one PC or several workshops/devices (this affects localStorage at stage 1)? Expand

Budget: 6000 UAH Deadline: 3 days

Good day!

I am interested in your project and I am ready to take on its execution. I have extensive experience in developing similar systems and admin panels - I am happy to help.

Here are the works I am NOT ASHAMED of:
1) Admin panels and CRM system modules
Behance

2) Telegram bot + admin panel
Behance

3) Development of an extension for Outlook:
Behance

Other works
Behance

Open to communication and discussion of details. Expand

Budget: 6000 UAH Deadline: 6 days

Hello!

The task is clear: it is necessary to not rewrite the system from scratch, but to bring the existing prototype to a working state — with real integration of LP CRM, a correct cutting formula based on the size×color matrix, and accounting for refusals in the forecast.

I have experience connecting CRM via REST API (including bypassing CORS through a proxy server) and building warehouse logic with multiple sources of inventory — I know the typical pitfalls of data desynchronization between systems.

I will start with an audit of the current code and the fields of the LP CRM API, connect the proxy on Render, and check the Plan-Warehouse-U cutting + Returns formula with real client data; then I will add a reducing coefficient based on the % of refusals to the plan calculation, consolidate the single warehouse into one table, and process the workshops with transfer history.

The first stage (CRM integration + working calculation formula) will take 5-6 days, approximately 6000 UAH; I will assess the rest (warehouse/workshops, button polishing) after the demo of the first stage, within your budget.

Please let me know: which specific fields/endpoints of LP CRM are already known (is there documentation or a test key), and is there an example of real data on inventory for checking the formula?

I am ready to discuss the details and start with the first stage. Expand

Budget: 6000 UAH Deadline: 10 days

The task is to connect the LP CRM API to the existing SPA so that the cutting formula calculates based on real data rather than placeholders.

Steps: first, set up a proxy on Render.com (Express + http-proxy-middleware) to bypass CORS and keep the API key on the server instead of in localStorage. Next, integrate stocks/orders/returns through the LP CRM REST, consolidating into a single matrix of size × color. Then, implement the cutting logic: Plan − Stock − In cutting + Returns adjusted for % of rejections per item — rejections reduce the plan rather than just being displayed in a table.

One risk worth discussing in advance: LP CRM sometimes paginates large queries into 100 records — do you already have an understanding of the volume of orders/stocks to account for proper batching on the first load?

Budget: 6000 UAH Deadline: 3 days

Good day.
I am interested in your task.
I have done integrations of CRM systems via REST API multiple times, so this will not be a problem here either.
I have some questions that I would like to discuss.
Feel free to write, I would be happy to discuss the details!

Budget: 6000 UAH Deadline: 14 days

Good day. I read the description and the task is clear to me: connect the LP CRM API via a proxy on Render, implement the cutting calculation formula (Plan - Stock - In Cutting + Returns), and consolidate all this into a working tool without rewriting what already exists.

I have 3.5 years of commercial experience in fullstack development (TypeScript, Vue/Nuxt, NestJS). I regularly work with REST API integrations, particularly with CORS bypass through a server proxy, so this aspect will not be a problem. I also have experience with B2B products, where warehouse logic, stock matrices, and return accounting are standard parts of the tasks.

I am ready to dive into the existing code, understand the structure, and complete what is missing, rather than rewriting from scratch. The budget is negotiable, so I suggest we briefly discuss the details and estimate the scope.

Budget: 6000 UAH Deadline: 5 days

🌟 Hello! I am ready to take on your task and provide the necessary technical support. I would be happy to discuss the details of our collaboration and start working.
🏆 Portfolio: Freelancehunt

I am glad to see you among my clients now and in the future.

Budget: 6000 UAH Deadline: 7 days

Good day!
I reviewed the demo page. I see that it was generated by artificial intelligence. I suggest this kind of panel, which you can view at the link. You can add all the necessary functionality written in Svelte.
https://lab.ich-desigen.de/panel.png
I can add all the required functionality within 7 days.
If you're interested, I can provide a demo for you to try out. I have experience with API integration and backend and frontend development. I have also worked on CRM system development for foreign companies. I have over 8 years of commercial experience. We can discuss the cost in more detail. I can bring the task to a logical conclusion. I saw that a developer was hired for this task who essentially did not cope. I have seen this task before.
Regarding this panel, it can replace the existing one you have with minimal effort. And add the missing functionality and interaction with RestAPI. The image of the panel is at the link above.

Budget: 6000 UAH Deadline: 10 days

Hello! I have reviewed the demo and the technical specifications. I understand the production logic and the formula (Plan − Stock − In Cutting + Returns * Refusal Coefficient). I am ready to bring the system to a working state, but I have an important technical note that will save your production from data loss.

The essence of the current stack problem:
Using `localStorage` to store "Cutting History" and the status "In Cutting" means that the data only exists on one computer. Another employee from a different device will not see it. And free CORS proxies on Render.com work extremely unstably for regular API requests.

My solution (without rewriting the frontend from scratch):
I will keep your HTML/JS interface, but instead of an unstable proxy, I will write a lightweight and reliable backend layer (on PHP/database).
What this will provide:
1. Reliable CORS bypass and security: LP CRM API keys will not be "exposed" in the browser.
2. Unified database: Data on "In Cutting," "Distribution by Workshops," and "Cutting History" will be stored in a real database. All employees will see the current picture from any device.
3. Refusal mathematics: I will implement an accurate calculation of the matrix (size/color), where the % of refusals from LP CRM will dynamically reduce the cutting plan, preventing re-sewing.
4. Reviving the UI: I will connect all placeholder buttons, consolidating the total stock (LP CRM + current cut) into one summary table.

Work format:
I agree to phased delivery. First, we connect the CRM and display the stocks -> then the calculation and refusal logic -> then the workshops and history. After each step - a demo.

The budget of 6000 UAH to start the basic logic is acceptable. I am ready to look at the current code and start working.

Estimated implementation time (7-10 days):

Since you prefer phased work, I propose the following sprint schedule:

- Stage 1 (2-3 days): Deploying the backend and database, setting up a secure connection with the LP CRM API (importing stocks, orders, and returns). [Demo]
- Stage 2 (2-3 days): Programming the cutting calculation logic and integrating refusal statistics (adjusting the cutting plan according to the size/color matrix). [Demo]
- Stage 3 (2-3 days): Transferring the status "In Cutting," distribution by workshops, and history from the local browser to a reliable database. [Demo]
- Stage 4 (1-2 days): Final polishing, "reviving" the remaining placeholder buttons in the interface, consolidating the total stock, and testing. Expand

Budget: 6000 UAH Deadline: 5 days

Hello! I looked at the demo (KroyLab v2) — I see the structure: Calculation, Workshops, Warehouse, Overall Warehouse, Refusals, History of Cuts, and in Settings, there are already fields for the API key LP CRM, subdomain, and proxy URL. The framework for integration is ready; right now, nothing is connected ("CRM not connected" on the screen).

Regarding the tasks:

LP CRM via proxy on Render — I will set up a lightweight proxy service that accesses the LP CRM API with the key on the backend (so the key is not exposed on the frontend) and returns data with the correct CORS headers. I have already encountered PaaS specifics (Render/Heroku — SSL, environment configuration) on a real project (WebRTC application on Heroku), so deployment nuances will not be a surprise.

The cutting formula — Plan − CRM Warehouse − In Cutting + Returns by size×color matrix — is essentially a deterministic calculation pipeline. I implemented similar logic (validation, aggregation, calculations on matrix data) in a project with aeronautical navigation data (Pandas/GeoPandas, FastAPI) — https://github.com/kamedashe/Avia-Navigation-Data-Pipeline-Admin-API.

Refusals affect the plan — I will add a reduction coefficient to the plan by position based on the % of refusals, rather than just outputting a number. This is a logical extension of point 2, without changing the structure.

Overall warehouse — consolidation of three sources (CRM + in cutting + returns) into one table, the same aggregation approach as in point 2.

Workshops and history of cuts — distribution, acceptance of returns, history of transfers — I will implement on top of the existing structure, without touching what already works.

Button stubs — I will bring them to a working state as I complete the relevant points.

I am ready to work with the existing code, not rewriting from scratch, and to deliver in stages with a demo at each step: CRM → calculation → warehouse/workshops → polishing, as you described.

Regarding the budget: 6000 UAH is reasonable for the first stage (connecting LP CRM + working calculation formula on real data), and we will discuss the cost of subsequent stages based on the volume.

I am ready to start with the CRM integration. Expand

Budget: 6000 UAH Deadline: 1 day

Hello!

I am a Full-Stack Software Engineer with over 7 years of experience in developing websites, SaaS solutions, complex web platforms, and MVPs for startups - from idea and architecture to production and support.

I work not only as a developer but also with a focus on business logic, scalability, and long-term support of solutions. My portfolio includes examples of completed projects of varying complexity.

Technology stack:
PHP (Laravel, Symfony, Yii2),
Frontend: JavaScript (Vue.js, React.js), HTML5, CSS3,
Databases: MySQL, PostgreSQL.

Regarding timelines and costs - at this stage, it is difficult to accurately assess them without clarifying the requirements. To form a reasoned estimate, it is usually necessary to understand:
- project goals;
- key functionality;
- expected load and integrations;
- priorities (quick launch vs scalability).

I suggest starting with a brief clarification of requirements or a call/email - after that, I will be able to provide a realistic estimate on timelines, budget, and implementation options.

I would be happy to discuss the details. Expand

Budget: 6000 UAH Deadline: 6 days

Good day, Kateryna.

In brief:

The formula Plan − Stock CRM − In cutting + Returns on paper works, but with real data LP CRM the main thing is to correctly match the size×color matrix between orders and stocks; otherwise, the cutting forecast will be distorted by discrepancies in identifiers. Your system will receive a single proxy on Render.com to bypass CORS and ensure a stable pull interval, and the % of refusals for positions will not only be displayed but will actually reduce the cutting plan — through a coefficient applied to a specific cell of the matrix, rather than globally.

In detail:

I noticed the demo — the interface is there, but the size×color matrix between orders and stocks has not yet been compiled, and without this, the cutting formula on real data LP CRM will yield inaccuracies due to discrepancies in position identifiers. Your system will receive a proxy on Render.com with one stable pull interval, and most importantly — normalization of product codes between CRM and internal accounting, so that each cell of the matrix maps unambiguously.

The percentage of refusals will work as a coefficient that reduces the cutting plan for a specific position in the matrix, rather than globally — this is what reduces re-sewing, not just displays statistics. A single stock will be compiled from three sources (CRM stocks + in cutting + returns) into one table with a transparent history of transfers across workshops. Placeholders on buttons will be replaced with real acceptance-return logic without rewriting the architecture — existing modules will be supplemented.

The phased approach, as you propose (CRM → calculation → stock/workshops → polishing), with a demo at each step — is optimal, as it allows checking the correctness of the matrix mapping before the logic of refusals and workshops is applied to it.

Options:

≈5 days: 4000–5000
- Stable connection with LP CRM via proxy server
- Working cutting calculation formula on real data
- Real-time updates of stocks and orders
- Fixing critical interface bugs

≈12 days: 8000–12000
- Full functionality of calculation according to the size×color matrix
- Automatic reduction of the cutting plan based on refusal statistics
- Unified stock table (stock + cutting + returns)
- Distribution system across workshops and history of product transfers
- Complete replacement of all placeholders with working functionality

≈18 days: 13000–18000
- All capabilities of the previous option
- Extended analytical dashboard on refusals and re-sewing
- Notification system for critical discrepancies in stocks
- Optimization of API query performance for large data volumes
- Priority support and maintenance after implementation Expand

Budget: 6000 UAH Deadline: 7 days

Hello! I looked at the demo and your list, and I will go through each point.

CRM: I will connect the LP CRM via REST using your key and subdomain, pulling in balances, orders, and returns. I will set up a proxy on Render, but I will immediately implement keep-alive: the free Render goes to sleep without activity, and the first request after a pause otherwise hangs for a long time, which is critical for a working tool.

Cutting formula: I will bring the Plan - Stock - In cutting + Returns to work with live data, calculating based on the size×color matrix, so it will be clear exactly how much and what needs to be cut.

Rejections: I will make it so that the % of rejections by size/color actually reduces the plan for this position, rather than just displaying a number next to it. I will review where the rejections come from in the CRM to ensure it is counted fairly.

Unified stock: I will consolidate the stock, in cutting and returns into one table, so that there is one balance instead of three numbers in different places.

Workshops and history: distribution by workshops, acceptance of returns, and history of transfers, so it will be clear where each batch is currently located.

Bugs: I will bring the placeholder buttons to a working state during the relevant stages, without rewriting everything from scratch.

Advice on the essence: currently, the data is in localStorage, which is one browser and gets lost when clearing the cache. For real accounting, it is better to keep the CRM via proxy, and leave localStorage as a cache. We will introduce it gradually, without rewriting.

I work in writing and deliver in stages, as you want: CRM, calculation, stock and workshops, polishing, with a demo at each stage. We can discuss the stages in private.
I look forward to collaborating! Expand

Budget: 15600 UAH Deadline: 12 days

Good day, Kateryna.

I have reviewed the project description and demo. I like that the system already has a ready-made interface and it needs to be brought to a working state rather than rewritten from scratch.

I work with JavaScript and improving existing web projects, so it is important for me to first understand the current architecture and logic before making changes. This approach helps avoid unnecessary rework and preserves what already works.

I suggest we carry out the work in stages:
✔️ code analysis and LP CRM integration;
✔️ checking and refining the calculation logic;
✔️ inventory, workshops, and history;
✔️ final testing and polishing.

At each stage, I will demonstrate the results so everything can be verified with real data.

Before the final assessment, I would like to review the source code and project structure. This will allow for an honest evaluation of the workload and avoid padding the budget.

Preliminary estimate:
• 12–15 working days
• 15,600 UAH (final after reviewing the code)

If part of the logic is already implemented well, the cost may be lower.

I would be happy to discuss the details. Expand

Budget: 6000 UAH Deadline: 2 days

Hello!
My name is Victoria. I am a web developer with over 3 years of experience in creating and refining web tools, CRM systems, and warehouse logic. I have reviewed your demo — the task is completely clear to me, and I am ready to delve into your production processes and bring the tool to a stable working state.
Why my experience is perfect for your accounting system:
Working with APIs and bypassing CORS (Render.com): I have extensive experience integrating REST APIs. Since my second professional stack is Python, I can quickly deploy a lightweight, reliable, and fast proxy server on Render (for example, using FastAPI/Flask), which will not only solve the CORS issue but also securely encrypt the LP CRM API keys so they do not "leak" into the user's frontend code.
Matrix logic (size × color) and accounting for failures: Mathematical calculations of stocks and forecasts are something I often work with. I will detail the logic where the failure percentage will dynamically adjust the formula Plan - Stock CRM - In Cutting + Returns, so production does not over-sew unnecessarily.
Thorough testing (QA): Thanks to my skills in testing, before delivering each stage, I personally check the system's performance against edge cases and rounding errors (especially in size matrices), so you will receive fully functional software without "surprises."
My proposal for the work format:
Communication: I fully support your format — written chat/messenger, clear, to the point, and with documentation of interim results.
Step-by-step development plan (as you suggested):
Setting up the proxy on Render + connecting the LP CRM API (importing orders, returns, stocks). Demo.
Implementing the cutting calculation formula considering the matrix and failure coefficient. Demo.
Consolidating a single stock, developing workshop logic and transfer history. Demo.
Replacing all placeholders with live interaction, final testing. Delivery.
I am ready to start discussing and analyzing the code today.
Best regards, Victoria. Expand

Budget: 6000 UAH Deadline: 7 days

Good day, I have over 5 years of experience in developing and integrating web tools with CRM systems via REST API - connecting LP CRM, bypassing CORS through a proxy on Render.com, bringing the logic of calculations to a working state with real data - all of this is in my stack. I will work with the existing code without rewriting from scratch, step by step: first CRM integration and proxy, then cutting logic and a unified warehouse, followed by workshops and polishing. Approximately 6000-8000 UAH depending on the actual volume of bugs and improvements, the price and deadlines will be more precise after reviewing the code and answering questions. What database is currently in use - is localStorage remaining or are you considering a transition to server storage? And is there access to a real LP CRM account for testing? I look forward to your message in private!

Budget: 6000 UAH Deadline: 6 days

Hello! I looked at the demo - the interface is really ready, just need to connect real data. My profile specializes in REST integrations and JS: I will connect your CRM API (orders, stock, returns), set up a lightweight proxy to bypass CORS, implement the calculation of cutting based on the size/color matrix and a single stock (warehouse + cutting + returns). I work with the existing code, without rewriting from scratch. I suggest a phased approach: first a working integration and one accurate calculation with real data, then the rest of the modules.

Budget: 6000 UAH Deadline: 1 day

On time, responsibly, with attention to detail.
I work quickly and efficiently.

Budget: 6000 UAH Deadline: 14 days

Returns for multiple SKUs to check the formula and method of accounting for return percentages? Good day.

I can bring your system to a working state: connect LP CRM via API with a proxy on Render, set up accurate cutting calculations based on the size×color matrix considering returns, and consolidate stock + cutting + returns into a single balance.
An important technical nuance of the order: the proxy must correctly proxy the authorization of LP CRM and account for possible API and CORS limitations.
I work with the existing code without rewriting from scratch, will bring the buttons, inter-department transfer logic, and cutting history to a working state.
I support phased delivery with a demo at each step.

Can you provide test access to LP CRM (key + subdomain) or export real balances?

Budget: 6000 UAH Deadline: 7 days

A proxy on Render.com for bypassing CORS is key, and this is where I will start to ensure the integration with the LP CRM API works smoothly. I will connect the LP CRM REST API through a proxy layer, extract inventory and orders in real-time, then refine the cutting calculation formula (Plan - Inventory - In Cutting + Returns) to a working state on a size×color matrix, embed the accounting of % refusals as a multiplier to the plan (not just a display), consolidate a single inventory from three sources into one table, distribute it across workshops with a history of transfers, and fix button placeholders. I will provide 2 weeks of free support after delivery. I am ready to start.

Budget: 6000 UAH Deadline: 6 days

😀 Hello!
✅ I will get your tool to a working state 👌
✅ I have done similar work before — integrations through API and web logic (CRM, proxy for CORS, data processing) 🎯
🛠 How I will do it: I will connect LP CRM via API (key/subdomain) through a proxy (CORS bypass), pull in stocks/orders/returns, consolidate a single stock (warehouse + in cutting + returns), finalize the cutting calculation and refusal statistics. I will check it on your demo.
🎥 Portfolio: Freelancehunt
✅ Feel free to reach out, I will look at the demo and code 👌🙂

Budget: 6000 UAH Deadline: 1 day

Good day! I have reviewed the task and am ready to start.

Experience:
• 4 years in Frontend and Backend development
• 2 years of commercial experience in product and blockchain
• Working with production code and real financial scenarios

Some of my projects:

https://contentbuilder.ai/ - a commercial project from the USA, where I worked as a full-stack developer and implemented most of the functionality

https://freelancehunt.com/showcase/work/procasino/2025898.html

https://freelancehunt.com/showcase/work/bionrgg/2025897.html Expand

Budget: 6000 UAH Deadline: 5 days

Katerina, I reviewed the demo of KroyLab, not just the project description. In the current version, I see a critical risk in working with access rights. I won't detail it in the open bid, but it needs to be fixed before synchronizing real data with LP CRM. I work with REST API, webhooks, and CRM synchronization. In such systems, I first check the actual API responses and field mappings: SKU, size, color, order status, and returns. Otherwise, the formula may look correct but miss or double count items.

I propose the following workflow:

1. Check the current code and methods of LP CRM.
2. Move access management to the server side of the proxy, add error handling and a synchronization log.
3. Connect stocks, orders, and returns, then test the formula with real examples.
4. Finalize the overall inventory, workshops, receiving, and cutting history.

I am ready to maintain the existing interface and change only those parts that hinder stable operation. After each stage, I will show a demo. One important question: will the system be used by one person in one browser or multiple employees from different devices? In the latter case, the cutting history cannot be left only in localStorage. I propose a budget of 6000 UAH for the first stage: audit, access protection, proxy, and working synchronization with LP CRM. After checking the code and API, I will provide an exact estimate for the remaining work.

Budget: 6000 UAH Deadline: 7 days

Hello! I have experience working with REST APIs and CRM system integrations, so I am ready to take on the refinement of your tool. I understand the specifics of inventory accounting and the logic of calculations necessary for optimizing cutting.

My work plan:
1. Setting up a proxy server on Render for proper operation with the LP CRM API and bypassing CORS.
2. Implementing integration to obtain data on stock levels, orders, and returns.
3. Introducing a mathematical model for cutting calculations considering failure statistics and the size/color matrix.
4. Optimizing the interface and transforming placeholders into functional elements.

I work in stages with demonstrations of results at each step so you can monitor the process. I am ready to propose solutions to enhance the reliability of the system. I look forward to the details to start working.

Budget: 12000 UAH Deadline: 6 days

The system needs to be brought to a fully operational state:
1) connect LP CRM via API and set up a proxy to bypass CORS;
2) obtain balances, orders, and returns, and verify the accuracy of the data;
3) implement a formula for calculating cuts based on sizes and colors using real data;
4) integrate rejection statistics into forecasts so that it influences the cutting plan;
5) combine inventory, cutting, and returns into a single table;
6) refine the logic of workshops, transfer history, and remove all placeholders.

The greatest attention should be paid to the business logic of calculations. If the integration is done without verifying the formulas against real data, the system may show an incorrect production plan.

After reviewing the current code and API, it is possible to immediately determine what has already been implemented and what remains to be completed in order to assess the exact scope of work. Expand

Budget: 6666 UAH Deadline: 1 day

Hello! I will complete your task quickly and efficiently.

My recent works
https://indexfast.pro - fast website indexing
https://mono-bank.pp.ua - everything about Monobank
https://mamamia.pp.ua - online store
https://programist.pp.ua/ua/portfolio/ - portfolio of works
https://monitortest.pp.ua - monitor testing
https://keytest.pp.ua - keyboard testing
https://pctest.pp.ua - computer testing
https://devroman.dev/portfolio/ - portfolio
https://vseetut.matviy.pp.ua - layout
https://indexfast.pp.ua - fast website indexing

My portfolio: https://freelancehunt.com/ua/freelancer/romas6ka.html#portfolio
Write to me, I will start working today. I will be happy to collaborate with you! Expand

Budget: 6000 UAH Deadline: 5 days

I understood the technical specifications on all six points: integration of LP CRM via proxy on Render (CORS has already been taken into account), formula for calculating cuts based on the size-color matrix considering rejection statistics, consolidation of inventory and cutting and returns into one total balance, distribution by workshops with transfer history, and final adjustment of the placeholder buttons to a working state.

Regarding architecture: I keep the LP CRM keys only on the proxy server; they do not enter the client HTML - this is both safer and does not interfere with CORS. I will check the cutting formula and the size-color matrix on a demo with real data before delivery, not just in theory. The history of cuts and transfers between workshops should be moved from localStorage to a small database - otherwise, the data only exists in the browser of one device and disappears when the cache is cleared, while you need a shared history across workshops.

In terms of deadlines: 2-3 days for LP CRM and proxy with real data verification, the rest of the time for the cutting formula, unified inventory, workshops, and final bug fixes - I can complete everything in a total of 5 days.

One question: does LP CRM have stable fields for size, color, and return or order status, or will they need to be mapped manually to your matrix?

Budget: 8000 UAH Deadline: 4 days

Kateryna, hello! /
I looked at the demo and your description, the topic is mine, the stack is all familiar.
I regularly integrate CRM via REST, I also work with a proxy under CORS, a small passthrough on Render rises quickly.
I am oriented towards LP CRM.
I will refine your code, submitting it in stages with a demo at each step. I can start with the CRM integration.
Write to me, we will discuss everything more precisely, we will synchronize on accesses and start.

Budget: 6000 UAH Deadline: 7 days

Good day!
I have reviewed the description and demo of the system. I am ready to refine the existing code without a complete rewrite: connect LP CRM via API and proxy, set up the retrieval of real balances, orders, and returns, as well as bring the logic for calculating cuts based on the size × color matrix to a working state.
I propose to work in stages:
Connecting and verifying LP CRM.
Logic for calculating cuts and accounting for refusals.
Overall inventory, workshops, and transfer history.
Fixing stubs and final testing.
Before the final assessment, we need to review the current code and examples of LP CRM API responses, as the structure of products, sizes, and colors affects the scope of integration.
I am ready to work in writing, show results after each stage, and suggest improvements where it will make the system more reliable and user-friendly.
Please write in private messages; I would be happy to review the code and discuss collaboration.

Budget: 6000 UAH Deadline: 5 days

Good day. I will set up integration with LP CRM via API on Node.js with a proxy for CORS, finalize the logic for cutting calculations, and combine inventory, cutting, and returns into a single accounting system without rewriting the existing application. I will also improve the workshop operations, the history of transfers, and eliminate all stubs to achieve a fully operational state. I suggest discussing the price and deadlines in private messages. I am ready to discuss the details and start working. I look forward to collaborating.

Budget: 6000 UAH Deadline: 10 days

Katerina, I see that the system lacks a connection between the actual data from LP CRM and the cutting calculation formula. Your goal is to automate accounting to avoid unnecessary re-sewing due to outdated data on stock or refusals.

I suggest setting up data exchange via API with a proxy on Render to stabilize CORS, and then writing the calculation logic where the percentage of refusals directly adjusts the cutting plan for each position by size and color. As a result, you will receive a table with the actual state of the inventory that updates automatically.

What specific data currently most often does not match between CRM and your database, and are you ready to provide documentation on the API from LP CRM?

Budget: 6000 UAH Deadline: 3 days

Feel free to contact me, I will do it.

Budget: 6000 UAH Deadline: 4 days

Hello.

I will handle the integration of your accounting system and bring everything to a working state so that it correctly displays balances and cutting calculations. Write to me, we will discuss the details and I will start immediately.

Budget: 6000 UAH Deadline: 5 days

The task is clear: first, I will set up a proxy on Render.com to bypass CORS and connect the LP CRM via key/subdomain — pulling in stock, orders, and returns. Next, I will refine the formula Plan − Warehouse CRM − Cutting + Return to work on the matrix size×color, and I will introduce the % of refusals as a reducing factor for the plan, rather than just outputting it in a table. Separately, I will consolidate the total stock and the history of cuts/workshops, and adjust the placeholder buttons. I am ready to refine the existing code without rewriting it, step by step with a demo. The first stage (CRM + proxy) is estimated to take about 5 days.