InfiPlex Knowledge Base

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.

Costco runs two vendor programs that share almost nothing, including the network they trade on. Costco Wholesale ships bulk freight to depots over ANSI X12 EDI, with the 850, 856, and 810 reconciled in a strict three-way match and an advance ship notice that has to beat the truck to the dock. Costco.com is a different world entirely: drop-ship orders to individual members, traded through Rithum's OrderStream network rather than raw EDI. This guide walks through both programs side by side, the documents each one requires, where Costco's own item numbering and GS1-128 label rules trip up new vendors, and what it takes to get certified and connected without building the EDI mapping in-house.

What people consistently say they love about QuickBooks Online is that it's simple enough to manage without an accounting background. Adding a multichannel operation on top of it puts that simplicity at risk, hundreds of individual order transactions can turn clean books into a mess fast if the setup is wrong from day one. This walks through the actual InfiPlex-to-QBO setup, step by step, including the decisions that determine whether your books stay organized once real order volume hits.

QuickBooks Online is increasingly not a choice, it's where Intuit is pushing every QuickBooks user, and its API reflects that it was built as an accounting system first. This covers what's actually happening with QuickBooks Desktop's shrinking support window, the real constraints QBO's API puts on any integration built against it, and how InfiPlex connects to it.

Prophet 21 doesn't have one clean API that hands over everything a connected system needs, and that shapes almost every integration built for it. This guide covers why P21 integration is a different problem than a modern cloud ERP, what the existing P21 integrator landscape mostly looks like, and how InfiPlex connects to it instead.

Most NetSuite integrations sync once a day because of how they're built, not because NetSuite makes them slow. This guide covers NetSuite's real concurrency and rate limits, why batching became the default workaround, and how a connection built around real-time, event-driven sync looks instead.