Chief operating officer
Owns lossless flow of goods and data: warehouse, deliveries, transfers, stock accuracy, quality and lead times.
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
- Stock accuracy and losses: the foundation for all other warehouse decisions. Stock accuracy, shrink and availability
- Compute accuracy by lines and by value and estimate the price of phantom stock. Stock record accuracy and the cost of mismatches
- The collection life cycle: stage owners, durations and joints where data is lost. Collection lifecycle and the critical path
- Supplier OTIF and the lead-time stack: find the worst supplier and the time overrun. Supplier OTIF and the lead-time stack
- The system landscape: who owns each reference and how often the exchange runs. Systems landscape and data exchange
- The price of stock-exchange delay shows whether more frequent synchronization pays back. Stock sync latency: the price of stale data
- Data quality: measure completeness, duplicates and update term of the SKU reference. Data quality and data owners
- Labeling: the code chain from factory to till and stock in the transition period. Marking and trading leftovers
- Collection calendar and materials: critical path, fabric MOQ and material unification. Collection calendar and materials
- 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
| Measure | Formula | How to read |
|---|---|---|
| Inventory record accuracy | Items with no variance ÷ items counted | No threshold: judge by what the error costs your revenue. |
| In-stock rate | Days in stock ÷ days in period, for selling sizes | Count by size, not by style. |
| Shrink | (Book stock − counted stock) × cost ÷ revenue | Find the cause: theft, record error, defect. |
| Transfer payback | Margin from selling at the new place − cost − margin lost | Move only when the result is positive. |
| OTIF | Orders delivered on time and in full ÷ all orders of the period | One base: orders. For a stricter check, calculate a separate “line-level OTIF” and label it. Add causes of failure. |
| Cost of order mismatches | Number of errors × average cost to fix | Compare with the cost of fixing the process. |
| Warehouse cost per order | All warehouse cost in the period ÷ number of orders | Compare with an operator rate at your volume. |
| Warehouse load by stage | Operation hours ÷ shift working hours, by stage BS, IS, AS, SO | The load peaks in the sale; plan staff for it. |
| Net defect loss | Defect cost − supplier return − reserve | Compare by supplier and by cause. |
| Sales recovered by stock visibility | Sales covered by store stock ÷ lost warehouse sales | Shows the value of a unified stock. |
| Supplier OTIF | Orders delivered on time and in full ÷ all orders of the period | Fix the on-time window and quantity tolerance before measuring; compare suppliers by the same rules. |
| Stock exchange lag | Time between a stock change in the warehouse and its visibility in the channel | The price of lag grows with turnover and the number of channels. |
Questions the role asks
- How much does stock inaccuracy cost us? Stock record accuracy and the cost of mismatches
- How much revenue do we lose to missing sizes? Availability and lost revenue
- Does moving goods between stores pay back? Does moving stock between stores pay back
- What loss share is acceptable for our business? Stock shrink: share, threshold and cost to profit
- How to inspect a lot by sample and what does a defect cost? Sampling inspection and cost of defects
- Which path is critical in the collection calendar? Collection calendar: critical path and slack
- What does a wrongly entered order cost? Cost of order mismatches and payback of the fix
- From which batch does a style reach the target margin? Micro-batch versus large: fixed costs, experience curve, break point
- Own warehouse or an operator: what is cheaper at our volume? Own warehouse or 3PL: cost per order and break-even volume
- What to do with leftovers without a marking code? Mark or sell off leftovers without a code, Light-industry marking waves: dates and leftovers
- Which delivery pays by type: courier, pickup point, post? Last mile by delivery type: courier, pickup point, post, Split shipments: the cost of several parcels versus consolidation
- What pays more: a transfer between stores or a discount? Transfers between points: surplus, need and the gain against a discount
- Which stage moves the shelf date and how much slack is left? Season calendar counted back from the shelf date, Collection calendar: critical path and slack
- Who owns each record in the systems and how often is exchange needed? Systems landscape and data exchange, Stock sync latency: the price of stale data
Route through Lab
- Stock accuracy, shrink and availability
- Stock record accuracy and the cost of mismatches
- Availability and lost revenue
- Stock shrink: share, threshold and cost to profit
- Does moving stock between stores pay back
- Replenishment and stock cover
- Sampling inspection and cost of defects
- Collection calendar: critical path and slack
- Order data quality
- Cost of order mismatches and payback of the fix
- OTIF
- Zero-based budget: cost packages, priority and the effect of cut-off by level
- Working with stock: transfers, top-up, defects, prices, order entry
- Transfers between points: surplus, need and the gain against a discount
- Replenishment by size: what and how much to send to stores by size
- Defects: losses, supplier recovery and a reserve
- Warehouse, fulfillment and the last mile
- Own warehouse or 3PL: cost per order and break-even volume
- Warehouse flows: hours, staff and load by sale stage (BS, IS, AS, SO)
- Last mile by delivery type: courier, pickup point, post
- Marking and trading leftovers
- Light-industry marking waves: dates and leftovers
- Mark or sell off leftovers without a code
- Omnichannel: click and collect and ship from store
- Click and collect: the economics against delivery
- Inventory visibility: how many sales a single stock view of stores and warehouse brings back
- Warehouse and delivery of an online store
- Collection lifecycle and the critical path
- Season calendar counted back from the shelf date
- Supplier OTIF and the lead-time stack
- Systems landscape and data exchange
- Stock sync latency: the price of stale data
- Data quality and data owners
- Collection calendar and materials
- Customs and regulation
- Cost of quality: prevention, appraisal, internal and external failure
- Work in progress and Little’s law
- Yield cascade across stages
- Warranty and repair reserve
First 30 days
- Open the stock topic and write down transfer and top-up rules. Working with stock: transfers, top-up, defects, prices, order entry
- Compute warehouse cost per order and compare with an operator. Own warehouse or 3PL: cost per order and break-even volume
- Check warehouse flows by sale stage. Warehouse flows: hours, staff and load by sale stage (BS, IS, AS, SO)
- List leftovers without a code and compute mark or sell off. Mark or sell off leftovers without a code
- Compute the last mile by delivery type. Last mile by delivery type: courier, pickup point, post
- Assess the value of store stock visibility. Inventory visibility: how many sales a single stock view of stores and warehouse brings back
- Describe the eight lifecycle stages: owner, system, deadline. Collection lifecycle and the critical path
- Calculate the critical path and slack to the shelf date. Season calendar counted back from the shelf date
- Draw the systems map and exchange frequencies. Systems landscape and data exchange
- 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