InfiPlex Knowledge Base

Selling on a Marketplace InfiPlex Does Not Connect To Yet: Inventory Out, Orders In, Tracking Back

Last Updated: Oct 9, 2026

A marketplace InfiPlex does not connect to yet still runs on InfiPlex inventory and ships from the InfiPlex order list; the difference is that three hand-offs happen by file instead of by API. Inventory goes out to the marketplace, its orders come in, and tracking goes back. Each hand-off has a manual version in the OMS and a scheduled version on the MCP server or the REST API, and all three go away the day the connection is built, which every Growth Package includes at no additional cost for API-based marketplaces. This guide covers the three loops and the path to the real integration.

Jump to What You Need

If You Want To…	Go To
Push stock to the marketplace	Inventory Out
Bring its orders into InfiPlex	Orders In
Send tracking back	Tracking Back
Replace the files with a connection	Getting It Connected

Inventory Out

InfiPlex holds the inventory for every warehouse; the unconnected marketplace just does not receive the automatic push. Two ways to carry the numbers across:

Manual, from the OMS. Run the Price & Inventory Download on Tools > Price & Inventory Tools for the warehouse that ships that channel, keep the sku and inventory columns, map them into the marketplace's own inventory upload template, and upload it in its seller portal. Details in Managing Inventory.
Scheduled, by agent or script. A read-only agent on the MCP server, or a cron job on Inventory Search, pulls the warehouse's rows every evening, keeps the SKUs on that marketplace, applies a hold-back, writes the marketplace's template, and uploads it or emails it to whoever does. The daily inventory by warehouse agent is the starting point; the instruction file below is the marketplace-shaped variant.

# Nightly stock file for NewMarket on InfiPlex

You run unattended and read-only.
1. Call warehouse_search once and find the warehouse_id for "Reno".
2. Page through inventory_search with warehouse_id set to Reno and limit 100 until every row is read.
3. Read newmarket-skus.csv in this folder (columns: sku, newmarket_sku). Keep only SKUs on that list.
4. Write newmarket-inventory-YYYY-MM-DD.csv with header: newmarket_sku,quantity. Quantity is the Reno quantity minus 2, never below 0.
5. Write a one-line summary with the row count and any SKU on the list that had no inventory row.

The hold-back in step 4 is the manual stand-in for an Inventory Buffer: it keeps the last units off a channel that only learns about sales once a day. If the marketplace uses its own item IDs, keep them as SKU Data instead of a side file and have the agent read them with sku_data_search.

Orders In

Orders from the unconnected marketplace have to reach the InfiPlex order list so they ship from the same queue, route to the same warehouses, and draw down the same stock. Three ways in, by volume:

A few orders a day: Manual Order Import. Orders > Import/Export takes a .csv with one row per order and up to 50 line items; name the marketplace in the order_source column and the orders land on the Order List under that source. Export the orders from the marketplace's seller portal, reshape the columns to the import file once in a spreadsheet, and reuse the mapping.
A recurring file: SFTP order files. Drop the same order file on InfiPlex's SFTP and it is picked up on a schedule.
From a system: Order Create. If the marketplace exposes its orders to you by API or feed, a short script creates them in InfiPlex as they appear, with the marketplace as the source.

However they arrive, imported orders ship, route, and sync inventory like any other order: the moment one is saved, the stock it consumed is subtracted and every connected channel gets the new level on its normal schedule. That is what keeps an unconnected marketplace from causing oversells elsewhere.

Tracking Back

Once the orders ship from InfiPlex, the marketplace needs the tracking numbers. Two sources:

Manual: the Shipping Item Report. Run it for the date range, scope it with a saved Order Filter on the marketplace's order source, and you have every shipped item with carrier, ship method, and tracking number, ready to reshape into the marketplace's shipment confirmation upload. The Packages export gives the same data at package level.
Scheduled: order_search plus order_get. A read-only agent or script pulls yesterday's shipped orders for that source and writes the marketplace's tracking file from each order's packages. Same key, same folder, same cron as the inventory file; the morning unshipped orders agent shows the order-side pattern.

Getting It Connected

The three loops above are the bridge, not the destination. Check the Integrations directory first; a marketplace is often connected before sellers expect it. If it is not there:

The marketplace has an API. Every Growth Package includes InfiPlex building the connection at no additional cost. Tell us what you need through Contact and it goes into the programming queue; the orders, inventory, and tracking loops become automatic and the files retire.
The marketplace or retailer is EDI only. InfiPlex Bridge serves EDI retailers without you running EDI; the retailer pages under Integrations list the ones already live.
The marketplace is file only. The scheduled agents above are the long-term answer, and the FTP Package Report and SFTP order files can carry two of the three loops with nothing custom.

Compare the per-connection fees and tier limits of other platforms on Cost of One Connection; on InfiPlex the new marketplace is a build request, not a line item.

Unconnected Marketplace Checklist

Check the Integrations directory and ask for the build if the marketplace has an API.
Keep the marketplace's SKU list, and its item IDs if it has them, as SKU Data.
Set up the nightly inventory file: download by hand to start, then the agent.
Map the marketplace's order export to the Manual Order Import file once and keep the mapping.
Run the Shipping Item Report on that order source after each ship day and upload the tracking.

Unconnected Marketplace Questions

Does InfiPlex still track inventory for a channel it does not connect to?
Yes. InfiPlex holds the inventory for every warehouse regardless of which channels are connected. What the unconnected channel lacks is the automatic push, so you carry the numbers to it by file or agent, and carry its orders back in.

Can I filter the inventory file to only the SKUs I sell on that marketplace?
By hand, the Price & Inventory Download's Sell On filter lists connected channels, so for an unconnected one keep a SKU list and filter the download in a spreadsheet. The agent version reads that list file first and writes only those rows.

Do imported orders affect my other channels?
Yes. An imported order draws down stock like any other order, and the new level goes to every connected channel on its normal sync schedule, so a sale on the unconnected marketplace lowers your Amazon and Shopify counts the same day.

How often should I push inventory to the unconnected marketplace?
As often as that channel's own upload allows and your sales rate needs. Nightly is common; busy channels get a midday run too. Holding back a few units per SKU in the file covers sales between pushes.

How do I get the marketplace connected properly?
Check the Integrations list first. If it is not there and the marketplace has an API, every Growth Package includes InfiPlex building the connection at no additional cost; tell us what you need and it goes into the programming queue. EDI-only retailers go through InfiPlex Bridge.

Can an AI assistant do the whole loop?
The inventory file and the tracking file, yes, as scheduled read-only agents. Order entry from the marketplace's export is the Manual Order Import or the Order Create API; an assistant can prepare the import file from the marketplace's export format.

THE OMS THAT NEVER SAYS WE DON'T SUPPORT THAT

The next marketplace is a build request, not a bill.

Every Growth Package includes InfiPlex building the API connections you need at no additional cost. Until it is live, the files above keep the channel in step with the rest of your inventory.

See InfiPlex Pricing Browse Integrations