Orgill as a Source
Summary
Orgill is a hardware and home-improvement distributor connected to Flxpoint via FTP (product and inventory feeds) and EDI (order transmission). Get Inventory (Primary) runs once daily and downloads Orgill's full catalog — WEB_INVENTORY.TXT, three-level categories from WEB_DEPT.TXT / WEB_DEPT_SKU.TXT, the online attribute and compliance Excel files, SKU restrictions, and per-warehouse Orgill-Standard-Data-File-DC-%s.xlsx files. Get Inventory (Secondary) runs more frequently and reads only WEB_INVENTORY.TXT to refresh per-warehouse quantities. Send Fulfillment Requests transmits orders to Orgill as an X12 850 EDI file using your Account Number and EDI Sender/Receiver trading-partner qualifiers and IDs. Supported warehouse locations span the US and Canada. Enable Archive/Un-Archive on one job only — GIP or GIS, not both — to avoid conflicting archive cycles.
Orgill uses one FTP connection, shared by Get Inventory (Primary) and Get Inventory (Secondary), plus separate EDI Trading Partner settings configured on Send Fulfillment Requests. Add an Orgill source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.
/orgillftp/webfiles/.ZZ.KTM.ORGILL.ZZ.DS-Dropship for dropship orders or NE-New Order for standard orders. Determines whether the TD5 shipping segment is included in the outbound 850 file./UP/ on the Orgill FTP server; inbound 856 ship-notice responses are typically read from /X12ASH856/. If FTP Test Connection fails with an SSL policy error on FTPS, enable Use Unbuffered Private Data Channel in Advanced Settings. For extended operation setup and field mapping beyond connection, contact support@flxpoint.com.GIP downloads multiple files — warehouse data comes from per-DC Excel files, not WEB_INVENTORY.TXT alone
GIP retrieves several files: WEB_INVENTORY.TXT (stock levels), WEB_DEPT.TXT + WEB_DEPT_SKU.TXT (three category levels), Orgill-Online-Attribute-File.xlsx (images, feature bullets, long descriptions), Orgill-Compliance-Info.xlsx (compliance custom fields), SKU_RESTRICTIONS.csv (shipping restrictions), and per-DC Orgill-Standard-Data-File-DC-%s.xlsx files for detailed per-warehouse quantities. Products appearing in multiple DC files are counted once from the first file.
Send FR requires Account Number, Sender/Receiver IDs, and Purchase Order Type — DS-Dropship for dropship orders
Send FR configuration requires: your Orgill Account Number (for authentication), Our Sender/Receiver Qualifier (e.g., ZZ), Our Sender/Receiver ID (e.g., KTM), Their Qualifier (e.g., ORGILL), and Their ID (e.g., ZZ). Set Purchase Order Type to DS-Dropship for dropship orders or NE-New Order for standard orders. Outbound folder is typically /UP/; inbound (for responses) is /X12ASH856/.
Do not enable Archive/Un-Archive on both GIP and GIS — use it on one only
Archive/Un-Archive manages products not in the Orgill feed by setting their quantity to zero. Flxpoint already enforces this limitation — the archive setting can be enabled on either GIP or GIS, but not both at the same time, even if you try to. It stays on one job only — typically GIP. GIS reads from WEB_INVENTORY.TXT and focuses on warehouse-specific quantity updates for the locations you select.
GIP supports up to 10 online feature bullets, images, and three category levels
The Orgill-Online-Attribute-File.xlsx provides rich product content: ONLINE-TITLE-DESCRIPTION, ONLINE-LONG-DESCRIPTION, APPLICATION, WARRANTY, feature bullets ONLINE-FEATURE-BULLET-1 through 10 (note: bullet 7 is skipped), and document names ITEM-DOCUMENT-NAME-1 through 3. Three category levels (Category 1, 2, 3) come from WEB_DEPT.TXT and WEB_DEPT_SKU.TXT.
Field mapping for this operation is configured with Flxpoint Support.
Field mapping for this operation is configured with Flxpoint Support.
| Source Field | Maps To (Orgill EDI) — Notes |
|---|---|
| Fulfillment Request Item → SKU | → PO1 line — SKU identifier (qualifier VN, Vendor's Item Number). Required, default active. The item mapper tries several EDI qualifiers in priority order (Buyer's Part/Catalog/Item Number, Purchaser's Item Code, Company Part Number, SKU, UPC, Vendor's Catalog/Item/Part Number) and sends the first one populated; only Vendor's Item Number (VN) is enabled in the default mapping template. |
| Fulfillment Request Item → Quantity | → PO102 Quantity. Required, default active. Units ordered, sent per PO1 line item. |
| Fulfillment Request Item → Cost | → PO104 Unit Price. Default active mapping; sent as the line's unit price. |
| Shipping address | → N1 Ship-To loop. Required. Populated from the order's shipping address; your Orgill Account Number is sent as the buyer identifier (N104). |
| Source Shipping Method | → TD5 segment (Carrier + Method). Required for the DS-Dropship Purchase Order Type. Only 3D, ND, and SE method codes are accepted — Flxpoint blocks the send with an error if the source shipping method isn't one of these. |
/orgillftp/webfiles/); (3) if using FTPS and seeing SSL errors, enable Use Unbuffered Private Data Channel in Advanced Settings; (4) confirm Orgill has placed the expected files in the configured directory — some files may have a delay after catalog updates./UP/) and the folder is accessible; (2) verify your Account Number is entered in the integration settings; (3) check Sender/Receiver Qualifier and ID values match what Orgill expects for your account — these are EDI trading partner identifiers and must be exact; (4) confirm Purchase Order Type is set to DS-Dropship for dropship orders. Contact Orgill EDI support if the file is transmitted but rejected on their side.What warehouse locations does Orgill support and how are per-warehouse quantities configured?▸
Orgill-Standard-Data-File-DC-%s.xlsx).What does GIS retrieve from Orgill, and how does it differ from GIP?▸
WEB_INVENTORY.TXT only and provides: SKU, warehouse-specific Quantity fields for all supported locations, and Selected Warehouse Quantity (total from chosen warehouses). GIS is designed for frequent quantity refreshes without re-importing the full catalog. GIP retrieves all product data including titles, descriptions, categories, images, compliance info, feature bullets, and dimensions, in addition to pricing and quantity. Run GIP daily and GIS more frequently to keep stock current.