CONTAX Logo

Arcus vs. SPS Commerce: Which EDI Model Fits Your SAP Team?

November 11, 2026  |  by Jodi Abrams

Picture it: your S/4HANA project is underway, the old EDI translator is on the retirement list, and someone has written two names on the whiteboard. One is SPS Commerce, one of the biggest names in retail EDI. The other is Arcus, the managed EDI service our team runs at CONTAX.

On paper they sound alike. Both are cloud-based, both connect to SAP through SAP BTP, and both promise to take EDI off your team's plate.

They are not the same model. And you want to know that before you sign, not after go-live.

Two Different Models

SPS Commerce is a network. Each retailer's requirements are mapped and maintained once, at the network level, so every customer connected to that partner benefits. SPS calls this full-service EDI, with its own team handling partner testing, map changes, and support, and says more than 2,000 SAP customers use it.

Arcus is a managed service built by an SAP consultancy. Maps are built for your partners and your SAP configuration, and the people who build them are SAP specialists who also monitor them every day.

How SPS and Arcus Compare, Point by Point

Here is how the two stack up on the things that tend to decide an SAP project. The SPS details come from its public website. Where the site is silent, I've said so and suggested what to ask.

Partner connections

  • SPS: Partner requirements are mapped and maintained once, at the network level, across a network SPS describes as 500,000+ connections. If your partner is already on the network, that work is already done.
  • Arcus: Maps are built to each partner's spec for your account, and a library of maps from partners already onboarded for other clients speeds things up. We target about 1.5 to 2 weeks per partner, depending on how quickly the partner responds.

Connecting to SAP

  • SPS: A connector for S/4HANA Private and Public Cloud that runs through SAP BTP and is listed on the SAP Store. SPS also lists support for Business One and ByDesign.
  • Arcus: Connects through SAP Cloud Connector, an encrypted tunnel with no open inbound firewall ports. Documents post to SAP as IDocs, and status IDocs come back so SAP shows where each document stands.

Your SAP setup

  • SPS: Handles partner requirements at the network level, and says the solution is then tailored to your business rules and workflows inside SAP. Its site doesn't say who matches those rules to your SAP configuration, so ask. Someone with SAP knowledge has to, and it may be your team.
  • Arcus: We understand SAP and have access to your system, so we can answer most of these questions ourselves, directly in the system. When a store number on an 850 has to become a sold-to and ship-to, we work out the partner profile, cross-reference, and output setup with you instead of waiting on your team to figure it out.

When an EDI document fails

  • SPS: SPS monitors the flow of documents and works with your trading partners to resolve problems on the EDI side. The connector gives you role-based visibility into each transaction.
  • Arcus: We monitor daily and look for problems before anyone reports them, including partner rejections and missing acknowledgments. We follow up with the trading partner directly.

When a document fails in SAP

  • SPS: SPS's site covers monitoring and support on the EDI side. It doesn't say who investigates a failure inside your SAP system, so ask who owns an order that stops at IDoc status 51. If the answer is your team, that is an SAP resource you will need to have.
  • Arcus: Our monitoring covers IDoc failures inside SAP as well as the EDI layer, and our team supports the SAP side, so we find the cause and fix it. One team owns both sides, so nothing gets passed between EDI support and SAP support.

Partner changes

  • SPS: SPS reports managing 9,000 retailer changes a year, handled by its team.
  • Arcus: Spec changes, new document types, and version upgrades are handled by CONTAX and included, with no change-order process.

Support hours

  • SPS: 24x7 support.
  • Arcus: Business days, 7:30 AM to 5:30 PM Eastern, with extended coverage by arrangement.

Pricing

  • SPS: Subscription-based pricing, set by quote. Adding new partners and requesting changes may be quoted and billed separately, so ask what is covered by the subscription and what is not, including which support is included and which is not.
  • Arcus: Per transaction, billed monthly, with no implementation fees or per-partner charges. Support is included at no extra charge, and so are map changes and new partner onboarding.

Beyond EDI

  • SPS: Sales and inventory data, item data sharing, marketplace and dropship order automation, and PDF order automation.
  • Arcus: API, file, and system integrations alongside EDI, including REST, SOAP, XML, JSON, and CSV.

The partner side is where SPS is strongest. The SAP side is where the two models differ most, so that is the part to press on in any demo.

SPS details are taken from SPS Commerce's public pages as of November 2026: SAP S/4HANA EDI integration, Fulfillment EDI, and Why SPS.

Where Arcus Is a Strong Fit

Arcus tends to fit when the hard part of your EDI isn't the connection to the partner. It's what happens inside SAP.

  • Your failures happen in SAP, not in the EDI layer - An inbound 850 lands as an ORDERS IDoc and stops at status 51 because the ship-to isn't in EDPAR. An 810 never goes out because the output condition record is missing. Arcus monitoring covers the full transaction, including IDoc failures inside SAP, and status IDocs are sent back so SAP shows where each document stands.
  • Your partners aren't all retailers - Manufacturing releases (830, 862), 3PL warehouse documents (940, 945, 943, 944), and EDIFACT all come with partner-specific habits. Arcus maps are built to the partner's spec and your SAP setup, one partner at a time.
  • You want to integrate a new process into SAP - A new 3PL, a new document type, or a new way of fulfilling orders usually changes something inside SAP as well as in the EDI. Because our team knows SAP, we work with you on the whole process and make suggestions for process improvements along the way.
  • You're coming off a legacy translator - Years of business rules are usually buried in Gentran or IBM B2Bi maps. Our team reads those maps directly.
  • You can't afford a big capital expense to migrate - Arcus is a per-transaction subscription billed monthly, so your cost follows your volume. There are no implementation fees and no per-partner charges, and map changes and new partner onboarding are included.
  • You want one team - The people who build your maps are the people who support them. They are full-time CONTAX employees, not subcontractors.

An order that reaches SAP and stops at status 51 isn't an EDI success. It's an SAP support ticket waiting for your team.

Questions to Ask Either Provider

Whichever names are on your whiteboard, these five questions will tell you more than a feature list.

  1. When an inbound order fails in SAP with IDoc status 51, who investigates and who fixes it?
  2. When a trading partner changes its spec, who makes the map change, and is there a charge?
  3. What does adding the tenth partner cost? The fiftieth?
  4. Who talks to my trading partners during testing and after go-live?
  5. Where will my business rules live - in the map, in the network, or in SAP?

Ask us the same questions. The right answer depends on your partners, your SAP landscape, and how much EDI knowledge you want to keep in-house.

A network connects you to your partners. Someone still has to connect your partners to SAP.

If you're weighing EDI options as part of an SAP project, please reach out at info@contax.com and ask for Jodi. We're happy to have a no-obligation conversation.

About the Author

Jodi Abrams

Jodi is an expert in SAP and eCommerce integration, and is Vice President of Applications for CONTAX.

Talk to Our Team

Questions about SAP, EDI or Acumatica? We're glad to help.