Demos · recorded on a live InfiPlex instance
These are recordings of an AI agent connected to a live InfiPlex instance through the InfiPlex MCP server. Nothing is staged inside a call: every answer comes from a tool the server exposes, on real orders and inventory, and every write stops at the server's preview until a person answers. Typing and tool waits are sped up, answers play at real speed. Each demo has chapters and a full transcript below it.
Demo 1
Chapters
| Time | What was asked | Tool the agent called | What came back |
|---|---|---|---|
| 0:03 | How many orders came in today, and how many are still unshipped? | order_search | 1 order today, still unshipped. |
| 0:16 | For the order today, what was the ship-to address and which warehouse(s) did it route to? | order_search | Order 103480 to Columbus, OH; split: HB-2201 from Reno, MK-88 from Columbus. |
| 0:30 | Why did it get routed to Reno? | order_warehouse_routing_explanation_get | Columbus passed zip rules but had 0 of HB-2201; Reno had 42, so the unit came from Reno. MK-88 stayed in Columbus. |
| 0:40 | Do I have any SKUs at the reorder point? | inventory_restock_list | Three: GL-410, GL-411, MK-88, with on hand and reorder point. |
| 0:53 | Add a note to order 103480 that the customer called about delivery. | order_note_create | Note added. |
| 1:05 | Set HB-2201 to $24.99. Then: actually, leave it. | price_get, price_set (preview) | Server previews the change from $27.50; declined in chat; no change made. |
| 1:20 | Show me Reno's routing settings. | warehouse_get | Reno's zip rules and why 43219 made it eligible for today's order. |
Transcript
You
How many orders came in today and how many are still unshipped?
Tool
order_search
AI agent
1 order came in today on Mark8, and it is still unshipped.
You
For the order today, what was the ship to address and which warehouse(s) did it get routed to?
Tool
order_search
AI agent
Order 103480 (Manual, 9:51 AM). Ship to: Jordan Rivera, 4400 Easton Way, Columbus, OH 43219, US. Routing: split across two warehouses.
You
Why did it get routed to Reno?
Tool
order_warehouse_routing_explanation_get
AI agent
Columbus was checked first (passed zip rules, set as default), but it had 0 units of HB-2201 at routing time. Reno was checked next, also passed zip rules, and had 42 on hand, so the 1 unit was pulled from there. MK-88 stayed in Columbus because it had 4 on hand, enough to cover the 2 ordered.
You
Ok. Do I have any SKUs at the reorder point?
Tool
inventory_restock_list
AI agent
Three SKUs at or below reorder point:
MK-88 dropped after today's order took 2 from Columbus.
You
Add a note to order 103480 that the customer called about delivery.
Tool
order_note_create
AI agent
Note added to order 103480: "Customer called about delivery."
You
Set HB-2201 to $24.99
Tool
price_get, then price_set (first call: server returns the preview and a confirmation token; nothing is written)
AI agent
HB-2201 is currently $27.50. Setting it to $24.99 will push to connected channels. Confirm?
You
Actually leave it at that
AI agent
Left at $27.50, no change made.
You
Show me Reno's routing settings
Tool
warehouse_get
AI agent
Reno (warehouse 14), Reno, NV 89502. Zip rules on, with the rule set that made it eligible; since 43219 matches the rule, Reno was eligible for today's order.
The routing answer at 0:30 is the one to notice. It is not the agent reasoning about what probably happened; it is the event log InfiPlex wrote when the order was allocated, returned by one tool. The price change at 1:05 is the other: the server issued the preview, the agent showed it, and a two-word reply ended it with nothing written. How every write is protected.
Demo 2
Every write in this one goes through the server's preview before anything changes, and the recording cuts to the InfiPlex admin after each step so you can see it really happened. Watch for the product step: the agent refuses to create a SKU with a UPC that fails its check digit and offers the corrected one.
Chapters
| Time | What was asked or shown | Tool | What happened |
|---|---|---|---|
| 0:03 | Create a warehouse called Dallas with zip rules 7* and 8*. | warehouse_search warehouse_create | Previewed, confirmed, created as warehouse 18. |
| 0:21 | (In the admin) the warehouse list. | Shown in the InfiPlex admin | Dallas is there, next to Columbus and Reno. |
| 0:24 | Create a product: LT-900, Headlamp 900 lumen, 49.00, UPC 812349000900, 6 oz. | pim_sku_get products_create | The agent flags that the UPC fails its check digit and offers 812349000906. "Use 906." Created. |
| 0:46 | Receive 30 units of LT-900 into Dallas and 12 into Reno. | warehouse_search inventory_set_bulk | One preview for both rows, confirmed, 42 on hand. |
| 0:59 | (In the admin) LT-900 inventory by warehouse. | Shown in the InfiPlex admin | 30 in Dallas, 12 in Reno. |
| 1:06 | Create a manual order for Priya Nair in Dallas, 2 x LT-900, dated now. | order_create | Preview with totals. Asked where it routed before confirming, the agent says it has not been created yet. |
| 1:33 | Yes, create it. Which warehouse did it route to and why? | order_create order_warehouse_routing_explanation_get order_get | Created as order 103481, routed to Dallas by zip distance, confirmed from the order record. |
| 1:43 | (In the admin) the orders list. | Shown in the InfiPlex admin | The new order at the top. |
| 1:56 | Ship it: UPS Ground, tracking, both units in one box, 14 oz. | order_get order_tracking_create | Previewed (the agent notes the tracking number is UPS's published sample), confirmed, recorded as a shipment. |
| 2:11 | (In the admin) the order with its tracking. | Shown in the InfiPlex admin | Shipped, with tracking. |
Transcript
You
Create a warehouse called Dallas at 2200 Irving Blvd, Dallas, TX 75207, with zip code rule of 7*,8* and an identifier of Dallas
Tool
warehouse_search, then warehouse_create (first call: preview and confirmation token; nothing written)
AI agent
No existing Dallas warehouse. Preview of what will be created: Name Dallas; Identifier Dallas; Address 2200 Irving Blvd, Dallas, TX 75207, US; Zip rules 7* and 8*, turned on. With zip rules on, this warehouse will only fill orders shipping to zips that start with 7 or 8. Confirm and I'll create it.
You
Confirm
AI agent
The Dallas warehouse is created as warehouse ID 18 and I checked that it saved correctly. The identifier is Dallas, the address is 2200 Irving Blvd, Dallas, TX 75207, US, and the 7* and 8* zip rules are on.
You
Create a product: SKU LT-900, Headlamp 900 lumen, price 49.00, UPC 812349000900, 6 oz.
Tool
pim_sku_get
AI agent
LT-900 doesn't exist yet, so this will create a new product: SKU LT-900, Title Headlamp 900 lumen, Price 49.00, UPC 812349000900, Ship weight 6 oz. The UPC 812349000900 fails the UPC-A check digit test. For the first 11 digits (81234900090), the check digit should be 6, which would make the UPC 812349000906, not a final 0. Marketplaces that validate UPCs will reject this one. Should I create it with 812349000900 as given, or use 812349000906?
You
Use 906
Tool
products_create (previewed and confirmed), then pim_sku_get
AI agent
LT-900 was created ("Product Created"). A price lookup confirms 49.00.
You
Receive 30 units of LT-900 into Dallas and 12 into Reno.
Tool
warehouse_search, then inventory_set_bulk (preview)
AI agent
This will add the following LT-900 stock, which then syncs to every connected channel: Dallas (warehouse 18) +30; Reno (warehouse 14) +12. Confirm and I'll run it.
You
Confirmed
AI agent
Both rows went through. LT-900 now has 30 units in Dallas and 12 in Reno, 42 in total.
You
Create a manual order for Priya Nair, 1900 Commerce St, Dallas, TX 75201 (use for both shipping and billing), priya@example.com, 2 x LT-900 at 49.00, ground shipping 9.00, dated now.
Tool
order_create (first call: preview and confirmation token)
AI agent
Here's the manual order ready to create. Source Manual; Customer Priya Nair; Ship to and bill to 1900 Commerce St, Dallas, TX 75201, US; Items 2 x LT-900 Headlamp 900 lumen at 49.00 = 98.00; Shipping Ground 9.00; Tax 0.00; Order total 107.00. The 75201 ship-to zip matches the 7* rule on both Dallas and Reno, so either warehouse could fill it. Confirm and I'll create it.
You
Which warehouse did that order route to and why?
AI agent
That order hasn't been created yet, so it hasn't routed anywhere. The last step was a preview waiting for your confirmation. Once you confirm, I'll create it and pull its routing explanation to show which warehouse filled each line and why. Should I create it as previewed?
You
Yes create it
Tool
order_create (with the token), then order_warehouse_routing_explanation_get
AI agent
Order 103481 was created, and both units of LT-900 routed to Dallas. The account is set to fill orders by zip code distance, so warehouses are tried nearest to the ship-to zip first. Dallas was checked first because its zip, 75207, is the closest to Priya's 75201. The ship-to zip 75201 passed Dallas's 7* rule. Dallas had 30 units, so it filled both and routing stopped. Dallas now has 28 units of LT-900.
You
Which warehouse was actually used for that order?
Tool
order_get
AI agent
Dallas (warehouse 18). The order record itself assigns both units of LT-900 to Dallas, and Dallas is the only warehouse listed as used on the order. That matches the routing log.
You
Ship it: UPS Ground, tracking 1Z999AA10123456784, both units in one box, 14 oz.
Tool
order_get, then order_tracking_create (preview)
AI agent
Ready to record this shipment on order 103481: UPS Ground; tracking 1Z999AA10123456784; one box holding 2 x LT-900, 14 oz; ships from Dallas (warehouse 18). 1Z999AA10123456784 is the sample tracking number UPS publishes in its documentation, not a live shipment. That's fine if this is a test order, but it would give a real customer a dead tracking link. Confirm and I'll record it.
You
Confirmed
AI agent
Order 103481 is shipped: 2 of 2 units, UPS Ground, tracking 1Z999AA10123456784, one 14 oz box.
Three moments to notice. The UPC: the agent did the check-digit math before writing anything, which is the difference between an assistant and a form. The order: asked where it routed before you had said yes, the agent answered that nothing had been created, because nothing had; the server does not write until the confirmation token comes back. And the shipment: it flagged that the tracking number was UPS's own documentation sample. How every write is protected, and how routing by zip distance works.
Do it yourself
Tools > Admin API > Create New API Key. Read scopes only for the first run. MCP Enabled: Yes. Set-up guide.
Paste your instance URL and the api-token header into the assistant's connector or config screen. The set-up guide has the steps for each one.
Orders today, one order's routing, why it routed there, the restock list, and a price change you decline. All prompts by role.
Add Write Orders and Write Inventory for tracking and receiving, or run the fully autonomous fulfillment agent. Headless order management explains the dial.
Frequently asked
Real. It is a screen recording of an AI agent connected to a live InfiPlex instance through the MCP server. The order, SKUs, and warehouses are sample records on that instance; every answer is what the tools returned. Typing and tool waits are sped up in the edit; nothing inside a tool call is cut.
Because the server makes it. Tools that change stock, prices, shipments, products, warehouses, or settings return a preview and a confirmation token on the first call and only execute on a second call carrying that token. The agent showed the preview and the person declined, so nothing was written. A fully autonomous agent completes that second call itself on a key you configure for it.
order_search, order_warehouse_routing_explanation_get, inventory_restock_list, order_note_create, price_get, price_set, and warehouse_get. All of them, with inputs and gates, are on the tools reference.
These recordings use Claude Desktop. Claude Code, ChatGPT through Codex (the CLI and IDE extension), Cursor, Windsurf, and any client that supports remote MCP servers with a header connect the same way and get the same tools. The ChatGPT web app itself requires OAuth for remote servers and is not supported at this time.
Nothing beyond API access, which is part of InfiPlex's Growth and Enterprise packages. No AI add-on and no per-call fee. See pricing.
Resources
Bring the question your team asks most. We will connect an agent to a live instance and answer it on the call, then hand you the key to do it yourself.
Open a key at Tools > Admin API, set MCP Enabled to Yes, and run the seven questions above. Questions: Contact us, email info@infiplex.com, or call 888‑770‑0857.
Recorded September 24, 2026 on a live InfiPlex instance with sample records. Claude is a trademark of Anthropic, PBC. ChatGPT and Codex are trademarks of OpenAI. Model Context Protocol is an open standard.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License