InfiPlex Knowledge Base

A scheduled AI agent that builds the day's ship queue from InfiPlex before the first shift: every open order not fully shipped, grouped by channel and sorted oldest first, with hours since it arrived, the warehouse each line routed to, and a LATE or DUE flag against that channel's handling window (Amazon Direct Fulfillment, Walmart DSV Expected Ship Date, Temu handling time, Seller Fulfilled Prime). For flagged orders it reads the warehouse routing explanation to show whether stock was short at routing. On a key with Write Orders it sets flagged orders to needs review with a note. Built on the InfiPlex MCP server with a Read Orders and Read Warehouse key, Claude Code in headless mode, and cron. Includes the window table with the rule each comes from, key settings, full instruction file, run script, sample queue, and checklist.

A scheduled AI agent for the InfiPlex shop log. Every morning it calls log_types_get, keeps every Failed type, searches each for the last 24 hours, groups failures by channel and cause, attaches the current state of every affected order, and checks the channel's success type after the last failure to mark each group ongoing or recovered. On a key with Write Orders it also adds an internal note to affected orders. Built on the InfiPlex MCP server with a Read Log and Read Orders key, Claude Code in headless mode, and one cron line. Includes how log types work, both key versions, the full instruction file, run script, schedule, a sample report showing Walmart DSV and Temu tracking sends that never reached the channel, and the checklist. It reports; repairs such as re-recording tracking stay previewed writes on a warehouse key.

A scheduled AI agent that reads InfiPlex every night on a read-only key and leaves a reorder sheet for the buyer: every SKU at or below its reorder point, units sold over the last seven days from the change history, stock in each warehouse, days of cover, and a suggested order quantity built from lead time, safety stock, and your order cycle. Uses the InfiPlex MCP server and four read tools (inventory_restock_list, inventory_change_history_get, inventory_get, warehouse_search), so nothing can change and there is no confirmation flow. Includes the key settings, the full instruction file, the Claude Code run script and cron line, a sample CSV and summary, and how to tune the suggested quantity. The same reorder point drives the Restock Alerts email; this adds how low, how fast, and where. Included with API access on every InfiPlex plan.

This guide sets up an AI agent that runs InfiPlex fulfillment on a schedule with no person in the loop. Every morning it applies the warehouse's receiving file in one batch, records the carrier's tracking export against the right orders so tracking reaches each marketplace, lists anything that fell to its reorder point, scans every channel's failed log type for the last 24 hours, and writes a plain-text report your team reads at 8 AM. It runs on the InfiPlex MCP server with a dedicated fulfillment API key whose scopes bound everything the agent can do, a standing instruction file that authorizes the agent to complete the server's preview-and-confirm flow itself, and Claude Code in headless mode launched from cron with tool, turn, and spend caps. The guide includes the exact key configuration, the full instruction file, the MCP config and run script, a read-only dry-run method, a sample morning report, the kill switch, and how to widen the agent's job one scope at a time.

The InfiPlex MCP server lets you connect Claude, ChatGPT through Codex, Cursor, or any MCP-compatible AI agent directly to your own InfiPlex instance, so your team can search orders, explain warehouse routing, check inventory, read the shop log, record tracking, and set prices in plain English. This guide covers the whole set-up in the order you will do it: opening or creating an API key, choosing which read and write scopes the agent should have, enabling MCP and understanding the two MCP flags that gate setting changes and live marketplace traffic, and then connecting each client with the two values shown on the key page. Separate walkthroughs cover Claude on claude.ai and Claude Desktop, Claude Code, ChatGPT via Codex, and generic MCP clients such as Cursor and Windsurf. It closes with five first questions that confirm the connection and the preview gate, a troubleshooting list keyed to the server's exact messages, and a set-up checklist.

InfiPlex geo routing fills every order from the warehouse or 3PL facility closest to the customer, on every sales channel, with the decision logged on the order. It runs on two settings: the site-wide Zip Code Distance fulfillment method and a list of zip code rules on each warehouse. This guide gives the full zip rule syntax (prefix plus trailing wildcard, why 60540 misses 60540-1234 and 60540* catches both), the step-by-step decision InfiPlex makes for each SKU, a US coverage map built from the ten first-digit zip regions with ready-to-paste two, three, and four-warehouse layouts, and how the same routing directs orders into individual facilities inside Extensiv 3PL Warehouse Manager, Logiwa, and any other WMS connected through the 3PL Connector. It also covers what geo routing does not override, why nearest-warehouse fulfillment lowers carrier zones and shipping cost, and a six-step set-up checklist.

BigCommerce's Channel Manager lets one account serve the primary storefront, any additional storefronts, and marketplace channels like Amazon, each with its own channel_id, and this guide documents the rule InfiPlex uses to tag every pushed order with the right one. The rule is a small JSON array on the BigCommerce connection: each entry names an order_source, either a specific marketplace or the catch-all ALL_ORDER_SOURCES, and pairs it with the action_type set_bc_channel_id and the target channel_id. A rule naming a specific source overrides the ALL_ORDER_SOURCES default for that source only, so a seller can send every order to their primary storefront channel by default while routing Amazon, eBay, or any other marketplace to its own channel with one added rule. The same order_source-scoped shape, pairing an action_type with a value, is the pattern behind InfiPlex's push rules on other connections as well, including NetSuite's custom field and order rule set.

What lands on a NetSuite sales order from InfiPlex, and what comes back, is controlled by three self-service layers, and this guide documents all of them with working syntax. First, the additional info keys the NetSuite push reads: terms, customer, class, department, location, ship method, order status, memo, discount, account, and the netsuite_custom_field_* pattern that sets any custbody field by its script ID. Second, the nine Set Order Data transforms in Order Automation that populate those keys from other order data, from FIELD_COPY and CUSTOM_VALUE to BULK_SHIPPING_MAP and DYNAMIC_DATA_MAP. Third, the push and pull rules on the connection: push rules that write custcol values from four data sources, substitute SKUs or prices for FBA lines only, and skip items; pull rules that filter NetSuite orders on a custom field value and stamp fields in either system after the pull. Includes complete JSON examples and the matching keys for QuickBooks Desktop and Dynamics 365.

Three InfiPlex tools get called bundles. SKU groups share one count, bundles are true builds from component stock, SKU maps translate SKUs per 3PL or ERP.

How InfiPlex captures gift messages and checkout notes from Shopify, Faire, Maisonette, and other channels, in the API and Order Additional Info.