• A day with
  • E-commerce
  • 5 min read

A Day with the Inventory FTE

Illustrative, not a customer story. Every event maps to a real tab and a real mechanism.

Author
ftes.ai Editorial
ftes.ai Team

The short answer

A day with the Inventory FTE, told as an illustrative scenario, runs from a morning brief ranking stockout risk by revenue and dead stock by cash, through a purchase order approved with its cash impact, a late receipt that widened a supplier's variance, a low-confidence forecast that produced a smaller order, and an evening log. No customer is named.

The role this piece is aboutInventory FTE · Inventory & Demand Planner

Key takeaways

  • The day starts in the Today tab with stockout risk ranked by revenue and dead stock ranked by cash.
  • A purchase order is approved in minutes because the forecast, lead time, cost and cash sit on one screen.
  • A late receipt changes a supplier's measured lead time and variance, and the reorder points that depend on it.
  • A new SKU's low-confidence forecast produces a smaller order and a question, not a confident number.
  • The evening log shows every approval, edit and rejection, and the cash committed against the ceiling.

Morning: the stock brief

The illustrative day begins when the store's owner opens the Today tab. The morning brief leads with what needs a decision: two purchase orders proposed overnight because their SKUs reached their reorder points, one of them for the store's best-selling consumable. Below that, the risk list: SKUs that will stock out within the horizon at current velocity, ranked by the revenue the store would lose, and the dead-stock list ranked by cash trapped. Cash already committed in approved orders this month sits against the ceiling. Spend against the token budget sits in the corner.

The owner reads the best seller's order first, because the brief put it first for the reason the owner would have chosen.

Morning briefwaiting on you firstApprovalsevidence attachedWork runson its own cadenceDetectionswith a proposed responseMonthly reviewits own honest reportFIVE MINUTES A DAYTHIRTY MINUTES A MONTH
Figure 1The illustrative day: stock brief, a purchase order approved, a late receipt that moved a lead time, a low-confidence order, a dead-stock decision, the log.

Mid-morning: a purchase order in Approvals

In Approvals the proposal for the best seller shows everything the owner would otherwise look up: the forecast and its high-confidence label from two years of steady sales, the supplier's lead time as measured from the last several receipts with its variance, the quantity and the arithmetic behind it, the minimum order applied, the landed cost including freight, the cash it ties up and the date it falls due under the supplier's terms, and the days of cover it buys. The order stays inside the month's ceiling, and it is below the second-approver threshold.

The owner approves. The Inventory FTE writes the approved order to the inventory system where the purchasing team expects it. Nothing was sent to the supplier until that click.

Midday: a late receipt, and a lead time that moved

The brief carried a receipt notice the owner returns to: a delivery from a second supplier arrived several days later than its measured lead time, and short by a portion of the order. The Inventory FTE has recorded the receipt, updated that supplier's measured lead time and variance, and recalculated the reorder points for every SKU the supplier provides. It shows which reorder points rose, and it flags one SKU whose stock is now below its new reorder point, with a proposal ready.

The owner approves that order too, and asks in a note for the supplier to be flagged if the next receipt is also late. The note becomes a rule.

Afternoon: a low-confidence forecast

The second overnight proposal is for a SKU launched a few weeks ago. Its forecast carries a low-confidence label, and the proposal reflects it: a smaller quantity than the reorder arithmetic would give a mature SKU, a shorter cover, and a question for the owner: is a campaign planned for this product, and which existing SKU does it most resemble? The FTE has proposed a comparable from the same category and shown the borrowed pattern it used, labelled as borrowed.

The owner answers both, names a different comparable, and approves the smaller order. The forecast will be revised with the new comparable and will upgrade its confidence as the SKU's own sales accumulate.

Late afternoon: dead stock, and a question for another role

In the Stock tab the dead-stock list shows the SKU with the most cash trapped: a seasonal item bought for a season that underperformed, with many months of cover at current velocity. The Inventory FTE has proposed a markdown, with the margin at the reduced price and the cash it would release, and a stop on reordering, which costs nothing. It has also noted that the Marketplace FTE reported the same SKU selling faster on a marketplace, and proposed transferring part of the stock there before marking it down.

The owner approves the reorder stop and the transfer, and asks for the markdown proposal to go to the Retention FTE for a win-back offer rather than a public discount. The proposal moves across, and the decision is logged.

Evening: the log

At the end of the illustrative day the Performance tab shows what happened: two purchase orders approved with their cash, one order triggered by a lead-time revision, a supplier flagged, a low-confidence order approved smaller with a new comparable recorded, a reorder stop, a transfer, and a markdown routed to another role, each with the person who decided and the evidence attached. Cash committed for the month sits against the ceiling; cash in dead stock sits against its target, with the day's actions noted.

Nothing in the day asked the owner to trust a system. It asked them to approve three orders with the arithmetic in front of them, answer two questions about a new product, and decide what to do with one shelf of stuck cash. The record exists already, which is what an audit trail means when it is built in.

Frequently asked questions

Is this a real customer story?

No. It is an illustrative scenario. Every event maps to a real mechanism in the ftes.ai workspace, but no customer or result is described.

What happens when a delivery is late?

The receipt updates the supplier's measured lead time and variance, reorder points are recalculated, and any SKU now below its point gets a proposal.

How is a new product's order sized?

Smaller and sooner, with a low-confidence label, a borrowed comparable shown, and a question for the owner about campaigns and resemblance.

Does the FTE mark down dead stock itself?

No. It proposes the markdown with its cash and margin effect; the owner decides, and the offer runs through another role on approval.

Where is the audit trail?

In the Performance tab, built as the day happens: every approval, edit, flag and decision with its evidence, and cash against the ceiling.

  • E-commerce
  • Inventory FTE
  • A Day With
  • Workspace
  • Illustrative
Further reading

Keep going.

Related guides on hiring and managing Digital FTEs.

Playbook · E-commerce · 6 min

The Inventory FTE's First 30 Days: A Step-by-Step Playbook

A time-boxed plan for the first month with an Inventory FTE: supplier records and the cash ceiling in Setup, the stock audit, the first purchase orders approved, daily risk alerts, and the accuracy review.

Read

Ready to hire your first Digital FTE?

Pick a role, connect the tools it needs, and review its first proposals this week.