What does a Warehouse Officer FTE own?
A Warehouse Officer FTE on ftes.ai owns the gap between what the system believes and what the shelf holds, and the gap between the promise at checkout and the moment a parcel leaves, in the Operations department of the e-commerce org chart. It is judged on orders shipped within promise and accountable for that and for receipts and counts being reconciled. It exists because every downstream number, the Inventory FTE's stock truth, the Allocator FTE's cover, the Cash Officer FTE's valuation, rests on a stock record that drifts.
It does not own the warehouse management system, the staff or the 3PL contract. It owns the measurement, the reconciliation and the flags.
How is ship-within-promise measured?
Ship-within-promise is the share of orders whose ship scan falls within the dispatch window the store promised at checkout, measured per order, by warehouse or 3PL, and by day. The Warehouse Officer FTE reads the promise from the order and the scan from the shipping tool or the 3PL feed, and names the orders that missed with the warehouse responsible. Misses that cluster on a shift, a day or a carrier cut-off are surfaced as a pattern with the orders behind it.
The measurement is separate from delivery-promise accuracy, which the Logistics Officer FTE owns from the delivery scan; this role owns the part the warehouse controls.
How are receipts and counts reconciled?
When a purchase order arrives, the Warehouse Officer FTE reconciles the receiving scans against the quantities ordered and the supplier's invoice: a short receipt, an over-receipt, or a substitution is named per line and routed to the Supplier Officer FTE for the scorecard and to the owner for the invoice hold. Cycle counts are reconciled against the stock record, and a variance beyond the owner's tolerance is raised as an exception with the bin and the SKU, for the Data Trust FTE's inventory domain and for a person to correct.
The FTE does not correct the record itself. It proposes the correction with the count behind it; a person makes it, and the next reconciliation confirms it.
How are error patterns and 3PL service levels handled?
Pick and pack errors, the wrong item, the wrong size, a missing unit, show up in returns with 'wrong item' reasons and in support tickets. The Warehouse Officer FTE reads both, attributes each to the warehouse, and where the data allows, to the line and shift, and surfaces patterns rather than single events. For a 3PL, the agreed service levels, ship-within, receipt-within, accuracy, are measured from the same scans, and a breach is reported with the orders as evidence the day it occurs, so the conversation with the 3PL starts from the record rather than from a feeling.
Proposals, such as a plan to get a 3PL inside its service levels before peak, wait for the owner's approval.
What does the Warehouse Officer FTE never do?
It never changes a stock record, directs warehouse staff, or operates the warehouse management system; it reconciles, flags and proposes, and a person acts. It never presents a count variance as resolved until the next reconciliation passes, and never reports ship-within-promise from the warehouse's own dashboard when scans exist.
It also never attributes an error to a person by name in a report; patterns are by line and shift, and what to do about them is the manager's decision.
What does it report, and how honestly?
The Warehouse Officer FTE reports ship-within-promise by warehouse and 3PL with the missed orders listed, receipt variance by line, count variance by bin and SKU, error patterns from returns and tickets, and 3PL service-level results with breaches evidenced. Ship-within-promise is measured from scans, and where a 3PL feed lacks scans for a period, that period is labelled as unmeasured rather than assumed on time.
A month with no breaches and no variances is reported as that, with the reconciliations that support it.
How does it work with the other roles, and in which tools?
The Warehouse Officer FTE feeds the Data Trust FTE's inventory domain, the Inventory and Allocator FTEs' stock truth, the Supplier Officer FTE's receipt record and the Order Support FTE's missing-scan escalations. It reads ShipStation, ShipHero, the store's 3PL feed, Cin7 or NetSuite, and orders from Shopify, WooCommerce or BigCommerce. Onboarding is custom because the warehouse or 3PL feed, and the agreed service levels, must be connected and written down before anything can be measured.