Internal system · In production

Warehouse stock sync

A one-way sync: the fulfilment warehouse is the source of truth, the online store only receives stock. A full run across a catalogue of about 22,000 products, and stock only: prices, orders and product cards are left alone.

The pain

Warehouse stock and the online store’s catalogue lived apart: a buyer saw availability the warehouse no longer had, and fixing it meant doing it by hand, item by item.

Now

A run takes fresh warehouse stock and brings the store catalogue in line with it. The state is recalculated in full, so discrepancies never accumulate, and only the items that changed are written.

What the business gets

A buyer sees the availability the warehouse actually has, not what was left in the catalogue last week.
Every run reads both sides afresh, so a missed day does not turn into an accumulated discrepancy.
Only changed items are written: there are no needless writes into a live store.
Items with no counterpart are shown separately - that is a question for the business, not a silent sync error.

From source to result

Warehouse feeds
Store catalogue
Comparison and delta
Circuit breaker
Writing the stock

Without an explicit flag the run only shows the plan and writes nothing. A real write is a deliberate step, and on a suspicious share of changes the circuit breaker stops it until someone looks.

How it works

Barcodes are written differently on the two sides: fourteen digits with a leading zero in the store, thirteen without it in the feeds. Matching is done on strings with the zero stripped, and that is what makes them meet: without stripping, about 13 % of the catalogue matched, with it about 95 %.

Stock from the two legal entities is added up per barcode; if an item is in neither feed its stock goes to zero - the feed is authoritative.

The physical quantity from the warehouse is what gets written, while the reserve held by orders is the store’s own count - the sync does not touch it.

A truncated feed never goes into work: the file is checked for completeness. An item the store rejects is pulled out of the batch and the rest are re-sent, and on a rate-limit refusal the run waits and retries.

Who maintains it now

The company’s content manager. The warehouse operator is left with the run log: intervention is needed when the circuit breaker fires or the tokens expire.

Other cases for this step

Internal system · In production

Product portal

Catalogue, labels and PDFs - one button

The pain: Every label was assembled by hand, in five steps through the external PLM. A typo in an SKU turned into a penalty and a return.
Now: The product catalogue, label printing, PDF generation and image conversion live in one portal. Five manual steps collapsed into a single «Print label» button.

Label printing: one button instead of five steps
Coverage: catalogue, labels, PDFs, conversion
Replaced: an external PLM system

The same system pays off across 2 more steps

Internal system · In production

Advertising management agents

The operator’s daily cycle runs itself

The pain: The morning started with a manual round of the accounts: spend, DRR, campaigns spending without orders, bids in a spreadsheet. It ate half a day.
Now: Calibration, the scanner and bid proposals run overnight; in the morning one command gives the operator the whole summary. The agents themselves never write into the account: a human confirms first.

Overnight cycle: calibration, scanner, bid proposals
Operator commands
Write into the account

The same system pays off on one more step

Own product · In production

Marketplace stores in Claude

Routine checks close with a question in chat

The pain: The daily checks - what is running out, what is blocked, what arrived in payouts - mean walking three accounts by hand. Nobody does that every day, and problems surface late.
Now: A check turns into a question in chat: Claude calls the marketplace methods it needs and answers to the point. A writing call does not go out first time: a preview first, the send on a second call.

Daily check: a question in chat instead of a round of accounts
A writing call
A read-only key

The same system pays off on one more step

mcp.hubmarket.ru

Internal system · Pilot

The company’s agent platform

Routine is ordered on a form, not filed as a developer’s task

The pain: Repetitive manual work settled in chat threads: someone asked for it to be automated, the request got lost between people, and nobody saw the next team asking for the same.
Now: An employee files a request on a form, in the language of their own work. An agent is one file with a prompt and no code of its own, and requests are visible to all, so identical asks stop drifting apart.

A new agent
The audit gate
What agents may do

Type: Internal system
Status: In production
Rhythm: a full run, started on a schedule or by command
Direction: warehouse → store, stock only
Replaced: editing stock by hand, item by item

PythonrequestsYMLWindows Task Scheduler