Guide · Shopify stores on InfiPlex
Shopify's fulfillment API separates the FulfillmentOrder, the location assignment, from the Fulfillment, the shipment, and since the 2024-10 API version an app can only fulfill what is assigned to its own location. InfiPlex already moves fulfillment orders to the location your rules define, on push and on pull, and keeps stock in sync across one store, several stores, or a store and its 3PLs through its Shopify integration. An AI agent on the InfiPlex MCP server answers the questions that used to mean opening three admin screens: where did this order route and why, did the inventory send reach Shopify, and why does a SKU show zero on the storefront when the warehouse has it.
Why Shopify
The Fulfillment Orders and multi-location routing guide covers the mechanics: Shopify's order routing assigns each line to a location automatically, assigned_location is the field that matters, and InfiPlex moves the fulfillment order to the location your rules name. Underneath that, InfiPlex routes every line to an InfiPlex warehouse and writes a routing record once, at pull time, that never changes. The agent reads that record and the log around it.
| What your team asks the agent | Tools it calls | What it hands back |
|---|---|---|
| "Which Shopify orders are unshipped, and where did each route?" | order_search on the Shopify channel, not fully shipped, oldest first |
Order ids, hours since placement, ship-to state, and the warehouse each line routed to |
| "Why did 4419040 go to Columbus? We stock that in Reno." | order_warehouse_routing_explanation_get |
The zip rule check, the default warehouse, and the Reno stock after buffers at the moment routing ran |
| "Did the inventory send to the store go through this morning?" | log_types_get, then log_search on the Shopify send inventory types |
Last successful send, or the failed sends with Shopify's error text |
| "Why does GL-410 show 0 on the storefront when Reno has 60?" | inventory_get, inventory_change_history_get, shop_setting_search on the Shopify buffer, log_search |
Which of the three it is: a buffer, a failed send, or a location mapping |
| "Connect the new client's store so we can pull their orders." | marketplace_connect_link_get with eal__shopify_connect_pull |
A one-time authorization link for the store owner, expiring the same day |
| "How many orders did store B send us this week versus store A?" | order_search with order_source_eq per store and just_count |
Counts per connection, since each store is its own order source |
Every tool above is documented on the tools reference. The multi-warehouse order routing page explains the rules the routing record reflects.
Routing
Every order line gets a routing record when InfiPlex pulls it: the zip rule that matched, the warehouses considered, the stock each had after its buffer, and where the units were taken from. It is written once and never changed, so it explains the decision as it was made, not as stock stands now. A customer service lead on a read-only key:
On a Shopify pull connection InfiPlex can move every pulled order's fulfillment order to one location in Shopify, so the store shows the order fulfilled from the InfiPlex-managed location; on a push connection it can move the resulting fulfillment order to a client-defined location. Those are connection settings the agent can read with shop_setting_search, described on the Shopify location router page.
Inventory
That gap has three usual causes: a per-channel buffer, an inventory send Shopify rejected, or a location mapping where InfiPlex is updating one Shopify location and the storefront is selling from another. The agent checks all three in one pass.
The re-create inventory webhook article covers the other common cause on push connections. For stores syncing to each other, the Shopify-to-Shopify inventory sync page explains why each store is its own connection and therefore its own log types and settings.
3PLs
A 3PL onboarding a new Shopify brand needs the store owner to authorize the connection. marketplace_connect_link_get issues that link from the agent, for the pull direction (orders out to the 3PL) or the push direction (orders in from the brand's other channels), and the link expires the same day. The account manager sends it; the owner authorizes without an InfiPlex login. From there the questions on this page work per client, because each store is its own order source. The AI agents for 3PL clients page covers per-client read-only keys and the first 3PL for Shopify sellers guide covers the brand's side.
Keys by role
The MCP server publishes a tool only when the key carries its scope, so the key is the whole permission model. Create each at Tools > Admin API on your instance with MCP Enabled, and send the URL and header from the set-up guide.
Read Orders, Read Inventory, Read Warehouse, Read Log, Read Settings. Both MCP flags No. Every routing, stock, and send question on this page works, including issuing a connect link; nothing can change.
Add Write Orders and Write Inventory. Tracking back to the store and stock corrections stop at a preview the person approves; notes and status write directly.
Same scopes as the warehouse key, used by an unattended agent from cron. The morning unshipped orders agent builds the day's ship queue per store; the failed sync watch agent reports every failed inventory and tracking send to Shopify each morning.
Prompts
The agent reads each store's stored channel name from your order data rather than guessing it, so "the UK store" in a prompt resolves to whatever your instance calls that connection. More prompts by role are on the prompts page.
Frequently asked
Not per order. InfiPlex moves fulfillment orders by connection rule, on push or on pull, and the agent can read those settings. Changing the rule is a setting write behind a preview on a key with Write Settings and MCP Allow Setting Writes.
The agent records the shipment in InfiPlex with order_tracking_create, and InfiPlex creates the Fulfillment in Shopify against the fulfillment order it owns, the same way a shipment recorded in the admin or by a connected shipping tool does. It is a previewed write on a key with Write Orders.
Not through InfiPlex. It reads the InfiPlex side of every exchange with the store: the pulled order, the routing record, the inventory and tracking sends and their results in the log. That is enough to say whether the store and InfiPlex agree and, when they do not, which send failed.
Yes. Each store is its own connection with its own order source, log types, and settings, so the agent can answer per store or across all of them. A 3PL with many client stores can hand each client a read-only key scoped to its own orders.
Everything that writes. Write tools are not published to a key without write scopes, so an agent on a read-only key has no tracking, inventory, note, or setting tool to call. It can read orders, routing records, inventory, warehouses, settings, and the log, which covers every question on this page.
No. The MCP server is included with API access on every InfiPlex plan. Keys are unlimited and MCP calls are not metered. Your AI vendor bills model usage.
Resources
We will connect an agent to a Shopify instance on a read-only key and read that order's routing record back to you, tool by tool.
Open Tools > Admin API, create a read-only key with MCP Enabled, and connect the assistant your team already uses. Questions: Contact us, email info@infiplex.com, or call 888‑770‑0857.
Order numbers, SKUs, quantities, times, location ids, and warehouse names are examples. Shopify is a trademark of Shopify Inc. 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