Skip to content

CuraScript SD EDI
integration guide.

Plan your CuraScript SD EDI integration using 2 listed document types across 1 channel. Compare channels, map business records and test the operational handoff.

Book an EDI demo Explore EDI documents
Listed documents
2
Partner document references
Listed channels
1
CuraScript SD by Evernorth
Implementation
Plan
Map, validate and reconcile

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Implementation guide

CuraScript SD: EDI implementation plan

Build a reliable EDI workflow for CuraScript SD. Use 2 document types across 1 channel to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 852 Product Activity DataListed on 1 channel: CuraScript SD by Evernorth product activity report

item, location, activity type and reporting period
  • Keep sales, returns and stock movements in separate measures.
  • Replace a corrected reporting period without counting the original activity twice.
X12 867 Product Transfer And Resale ReportListed on 1 channel: CuraScript SD by Evernorth product transfer and resale record

product, transfer or resale reference and reporting period
  • Keep a transfer between locations separate from a sale to an end customer.
  • Deduplicate corrected resale reports before calculating rebates or channel demand.

Implementation steps

  1. Choose the trading account and channel

    Choose among CuraScript SD by Evernorth. Confirm the business unit and account before copying a mapping from another channel.

  2. Map records and assign owners

    Start with product activity report, product transfer and resale record. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the CuraScript SD production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using item, location, activity type and reporting period. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for CuraScript SD

2 transactions across 1 channel.

Document flow

Example document relationships for CuraScript SD

Where each document sits in its trading cycle, based on the 2 document types listed for CuraScript SD across 1 channel. These are example relationships; the trading agreement determines the required sequence.

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed for CuraScript SD
  2. 846 Inventory Inquiry / Advice not listed for CuraScript SD
  3. 852 Product Activity Data
LEGACY EDI MIGRATION FUND

Still with a legacy EDI vendor? We cover the buyout.

Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.

Check your eligibility for the EDI migration fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more

Related references

Partners with related document listings

Compare document requirements for similar business processes.

Cardinal Health, Inc. 11 docs · 3 channels Granite City Electric 10 docs · 1 channel Cencora (ASD Health Care) (formerly AmerisourceBergen) 6 docs · 1 channel BioCare, Inc. 5 docs · 1 channel The Home Depot 48 docs · 11 channels Nordstrom 28 docs · 8 channels JCPenney 25 docs · 20 channels Target 23 docs · 4 channels Saks Fifth Avenue & Saks OFF 5th 21 docs · 10 channels NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels Ulta Beauty 18 docs · 3 channels Macy's 17 docs · 5 channels Master Electronics 16 docs · 4 channels Dot Foods, Inc. 14 docs · 2 channels Boscov's Department Stores 13 docs · 2 channels Bloomingdale's 12 docs · 3 channels PetSmart 11 docs · 2 channels Kroger Modernized Systems 10 docs · 1 channel Core-Mark (via SPS Commerce) 9 docs · 1 channel Sportsman's Warehouse 8 docs · 1 channel Superior Communications 7 docs · 1 channel

Showing 21 of 37 references

Browse the full directory

FAQ

CuraScript SD EDI questions

Which EDI documents are listed for CuraScript SD?

X12 852 Product Activity Data; X12 867 Product Transfer And Resale Report. Confirm which documents, directions and versions apply to your account.

How should I choose the CuraScript SD EDI channel?

The directory lists 1 channels for CuraScript SD, including CuraScript SD by Evernorth. Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the CuraScript SD mapping preserve?

For X12 852 Product Activity Data, plan around item, location, activity type and reporting period. For X12 867 Product Transfer And Resale Report, use product, transfer or resale reference and reporting period. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean CuraScript SD accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching CuraScript SD EDI?

Keep sales, returns and stock movements in separate measures. Replace a corrected reporting period without counting the original activity twice. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Get started