Weigh the promise on an order against what stock and the pick line can actually do, then draft the notice the rule requires and hold it for the fulfilment lead, who sends it.
An order completes when payment and every element needed to ship are there, and the clock starts then.
02
A shipping time stated in the solicitation displaces the thirty-day fallback, a shorter one included.
Reason
03
An order ships when the goods are placed in the possession of the carrier, which is not delivery.
04
A promise moves, and 435.2(b) wants the option offered clearly and without waiting to be asked.
05
A revised date thirty days or less past the applicable time is one silence is treated as consent to.
Decide
06
A longer or open-ended delay cancels the order instead, unless consent arrives inside thirty days.
07
A card already on file is payment, not an application for credit, so no fifty-day clock opens.
Out
08
An order shipped late with no notice offered is already cancelled, and the shipment does not cure that.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Timing, reading stock and drafting the notice belong to the agent. Sending it, cancelling an order and refunding belong to a named fulfilment lead.
Example workflow
One order, promise to notice
AgentHuman
1Order receivedWeb checkout, marketplace feed, telephone order or an order-management record
2Clock set from the promiseThe time the channel stated, the day the order was completed and the date shipment is owed
3Stock and pick line readOn-hand, allocated, inbound and what the pick line can clear before that date
4Controls appliedPromise checks, completeness checks, carrier-tender checks and shipment confidence
No human action required
Stages 1 to 4 run unaided, and no notice leaves at any of them — the agent is timing, and the lead lane opens at the shipment gate.
5DecisionSplits at the shipment gate
Shipment on time
Goes to the named fulfilment lead.
Anything late
Adds a customer operations read first.
Lead review
The order is held with its stated time, its revised date and the notice drafted for it.
Release notice · Amend notice · Send to operations review
Released — by the fulfilment lead▼
6Order and notice records updatedOnly where write access and records policy allow it
7Outcome evaluatedPromise accuracy, notice timing, lead corrections and what review found
Corrections
Each fulfilment-lead correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding that a promise on an order may move.
Sending the delay notice a buyer receives.
Releasing a prompt refund inside seven working days.
Setting the shipping time a channel advertises.
Automation boundaryAgent acts unaided
✓Check what each order still needs before shipment.
✓Draft the delay notice and the definite revised date it must carry.
✓Time the applicable shipping clock from the order that started it.
✓Flag each order whose promised time is at risk.
No notice leaves except by a named fulfilment lead, inside the agreed boundaries.
Judging whether an order was properly completed.
Committing stock that no count has confirmed.
Telling a regulator what an order record means.
Changes to promise rules, channels or thresholds.
Example output
One order promise, annotated
This serves an operations team whose records have to show systems and procedures assuring compliance in the ordinary course; below is one order exactly as the agent leaves it.
Order record · single promiseIllustrative example
Order
Recorded as
Applicable time
Evidence of record
Confidence
Held for
Marketplace order, promised date
Late against the stated time
Two days, as advertised
Carrier tender, 6 May 2026
Held unsent
The named fulfilment lead
As receivedTaken from the order record and the carrier tender on file, and it asserts nothing beyond them.
What the record holdsOrder completionCarrier tenderStock allocation
Why no notice hereMoving a promise on an order is a judgement the fulfilment lead makes.
ActionRelease noticeAmend noticeSend to operations review
What the score decidesBelow the configured threshold the order gets an operations read before the lead sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every orderFrom the channel that promised it
03Evidence
Where the promise is tested
Warehouse orchestration releases and sequences work inside the four walls; this is the promise made to the customer, the clock it started and the notice owed when that promise moves.
01Approved path
Shipping is not delivering
The clock in 435.1(e) turns on the act by which merchandise is physically placed in the possession of the carrier, so the EU and UK delivery rules are answering a different question.
02Human review
What was checked, and not found
Checked in the current text: Part 435 carries no signature, no certification, no filing and no prescribed retention period, and nothing in it regulates inventory accuracy for an ordinary company — no count cadence, no stock-record format, no tolerance.
04Build an evidence trail
The order, the notice sent about it and the date the promise moved stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Order managementNetSuite · Manhattan Active Order records and the dates promised
A channel-level promise-accuracy figure can read clean while marketplace promised-date orders carry most of the corrections. Nestack reports the correction rate by channel, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Marketplace promised-date orders
10.9%
3.7×
Review
Pre-orders and backorders
7.8%
2.6×
Review
Split shipments across sites
4.8%
1.6×
Watch
Standard in-stock orders
2.0%
0.7×
Normal
Bar: correction-rate lift vs. standard-order baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a moved promise costs
A loop shuts when the promise moved without notice is a standing case. That suite is what the next order released is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on marketplace promised-date orders.
02Diagnose
The two-day badge on the product page for an item that had not been picked in a week is worked backwards until one cause is left standing.
03Improve
The change leaves numbered, and the orders that caused it ride with it.
04Verify
One order case still red is enough to hold the release back.
05Learn
It stays a standing test, and the notice rules are amended alongside it.
Learn → DetectThe return edge. The next order released runs against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, promise timing, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Promise-boundary and automation-boundary work.
02Order, stock and carrier sources.
03Channel-promise and shipment-clock derivation.
04Order and stock ingestion.
05Promise, clock and order binding.
06Shipment scoring and review routing.
07Lead notice-release workflow.
08Order-system integration.
09Promise and notice cases.
10Guardrails and cancellation controls.
11Order-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne channel, one siteProductionProduction fulfilment workflowAdvancedMultiple channels / sites
Introduced at Pilot
Promise timing to your channels✓✓✓
Named lead notice release✓✓✓
Order-promise baseline✓✓✓
Introduced at Production
Reporting by order channel—✓✓
Lead review workflow in your systems—✓✓
Approved write-back—✓✓
Order-management integration—✓✓
Introduced at Advanced
Multi-channel promise sets——✓
Cross-site shipment packs——✓
Large order volumes——✓
Multi-channel promise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, order volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live channels and the shipping time each one states→Promise capture and clock derivationWeek 1
02Representative orders, stock positions and carrier tenders→Stock binding, clock logic and the promise baselineWeek 2
03Your notice templates and the leads they name→Promise mapping, clock derivation and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Order, stock and carrier source assessment, then integration setupWeek 2
05Promises you would not want quoted back→Notice cases and failure-mode testingWeek 4
06What no shipment notice may waive→Shipment scoring, review routing, guardrails and release controlsWeek 3
07A named fulfilment lead who releases notices→Release to the fulfilment lead, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
This is a schedule rather than an illustration, which is why two phases genuinely share week five.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Promise discovery, clock derivation and the automation boundaryW2Source integration and the order-promise baselineW3Stock binding, shipment logic and release controlsW4Evaluation suite, notice cases and failure-mode testingW5Order-system integration, pilot channels and targeted correctionsW6One peak season run under the fulfilment lead, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and week five is shared by design.
At the end of W6Once the shipment record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Operations AI agent
Build an order fulfilment agent around the promise your product page makes before the pick line has seen it.
Show us one channel, the shipping time it states and the last order that missed it. What does the record show when a promise moves — a notice offered without prior demand, or nothing, which is the absence 435.2(d) turns into a presumption against the seller?
