twimco.Let’s talk ↗︎
Menu
Field notes / AI in practice

ShipBob's Bobby can create WROs in chat. Keep the confirm step sacred

ShipBob's Bobby is generally available in the merchant dashboard and can create warehouse receiving orders after it confirms with you. The operating move is listing which chat actions are allowed before peak volume climbs.

Editorial engraving of a sunny ops loft where a supply-chain manager reviews a soft confirm card on a laptop while a coordinator holds a paper WRO checklist.

ShipBob's Fall '26 release (updated November 3, 2026) makes Bobby generally available to every merchant in the dashboard: ask about inventory, create WROs in the same chat, pull ship and delivery rates, and update product details, with confirmation before changes and actions logged as yours. ShipBob MCP connects external agents like Claude to the same APIs. Write an allowlist for peak—questions yes, WROs with confirm yes, silent catalog edits no—before someone grants MCP access from a shared laptop.

What Bobby is allowed to touch

ShipBob's Fall '26 release post, updated November 3, 2026, says Bobby is generally available to every merchant inside the ShipBob dashboard. You can ask which SKUs will run out in the next thirty days, pull on-time ship and delivery rates, clear stuck orders, create warehouse receiving orders (WROs) and update product details. Co-founder Dhruv Saxena is quoted saying Bobby confirms before it makes any change, and every action performed through Bobby is logged as yours.

ShipBob MCP uses the same APIs for external agents such as Claude. Bobby additionally carries full account context and can connect you to live support. Same verbs, different front door.

Confirmation is the product. If Bobby skips the ask, you do not have an assistant—you have an unsupervised clerk.

Write the allowlist before peak

Peak is when people grant tools quickly. Write the list while you are calm.

Always allowed. Inventory questions, OTIF and delivery rate pulls, explanations of a stuck order—read paths that cannot create inbound freight.

Allowed with confirm. Creating a WRO, updating product details Bobby is allowed to touch. Keep the confirm step visible. Do not train the team to auto-approve in the chat habit.

Never from chat. Carrier account changes, billing contacts, blanket catalog wipes, anything that moves money outside ShipBob's logged merchant actions. If it is not in Bobby's published verbs, do not invent it.

MCP-specific. External agents via MCP should get the same allowlist, plus a named human who owns the Claude/Cursor workspace. A shared laptop with MCP connected is a shared warehouse clerk.

Decision guide

Allowlist for Bobby and MCP

ConsiderationActionDefault gate
Inventory / OTIF questionsRead-only answers.Allow
Create WROCreates inbound work.Allow only with confirm + unit cap
Update product detailsChanges catalog fields.Allow with confirm; ban bulk wipes
MCP from shared laptopExternal agent front door.Deny until named workspace owner
Decision framework; verbs from ShipBob Fall '26 Bobby section, limits are yours to set.
Confirmation is the product. If Bobby skips the ask, you do not have an assistant—you have an unsupervised clerk.

How to run the first week

  1. Enable Bobby for two operators, not the whole company.
  2. Script five prompts: low-stock SKUs, one OTIF pull, one stuck order, one WRO draft you will cancel, one product field update you will revert.
  3. Screenshot the confirm step. Put it in the SOP so new hires know what "good" looks like.
  4. Only then consider MCP from a locked-down agent workspace.
  5. Review the action log daily for a week—ShipBob says actions log as yours; read them like audit events.

Sequence of work

First-week Bobby drill

  1. Day 1

    Enable for two operators; capture confirm UI.

  2. Days 2–3

    Run five scripted prompts including a canceled WRO.

  3. Day 4

    Publish allowlist; review action log.

  4. Day 5+

    Consider MCP only from a locked workspace.

Illustrative rollout; not a ShipBob screenshot.

Failure modes to expect

Confirm fatigue. After twenty yeses, people stop reading. Cap autonomous suggestions; require a second person for WROs above a unit threshold you choose.

Wrong warehouse. A WRO aimed at the wrong node burns appointment capacity. Echo building and SKU list in the confirm card.

MCP sprawl. Three contractors with Claude connected is three clerks. Provision and revoke like VPN access.

Trusting narrative over log. If Bobby summarizes "all set," open the WRO record anyway until the habit sticks.

What this is not

This is not a review of ShipBob robotics, branded tracking or survey statistics from the same blog post. Those are separate buys. This note is only about agent actions that create warehouse work.

Make the action log part of stand-up.

ShipBob's promise that actions log as yours only helps if someone reads the log. Add a five-minute "Bobby yesterday" review to the ops stand-up for the first two weeks: WROs created, product fields changed, confirms dismissed. Patterns show up fast—usually one person approving everything without reading.

Inbound appointments are scarce at peak. A chat-created WRO that lands on the wrong day costs real dock time. Require the confirm card to echo appointment constraints you already enforce in the UI.

If you use ShipBob MCP from Claude, store the connection in a company-owned workspace with SSO, not a personal free account. Revoke access when people leave, the same day you revoke ShipBob dashboard seats.

Do not let Bobby become the only person who "knows" which SKUs are short. Export the low-stock answers into the planning sheet your demand planner already owns. Agents advise; the plan remains a document with an owner.

Put this into practice

If you fulfill with ShipBob, publish a one-page Bobby/MCP allowlist before the next inbound surge. For help tying agent confirmations, WRO discipline and fulfillment operations audit logs together, get in touch with your current ShipBob roles list and a sample WRO.

Keep a short evidence packet: Fall '26 post URL, allowlist version, operators enabled, and a week of action-log samples. When a bad WRO ships, that packet shows whether process or product failed.

Finance may ask whether Bobby actions create billable receiving events. Know the answer before peak, not after a surprise invoice.

If you disable Bobby for a season, write that decision down too. Tools that flicker on and off without a record produce folklore.

Warehouse managers should see Bobby as another associate with audit logging—not as a dashboard toy. If WROs created in chat skip a check that UI-created WROs enforce, escalate to ShipBob. Your allowlist assumes confirmations are meaningful.

Support escalations via Bobby's live-support path should still open a ticket you can find later. Chat that disappears is not an ops record.

Publish the allowlist in the same place you publish packing SOP changes so associates see agent rules next to bench rules. If Bobby suggests a WRO that violates your appointment calendar, the confirm step must make that conflict visible—or you need a human checklist after confirm. Rotate which operator reviews the action log so the duty does not become invisible. For MCP, require a second person to approve connecting a new agent workspace, the same way you approve production API tokens. Peak is a bad time to discover a contractor still has Claude wired to create WROs after their project ended. Close the loop by sampling one Bobby-created WRO end-to-end each week: chat confirm, ShipBob record, dock appointment, receiving completion.

When Bobby is right, still keep the planning sheet updated by a human. The point of the tool is faster drafts and logged actions—not a second source of truth that drifts from demand planning.

Pair Bobby training with a one-page "what not to ask" list for peak temps: no billing changes, no carrier account edits, no jokes that turn into confirmations. Humor in a chat UI is how accidental WROs happen. Keep the tone boring and the confirms explicit. Rehearse a bad confirm: operator clicks yes on the wrong building, then follows the cancel path while the dock lead watches.

Related work: Spin Market.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎