How to Calculate Available to Promise for eCommerce Inventory Planning

Available to Promise Inventory that can be promised to customers for purchase or future fulfillment. In eCommerce planning the calculation of available-to-promise (ATP) converts inventory, incoming receipts, allocations and commitments into a single number or timeline you can use to confirm order dates and quantities to customers.

Accurate ATP prevents over‑promising, reduces cancellations, and supports realistic delivery dates on product pages and checkout flows. For merchants the ATP calculation is part math, part business rules: you combine physical stock, inbound supply, and reserved quantities, then apply rules for safety stock, allocation priorities and partial shipments. The result drives both customer-facing promises and internal pick/pack schedules.

What The Calculation Typically Uses

ATP pulls from several operational data sources; make sure each is current and reconciled before using ATP to promise customer orders.

• On‑hand inventory: Physical units in the warehouse that are available for picking (exclude quality holds and quarantined stock).
• Allocated stock: Units already reserved for confirmed orders, internal transfers, or production (these reduce ATP).
• Scheduled receipts: Purchase orders, production runs or transfers due to arrive within the promise window.
• Safety stock: Buffer quantity set by SKU, location, or SKU‑location; may be excluded from ATP depending on policy.
• Committed demand: Backorders or unshipped confirmed orders that must be fulfilled before new promises.

Basic Calculation Approaches

There are three common approaches to calculating ATP in eCommerce. Choose the one that matches your fulfillment complexity and customer expectations.

• Simple snapshot ATP: ATP = On‑hand − Allocations. Use when lead times are short and receipts are infrequent; suitable for single‑warehouse sellers.
• Forward‑looking ATP (time‑phased): ATP by future date = (On‑hand at day 0 + scheduled receipts by date − cumulative allocations and promise commitments by date). Use this for multi‑period promises and preorders.
• Order‑driven ATP with rules: Similar to time‑phased but applies business rules (customer priority, partial shipment preferences, configurable reserve). Common in marketplaces and multi‑location networks.

How To Implement The Calculation

Implementation steps combine systems work with policy decisions. Follow a repeatable sequence to avoid surprises.

• Define policy: Decide whether safety stock is included/excluded, how to treat incoming transfers, and whether to allow partial promises.
• Map data sources: Connect WMS, ERP, purchase order systems and eCommerce platform to pull real‑time inventory, receipts and commitments.
• Choose calculation window: Short (same day/next day) for fast movers, longer windows for preorders or made‑to‑order items.
• Build time‑phased logic: For each SKU create a timeline of on‑hand + receipts − allocations; compute cumulative ATP per day.
• Expose results: Return a single promise date/quantity to the storefront or show available dates during checkout.

Practical Example

SKU A at Warehouse 1: On‑hand = 50 units. Allocations = 20 units for confirmed orders. Scheduled receipts: PO for 100 units arriving in 5 days. Safety stock set to 10 units and excluded from promises.

Snapshot ATP = 50 − 20 − 10 (safety) = 20 units available to promise immediately. If a customer orders 30 units, your system can either promise 20 immediately and the remaining 10 with a future date (after the PO arrives), or decline the extra 10 depending on your partial allocation rules.

Edge Cases And Adjustments

ATP calculations must handle returns, cancellations, and supply disruptions. Build rules for these events:

• Returns processing: Decide whether returned items are immediately available to promise or need inspection/quarantine.
• Lead‑time variability: Use conservative receipts when supplier reliability is low — hold a portion of receipts as contingent until confirmed.
• Cross‑dock and transit stock: Include inbound shipments in ATP only when you can guarantee arrival within the promise window.

Implementation Tips For eCommerce Teams

Practical measures reduce promise failures and customer dissatisfaction.

• Automate reconciliation: Reconcile WMS and eCommerce platform stock counts hourly during peak periods.
• Keep promises conservative: Prefer slightly longer lead times over late deliveries; a one‑day cushion can reduce SLA breaches.
• Segment rules by SKU: Apply aggressive ATP for fast‑moving SKUs and conservative ATP for fragile or high‑value items.
• Expose partial availability: Show customers what ships now and what ships later to set expectations.

In short, the Available to Promise calculation for eCommerce turns live inventory, incoming supply and allocation rules into concrete customer promises. Accurate ATP requires clean data, clear business rules and a time‑phased approach when promises extend beyond the same day. Properly implemented, ATP reduces cancellations, improves order fill rates and makes delivery dates reliable for customers and operations alike.