EDI Help Center Overview

Flxpoint EDI Overview & General Guidelines

What is Flxpoint EDI?

Flxpoint ("FLX") solves one-to-many integration relationships for retailers and suppliers in drop shipping operations. The platform handles Inventory management, Order management, consolidation, and automation.

This EDI specification is for suppliers connecting via EDI to Flxpoint for their Retail Partners.

Standard Version

004010VICS is the preferred version for inbound files.

Flxpoint's parser also accepts 004010 (no VICS) and 005010 (Faiyaz 2026-04-16):

Files without the VICS suffix are processed with a warning, not a hard rejection.
The authoritative source for parser acceptance is Flxpoint Parser Rules.
Partners should still standardize on 004010VICS — it is the cleanest match for the VICS-specific segments Flxpoint expects.

Supported Transactions

Code	Name	Direction	GS-01 Code	Purpose
846	Inventory Advice	Supplier → FLX	IB	Inform retailer of inventory availability
850	Purchase Order	FLX → Supplier	PO	Transmit new orders to supplier
855	PO Acknowledgement	Supplier → FLX	AD	Acknowledge receipt and accept/reject each line
856	Advance Ship Notice (ASN)	Supplier → FLX	SH	Tracking info for shipped orders
810	Invoice	Supplier → FLX	IN	Cost info for retailer to pay supplier
832	Price/Sales Catalog	Supplier → FLX	PI	Vendor price and catalog updates
997	Functional Acknowledgement	Both directions	FA	Confirm transaction receipt

Transaction Flow

code

Retailer → FLX → [850 Purchase Order] → Supplier
Supplier → [846 Inventory] → FLX → Retailer
Supplier → [856 ASN/Ship Confirm] → FLX → Retailer
Supplier → [810 Invoice] → FLX → Retailer
Each direction: 997 acknowledgement returned

Data Communications

Protocol: SFTP only. AS2 is NOT supported.
Every FLX account includes a dedicated FTP/SFTP account.

SFTP Directory Structure

Directory	Purpose
`/in`	Supplier places files TO Flxpoint here
`/out`	Flxpoint places files FOR supplier here
`/out/archive`	Recommended: supplier moves processed `/out` files here

SFTP Rules

Supplier → FLX files go in /in directory
FLX processes inbound file, places 997 on /out
FLX outbound files (850s, 997s) deposited in /out
Supplier should place 997 acknowledgements in /in
Do NOT delete files from /out — archive them instead
FLX does NOT archive or modify files in /out

Interchange ID

Default Qualifier: "ZZ" (Mutually Defined)
Default Receiver ID: "FLXPOINT" (if no specific ID agreed at setup)
Can use customer's name instead of FLXPOINT

Delimiters (Default)

Delimiter	Character	Decimal	Hex
Segment Terminator	`~`	126	7E
Element Separator	`*`	42	2A
Sub-element Separator	`>`	62	3E

Configurable per job, but these are the defaults.

ISA Control Numbers

Inbound: FLX does NOT require unique ISA Control Numbers (but best practice to use them)
Outbound: FLX provides sequential ISA Control Numbers

997 Acknowledgements

FLX requires a 997 for each transaction sent to the supplier
FLX generates a 997 for each transaction received
997s are deposited in /out directory
FLX does NOT support routing 997s to external destinations
A 997 confirms the transaction was received, NOT that the content is correct

Timing / Frequency

Transaction	Recommended	Minimum	Notes
846 Inventory	Hourly	Daily	Critical for accurate stock levels
850 Purchase Order	Hourly	Daily	Can arrive at any time of day
856 Ship Notice	Hourly	Daily	At least daily
810 Invoice	Within 24hrs of shipment	Daily	Only for shipped items

Data Integrity Rules

PO Number and UPC sent on the 850 MUST be returned on 856 and 810
Invoice data accepted only for shipped items
UPC/EAN/SKU codes at variant level must be unique for accurate inventory/order tracking
Product catalog info (descriptions, images) must come via flat file (CSV/TAB/Excel), NOT EDI
Images provided via HTTPS link in catalog or in shared folder named by SKU/UPC

Contact

EDI Support: connect@flxpoint.com

Something unclear?

Ask our AI assistant — it knows this spec and can explain any segment, error, or rule in plain English.