Guide · Amazon Vendor Central on InfiPlex
Vendor Central runs on clocks Amazon measures automatically: 24 hours to acknowledge, a required ship date, 4 hours to confirm a Direct Fulfillment shipment, an ASN before a retail carton reaches the fulfillment center, and an invoice that has to match the acknowledged cost. InfiPlex already automates every one of those documents through its SP-API approved Vendor Central integration. What was still manual was the questions: which DF orders are due out today, did the invoice post, why did that PO route to Reno, what caused the chargeback line. With the InfiPlex MCP server, an AI agent on a scoped key answers those from your live instance, in your own words, and on a warehouse key records the shipment and closes the loop.
Why Vendor Central
InfiPlex pulls Vendor Central purchase orders about every 20 minutes, acknowledges them from live inventory, sends the ASN or ship confirmation from the ship scan, and submits the invoice after shipment. That is the part Amazon measures. The part your team still does by hand is looking things up: a buyer asks why a PO shipped short, finance asks what a chargeback line refers to, the warehouse asks which DF orders must leave before the carrier cutoff. Each of those is a login, three screens, and a message back. An agent on the MCP server does the lookup and hands back the answer with the order id, the timestamp, and the log entry, so the person who asked can act on it.
| What your team asks the agent | Tools it calls | What it hands back |
|---|---|---|
| "Which Direct Fulfillment orders have to ship today?" | order_search on the DF channel with ship_by_end_date set to today, fully_shipped 0 |
Order ids, ship-by date, ship-to state, line counts, and hours since the PO arrived |
| "Did every DF shipment from yesterday get confirmed to Amazon?" | order_search with marketplace_fulfillment_error 1 on the DF channel, then log_search on the ship confirmation types |
Orders whose confirmation to Amazon failed, with the error text from the log |
| "Why did PO 8P4Q7XZ ship from Reno instead of Columbus?" | order_search on the PO number, then order_warehouse_routing_explanation_get |
The zip rule check, the default warehouse, and the inventory each warehouse had when routing ran |
| "What is this chargeback line about?" | order_get, order_warehouse_routing_explanation_get, log_search on the order id |
PO date, ship confirmation time, tracking, and every log entry for that order, so the dispute writes itself |
| "Are we about to acknowledge a retail PO we cannot fill?" | inventory_restock_list, then inventory_get per SKU on the PO |
SKUs at or below reorder point with stock by warehouse, before the acknowledgment goes out |
| "Did the Amazon PO pull run overnight?" | log_types_get, log_search on the Amazon Get Orders types |
Last successful pull time and any failed pull with its message |
The Direct Fulfillment order lifecycle and the retail PO lifecycle explain each clock the agent is checking. Every tool above is documented on the tools reference.
Direct Fulfillment
In Direct Fulfillment each customer order is a PO with a required ship date and a ship method Amazon chose. InfiPlex acknowledges on pull and confirms from the ship scan, so the clocks are met automatically. The agent's job is the exception: the order that never got a scan, the confirmation that failed, the label that was never pulled. Here is a warehouse lead at 3 PM on a warehouse key.
The preview is the server's, not the agent's: it describes the exact arguments, binds a token to them, and expires it in ten minutes. That is what lets the same conversation run fully unattended from cron, as the autonomous fulfillment agent guide shows. The gates are described in how AI agent writes are protected.
The PO's required ship date is the order's ship-by date in InfiPlex, so ship_by_end_date set to today returns exactly what must leave. Ask again at the carrier cutoff with has_tracking 0 and it lists only what is still open. Nobody builds the report; the agent asks the instance.
InfiPlex flags an order whose confirmation the marketplace rejected, and order_search with marketplace_fulfillment_error 1 returns those directly. The shop log has the reason: log_search on the failed confirmation types gives the error text, before the four-hour window becomes a chargeback.
"Did we invoice PO 8P4Q7XZ?" is a log question. The agent searches the log for the order id and returns the invoice send entry with its time and status, or its failure message.
On a key with Write Orders the agent adds an internal note to the order ("carton damaged, repacked, shipped 14:10") without a preview, since notes never reach Amazon or the customer.
Vendor Central Retail
A retail PO is Amazon buying wholesale for its own fulfillment centers, with a ship window, a destination FC, and a unit cost that has to match from acknowledgment to invoice. The retail chargebacks that hurt most, NotFilled and Unconfirmed Units, come from acknowledging quantities the shelf did not have. An account manager on a read-only key gets ahead of that before the acknowledgment window closes.
The agent is reading the same inventory InfiPlex acknowledges from, so its recommendation and the automated acknowledgment agree. For the ASN side, "did the ASN for 6K2M9RTQ go out" is a log_search on the order id, and "what did it contain" is order_get, which returns the shipment record with tracking and line quantities.
| Retail chargeback category | What the agent checks before it happens | Tools |
|---|---|---|
| PO On-Time Accuracy: NotFilled | Stock by warehouse against every line before acknowledgment | order_get, inventory_get, inventory_restock_list |
| ASN missing or late | Shipped retail POs with no ASN send in the log | order_search fully_shipped 1, log_search on the ASN types |
| Unconfirmed PO units | Shipment quantities against the acknowledged lines on the order | order_get |
| Any date-stamped category | The full event trail for one PO, ready for the dispute | order_get, order_warehouse_routing_explanation_get, log_search |
Keys by role
The MCP server publishes a tool to an agent only when the key carries that tool's 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. Both MCP flags No. Every question on this page works; nothing can change. This is the key for anyone who talks to Amazon's buyer or disputes chargebacks.
Add Write Orders and Write Inventory. Tracking and inventory changes stop at a preview the person approves; notes and additional info fields write directly. This is the key for the pack station and the shift lead.
Same scopes as the warehouse key, used by an unattended agent that is instructed to complete the preview-and-confirm flow itself. The autonomous fulfillment agent guide is the recipe; point its shipments file at your DF carrier export and it records every confirmation before the four-hour window opens.
Credential settings return only whether a value is set, never the value, on every key. Every MCP call is an API request under the named key, so the API log shows exactly which agent asked and changed what.
Prompts
shop_setting_search, read scope)The agent reads the stored channel name from your order data rather than guessing it, so "Direct Fulfillment" in a prompt resolves to whatever your instance calls that channel. More prompts by role are on the prompts page.
Frequently asked
No, and it does not need to. InfiPlex acknowledges POs automatically on pull from live inventory, inside Amazon's 24-hour window, for both Direct Fulfillment and retail. The agent reads the result, checks stock before a retail acknowledgment, and surfaces any acknowledgment that failed in the log.
Yes. order_tracking_create records the shipment and InfiPlex submits the confirmation to Amazon through the integration, exactly as a shipment recorded in the admin would. It is a previewed write: the first call returns a plain-English preview and a token, the second call executes. On a warehouse key a person confirms; on a scheduled agent key the agent is instructed to confirm.
Not directly; chargebacks live in Vendor Central. What the agent gives you is your side of the record for any PO on the report: when it arrived, when it was acknowledged, when it shipped and was confirmed, what tracking went out, how it was routed, and every log entry for it. That is the evidence a dispute needs, assembled in one answer.
Orders carry the channel name your instance stores for each connection. The agent reads that value from earlier results and uses it exactly in order_search; it is instructed not to guess. If you run DF and retail as separate connections, each shows up as its own channel and the agent can filter to either.
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, inventory, warehouses, and the log, which covers every question on this page.
Yes. The agent works on InfiPlex orders, inventory, and log, which are the same whether the connection is SP-API or EDI. Document names in the log differ (855, 856, 810 versus acknowledgment, shipment confirmation, invoice), and log_types_get gives the agent whichever your instance uses. EDI vs SP-API for Vendor Central covers the difference.
Resources
We will connect an agent to a Vendor Central instance on a read-only key and assemble the dispute record for that PO, tool by tool, while you watch.
Open Tools > Admin API, create a read-only key with MCP Enabled, and connect the assistant your account team already uses. Questions: Contact us, email info@infiplex.com, or call 888‑770‑0857.
Order ids, PO numbers, SKUs, quantities, and warehouse names are examples. Amazon, Vendor Central, and Direct Fulfillment are trademarks of Amazon.com, Inc. or its affiliates. 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