Ecommerce AI Coordination Playbook
Coordination practices for AI agent teams managing e-commerce operations -- inventory management, order fulfillment, pricing and promotions, marketplace management, customer experience, returns, and catalog coordination. Built for the speed and multi-channel complexity of online retail.
Fulfillment
Carrier Performance Scorecard
The fulfillment agent tracks carrier performance by: on-time delivery rate, damage rate, cost per package by zone, and customer complaint rate. When a carrier's on-time rate drops below 90% for 2 consecutive weeks, the fulfillment agent shifts volume to the next-best carrier for affected routes. Carrier selection is data-driven, not contract-driven.
What goes wrong without this
The company uses one carrier for everything because they signed a volume discount contract. That carrier's performance degrades in Q4 due to holiday volume. 30% of packages arrive late. Customer complaints spike. The company cannot switch carriers mid-season because nobody tracked performance or maintained alternatives.
Fulfillment SLA Monitoring
The fulfillment agent tracks every order from payment to shipment against the promised SLA (same-day, next-day, 3-5 business days). Orders approaching SLA breach get escalated with the specific blocker: warehouse delay, carrier issue, payment hold, or inventory mismatch.
What goes wrong without this
A "next day delivery" order sits in the warehouse for 3 days because the picker could not find the item. The customer contacts support. Support has no visibility into warehouse status. The customer gets a generic "we're looking into it" response and files a chargeback.
Fulfillment SLA Monitoring with Blocker Identification
The fulfillment agent tracks every order from payment to shipment against the promised SLA (same-day, next-day, 3-5 business days). Orders approaching SLA breach get escalated with the specific blocker: warehouse delay, carrier issue, payment hold, inventory mismatch, or address verification failure. The escalation includes a recommended resolution, not just a flag.
What goes wrong without this
A "next day delivery" order sits in the warehouse for 3 days because the picker could not find the item (it was in the wrong bin). The customer contacts support. Support has no visibility into warehouse status. The customer gets a generic "we are looking into it" response and files a chargeback.
Return-to-Inventory Speed
The returns agent tracks returned items from receipt to restocked status. Target: returned items back in sellable inventory within 24 hours of warehouse receipt. Items sitting in returns limbo are invisible to the inventory agent and cannot be sold.
What goes wrong without this
Returns pile up in the inspection queue. 50 units of a popular item are "in transit" in the returns system but physically sitting on a shelf. The inventory agent shows them as unavailable. The purchasing agent reorders unnecessarily.
Return-to-Inventory Speed Tracking
The returns agent tracks returned items from warehouse receipt to restocked status. Target: returned items back in sellable inventory within 24 hours of receiving. Items sitting in returns limbo are invisible to the inventory agent and cannot be sold. The returns agent reports daily: items received, items inspected, items restocked, items rejected, average processing time.
What goes wrong without this
Returns pile up in the inspection queue. 50 units of a popular item are "in transit" in the returns system but physically sitting on a shelf. The inventory agent shows them as unavailable. The purchasing agent reorders unnecessarily. The company pays for new stock while saleable returns sit unprocessed.
Split Shipment Coordination
When an order contains items from multiple warehouses or with different availability dates, the fulfillment agent decides: ship partial now and partial later, or hold and ship complete. The decision follows rules based on customer tier, item value, and shipping cost. The customer agent communicates the decision proactively.
What goes wrong without this
An order with 3 items ships in 3 separate packages because each item was in a different warehouse. The customer pays one shipping fee but receives 3 deliveries on 3 different days. They contact support confused. Shipping cost triples.
Split Shipment Decision Engine
When an order contains items from multiple warehouses or with different availability dates, the fulfillment agent decides: ship partial now and partial later, or hold and ship complete. The decision follows rules based on customer tier (VIP gets faster partial), item value (high-value items ship immediately), and incremental shipping cost (split only if cost delta is under $X). The customer agent communicates the decision proactively before the first package ships.
What goes wrong without this
An order with 3 items ships in 3 separate packages because each item was in a different warehouse. The customer pays one shipping fee but receives 3 deliveries on 3 different days. They contact support confused about why they got "part of their order." Shipping cost triples and the customer experience is fragmented.
Stay in the loop
Get weekly coordination intelligence updates. No account required.