Operations
PILOT — NOT SHIPPING YETInventory state, replenishment drafts, stockout alerts, fulfillment exception handling. The next Layer-2 role-agent we're piloting, after the Trading Agent shipped.
We're piloting this with a small group of merchants. There's no public launch date and no waitlist trick. If your inventory pain matches what's below, talk to us.
PILOT — NOT SHIPPING YET
Why Operations is the role we're piloting next
Trading shipped first and runs the storefront. Operations is the inventory role we're piloting next — and it's the right next one because the merchant ROI is concrete: 'you would have stocked out in N days; here is the PO draft.' The depth it needs — vendor lead times, supplier identifiers, and order-history pattern recognition — is exactly the kind that compounds over time and is specific to how LatAm merchants actually buy. So we're building it one role at a time, with a small group of real merchants, instead of shipping a shallow version.
What it will own
- Replenishment drafts based on demand forecasting
- Stockout alerts before they bite — with lead time as the variable
- Fulfillment exception handling (lost shipments, damaged returns, 3PL coordination signals)
- Returns triage with the customer's conversation context already attached
- Vendor / supplier coordination signals (when integrations exist)
What it will wield
- Inventory state read across your store
- Order-history pattern recognition
- Vendor lead-time registry
- Stockout alert pipeline
- Replenishment PO draft writer
- A first supplier integration (the most-requested one among pilot merchants)
WHERE IT WOULD SIT
Layer 1 — Customer-facing
Layer 2 — Role-aligned operators
Layer 3 — Meta / orchestration