EDI · Onboarding connector
EazyPlano + SPS Commerce (EDI)
Suppliers selling to chains: send opening orders and resets through EDI, read retailers' POS data (852) where shared.
Data flows
What moves between the systems
How it connects
Technical approach
- SPS Commerce Fulfillment API or AS2 / SFTP
- Partner maps per retailer
The SPS Commerce connector is configured by our team for each customer during onboarding: we agree which fields and stores to read, set up authentication with the least access needed, map your categories and units, and schedule the sync. Until it is live, the same data can come in as files.
Questions
SPS Commerce and EazyPlano
Do we need to change anything in SPS Commerce?
No changes to your setup. We need an account or key with read access to the data listed above (and write access only if you want orders sent back).
How long does setup take?
The timeline is agreed during onboarding and depends on access and how custom your data is. Files can be used from day one meanwhile.
Is our data safe?
Data travels over HTTPS, is kept per workspace, and cost and margin are never shown in share links or exports for stores. See Security & data.
Related
See it on your shelves.
Send us a fixture list and a few months of sales. In the demo you’ll see planograms for your own stores — not a sample file.