RELAYSHIP vs FULFILLEO
Fulfilleo wants your supplier to be technical. Yours isn’t.
Fulfilleo pulls tracking data from email, REST API, or FTP — but only reads structuredformats (CSV, Excel, JSON, XML). If your supplier sends a plain-text email or a PDF shipping label, Fulfilleo can’t help.
Subject: Dispatch confirmation — Order #5829
Hi Leandro,
Your shipment has been dispatched today. Tracking: 1Z999AA10123456784 (UPS).
Items shipped: 2x BLUE-M, 1x RED-L.
ETA 5-7 business days.
Thanks,
ACME Wholesale
It’s a real dispatch email. There’s no CSV, no JSON, just a paragraph of English. Fulfilleo can’t parse it. Relayship’s extraction: { tracking: '1Z999AA10123456784', carrier: 'UPS', orderReference: '#5829', skus: ['BLUE-M', 'RED-L'] }. Matched to order #5829, fulfilled in 45 seconds.
That’s the whole difference. The rest of this page is details.
Fulfilleo pulls tracking from email, REST API, or FTP, but only reads structured formats (CSV, Excel, JSON, XML). If your supplier attaches a CSV, Fulfilleo reads the CSV. If there’s no attachment (or it’s a PDF label, or the tracking is in the body text), Fulfilleo is stuck.
Relayship reads whatever’s in the email. Plain text body, HTML tables, PDF shipping labels. Gemini’s multimodal model extracts tracking numbers from unstructured content. No attachment required.
| Feature | Fulfilleo | Relayship |
|---|---|---|
| Plain-text email body | No | Yes |
| HTML email body / tables | No | Yes |
| PDF shipping label | No | Yes |
| CSV / XLS attachment | Yes | Yes (if present) |
| JSON / XML attachment | Yes | Yes (if present) |
| REST API pull | Yes | Roadmap (Scale+) |
| FTP / SFTP pull | Yes | Not planned |
| Custom supplier prompt tuning | No | Yes (Growth+) |
| Per-supplier format learning | No | Yes |
| Confidence-gated human queue | No (runs the file as-is) | Yes |
Some suppliers skip the email text entirely and just attach a PDF label from UPS, FedEx, DHL, or YunExpress. Gemini reads the barcode region of those labels directly and extracts the tracking number. Fulfilleo doesn’t do OCR; it treats the PDF as an opaque blob.
If your 3PL pushes a structured fulfillment feed on a schedule and that feed hasn’t broken in months, Fulfilleo’s polling model works fine. It’s purpose-built for structured data.
Most merchants don’t have that feed.