InfiPlex MCP tools reference: all tools, what they do, and what they need

order_search shop_order_read Read

Search orders by date, ship-by date, status, channel, customer, address, SKU, total, tag, picking state, invoice state, or fulfillment error. Returns full order records; use order_get for one known order. 61 filters, grouped below.

• ship_by_start_date / ship_by_end_dateoptional Ship-by date window: the required ship date on an Amazon Direct Fulfillment PO, the Expected Ship Date on a Walmart DSV PO, or any ship-by date the channel supplied. Format 2018-01-01 10:10:10 AM.
• estimated_ship_date_gteq / estimated_ship_date_lseqoptional Estimated ship date window.
• label_created_date_filter, label_created_start_date, label_created_end_dateoptional Set the filter to 1 and send both dates to select orders by the date a shipping label was created.
• date_created_greater_equal_than / date_created_less_equal_thanoptional Created-date window. Format 2018-01-01 10:10:10 AM.
• last_modified_start_date / last_modified_end_dateoptional Modified-date window; the start is exclusive.
• order_status_eq / order_status_neqoptional One of new, needs_review, in_process, pick_up_ready, pick_up_confirmed, closed, pending, canceled. eq keeps that status; neq drops it.
• order_source / order_source_eqoptional Channel exactly as stored, for example Amazon.com. Case does not matter; partial values match nothing. The two are the same filter.
• order_tag, coupon_codeoptional Filter on an order tag, or on the coupon code the order used.
• order_last_name_begins_with, order_email_likeoptional Customer last name prefix; partial match on customer email.
• search_term / text_searchoptional Partial match on InfiPlex order id, marketplace order number, or ship city. text_search also accepts additional info:field_name=value, for example additional info:netsuite_class_id=5. Neither searches SKUs or tracking numbers.
• product_sku / item_sku_eqoptional Orders containing this exact SKU. Partial SKUs match nothing.
• item_sku_neqoptional Orders with no line of this SKU; an order that has the SKU on any line is dropped whole.
• product_idoptional Orders containing this InfiPlex product id.
• order_city, order_state, order_zipoptional Matches the ship-to or the bill-to address.
• shipping_city, shipping_state, shipping_region, shipping_zip, shipping_countryoptional Exact match on the ship-to address.
• billing_city, billing_state, billing_region, billing_zip, billing_countryoptional Exact match on the bill-to address.
• fully_shippedoptional 1 for fully shipped only; 0 for not fully shipped, including partially shipped.
• is_canceled, is_seller_fulfilled_primeoptional Set to 1 to restrict.
• has_trackingoptional 1 for orders with at least one tracking number, 0 for orders with none.
• picking_statusoptional 0 not picking, 1 being picked, 2 fully picked.
• marketplace_fulfillment_erroroptional 1 for orders the channel rejected a fulfillment on (tracking, confirmation), 0 for orders without one.
• invoice_flagoptional 0 no invoice, 1 open invoice, 2 closed invoice, 10 open or closed, 30 open invoice with tracking.
• minimum_order_number / maximum_order_number, order_id_greateroptional Order id range, inclusive; order_id_greater is exclusive.
• order_min_total / order_max_totaloptional Order total range.
• filter_items_after_query_by_warehouse_identsoptional Comma separated warehouse identifiers, for example main,west. After the search, each order's lines are narrowed to those warehouses.
• include_order_notes, include_order_additional_info, include_pick_info_data, include_invoice_base_data, include_drop_shipper_dataoptional Set to 1 to add that block to each order; additional info makes results much larger.
• just_basic_order_data_resultsoptional Set to 1 for much smaller results: each order comes back without tracking_numbers, order_automation, order_used_warehouses, shipping_tags, pick_info, additional_info, invoice_base_data, drop_shipper_data, and order_packing_slip_url.
• just_countoptional Set to 1 to return only the count.
• sortoptional Sort expression, default shop_orderid DESC.
• limit / limit_startoptional Paging, maximum 100 per call.

• Use just_count for how-many questions instead of paging, and just_basic_order_data_results 1 whenever shipments and extras are not needed.
• Ship-by date is the deadline query: ship_by_end_date set to today with fully_shipped 0 is the Direct Fulfillment or DSV due-out list.
• The assistant is told to read order_source from earlier output rather than guess the stored value.

order_get shop_order_read Read

One complete order by InfiPlex order id: line items (with itemid), addresses, totals, shipment state.

• orderidrequired InfiPlex internal order id, not the marketplace order number.

• If only a marketplace number is known, the assistant finds the order with order_search first.
• Returns the itemid values that order_tracking_create needs.

order_warehouse_routing_explanation_get shop_order_read Read

The step-by-step record of how each line of an order was routed to a warehouse.

• orderidrequired InfiPlex internal order id.

• One entry per order line, in processing order; process_events lists each step, and every Valid Warehouse Found event carries the zip rule check, default warehouse, and inventory adjustment as child_events.
• quantity_to_process_at_warehouse is negative for units taken, 0 when none were.
• An Overflow Inventory Quantity Adjustment event means no warehouse could fill the full quantity and the shortfall went to the default warehouse.
• Written once when routing runs and never changed, so inventory figures are as of that moment. For current stock the assistant uses inventory_get.

order_note_create shop_order_write Write, no preview

Add an internal note to an order.

• orderidrequired InfiPlex internal order id.
• order_noterequired Note text.

• Notes are internal; nothing is sent to the customer or the marketplace.
• Readable back through order_get or order_search with include_order_notes.

order_additional_info_create shop_order_write Write, no preview

Set one additional info field on an existing order.

• orderidrequired InfiPlex internal order id.
• additional_info_namerequired Field name, for example warehouse_being_picked_from or netsuite_class_id.
• additional_info_valuerequired Field value.

• These fields are consumed by Order Automation and ERP push logic, including every netsuite_custom_field_* name.
• The name must exactly match one the account uses; an unknown name is stored but maps to nothing, so the assistant confirms the exact name rather than guessing.

order_tracking_create shop_order_write Write, preview + token

Record a shipment against an order and submit tracking to the sales channel.

• orderidrequired InfiPlex internal order id.
• tracking_numberrequired Carrier tracking number.
• carrier_namerequired Carrier as the customer wants it recorded, for example UPS, FedEx, USPS. Any value accepted.
• package_itemsrequired Every line in this package with quantity, keyed by itemid from order_get (not SKU). Required even when the package holds the whole order. Optional lot_number and serial_number per line.
• carrier_methodoptional Service level, for example Ground, 3rd Day.
• weight_oz, length_inches, width_inches, height_inchesoptional Package dimensions.
• save_items_as_qty_oneoptional Record each unit as its own line; needed for lot or serial tracked items.
• set_ship_from_info + ship_from_*optional Override the ship-from address, or ship_from_warehouse_id to name the warehouse.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Externally visible to the customer and the marketplace, so it sits behind the confirmation preview.
• One call is one package with one tracking number.

order_processed shop_order_write Write, no preview

Flag an order as handled internally, or clear the flag.

• orderidrequired InfiPlex internal order id.
• is_processedoptional 1 to mark processed (default), 0 to clear.

• Does not create a shipment, send tracking, or notify anyone. Shipping is order_tracking_create.

order_update_status shop_order_write Write, no preview

Set an order to a workflow status.

• orderidrequired InfiPlex internal order id.
• statusrequired One of new, needs_review, in_process, pick_up_ready, pick_up_confirmed, closed.

• General status tool. The assistant is directed to order_processed and order_cancel for those two transitions.

order_cancel shop_order_write Write, preview + token

Cancel an order, and send the cancellation to the marketplace where supported.

• orderidrequired InfiPlex internal order id.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Externally visible and generally irreversible, so it sits behind the confirmation preview and the assistant confirms the specific order first.
• Not for fixing a data mistake; that is order_update_status.

order_create shop_order_write Write, preview + token

Create an order manually: offline, phone, wholesale, or test.

• order_sourcerequired Channel to attribute the order to, for example Manual.
• order_itemsrequired Lines with sku, quantity, price, and optional product_name, item_total, tax_total, discount_total.
• ship_* / bill_*optional Full ship-to and bill-to address fields; ship_country is a two letter code.
• order_daterequired Order date. Never filled in by the server; an order created without one is stored dated 1970-01-01.
• email, phone, po_number, external_order_num, order_tagoptional Customer and reference fields.
• ship_label, ship_price, ship_total, tax_total, discount_total, item_total, order_totaloptional Totals as decimal strings; order_total must reconcile.
• additional_infooptional Key-value pairs consumed by automation and ERP push, for example netsuite_class_id.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Never used to re-enter an order that already exists on a channel; channel orders are ingested automatically.
• Payment card details are never collected or sent through this tool.

inventory_get shop_inventory_read Read

Current inventory for one SKU, total or per warehouse.

• skurequired Product SKU.
• warehouse_idoptional Omit for the total across all warehouses.

inventory_search shop_inventory_read Read

Search inventory across SKUs with warehouse, active-state, and modified-date filters.

• search_termoptional Free text match.
• warehouse_idoptional Restrict to one warehouse.
• is_activeoptional 1 active only, 0 inactive only.
• date_modified_greater_than / date_modified_less_thanoptional Modified window. Format 2018-01-01 10:10:10 AM.
• just_countoptional 1 for count only.
• limit / limit_startoptional Paging.

• Designed for catalog-scale accounts; the assistant pages rather than pulling everything.

inventory_change_history_get shop_inventory_read Read

Change history for one SKU, newest first, up to 100 entries.

• skurequired Product SKU.

• Each entry shows when, the resulting total, whether it was a delta (quantity_added, negative for a decrease) or an absolute set (quantity_set), and a note on the cause such as an order number or product creation.
• total_quantity on each entry is the total across all warehouses; timestamps are in the account time zone.
• This is how the assistant explains why a SKU has the quantity it has.

inventory_restock_list shop_inventory_read Read

Every parent product and child SKU at or below its reorder point, summed across warehouses.

• just_countoptional 1 to return only restock_skus_count.
• limit / limit_startoptional Paging, maximum 100; sorted by item_type then item_id so paging is stable.

• Rows carry item_type, sku, item_id, reorder_point, total_inventory (negative when oversold), restock_delivery_lead_time, restock_safety_stock_level.
• Uses the same weighted reorder point as the Restock Alerts email. Items with no warehouse inventory records are not returned.

inventory_set shop_inventory_write Write, preview + token

Change inventory for one SKU by absolute value or delta.

• skurequired Product SKU.
• quantity_to_setoptional Absolute quantity. Exactly one of this or quantity_to_add.
• quantity_to_addoptional Delta; negative subtracts.
• warehouse_idoptional Warehouse the quantity applies to. Omitted, it defaults to the first warehouse in the system, so the assistant names the warehouse on multi-warehouse accounts.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Propagates to every connected channel, so it sits behind the confirmation preview.
• For more than a few SKUs the assistant is directed to inventory_set_bulk.

inventory_set_bulk shop_inventory_write Write, preview + token

Change inventory for many SKUs in one call, mixing sets and deltas per row.

• itemsrequired Rows of sku, warehouse_id, and exactly one of quantity_to_set or quantity_to_add. No fixed batch limit. A row without warehouse_id applies to the first warehouse in the system.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• One preview covers every row.
• A row for a SKU the API cannot resolve returns null for that row rather than failing the call, so the assistant checks each row.

bin_location_set shop_inventory_write Write, no preview

Assign or update bin locations for SKUs within warehouses.

• bin_locationsrequired Rows of sku, warehouse_id, bin_location, for example bin09. The same SKU may appear for different warehouses. A row without warehouse_id applies to the first warehouse in the system.

• Affects pick paths and is required before fulfillment in bin enabled warehouses. Does not change quantity.

inventory_buffer_search shop_inventory_read Read

List Inventory Buffers: the units held back from every channel per SKU, and the marketplaces excluded from the buffer.

• search_termoptional Partial match against the SKU.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100.

• Rows carry shop_inventory_buffer_id, sku, buffer_amount, and excluded_mps, the marketplace codes that receive the actual quantity. With a buffer of 4 and 10 on hand every channel is told 6 and an excluded marketplace is told 10; null excluded_mps means the buffer applies everywhere.
• A connection set-to-zero threshold fires before the buffer. One buffer per SKU. This is how the assistant explains why a channel shows fewer units than inventory_get reports, or which channel sells the last units.

inventory_buffer_get shop_inventory_read Read

One Inventory Buffer by id: sku, buffer_amount, excluded_mps.

• buffer_idrequired shop_inventory_buffer_id from inventory_buffer_search.

• For a SKU rather than an id, inventory_buffer_search with the SKU as search_term returns the same fields.

inventory_transmission_search shop_inventory_read Read

The inventory transmission log: every quantity that successfully crossed between InfiPlex and a connection, per SKU, after buffers and thresholds.

• skuoptional Exact match; several as a comma separated list. Partial SKUs match nothing.
• source_name / destination_nameoptional The connection the quantity came from or went to, for example ShipHero or Amazon.com; InfiPlex for the InfiPlex side.
• connection_nameoptional Rows where this connection is either side.
• source_warehouse_ident / destination_warehouse_identoptional Warehouse ident on either side (main, secondary, or the connection location code), not the numeric id.
• shop_log_idoptional Every row written by one transmission run, from log_search.
• quantity_less_equal_thanoptional 0 finds every SKU a connection was told was out of stock.
• date_created_greater_equal_than / date_created_less_equal_thanoptional Datetime window, format 2026-10-01 12:00:00 AM.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100, newest first.

• A send to a sales channel is source InfiPlex, destination the channel; a pull from a 3PL or feed is the reverse. quantity is the value that actually went across, so this answers what Amazon was told for a SKU and when, with nothing to reconstruct.
• Only successful transmissions are here; failures are in the shop log, and every row carries the shop_log_id of its run. Edits made inside InfiPlex (uploads, inventory_set, order changes) are in inventory_change_history_get instead.

price_get shop_price_read Read

Current price for one SKU.

• skurequired Product SKU.

• Price is stored per SKU, not per channel.

price_search shop_price_read Read

List prices, optionally by modified date.

• date_modified_greater_than / date_modified_less_thanoptional Modified window.
• limit / limit_startoptional Paging.

• Built for pricing audits and finding recently changed prices.

price_set shop_price_write Write, preview + token

Set the price for one SKU.

• skurequired Product SKU.
• pricerequired New price, 0 or greater.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Propagates to connected channels and becomes visible to customers, so it sits behind the confirmation preview.
• The assistant reads the current value with price_get first.

products_create shop_products_write Write, preview + token

Create one or more new products in a batch.

• productsrequired Rows with sku and title required; optional price, upc, gtin, asin, isbn, barcode, image_url, ship_weight_oz, ship_length_inches, ship_width_inches, ship_height_inches. No fixed batch limit.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Only for SKUs that do not exist; the assistant checks pim_sku_get first because a duplicate SKU fragments inventory and pricing across channels.

pim_sku_get shop_pim_read Read

The full product information record for one SKU, including attributes.

• skurequired Product SKU.

pim_nightly_file shop_pim_read Read

Download a nightly PIM data file built automatically by InfiPlex.

• file_idrequired Nightly file identifier. Currently true_value.

• Returns bulk file content; used only when the whole export is wanted.

sku_data_fields shop_products_read Read

List the SKU Data names in use: reserved system names, reserved prefixes, and the custom names this account created with a SKU count each.

• No inputs.

• Call this before setting SKU Data so the exact reserved spelling is reused: home_depot_sku saves as a custom entry and Home Depot reads thehomedepot_sku. A custom name with sku_count 1 that resembles a reserved name is usually a misspelling.

sku_data_get shop_products_read Read

Every SKU Data entry on one SKU, one row per data name with its value and date modified.

• skurequired Product SKU.

• SKU Data is the per-SKU key and value store connections read: thehomedepot_sku, costco_sku, autozone_item_num, and the rest of the reserved names listed in the tool description, plus any custom name the account keeps (a legacy item ID, a supplier code).
• Values are returned exactly as stored, as strings, JSON included. An empty list means the SKU has no entries.

sku_data_search shop_products_read Read

SKU Data across SKUs and data names, pivoted: one row per SKU with one key per data name requested.

• sku_search_typerequired all, single, or multiple.
• skuoptional With single, one SKU; with multiple, a comma separated list.
• data_name_search_typerequired all, single, or multiple.
• data_nameoptional With single, one name; with multiple, a comma separated list, for example costco_sku,thehomedepot_sku.
• data_name_valueoptional Only with data_name_search_type single: return only SKUs whose value matches. The way to find which SKU a channel identifier belongs to.
• date_modified_afteroptional Only entries saved after this datetime.

• Two questions only this tool answers: what a channel identifier is for a set of SKUs, and which SKU a channel value belongs to (Home Depot sent 1004567890: sku_search_type all, data_name_search_type single, data_name thehomedepot_sku, data_name_value 1004567890).
• With sku_search_type all every SKU on the account is a row and the result is not paged, so narrow with data_name_value or a SKU list where possible. This is the tool a scheduled report joins on SKU to add a secondary ID or supplier code column.

sku_group_search shop_products_read Read

List SKU Inventory Groups: sets of SKUs that share one inventory level.

• search_termoptional Partial match against the group name.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100.

• Rows carry shop_product_inventory_group_id, group_name, and product_count. Any inventory change to one SKU in a group is applied to every SKU in it. Members come from sku_group_get.

sku_group_get shop_products_read Read

One SKU Inventory Group with its member SKUs.

• group_idrequired shop_product_inventory_group_id from sku_group_search.

• Each member row carries sku, the InfiPlex product id, and the child SKU id (null when the member is a parent product). Setting inventory on any one member through inventory_set sets all of them.

sku_map_search shop_products_read Read

List SKU Maps: named lists of SKU pairs that translate the SKU on an order into the SKU a fulfillment partner uses.

• search_termoptional Partial match against the map name; does not search the pairs.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100.

• Rows carry shop_sku_map_id, map_name, and total_skus_mapped. A 3PL, fulfillment service, or drop shipper connection chooses its map in its settings; maps do not change inventory. The pairs come from sku_map_get.

sku_map_get shop_products_read Read

One SKU Map with every pair: source_sku on the order, dest_sku the partner knows.

• sku_map_idrequired shop_sku_map_id from sku_map_search.

• Answers what SKU a partner will receive for an order line, or whether a SKU is missing from the map; a SKU with no source_sku entry is sent unchanged. Returned whole.

bundle_search shop_products_read Read

List Bundles: SKUs built from component SKUs, with thresholds and component list.

• search_termoptional Partial match against the bundle name or bundle SKU; does not match component SKUs.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100.

• A bundle SKU has its own inventory at one warehouse, created by consuming components there. When bundle stock reaches minimum_inventory_amt, InfiPlex builds auto_add_inventory_amt more; if components cannot cover the full amount nothing is built.
• Rows carry shop_bundle_sku_id, bundle_name, bundle_sku, the warehouse, the two thresholds, assoc_skus (component sku and quantity_in_bundle), and bundle_sku_warehouse_inventory. Bundle inventory moves through the Bundle tool, not inventory_set: setting a bundle SKU directly does not move component stock.

bundle_get shop_products_read Read

One Bundle by id, same fields as bundle_search.

• bundle_idrequired shop_bundle_sku_id from bundle_search, not the bundle SKU.

• To tell whether a build is possible, read each component with inventory_get at the bundle warehouse and compare to quantity_in_bundle times auto_add_inventory_amt.

unknown_sku_search shop_products_read Read

The Unknown SKUs InfiPlex recorded: SKUs that arrived from a channel in an order, price feed, or inventory feed and matched no product.

• search_termoptional Partial match against the SKU or the alert email address.
• is_emailedoptional 1 only alerted, 0 only not alerted, -1 either.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100.

• Rows carry sku, unknown_sku_source (same values as order_source), date_inserted, the alert email fields, created_product and created_product_id (whether InfiPlex auto-created a product under the oms_order_create_unknown_sku_enabled setting), and the title and price that came with it.
• A row with created_product 0 still has no product; fix it with products_create or a SKU map. Records are history and stay after a product exists. This answers why an order did not import cleanly or which channel is sending SKUs the account does not know.

warehouse_search shop_warehouse_read Read

List and filter warehouses; resolves a name to the warehouse_id other tools need.

• search_termoptional Free text match.
• just_countoptional 1 for count only.
• limit / limit_startoptional Paging.

warehouse_get shop_warehouse_read Read

Configuration for one warehouse: address and routing settings.

• warehouse_idrequired Warehouse id.

warehouse_create shop_warehouse_write Write, preview + token

Create a new warehouse.

• warehouse_namerequired Display name.
• warehouse_identifieroptional Short code, for example main.
• street1, street2, city, state, region, zip, countryoptional Address.
• use_zip_rulesoptional "0" or "1": whether zip based routing rules apply.
• fulfill_ordoptional ASC or DESC, sort direction used when ordering this warehouse for fulfillment.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• A structural change that affects routing on every channel, so it sits behind the confirmation preview and the assistant checks warehouse_search first to avoid duplicates.

warehouse_set shop_warehouse_write Write, preview + token

Update an existing warehouse.

• warehouse_idrequired Warehouse id.
• warehouse_name, warehouse_identifieroptional Naming.
• street1, street2, city, state, region, zip, countryoptional Address.
• use_zip_rulesoptional "0" or "1".
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Address and routing changes affect allocation on every channel, so it sits behind the confirmation preview; the assistant reads warehouse_get first.

shop_setting_search shop_setting_read Read

Find settings by name and return each with its current value and a description of what it controls.

• search_termrequired Text to match against setting names, for example amazon, tracking, inventory, restock.

• This is how setting names are discovered; shop_setting_get needs an exact name.
• Settings the API cannot view or set (mostly refresh tokens) are excluded by the settings API itself, so returned values are shown plainly.

shop_setting_get shop_setting_read Read

Read one setting by exact name.

• setting_namerequired Exact setting name.

• Credential settings return only whether a value is set, never the value, so this confirms a channel is configured without exposing keys or tokens.

shop_setting_set shop_setting_write Write, preview + token + opt-ins

Change one setting.

• setting_namerequired Setting name.
• setting_valuerequired New value, sent as a string.
• confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.

• Settings govern routing, inventory propagation, and channel behavior account wide, so it sits behind the confirmation preview and the assistant reads the current value first.
• Refused unless the key has MCP Allow Setting Writes in addition to the setting-write scope.
• Settings that start or stop live marketplace traffic (pulling orders, sending inventory or tracking) are additionally refused unless the key has MCP Allow Arming.
• Credential settings cannot be written here at all.

marketplace_connect_link_get shop_setting_read Read

Generate a one time authorization link that lets the marketplace account owner connect their account to this instance.

• setting_namerequired Which connection: eal__sp_api_connect (Amazon Selling Partner), eal__walmart_connect, eal__etsy_connect, eal__tiktok_connect, eal__shopify_connect_push, eal__shopify_connect_pull.

• Listed under the settings read scope because it only issues a link; it does not connect anything by itself. The account owner authorizes without needing an InfiPlex login.
• Expires the same day. Anyone holding it can attach an account, so it goes only to the person who owns the marketplace account.
• Shopify is split into push and pull; the assistant asks which direction if unclear.

fulfillment_connection_list shop_connection_read Read

Every fulfillment connection turned on for the account (3PLs, fulfillment services, drop shippers) with its settings.

• No inputs.

• Rows carry id (the connection key), name, type (fulfillment or drop_ship), enabled_setting, the linked warehouse ids, credentials_set as true or false per credential (values never returned), and every other setting under its own name. Setting names carry the connection prefix, so read the ending: _how_to_push_orders, _inventory_warehouse_id, _sku_map_id, _bundle_group_id, _inventory_offset.
• Use this first for any question about how orders reach a 3PL or drop shipper, which warehouse a partner serves, or why a SKU was translated or exploded on the way out.

fulfillment_connection_products shop_connection_read Read

The products a fulfillment connection has reported to InfiPlex: the partner side view of the catalog under the partner SKUs, one row per item per partner warehouse.

• fulfillment_idrequired The id from fulfillment_connection_list, for example wayfair_castlegate or logiwa_fbl.
• skuoptional Only rows for this exact SKU as the partner identifies it.
• ds_warehouse_idoptional Only rows from this partner warehouse code.
• limit / limit_startoptional Paging, maximum 100.

• Rows carry stock_level from the partner last report, last_update_time, the partner warehouse code and the InfiPlex warehouse it maps to. stock_level already includes the connection inventory offset; Inventory Buffers apply later. These rows are what inventory sync for that partner reads, so compare to inventory_get to explain a difference between what the partner reports and what InfiPlex stores.
• Seven older connections return rows with their own field names (three_pl_central, american_tire, flexe, infiplex_fbi, midwest, shipstream, zhenhub); each still carries a SKU, a stock figure, and a last checked date. An enabled connection with no inventory pull returns an empty list.

fulfillment_item_bundle_search shop_connection_read Read

List Item Bundle Groups: how a fulfillment partner should ship a bundle SKU as its components.

• search_termoptional Partial match against the group name; does not search the SKUs inside.
• just_countoptional 1 to return only a count.
• limit / limit_startoptional Paging, maximum 100.

• Each entry maps one source_sku, the bundle SKU on the order, to one or more dest_sku lines with a quantity each; when an order line matches, InfiPlex sends the partner the component lines, quantities multiplied by the amount ordered. Only fulfillment connections use these and they do not change inventory. Different from bundle_search (Bundles build real stock) and sku_map_search (one SKU swapped for one).

fulfillment_item_bundle_get shop_connection_read Read

One Item Bundle Group with every component line.

• item_bundle_idrequired shop_drop_shipper_item_bundle_group_id from fulfillment_item_bundle_search.

• Under bundle_skus: source_sku, dest_sku, dest_sku_qty per one bundle. Answers what a partner will receive for a bundle SKU, or whether a bundle SKU is missing from the group a connection uses.

log_types_get shop_log_read Read

List every shop log type on this instance, as an object mapping each log_type id to its label, for example 1026 Amazon Get Orders: Failed and 1027 Amazon Get Orders: Successful.

• No inputs.

• This is how the assistant finds the log_type id to pass to log_search. Most labels name the channel, the action, and whether it failed or succeeded.
• Each channel also has an Any Log type, for example 1999 Amazon: Any Log, that matches every log for that channel.

log_search shop_log_read Read

Search the shop log by log type, text, and date range.

• log_typeoptional Log type id from log_types_get, for example 1026 for Amazon Get Orders: Failed.
• search_termoptional Text to match in the log body (log_message), for example an InfiPlex order id such as 104404. Does not match log type labels; use log_type for that.
• start_date / end_dateoptional Written on or after / on or before. Format 2026-09-01 12:00:00 AM.
• sortoptional Sort expression, for example log_time DESC.
• just_countoptional 1 to return only the count.
• limit / limit_startoptional Paging, maximum 100.

• Each row carries log_time, log_type, log_type_message (the label), and log_message (the detail). log_message is returned decoded when it holds JSON, otherwise as text.
• Log messages can be large, so the assistant is told to narrow by log_type and date range and keep limit small.
• Typical use: find why orders did not import from a channel, why tracking or inventory did not reach a channel, or everything logged for one order, then pair with order_get or shop_setting_get to explain it.