Integrating to FLX EDI
Summary
A quick orientation to Flxpoint EDI (X12 EDI over SFTP) (supported transactions, SFTP basics, and getting started) that bridges to the dedicated EDI Help Center for the full, always-current spec.
Flxpoint (“FLX”) EDI lets suppliers exchange inventory, orders, shipments, invoices, and catalog data with their retail partners using X12 EDI over SFTP. This page is a quick orientation: the full, always-current specification (every transaction set, validation rules, example files, and parser specifics) lives in the dedicated EDI Help Center.
📚 Flxpoint EDI Help Center: the source of truth
Field-level specs, the Flxpector validator reference, example files, and error catalog are maintained there and kept up to date. Always link clients to it rather than copying specs, so nobody works from a stale version.
Open the EDI Help Center ↗| Code | Transaction | Direction | Purpose |
|---|---|---|---|
| 846 | Inventory Advice | Supplier → FLX | Inform the retailer of inventory availability |
| 850 | Purchase Order | FLX → Supplier | Transmit new orders to the supplier |
| 855 | PO Acknowledgement | Supplier → FLX | Acknowledge receipt and accept/reject each line |
| 856 | Advance Ship Notice (ASN) | Supplier → FLX | Tracking info for shipped orders |
| 810 | Invoice | Supplier → FLX | Cost info for the retailer to pay the supplier |
| 832 | Price/Sales Catalog | Supplier → FLX | Vendor price & catalog import (via GIP) |
| 997 | Functional Acknowledgement | Both directions | Confirm a transaction was received |
Click any code above for its full field-level spec in the EDI Help Center.
| Item | Detail |
|---|---|
| Standard version | 004010VICS preferred. The parser also accepts 004010 (no VICS) and 005010 with a warning: standardize on 004010VICS for the cleanest match. |
| Protocol | SFTP only: AS2 is not supported. Every FLX account includes a dedicated SFTP account. |
| Directories | Supplier drops files in /in; FLX places files (850s, 997s) in /out. Don’t delete from /out: archive instead. |
| Delimiters (default) | Segment ~ · Element * · Sub-element > (configurable per job) |
| Interchange ID | Qualifier ZZ, default Receiver ID FLXPOINT unless agreed otherwise at setup |
| 997s | Required for each transaction FLX sends; FLX generates one for each it receives. A 997 confirms receipt, not that content is correct. |
| Step | Action |
|---|---|
| 1 | Confirm your SFTP account with Flxpoint (every account includes one) and the /in & /out directory structure. |
| 2 | Standardize your files on 004010VICS and the default delimiters. |
| 3 | Start sending 846 Inventory (hourly recommended); FLX sends you 850 Purchase Orders. |
| 4 | Return 855 (acknowledge), 856 (ship/tracking), and 810 (invoice for shipped items): always echoing the PO Number and UPC from the 850. |
| 5 | For exact field requirements and validation, follow the matching page in the EDI Help Center. |
- PO Number and UPC sent on the 850 must be returned on the 856 and 810.
- Invoice (810) data is accepted only for shipped items.
- UPC/EAN/SKU at the variant level must be unique for accurate inventory and order tracking.
- Product catalog data (descriptions, images) comes via flat file (CSV/Excel), not EDI.
Why is the detailed EDI spec on a separate site?
Which protocol does Flxpoint EDI use?
Which X12 version should I use?
Is EDI how product descriptions and images are sent?
What it does
Standard EDI V2 integrations support advanced file actions that allow you to manage files on a remote server (such as SFTP) as part of your automated workflow. Instead of simply downloading a file, you can now define how Flxpoint interacts with the file after processing, which is particularly useful for vendor workflows involving Centric and similar platforms.
Supported file actions
When configuring your EDI source integration, you can select from the following operations:
Read: Downloads and processes the file content without modifying the original file on the server.
Move: Relocates the file to a specified directory (such as an /archive folder) after a successful sync to prevent re-processing.
Append: Adds new data to the end of an existing file. This is often used for logging or accumulating batch data.
Delete: Removes the file from the source server immediately after Flxpoint has successfully read the data.
Configuration
These actions are configured within the Get Inventory or Get Orders integration settings for any source using the Standard EDI V2 connector.
Navigate to the Sources menu and select your EDI source.
Open the Integrations tab and select the relevant job (e.g., Get Inventory).
In the File Action dropdown, select the desired operation.
If selecting Move or Append, provide the target file path or directory in the configuration inputs provided.
Save the integration settings.
Note: Ensure your EDI credentials have the necessary permissions (Write/Delete) on your vendor's server to perform Move, Append, or Delete actions.