Batch Expiry & Delivery Shelf Life Preflight

Check whether your supplied inventory lots meet a customer's minimum remaining shelf life on one planned delivery date. The report separates eligible, blocked, expired, short-dated and unknown-expiry stock, then calculates whether the known eligible quantity covers each requirement.

This is useful when a warehouse export shows enough total stock but some batches cannot meet the customer's date requirement. It is a date-and-quantity review, not a product safety assessment or shipment approval.

Try the example

The example needs 12 units on October 22, 2026, with at least 30 days remaining. Eight units expire November 1 and fail the rule; ten units expire December 1 and meet it. The completed report shows ten known eligible units and a confirmed two-unit shortfall because coverage is explicitly complete and no relevant expiry date is unknown.

The run writes one dataset record and saves the full JSON in REPORT. OUTPUT contains the run summary. Export through the dataset as JSON, CSV or Excel.

Input contract

Pass one caseJson string with caseId, asOfDate, deliveryDate, coverageConfirmed, requirements and lots. The supplied snapshot date must not be after delivery. Nothing is inferred from the run's clock.

Each requirement has an exact sku and unit, a positive whole-unit quantity, and minimumRemainingDays (0–36,500). Each lot has lotId, sku, unit, whole-unit quantity, expiryDate (YYYY-MM-DD or null), and a boolean blocked. Use unreserved quantities and independently verify the data before acting. One requirement per exact SKU/unit; one lot row per exact SKU/unit/lotId. No unit or SKU conversion occurs.

The explicit date rule is expiryDate >= deliveryDate + minimumRemainingDays. Equality passes this supplied rule. An expiry before delivery fails. This date convention does not override a product label, contract, storage condition or local rule. A blocked lot is excluded even when its expiry is unknown.

Set coverageConfirmed true only if all relevant stock and blocking information are present. With complete coverage, an empty lot list means zero stock. Without complete coverage, or when relevant unblocked positive stock has unknown expiry, confirmedShortfall is null. uncoveredByKnownEligibleQuantity remains visible and is not called a confirmed shortage. Unknown unblocked stock can make the review incomplete even when known eligible stock already covers demand.

Unused SKU/unit lots remain visible in unusedLots; they do not change another SKU's result. The Actor does not allocate stock across separate deliveries or remember reservations across runs.

Pricing

$0.05 per completed report, including reports with findings or incomplete coverage. Malformed inputs and runs with insufficient report-event budget produce no completed report event. A repeated run is a new review. Platform usage can apply separately; check the live price and set an Apify maximum-charge limit.

Limits, data and safety

At most 500 requirements, 1,000 lots and 1 MB of UTF-8 input. Quantities are integers up to 1,000,000,000,000. Identifiers are exact, case-sensitive strings of 1–100 characters. Duplicate keys, conflicting records, invalid dates, noninteger quantities and unexpected fields fail before billing. Missing expiry is allowed only as explicit null.

No external network calls, AI, OCR, paid API, inventory writes or automated approvals occur. Do not include customer names, addresses, banking details or credentials. Input and output stay in your Apify storage under its access and retention settings. Source-code visibility is restricted; that does not change your responsibility to protect operational data.

Reference basis and limitations

Microsoft documents customer sellable-day rules and batch expiration controls. Oracle documents minimum remaining shelf life relative to a shipment or arrival date. This Actor implements only the explicit delivery-date rule supplied in its input; it does not emulate an ERP's full policy hierarchy or certify compliance.

• https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/planning-optimization/shelf-life
• https://docs.oracle.com/en/cloud/saas/readiness/scm/26d/order26d/26D-order-mgmt-wn-f50210.htm

Always review the source labels, applicable contract, physical condition, temperature history and other product requirements before deciding whether to ship or use a lot.