Test a stockout warning against dated sellable inventory, unit demand and the actual receipt assumption.
A day-13 receipt changes the answer
Use this synthetic single-SKU example, not a customer result. A timestamped FBA snapshot shows 120 fulfillable units and 80 inbound. Fifty-six units were ordered over the previous seven complete days. The assumed rate is 56/7 = 8 units per day, and immediate cover is 120/8 = 15 days. If all inbound stock becomes fulfillable only at the start of day 20, the simple constant-demand model reaches zero at day 15 and has a five-day gap before receipt. The inbound quantity does not belong in today’s available-stock numerator.
In a 1stPage-connected Claude session, request inventory_analytics with the restock dataset for the actual SKU and fulfillment channel. Pair its dated stock state with seller_analytics demand for a compatible period; keep inbound separate from fulfillable units. Ask about advertising exposure only after an authorized advertising_analytics result maps the same advertised product. The connector supplies sources, not an automatic stockout verdict.
Change only the receipt date to the beginning of day 13. At eight units daily, the first 12 days consume 96 units, leaving 24. Receiving all 80 raises the sellable balance to 104; that lasts another 104/8 = 13 days, to day 25 from the starting snapshot. The shorthand 200/8 = 25 days happens to work because receipt precedes depletion. Split receipts, reservation changes or a slower receiving process invalidate that shortcut. An arrival estimate is not proof that the units are already fulfillable.
The join can defeat a neat cover calculation
For an FBA offer, use fulfillable inventory from an authorized source at a named timestamp. FBA inventory distinguishes fulfillable, reserved, unfulfillable, researching and inbound quantities. Do not merge those states. A merchant-fulfilled offer needs the seller’s own sellable on-hand and fulfillment records instead; an FBA snapshot is not a warehouse count for merchant fulfillment. A flat-file Inventory Report’s listing quantity is not automatically identical to FBA fulfillable quantity either.
Match demand and stock on seller account, marketplace and seller SKU, then cross-check ASIN and fulfillment channel. Two SKUs can point to the same ASIN without being the same sellable offer. A missing row is not zero stock. Resolve report processing status and SKU mapping before assigning a red flag. When a source supplies only ASIN-level sales, do not pretend its units belong to one SKU if other offers share that ASIN. State the aggregation you actually have or get a finer-grained authorized demand source.
Use units, not sales dollars, as the demand numerator. Name whether they are ordered or shipped and count only complete observation days. Recent stockouts suppress observed sales, while a promotion can inflate a seven-day rate; show a slower and faster unit-demand case if those conditions matter. The timestamped stock snapshot and historical demand window have different grains. Keep that mismatch visible rather than projecting a precise calendar date from an average.
Ads are a separate verification, not the cause by default
A low-stock calculation says nothing about whether advertising for the item is active. Get an authorized Ads report or current campaign view, map the advertised product back to the relevant SKU or ASIN, and inspect status, clicks and spend for the days in question. Campaign targeting and advertised-product rows do not always map one-to-one onto inventory. If the mapping fails, report account or product-family exposure at its actual grain; do not assign every click to the single SKU.
Next inspect offer status and the inventory event sequence. Was the offer unavailable before the sales dip? Did receipt slip after the original promise? Did the advertised product change? Each question points to a different record and owner. Advertising spend may continue around a stock problem, but the stock snapshot alone neither proves wasted spend nor gives permission to pause a campaign. An offer suppression is not the same operational issue as an empty FBA shelf.
Hand over a conditional warning
A useful handoff reads: “At the snapshot time, 120 fulfillable units and an eight-unit daily assumption give 15 days of immediate cover. Receipt after day 15 creates a modeled gap; receipt at the start of day 13 avoids it under constant demand.” Attach the stock definition, SKU mapping, seven complete demand days and source timestamp. Operations verifies receiving and current sellable stock; the ad owner verifies campaign exposure. Refresh the snapshot before action.
If receipt timing is unknown, leave it unknown. If the unit history includes an outage, mark the demand estimate biased low. The result is a scenario with explicit inputs, not a forecast of an exact stockout day or a claim that a 1stPage connection supplies both Ads and inventory. That restraint is more useful than a confident alert built from mismatched rows.
Calculate immediate cover from fulfillable units only, then simulate each dated receipt. Show SKU and marketplace joins, complete-day unit demand, and unknown receipt or Ads status without filling gaps.
Sources and boundaries
Check the current permissions and report definitions before acting on an answer. Example prompts are questions, not live account results.