For retail suppliers comparing an outside team for retailer setup and ongoing EDI work. Ask SPS which tasks it handles and which stay with your operations, IT or warehouse team.
What the provider offers
Cloud fulfillment platform with full-service EDI and system integration options
Scoped quote required
NetSuite, QuickBooks, SAP, Microsoft Dynamics, Shopify (confirm plan and path)
Official provider documentation checked; capabilities are vendor-documented. No hands-on testing, customer interviews, scoped quotes or independent service-quality assessment.
Features described by the provider
The following points describe the provider’s published offering. Confirm that the proposed product and contract cover your particular requirements.
- Retail-focused fulfillment workflows and trading-partner requirements are central to its offering.
- Published ERP coverage includes NetSuite, QuickBooks, SAP and Microsoft Dynamics.
- Vendor materials describe map changes, testing and ongoing EDI support as part of the full-service approach.
Pricing and scope
Request implementation, recurring fees, partner additions, volume charges and ERP integration as separate line items.
What to confirm before choosing
- No general-purpose US rate card was established from the reviewed product pages; obtain a scoped quote.
- Confirm exactly which exception-resolution, ERP and warehouse tasks SPS owns versus your internal team.
- Retailer-specific prices and older app announcements should not be treated as a current all-in price.
- Detailed NetSuite operating responsibilities were checked on a regional SPS page; confirm the applicable US contract and package.
What SPS Fulfillment covers
SPS positions Fulfillment around retail trading-partner connections and order management. Its public materials describe connections to an existing ERP rather than replacing that system. The reviewed NetSuite page also describes SPS taking responsibility for EDI map changes and partner testing. That page is regional; ask SPS to confirm the responsibilities in your US proposal.
What to establish before signing
Give SPS your retailer programs, ERP edition, warehouse setup and required document flows. Ask which failures its team will investigate and where your staff must act. A connection being listed does not establish that every custom field, packing process or warehouse handoff is included. Request a written breakdown of setup, ongoing service, new partners and integration costs.
Questions to ask the provider
Ask for answers against the same requirements brief you use with every provider.
- Which of our retail programs and document types are included?
- Who investigates an order that fails between EDI, ERP and warehouse?
- What changes the bill when we add a retailer or increase volume?
Prepare your requirements
Document your business systems and editions, named trading partners, required document flows, and the work you expect the provider to own. Ask what changes the price when volume or partner count grows.
Get the requirements checklist ↗Sources and scope
Official sources support their published descriptions. Availability, contract terms, and suitability for your specific workflow require confirmation.
- SPS Fulfillment product pageCurrent SPS Fulfillment retail workflow, ERP names, acknowledgments/ship notices/invoices and contact-sales route. No general US rate card observed.
- SPS NetSuite integrationRegional NetSuite product description: map/spec changes, testing, monitoring and dedicated NetSuite support. Confirm applicability to the US proposal; not US pricing.
- SPS Shopify EDI integration pathsDescribes multiple Shopify order-management paths, including EDI orders directly into Shopify Plus. Confirm the applicable plan and exact flow.