Interviews first, code second
We talk to the people who do the work — the planner, the buyer, customer service — not just the director. The interviews give us the system’s constants: reservation periods, order cadence, minimum lot sizes.
12.0 t reserved, 6.4 t added to the blending plan
An accounting system records documents. Everything else lives between them: promises to customers, the blending queue, the raw material schedule, priorities. It’s usually kept in spreadsheets, messaging apps and people’s heads.
Production is planned without signals from sales or channel inventory. The warehouse holds two months’ worth of product, yet the SKUs you need may still be out of stock.
There’s no screen that matches an order against stock and the plan. A rush order jumps the queue through whoever sits closest to the planner.
The sales plan, the tank plan, distributor reports and receivables are pulled together by hand at month-end. Decisions rest on an outdated summary.
There’s no big-bang cutover. Data that lives in spreadsheets, phones and people’s heads today moves into the system right away. Data from 1C is first read and reconciled, and the system takes it over only when its screen is more convenient and more accurate than the report.
Every step has its own workstation, and management sees each step the moment it happens
A distributor builds an order from the catalog at their tier’s prices. An account manager or a customer service rep turns an email into an order in 30 seconds.
The system checks the order on six counts: stock, raw materials, capacity, cost, customer credit and logistics. The result: a priority, a promised date and what still needs to be produced.
Blending job, sample, lab release, batch certificate, packaging with a label. Every action becomes an event in the system, not an entry in a notebook.
The batch goes into a storage bin, and orders are picked from the shipping queue with batch expiry dates taken into account.
Trip, dock slot, loading, documents on the driver’s phone. The customer sees the status without calling their account manager.
Payment is tied to the shipment, credit limits and overdue debt are tracked across the customer’s group of companies, and rebates accrue under the dealer policy rules.
Each tab shows what the system calculates and displays. The sequence follows the implementation stages: sales before production, money after orders
Primary sales from 1C, secondary sales from distributors, the plan by version. A heat map of account managers and distributors shows where the plan isn’t adding up, and the month-end forecast is based on the run rate.
Month-end forecast at the current pace: 98% of plan. The South is behind pace, and four of its distributors are on the dormant-customer list. Units: kL.
A terminal does one job and does it in three taps. Your accounting system has no data on the shop floor, the yard or the warehouse, so that data originates here
Blending tanks, top-ups, samples, flushes
Batch queue, testing, release, rework or reject
Line plan, filling, actual output, QR-coded label
Put-away into bins, order picking
Tank trucks: gross, tare, net, clearance to unload
Trip, loading, waybill, today’s slots
Purchase orders, rejects, pallet labels
Vehicles in and out, yard visits
Slot, statuses and route on their phone
Tanks, blends and alerts displayed over the shop floor, refreshed every 30 seconds
The same principle as a fast-food register: the procedure is built into the screen, not into instructions on the wall
Access is separated at the data level, not by hiding buttons
The entire sales channel, production, warehouse, logistics, money, alerts and recommendations.
Assigned distributors only: plan and actual, orders, receivables, tasks for the day.
Their own orders and shipments, prices for their tier, rebates and accruals under the dealer policy. They submit secondary sales reports and get analytics on their own business in return.
A motor oil manufacturer with several hundred SKUs and a network of some forty distributors. Accounting in 1C, everything else in spreadsheets and phone calls.
Finished goods inventory was twice the monthly shipments, yet the service level was held at 91–93% by people’s manual effort. Production priorities were settled by informal agreement, the tank plan lived in three spreadsheets, the raw material schedule on the buyer’s phone, and distributor reports came in different formats. The move to a new 1C configuration was still under way, and master data in the old and new databases didn’t match. Raw material shortages kept the plant from planning more than a week ahead.
Thirteen interviews: the commercial and finance directors, sales, customer service, planning, procurement, logistics, contract manufacturing, process technologists and the 1C administrator. We broke eleven working files down into data. From that we built a working system on demo data: all of the plant’s processes, three roles, ten terminals and the end-to-end order flow. It took the place of a thick specification: a spec you can actually get your hands on.
We built the sales area first: actual shipments from 1C, plan vs. actual, the commercial director’s budget and an owner’s view. Every screen was checked against a report the company trusts. Monthly sales matched the finance team’s file to the penny once we found that sales adjustments had been counted three times.
The work cycle is one week: a task on Monday, a demo at the end of the week, and after every meeting a log of open questions, each with an owner. Every question to the plant states the amount that hinges on the answer and asks for a one-line reply. Work is prioritized by harm: first whatever turns wrong numbers into right ones, then explainability, then new data links.
Orders and coverage with the distributor portal, production planning and blind spots, money and dealer policy, terminals at the stations and, finally, the new system as the system of record: documents originate there, and 1C receives them for accounting.
The plant’s name is withheld by agreement with the client. Figures are rounded.
They took shape at the plant and apply to every implementation
We talk to the people who do the work — the planner, the buyer, customer service — not just the director. The interviews give us the system’s constants: reservation periods, order cadence, minimum lot sizes.
Processes are assembled into a working system on demo data before integration begins. Every screen has a hint explaining what it shows and where each number comes from. Feedback is given on live screens, not on a document.
A task on Monday, a demo at the end of the week. After every meeting, a log of open questions with an owner and a deadline: nothing is left to memory.
Work is prioritized by harm: errors that produce wrong numbers come first, then labels and explainability, then data that already exists and addresses known pain points, and only then new data links.
Every screen is reconciled against a report the company trusts, down to a gap of under 1%. A screen isn’t done until the numbers reconcile.
Every question about accounting methodology names a specific 1C document and the amount that depends on the answer. The answer takes one line, and the number on screen changes the same day.
Off-the-shelf ERP makes the plant fit its configuration. Spreadsheets make the process depend on people. A dashboard shows what has already been recorded. A plant operating system runs the process where it happens.
| Criterion | Spreadsheets and chat apps | Off-the-shelf ERP | Dashboard on top of 1C | Plant operating system |
|---|---|---|---|---|
| Where data originates | In files and messages | In accounting system forms | In 1C, after period close | At the station, as it happens |
| Order queue | Everyone keeps their own | A document with no coverage check | End-of-day report | One queue with priority and date |
| Production priority | Informal agreement | Manual plan | Not visible | Calculated from orders and days of cover |
| Shop floor, warehouse, yard | Notebook and phone | A paid license per workstation | No data | Glove-friendly terminals with PIN login |
| Changing the rules | Rewrite the spreadsheet | Months of configuration work | Rebuild the report | Rules live in data, change in a day |
| Role of 1C | Accounting separate from the process | Everything in one system | The only data source | Accounting and reporting |
Off-the-shelf ERP makes sense when your processes match its configuration. For a plant with its own production logic, a system built around that logic costs less.
Six stages, each with its own sign-off. You can stop after any of them: every stage delivers a result that works on its own.
Actual shipments from 1C, plan vs. actual, the commercial director’s budget, an owner’s view. Reconciled with the finance team’s report.
Order center, reservations, promised dates, distributor portal, intake of secondary sales reports.
Production plan, tanks, formulations, norms, raw material schedule: everything that used to live in spreadsheets and on phones.
Dealer policy as a calculation engine, cost built up in layers, cash flow, receivables.
Shop floor, lab, packaging, warehouse, truck scale, loading dock, checkpoint. Data originates at the station.
Orders, the plan, batches and shipments originate in the system. 1C receives the documents for accounting and reporting.
Timelines start once we have access to 1C: the first area usually takes four to six weeks, then a month to a month and a half per stage. The schedule depends on how quickly questions about accounting methodology get answered.
management sees the sales channel, warehouse and production as they are today, not at month-end
of orders, with priority, promised date and what still needs to be produced
for every SKU instead of tons in the warehouse: you see what to stop and what to produce more of
every figure traces back to its source line in 1C or to an event at a station
How deep it goes depends on what data 1C makes available and on data-entry discipline at the stations. We measure the impact on the plant’s own data in the first area.
The demo environment recreates the plant using sample data: three roles, ten terminals and the end-to-end order flow, from the distributor portal to shipment.
Sign in as a distributor and build an order from the catalog at your prices.
Switch to the management role: the order is already in the queue with a status, priority and promised date.
Open the capacity view: see how the order fits into the plan and what else is keeping production busy.
Updated
No. Accounting, tax, payroll and product marking stay in 1C. The system handles what 1C doesn’t cover and never will: orders with coverage checks, the production plan, batches, shop-floor and warehouse stations. It exchanges data with 1C: at first it only reads, and at the final stage it passes its own documents to 1C for accounting.
1C records documents, not events. A terminal records an event where it happens: a batch is discharged, a sample is submitted, a pallet goes into its bin. Without that there’s no traceability, and priorities go back to being settled by phone.
The sales area usually takes four to six weeks from the moment we get access to 1C. After that, each stage takes a month to a month and a half, with its own sign-off. The schedule depends on how quickly questions about accounting methodology get answered.
The system will be the first to show it: empty fields, unmatched master data and transactions missing analytic dimensions go into the log of questions for the plant. Each question names the document and the amount that depends on it.
Yes. Companies usually start with the sales area or with orders and coverage: that data is already in 1C, and results show within a few weeks. Terminals and the system-of-record stage come later.
It depends on the number of data sources, stages and stations. Once we get your request, we send the scope of the first stage and an estimate for your 1C configuration.