How to set up and configure file-based order ingestion in WarpWare — SPS Commerce EDI, SFTP file drops, CSV/Excel uploads, and email inbox monitoring.

115,000+ retail trading partners — Target, Walmart, Costco, Home Depot, and more
Connects WarpWare to the SPS Commerce EDI network via OAuth 2.0. Inbound EDI 850 Purchase Orders are automatically parsed into WarpWare orders. When orders ship, WarpWare generates and sends EDI 856 Advance Ship Notices back through SPS to the retailer.
Monitor a remote directory for incoming order files
WarpWare polls an SFTP directory on a configurable interval. When new files appear, they're downloaded, parsed (CSV, Excel, or EDI), and ingested as orders. Processed files are moved to an archive directory to prevent re-ingestion.
Security: Always use SFTP (port 22) over FTP. All credentials are encrypted at rest using AES-256. SSH key authentication is recommended over password.
Auto-parse order attachments from a dedicated email inbox
Monitors an email inbox via IMAP. When emails arrive with order file attachments (CSV, Excel, PDF), WarpWare downloads, parses, and ingests them as orders automatically. Works with Gmail, Outlook, Yahoo, or any custom IMAP server.
Best practice: Create a dedicated email (e.g., [email protected]) for WarpWare to monitor. Use sender filters to avoid processing irrelevant emails.
Auto-detects one-row-per-item and one-row-per-order layouts. Column mapping via Walter Rosetta if non-standard.
Via: SFTP, Email, UploadSame auto-detection as CSV. Multi-sheet files use the first sheet by default.
Via: SFTP, Email, UploadParsed via SPS Commerce integration or direct file drop. ANSI X12 and EDIFACT supported.
Via: SPS Commerce, SFTPProcessed by Walter Rosetta AI — extracts order data from any PDF layout. Requires "Accept PDFs" enabled.
Via: Email (with Rosetta)Structured order data in JSON format. Must match WarpWare standard order schema or use Rosetta mapping.
Via: SFTP, Email, APITreated as CSV with auto-delimiter detection (comma, tab, pipe).
Via: SFTP, EmailNon-standard columns? Use Walter Rosetta to let AI auto-map your columns — no manual configuration needed.
Regardless of ingestion method, every order enters the same WarpWare pipeline. Your automation rules, routing, holds, and pre-order splits apply identically to EDI orders, CSV imports, email attachments, and API orders.
The test only checks TCP connectivity. Verify that the Watch Directory path is correct and contains files. Check that credentials have read access to the directory. Look at the error logs for authentication failures.
Verify the email is arriving in the monitored folder (default: INBOX). Check Sender Filter — if set, only matching senders are processed. For Gmail, ensure you're using an App Password (not your regular password) if 2FA is enabled.
Your column names may not match WarpWare's expected names. Use Walter Rosetta (Walter AI → Rosetta) to auto-map non-standard columns, or rename your columns to match: order_number, sku, qty, customer_name, address1, city, state, zip.
Check the order timeline for the specific error. Common causes: missing required segments (BEG, PO1), SKU not found in product catalog, or address validation failure. SPS Commerce compliance errors will show the specific segment that failed.
WarpWare deduplicates by external_id + source + client_id. If the same file is processed twice (e.g., not archived), duplicates are automatically rejected. Check that your Archive Directory is configured so processed files are moved.
PDF parsing requires "Accept PDF order attachments" to be enabled in the email connection's Advanced Settings. PDFs are processed by Walter Rosetta AI, which needs at least one successful mapping before it can auto-parse.
We can configure your SPS Commerce EDI, SFTP connection, or email monitoring for you.