InfiPlex Knowledge Base

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.

Walmart runs two very different supplier relationships under the word "integration," and mixing them up is the fastest way to build the wrong connection. This guide covers Walmart Marketplace and Walmart DSV side by side: how to tell which one you're in, the EDI documents DSV requires, and where Walmart Fulfillment Services actually fits.

Target runs two separate EDI vendor programs, and mixing up their rules is where most new vendors get hurt. This guide covers the 850, 855, 856, and 810 for both Target Stores and Target DVS: what goes in each document, where the two programs diverge on labeling and invoicing, and why the 856 causes the most chargebacks.