We build CRMs, B2B portals and internal tools for food manufacturers that sell through their own online store, marketplaces, wholesale customers and branded retail outlets at the same time. Orders, stock, shipping labels and product master data come together in one system integrated with 1C/BAS.
What's included
One dashboard brings together feeds, orders, stock, waybills and prices from a WooCommerce store and the MauDau and Rozetka marketplaces. Data syncs automatically on a schedule, so the team no longer moves information between dashboards by hand and has a single point of control for all channels.
The CRM brings together wholesale orders, picking by actual weight, documents and settlements, while a separate portal lets customers see their orders, invoices and balance on their own. We built it on a proven foundation from a previous project, so the first working version with all modules was ready in about 3 hours.
Instead of an Excel template passed from person to person, we built a service where 5 departments fill in a new product card in parallel, the CFO approves it, and accounting exports the 65-column BAS technical sheet with one click. Development took 6 days, and manual data transfer into the accounting system is no longer needed.
A typical food manufacturer with its own chain of stores sells through several channels at once: branded outlets, its own online store, marketplaces and wholesale customers. Each channel has its own rules and its own data. A marketplace requires a feed with categories and attributes, a wholesale customer wants to see invoices and outstanding balances, the courier service needs a shipping label, and accounting lives in 1C or BAS. Without a single system, the team moves data between dashboards by hand, drowns in spreadsheets and messengers, and errors only surface when a buyer cancels an order.
Food production also has technical pitfalls that ordinary e-commerce does not. Products are sold by weight, while marketplaces expect a price per unit. The actual weight at picking differs from the ordered weight, and the invoice has to reflect that. The range is large and constantly changing, and every new item has to pass through several departments before it reaches the accounting system.
Off-the-shelf CRMs work well with a single store but poorly with several marketplaces and accounting systems at once. That is why we build the system around the company's actual process rather than forcing the process into a template.
For a food manufacturer we have worked with since 2024, we developed a CRM for marketplaces and orders. One panel brings together orders, stock, prices and Nova Poshta shipping labels from the company's WooCommerce store and the MauDau and Rozetka marketplaces. Within a few months the system grew to 18 screens, 74 API routes and 5 scheduled automations, with 6 roles and separated access rights. Attributes and translations for product cards are prepared from XLSX files using the Claude API, and orders and products are passed to Bitrix and 1C by item codes. Management can see operator activity against the shift schedule and cancellation reasons grouped by responsible party.
On the same foundation we built a B2B CRM with a wholesale customer portal: 19 screens for the team and 9 for customers, with the first working version of all modules ready in about 3 hours. Customers see their own orders, invoices and balances, picking takes actual weight into account, sessions are tied to the password version, and the system keeps 30 daily backups.
For new product onboarding, we replaced an Excel template with a service where 5 departments fill in the product card in parallel, the CFO approves it, and accounting exports a 65-column BAS technical sheet with one click. The service covers 168 1C categories across 4 levels, and development took 6 days.
When the company entered a marketplace, we prepared a feed of 426 products, filled in the package weight for 204 products automatically, and set prices for sold-by-weight items using a formula: price per kilogram multiplied by the minimum weight. The feed check revealed that 97 of 422 products were shown as in stock with nothing available, and we fixed that logic.
For the same brand's marketing team, we built a marketing plan platform with an Instagram feed preview and daily reminders.
A first working version is ready within days or weeks depending on scope, after which the system grows module by module. You get a system built around your process, integrations with sales channels and the accounting system, roles and permissions for each department, backups and ongoing support. Because we handle both marketing and development, feeds, stock and prices are built correctly for every channel from the start.
Updated:
How we work
No lengthy preparation or vague promises: at every stage you know what is happening, how long it takes and what you get.
Day 1
A 30-minute call about your goals, market, competitors and budget. We agree on access to the website, GA4 and Search Console.
What you get
1-2 weeks
Technical health, indexing, keywords, competitors, brand visibility in AI answers and analytics quality.
What you get
Weeks 2-3
We prioritize work by impact on leads and revenue, set KPIs and lay out a month-by-month plan.
What you get
From month one
Technical fixes, content, links, ads or development in weekly sprints. Every task is visible in our CRM.
What you get
Monthly
A report with GA4 and Search Console numbers, a review call and plan adjustments. We scale what brings leads.
What you get
Didn't find your answer? Drop us a line and we'll reply within one business day.
Yes. We have built order and product transfer to 1C and Bitrix by item codes, as well as a service that generates a 65-column file for BAS. Accounting imports it without any manual restructuring.
On a schedule, the system synchronizes products, orders, stock and prices with your own store and each marketplace. Orders from all channels are processed in one panel, and courier shipping labels are created from the same place.
Marketplaces expect a price per unit, so we calculate it as the price per kilogram multiplied by the minimum package weight. Buyers see the real price, and the manufacturer does not sell at a loss.
Wholesale customers can see the catalog, their orders, invoices and balance on their own, and managers spend less time on correspondence and reconciliations. The portal runs through the CRM's API, so the customer and the manager always see the same figures.
A first working version is ready within days or weeks, then the system grows module by module. We built the product onboarding service for 5 departments in 6 days, and the first version of a B2B CRM on an existing foundation was ready in about 3 hours.
Each role's permissions are checked at the database level, so a department cannot edit another department's section and an interface bug cannot expose someone else's data. We also set up daily backups and tie sessions to the password version.
Leave your details and we'll put together a scope of work and a budget estimate.
We'll run a quick audit of your website and show you where you're losing traffic and leads. Free, no strings attached.