Minas Sarkisyanwebkoth.com
ENRU

Internal system · In production

Product portal

A product portal instead of an external PLM system: product catalogue, label printing, PDF generation and image conversion. Built in a few days with the production pipeline ready on day one; 73 % of changes are made by the company’s product specialist.

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.

Effect across the steps

04 · From routine to automation
Five manual steps to a label collapsed into one button
05 · Faster processes
The external PLM was replaced in days; changes now ship the same day
06 · Freer resources
The product specialist runs the portal: 73 % of changes are theirs

What the business gets

  • Product data belongs to the company, not to the vendor of someone else’s system.
  • A label is printed by a button, so there is nowhere for an SKU typo to come from.
  • A missing attribute or export format is added by the person who needs it, not by a queue to a developer.
  • The colour reference runs on the PowerShell built into Windows - used by people with no IT environment at all.

From source to result

  1. Product card
  2. Portal catalogue
  3. Label template
  4. Image conversion
  5. PDF and printing

Attributes come from the catalogue rather than being carried over by hand: the label and the PDF are assembled from the same card the product specialist maintains.

By hand, then one button

  1. 1.Open the external PLM
  2. 2.Find the product, copy its attributes
  3. 3.Paste into the label template
  4. 4.Convert the image to the right format
  5. 5.Assemble the PDF, send to print

How it works

Database, auth with roles, tests and auto-deploy to two environments existed on the day of the first commit: the delivery pipeline was assembled before the domain part rather than bolted on after it.

The domain part - catalogue, label templates, export formats - is run by the product specialist through Claude Code; code reaches production only through engineering review.

Who maintains it now

The company’s product specialist. The engineer owns review and the release to production.

Other cases for this step

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

Open the case

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
Open the case

Internal system · In production

Warehouse stock sync

Warehouse stock reaches the store on its own

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.
Catalogue
~22,000 products
The run
a full recalculation, one command
Circuit breaker
Open the case

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
Open the case
Type
Internal system
Status
In production
Timeline
days to replace an external PLM
Maintained by
a product specialist
Replaced
an external PLM system
Next.jsReactTypeScriptPrismaPostgreSQLGitHub ActionsPM2