ATP Promising Canonical URL: https://babadook.tech/sub-modules/atp-promising Entity: sub-modules Content hash: 536409584278e0a5446dca253083238a0c17f5a2eba627584b7c3630222eb961 Quote dates your operations already approved — before the customer hears them. Nothing poisons a customer relationship faster than a confident date that collapses a week later. ATP Promising puts operations in the room before the quote leaves: stock, reservations, capacity, and transit resolve into a date the network has proven — or the honest gap preventing one. How promising works A sales request carries item, quantity, and requested date. ATP resolves stock availability, reserved quantities, planned supply, production lead time, and carrier transit into one verdict: commit the date, offer the earliest feasible date, or escalate the constraint with its owner and sensitivity. data Viz data View section: how-it-works Stock Check On-hand balances minus reservations plus planned supply resolve per item-location. Lot and serial constraints apply where policies require them. Capacity Check Production lead time from routings and work-center load, plus labor availability from the worker graph. Constrained resources name the bottleneck order competing for them. Transit Check Carrier transit times with service-level options resolve the ship-to promise date. Expedite paths quote with cost differentials attached. Commit or Counter All three checks green commits the date and reserves stock. Any red returns the earliest feasible alternative with the binding constraint named for negotiation. Promising guarantees - Live inputs: Stock, reservations, planned supply, capacity, and transit resolved per request - Named gaps: Refusals cite the binding constraint with the earliest feasible alternative - Held stock: Accepted promises reserve against the same truth execution consumes - section: capabilities Promising by industry Promise checks bend per industry — same ATP verdict structure, different feasibility stakes. data Viz data View section: industries Manufacturing Make-to-order promises check component availability, capacity, and lead time together. Configured products resolve matrix BOMs before the date commits. Retail and E-commerce Storefront promises check allocated stock across warehouses and stores with ship-from-store options. Backorder dates derive from supply plans, not guesses. Distribution Bulk and lot-controlled promises validate FEFO and customer-specific stock before committing. Multi-warehouse sourcing picks the feasible origin automatically. ATP Promising questions Section 1 What happens when stock is short? The system refuses the requested date and returns the earliest feasible alternative with the constraint identified — stock, capacity, or transit — so sales can negotiate from facts instead of guessing. Section 2 Does promising reserve inventory? Yes. An accepted promise creates a reservation against the same stock truth that warehouse execution consumes, preventing double-promising the same units. Section 3 Won't honest dates lose us deals to competitors who promise faster? They win the quote and lose the customer at delivery. Verified dates close slightly slower and renew dramatically more — commission follows kept promises. data View section: faqs content section value: Promising is evidence until the owner accepts: inventory, capacity, and logistics outcomes are read back from their authoritative parts before the promise commits. Section 6 Available-to-promise against live stock and reservations Section 7 Capacity-aware promising with production feasibility checks Section 8 Shortage explanation with earliest feasible alternative Section 9 Reservation hold on promise acceptance Relationships products - XRP — https://babadook.tech/products/xrp modules - Supply Chain — https://babadook.tech/modules/supply-chain