Syntha Lab RU

Chief operating officer

Owns lossless flow of goods and data: warehouse, deliveries, transfers, stock accuracy, quality and lead times.

Brand and retail

Open interactively →

About the role

The chief operating officer makes sure goods and data move without losses: warehouse, deliveries, transfers, stock accuracy, quality and timing. The question is not how much was sold but whether the right items reached the right place on time and in full. The result is measured by on-time-in-full order performance (OTIF), stock accuracy, losses (defects, shortages, returns) and time from order to shelf.

The role covers the whole collection process: from order entry and references to receiving, labeling, storage, distribution to stores and the last mile. The COO also owns the systems that hold it up: warehouse, accounting, exchange with platforms. There is no room for different versions of the truth, so the COO insists on one system of record and a single SKU key.

The main skill is seeing the whole chain: a late factory, a master-data error and a skipped stock reconciliation look like three different problems but lead to one result, an empty shelf or excess stock.

A working day

The morning starts with an operations summary: what arrived at the warehouse, what was shipped, where the delays and discrepancies are. Then a check of key deadlines: which deliveries are critical this week, which suppliers' OTIF has dropped. In the afternoon the COO handles issues with logistics and the warehouse: transfers between points, rush reorders, receiving and labeling problems. In the evening the COO reads the data-exchange log and stock reconciliation.

Documents: supplier orders, delivery notes and universal transfer documents (UPD, UKD), receiving and discrepancy acts, inventory acts, labeling codes and documents of putting them into circulation, contracts with 3PL and carriers, the exchange log between systems, reports on stock accuracy and OTIF.

Typical decisions

  • Which suppliers get rush orders and which to replace, by their OTIF and spread of delivery times.
  • Where to put the time buffer: at which stages of the cycle the overrun is systematic.
  • How often to exchange stock with the site and platforms, comparing the price of delay with the exchange cost.
  • Whether to transfer stock between stores and when a transfer pays back.
  • Whether to move from paper to electronic documents and with whom to start.
  • What to do about stock mismatches: recount, adjustment, causes and who is responsible.
  • How to build labeling into receiving, storage and sale without stopping the warehouse.

Study path

  1. Stock accuracy and losses: the foundation for all other warehouse decisions. Stock accuracy, shrink and availability
  2. Compute accuracy by lines and by value and estimate the price of phantom stock. Stock record accuracy and the cost of mismatches
  3. The collection life cycle: stage owners, durations and joints where data is lost. Collection lifecycle and the critical path
  4. Supplier OTIF and the lead-time stack: find the worst supplier and the time overrun. Supplier OTIF and the lead-time stack
  5. The system landscape: who owns each reference and how often the exchange runs. Systems landscape and data exchange
  6. The price of stock-exchange delay shows whether more frequent synchronization pays back. Stock sync latency: the price of stale data
  7. Data quality: measure completeness, duplicates and update term of the SKU reference. Data quality and data owners
  8. Labeling: the code chain from factory to till and stock in the transition period. Marking and trading leftovers
  9. Collection calendar and materials: critical path, fabric MOQ and material unification. Collection calendar and materials
  10. Customs and regulation: compliance costs, labeling and Russian and EAEU rules; check with a broker. Customs and regulation

What to understand

Stock accuracy
When book stock differs from physical, replenishment, online sales and the buying budget break. Phantom stock looks like goods in stock that are not on the shelf.
Product availability
Availability is the share of time a selling size is on the shelf. Lost revenue comes from the gap between demand and availability, not from warehouse stock.
Transfers and stock handling
Moving goods between stores pays only if sales at the new place beat the cost and margin lost at the old one. Re-assortment and rebalancing are a calculation, not a reflex.
Losses: defects, shrink, returns
Factory defects, store shrink and customer returns are different losses with different causes and costs. Sample inspection and cause coding help locate the source.
Order entry and reference data
An error in a product card or order (size, color, price, category) travels through the whole cycle. Unified reference books of sizes, attributes and categories cut mismatches.
Lead times: order to shelf
The collection calendar shows the critical path and slack. A late fabric or inspection shifts the sales start and breaks the season.
Delivery performance
On-time-in-full (OTIF) and order fill rate show supplier and warehouse reliability in one number.
Stock as a separate process
Transfers between stores, top-up, defects and season leftovers follow rules, not manual routine. Compare the benefit of a transfer with a discount, and count defects net of reserve and supplier return.
Warehouse, 3PL and the last mile
Own warehouse or an operator: compare order cost and breakeven volume. Warehouse flows by sale stage (BS, IS, AS, SO) set staff load. Delivery to the customer depends on the type: courier, pickup point, post.
Marking and leftover stock
Mandatory marking arrives in waves by product group, and leftovers without a code cannot be put into circulation after the deadline. Check the code chain from factory to till and the decision to mark or sell off. Check deadlines and group lists with a lawyer.
The store as a warehouse and pickup point
Click and collect and ship from store save stock and cut delivery, but load staff. A unified view of stock returns sales that otherwise go to out of stock.
Eight lifecycle stages and the critical path
From the collection plan to season close each stage has an owner, a system and a deadline. The latest start day and slack by stage show which date cannot slip without losing the shelf date.
Systems landscape and data exchange
PLM, ledger, warehouse, till, CRM and BI hold different records. Assign an owner and the needed exchange frequency for each: website stock must not lag the warehouse longer than the sales you can afford to lose.
OTIF and stock accuracy
OTIF is measured on a pre-set window and receiving tolerance. Stock accuracy (count versus book) decides whether availability on the site and in replenishment can be trusted.

Key measures

MeasureFormulaHow to read
Inventory record accuracyItems with no variance ÷ items countedNo threshold: judge by what the error costs your revenue.
In-stock rateDays in stock ÷ days in period, for selling sizesCount by size, not by style.
Shrink(Book stock − counted stock) × cost ÷ revenueFind the cause: theft, record error, defect.
Transfer paybackMargin from selling at the new place − cost − margin lostMove only when the result is positive.
OTIFOrders delivered on time and in full ÷ all orders of the periodOne base: orders. For a stricter check, calculate a separate “line-level OTIF” and label it. Add causes of failure.
Cost of order mismatchesNumber of errors × average cost to fixCompare with the cost of fixing the process.
Warehouse cost per orderAll warehouse cost in the period ÷ number of ordersCompare with an operator rate at your volume.
Warehouse load by stageOperation hours ÷ shift working hours, by stage BS, IS, AS, SOThe load peaks in the sale; plan staff for it.
Net defect lossDefect cost − supplier return − reserveCompare by supplier and by cause.
Sales recovered by stock visibilitySales covered by store stock ÷ lost warehouse salesShows the value of a unified stock.
Supplier OTIFOrders delivered on time and in full ÷ all orders of the periodFix the on-time window and quantity tolerance before measuring; compare suppliers by the same rules.
Stock exchange lagTime between a stock change in the warehouse and its visibility in the channelThe price of lag grows with turnover and the number of channels.

Questions the role asks

Route through Lab

  1. Stock accuracy, shrink and availability
  2. Stock record accuracy and the cost of mismatches
  3. Availability and lost revenue
  4. Stock shrink: share, threshold and cost to profit
  5. Does moving stock between stores pay back
  6. Replenishment and stock cover
  7. Sampling inspection and cost of defects
  8. Collection calendar: critical path and slack
  9. Order data quality
  10. Cost of order mismatches and payback of the fix
  11. OTIF
  12. Zero-based budget: cost packages, priority and the effect of cut-off by level
  13. Working with stock: transfers, top-up, defects, prices, order entry
  14. Transfers between points: surplus, need and the gain against a discount
  15. Replenishment by size: what and how much to send to stores by size
  16. Defects: losses, supplier recovery and a reserve
  17. Warehouse, fulfillment and the last mile
  18. Own warehouse or 3PL: cost per order and break-even volume
  19. Warehouse flows: hours, staff and load by sale stage (BS, IS, AS, SO)
  20. Last mile by delivery type: courier, pickup point, post
  21. Marking and trading leftovers
  22. Light-industry marking waves: dates and leftovers
  23. Mark or sell off leftovers without a code
  24. Omnichannel: click and collect and ship from store
  25. Click and collect: the economics against delivery
  26. Inventory visibility: how many sales a single stock view of stores and warehouse brings back
  27. Warehouse and delivery of an online store
  28. Collection lifecycle and the critical path
  29. Season calendar counted back from the shelf date
  30. Supplier OTIF and the lead-time stack
  31. Systems landscape and data exchange
  32. Stock sync latency: the price of stale data
  33. Data quality and data owners
  34. Collection calendar and materials
  35. Customs and regulation
  36. Cost of quality: prevention, appraisal, internal and external failure
  37. Work in progress and Little’s law
  38. Yield cascade across stages
  39. Warranty and repair reserve

First 30 days

  1. Open the stock topic and write down transfer and top-up rules. Working with stock: transfers, top-up, defects, prices, order entry
  2. Compute warehouse cost per order and compare with an operator. Own warehouse or 3PL: cost per order and break-even volume
  3. Check warehouse flows by sale stage. Warehouse flows: hours, staff and load by sale stage (BS, IS, AS, SO)
  4. List leftovers without a code and compute mark or sell off. Mark or sell off leftovers without a code
  5. Compute the last mile by delivery type. Last mile by delivery type: courier, pickup point, post
  6. Assess the value of store stock visibility. Inventory visibility: how many sales a single stock view of stores and warehouse brings back
  7. Describe the eight lifecycle stages: owner, system, deadline. Collection lifecycle and the critical path
  8. Calculate the critical path and slack to the shelf date. Season calendar counted back from the shelf date
  9. Draw the systems map and exchange frequencies. Systems landscape and data exchange
  10. Review stock accuracy and the price of mismatches. Stock record accuracy and the cost of mismatches

Common mistakes

  • Counting availability for the warehouse overall, not for sizes on the shelf.
  • Moving goods without a calculation just because it sells better there.
  • Not coding the cause of variance: losses cannot be cut without a cause.
  • Keeping category and size reference books different across departments.
  • Planning warehouse staff for an average month, not the sale.
  • Sending unmarked leftovers into circulation without checking the deadline.
  • Measuring OTIF without a pre-agreed window and receiving tolerance.
  • Not naming a record owner across systems: the same record is edited in two places.

Reports to keep

  • Stock variance report: Book versus counted by store and category, causes.
  • Transfers report: What moved where, what it cost and what sold.
  • Defects report: Defects by supplier, style and cause.
  • Availability report: In-stock share of selling sizes and lost revenue.
  • Defect and return report: Defects by cause and supplier, reserve, return, net loss.
  • Stock and stock-age report: Stock by age and store, transfer candidates.
  • Stages and deadlines map: Lifecycle stages, owner, system, date and slack to the shelf date.

Data to keep

  • Stock by warehouse and location, exchange with channels. Warehouse and stock system; ERP and accounting system
  • Order and delivery statuses and lead times. ERP and accounting system; PLM and production records
  • Register of systems and record owners. ERP and accounting system; Warehouse and stock system; PLM and production records

Open interactively →