---
title: "JCPenney EDI Integration | Stacksync"
description: "JCPenney EDI: 13 listed document types, channel comparison, record mapping and validation guidance for your integration."
canonical: https://www.stacksync.com/edi/jcpenney
last_modified: 2026-09-15
---

# *JCPenney* EDI integration guide.

> For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md

Plan your JCPenney EDI integration using 13 listed document types across 20 channels. Compare channels, map business records and test the operational handoff.

[Book an EDI demo](https://www.stacksync.com/book-a-demo) Explore EDI documents

|  |  |  |
| --- | --- | --- |
| Listed documents | 13 | Partner document references |
| Listed channels | 20 | JCPenney Catalog → JCPenney (Stores Retail) (852) |
| Implementation | Plan | Map, validate and reconcile |

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

- Gladia Case study
- IDEXX
- MedPro Migrated from MuleSoft
- Eko Case study
- Ubicloud
- Vimeo
- Codility Migrated from Celigo
- ACERTUS Migrated from Heroku Connect
- Syringa Migrated from Matillion
- Truora
- Streaam Case study
- SEAL SQ
- Rinsed Migrated from Fivetran
- IA Capital Group Case study
- Meter
- Golden Pear Funding Migrated from Celigo

Implementation guide

## JCPenney: EDI implementation plan

Build a reliable EDI workflow for JCPenney. Use 13 document types across 20 channels 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 decision | Record and matching IDs | What to test |
| --- | --- | --- |
| [X12 850 Purchase Order](https://www.stacksync.com/edi/jcpenney/jcpenney-catalog/x12-850-purchase-order) Listed on 3 channels: JCPenney Catalog, JCPenney Retail, JCPenney Dropship (via Rithum) | **purchase order or sales order** buyer purchase order, order line and trading-party identifiers | Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. |
| [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/jcpenney/jcpenney-catalog/x12-860-purchase-order-change-request-buyer-initiated) Listed on 2 channels: JCPenney Catalog, JCPenney Retail | **buyer order-change request** original purchase order, change revision and affected line | Apply a quantity reduction to the existing order instead of creating another order. Test a cancellation arriving after allocation or shipment and route it to an exception owner. |
| [X12 824 Application Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-accounting-all-business-types-824/x12-824-application-advice) Listed on 1 channel: JCPenney (Accounting (All Business Types)) (824) | **application validation result** original document reference, error location and response status | Return an error for one line and associate it with that line rather than rejecting unrelated records. Keep application acceptance distinct from transport receipt and syntax acknowledgment. |
| [X12 820 Payment Order Remittance Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-all-business-remittance-advice/x12-820-payment-order-remittance-advice) Listed on 2 channels: JCPenney All Business Remittance Advice, JCPenney (Freight) (820) | **payment or remittance record** payment reference, invoice references and amounts applied | Allocate a partial payment across several invoices and preserve the remaining balances. Keep receipt of remittance information distinct from confirmation that funds settled. |
| [X12 810 Invoice](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-810/x12-810-invoice) Listed on 4 channels: JCPenney (eCom Catalog) (810), JCPenney Dropship (via Rithum), JCPenney (Stores Retail) (810)… | **accounts-receivable or accounts-payable invoice** invoice number, purchase order and invoice line | Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. |
| [X12 870 Order Status Report](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-870/x12-870-order-status-report) Listed on 2 channels: JCPenney (Stores Retail) (870), JCPenney (eCom Catalog) (870) | **order-status response** purchase order, status time and order line | Represent mixed line statuses without declaring the whole order shipped. Keep an older status report from overwriting a more recent fulfillment state. |
| [X12 753 Request For Routing Instructions](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-753/x12-753-request-for-routing-instructions) Listed on 1 channel: JCPenney (eCom Catalog \| Store Retail \| TMS) (753) | **routing request** routing request, purchase order and ready-to-ship date | Test an order split into two pickups and keep each routing request distinct. Handle a changed ready date while the original routing request is still open. |
| [X12 852 Product Activity Data](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-852/x12-852-product-activity-data) Listed on 2 channels: JCPenney (Stores Retail) (852), JCPenney (eCom Catalog) (852) | **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 856 Ship Notice Manifest](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-856/x12-856-ship-notice-manifest) Listed on 4 channels: JCPenney (eCom Catalog) (856), JCPenney Dropship (via Rithum), JCPenney (Stores Retail) (856)… | **shipment notice (ASN)** shipment, order, package and item references | Reconcile item quantities through shipment, order and packaging levels against the physical shipment. Test split shipments for one purchase order and prevent the second ASN from replacing the first. |
| [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum/x12-846-inventory-inquiry-advice) Listed on 1 channel: JCPenney Dropship (via Rithum) | **inventory availability record** item, location, quantity type and snapshot time | Distinguish on-hand, available and reserved quantities before publishing availability. Deliver an old snapshot after a new one and prevent stale stock from replacing current values. |
| [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-ecom-catalog-855/x12-855-purchase-order-acknowledgment) Listed on 1 channel: JCPenney (Stores Retail / eCom Catalog) (855) | **purchase-order response** original purchase order, response revision and order line | Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. |
| [X12 812 Credit Debit Adjustment](https://www.stacksync.com/edi/jcpenney/jcpenney-all-business-debit-credit/x12-812-credit-debit-adjustment) Listed on 1 channel: JCPenney All Business Debit - Credit | **credit or debit adjustment** adjustment reference, original invoice and reason | Test opposite credit/debit signs and verify their ledger effect. Apply a partial adjustment to the correct invoice line while preserving the original invoice. |
| [X12 754 Routing Instructions](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-754/x12-754-routing-instructions) Listed on 1 channel: JCPenney (eCom Catalog / Store Retail / TMS) (754) | **routing instruction** routing reference, order and shipment | Match instructions to the correct open routing request. Test a carrier reassignment after warehouse planning and require the shipping record to be updated. |

### Implementation steps

1. #### Choose the trading account and channel

   Choose among JCPenney Catalog, JCPenney (Accounting (All Business Types)) (824), JCPenney All Business Remittance Advice, JCPenney (eCom Catalog) (810) and the other channels listed below. Confirm the business unit and account before copying a mapping from another channel.
2. #### Map records and assign owners

   Start with purchase order or sales order, buyer order-change request, application validation result. 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 JCPenney production handoff and save the results of each approved test.
4. #### Check results after launch

   Match records between systems using buyer purchase order, order line and trading-party identifiers. 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.

### Related documents and resources

- [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook)
- [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist)
- [Evaluate your integration requirements](https://www.stacksync.com/blog/integration-evaluation-worksheet)

**Sources.** Directory data as of 2026-05-07. Sources reviewed 2026-09-15.

- [X12 transaction-set directory](https://x12.org/products/transaction-sets)
- [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/)
- [JCPenney document reference](https://www.orderful.com/network/jcpenney)

Document catalog

## EDI documents listed for JCPenney

25 transactions across 20 channels.

### [JCPenney Catalog](https://www.stacksync.com/edi/jcpenney/jcpenney-catalog)

2 docs

- [X12 850 Purchase Order](https://www.stacksync.com/edi/jcpenney/jcpenney-catalog/x12-850-purchase-order)
- [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/jcpenney/jcpenney-catalog/x12-860-purchase-order-change-request-buyer-initiated)

### [JCPenney (Accounting (All Business Types)) (824)](https://www.stacksync.com/edi/jcpenney/jcpenney-accounting-all-business-types-824)

1 doc

- [X12 824 Application Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-accounting-all-business-types-824/x12-824-application-advice)

### [JCPenney All Business Remittance Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-all-business-remittance-advice)

1 doc

- [X12 820 Payment Order Remittance Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-all-business-remittance-advice/x12-820-payment-order-remittance-advice)

### [JCPenney (eCom Catalog) (810)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-810)

1 doc

- [X12 810 Invoice](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-810/x12-810-invoice)

### [JCPenney (Stores Retail) (870)](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-870)

1 doc

- [X12 870 Order Status Report](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-870/x12-870-order-status-report)

### [JCPenney Retail](https://www.stacksync.com/edi/jcpenney/jcpenney-retail)

2 docs

- [X12 850 Purchase Order](https://www.stacksync.com/edi/jcpenney/jcpenney-retail/x12-850-purchase-order)
- [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/jcpenney/jcpenney-retail/x12-860-purchase-order-change-request-buyer-initiated)

### [JCPenney (eCom Catalog | Store Retail | TMS) (753)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-753)

1 doc

- [X12 753 Request For Routing Instructions](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-753/x12-753-request-for-routing-instructions)

### [JCPenney (Stores Retail) (852)](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-852)

1 doc

- [X12 852 Product Activity Data](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-852/x12-852-product-activity-data)

### [JCPenney (eCom Catalog) (856)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-856)

1 doc

- [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-856/x12-856-ship-notice-manifest)

### [JCPenney Dropship (via Rithum)](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum)

4 docs

- [X12 850 Purchase Order](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum/x12-850-purchase-order)
- [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum/x12-846-inventory-inquiry-advice)
- [X12 810 Invoice](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum/x12-810-invoice)
- [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum/x12-856-ship-notice-manifest)

### [JCPenney (Stores Retail / eCom Catalog) (855)](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-ecom-catalog-855)

1 doc

- [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-ecom-catalog-855/x12-855-purchase-order-acknowledgment)

### [JCPenney (Stores Retail) (810)](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-810)

1 doc

- [X12 810 Invoice](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-810/x12-810-invoice)

### [JCPenney (eCom Catalog) (870)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-870)

1 doc

- [X12 870 Order Status Report](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-870/x12-870-order-status-report)

### [JCPenney (eCom Catalog) (852)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-852)

1 doc

- [X12 852 Product Activity Data](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-852/x12-852-product-activity-data)

### [JCPenney (Custom Decorating) (810)](https://www.stacksync.com/edi/jcpenney/jcpenney-custom-decorating-810)

1 doc

- [X12 810 Invoice](https://www.stacksync.com/edi/jcpenney/jcpenney-custom-decorating-810/x12-810-invoice)

### [JCPenney (Stores Retail) (856)](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-856)

1 doc

- [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-856/x12-856-ship-notice-manifest)

### [JCPenney All Business Debit - Credit](https://www.stacksync.com/edi/jcpenney/jcpenney-all-business-debit-credit)

1 doc

- [X12 812 Credit Debit Adjustment](https://www.stacksync.com/edi/jcpenney/jcpenney-all-business-debit-credit/x12-812-credit-debit-adjustment)

### [JCPenney (Freight) (820)](https://www.stacksync.com/edi/jcpenney/jcpenney-freight-820)

1 doc

- [X12 820 Payment Order Remittance Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-freight-820/x12-820-payment-order-remittance-advice)

### [JCPenney (eCom Catalog / Store Retail / TMS) (754)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-754)

1 doc

- [X12 754 Routing Instructions](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-754/x12-754-routing-instructions)

### [Channel 47830](https://www.stacksync.com/edi/jcpenney/channel-47830)

1 doc

- [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/jcpenney/channel-47830/x12-856-ship-notice-manifest)

Document flow

## Example document relationships for JCPenney

Where each document sits in its trading cycle, based on the 13 document types listed for JCPenney across 20 channels. These are example relationships; the trading agreement determines the required sequence.

### Order-to-cash

All example steps listed

1. [850 Purchase Order](https://www.stacksync.com/edi/jcpenney/jcpenney-catalog/x12-850-purchase-order)
2. [855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-ecom-catalog-855/x12-855-purchase-order-acknowledgment)
3. [856 Ship Notice Manifest](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-856/x12-856-ship-notice-manifest)
4. [810 Invoice](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-810/x12-810-invoice)

### Catalog & inventory

Some example steps listed

1. 832 Price / Sales Catalog not listed for JCPenney
2. [846 Inventory Inquiry Advice](https://www.stacksync.com/edi/jcpenney/jcpenney-dropship-via-rithum/x12-846-inventory-inquiry-advice)
3. [852 Product Activity Data](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-852/x12-852-product-activity-data)

- 753 Request For Routing Instructions — is listed on 1 of JCPenney's 20 channels
- 754 Routing Instructions — is listed on 1 of JCPenney's 20 channels
- 810 Invoice — is listed on 4 of JCPenney's 20 channels
- 812 Credit Debit Adjustment — is listed on 1 of JCPenney's 20 channels
- 820 Payment Order Remittance Advice — is listed on 2 of JCPenney's 20 channels
- 824 Application Advice — is listed on 1 of JCPenney's 20 channels
- 846 Inventory Inquiry Advice — is listed on 1 of JCPenney's 20 channels
- 850 Purchase Order — is listed on 3 of JCPenney's 20 channels
- 852 Product Activity Data — is listed on 2 of JCPenney's 20 channels
- 855 Purchase Order Acknowledgment — is listed on 1 of JCPenney's 20 channels
- 856 Ship Notice Manifest — is listed on 4 of JCPenney's 20 channels
- 860 Purchase Order Change Request Buyer Initiated — is listed on 2 of JCPenney's 20 channels

Network context

## JCPenney channel references for Rithum

These network names are derived from the listed JCPenney channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.

### Rithum

25 channels · 23 trading partners in the catalog

JCPenney channel on this network: JCPenney Dropship (via Rithum)

Most frequently listed documents

- 850 25 ch
- 856 25 ch
- 846 24 ch
- 810 20 ch
- 870 10 ch

Also listed with Rithum

- [Staples Advantage](https://www.stacksync.com/edi/staples-adv)
- [HD Supply Holdings, Inc.](https://www.stacksync.com/edi/hd-supply-commerce-hub)
- [Men's Wearhouse via DSCO](https://www.stacksync.com/edi/mens-wearhouse)
- [URBN](https://www.stacksync.com/edi/urbn)
- [JOANN](https://www.stacksync.com/edi/joann)
- [Michaels Stores](https://www.stacksync.com/edi/michaels-stores)

LEGACY EDI MIGRATION FUND

## Still with a legacy EDI vendor? Ask about a contract buyout.

Stacksync can buy out your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. Eligibility and terms are confirmed on a call.

[Check your eligibility for the EDI migration fund](https://www.stacksync.com/book-a-demo)

|  |  |
| --- | --- |
|  | [Migrate from SPS Commerce](https://www.stacksync.com/sps-commerce-alternative) |
|  | 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](https://www.stacksync.com/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 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more

Related references

## Partners with related document listings

Compare document requirements for similar business processes.

[The Home Depot 48 docs · 11 channels](https://www.stacksync.com/edi/the-home-depot) [Nordstrom 28 docs · 8 channels](https://www.stacksync.com/edi/nordstrom) [Amazon 24 docs · 4 channels](https://www.stacksync.com/edi/amazon) [NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) [Dillard's Department Stores, Inc. 30 docs · 3 channels](https://www.stacksync.com/edi/dillards-department-stores-inc) [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [Macy's 17 docs · 5 channels](https://www.stacksync.com/edi/macys) [AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) [PetSmart 11 docs · 2 channels](https://www.stacksync.com/edi/petsmart) [Bealls Inc. 11 docs · 2 channels](https://www.stacksync.com/edi/bealls-inc) [Costco 55 docs · 12 channels](https://www.stacksync.com/edi/costco) [Walmart 32 docs · 8 channels](https://www.stacksync.com/edi/walmart) [Saks Fifth Avenue & Saks OFF 5th 21 docs · 10 channels](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th) [Lowe's 13 docs · 2 channels](https://www.stacksync.com/edi/lowes) [Kroger Modernized Systems 10 docs · 1 channel](https://www.stacksync.com/edi/kroger-modernized-systems) [Core-Mark (via SPS Commerce) 9 docs · 1 channel](https://www.stacksync.com/edi/coremark-pfgcoremark) [Jordan's Furniture 8 docs · 1 channel](https://www.stacksync.com/edi/jordans-furniture) [Sportsman's Warehouse 8 docs · 1 channel](https://www.stacksync.com/edi/sportsmans-warehouse) [PFG Customized Distribution 7 docs · 1 channel](https://www.stacksync.com/edi/pfg-customized-distribution) [Nebraska Furniture Mart (NFM) 7 docs · 1 channel](https://www.stacksync.com/edi/nebraska-furniture-mart) [PFG PerformanceFoodservice North 7 docs · 1 channel](https://www.stacksync.com/edi/pfg-performancefoodservice-north)

[Browse the full directory](https://www.stacksync.com/edi)

FAQ

## JCPenney EDI questions

### Which EDI documents are listed for JCPenney?

X12 850 Purchase Order; X12 860 Purchase Order Change Request Buyer Initiated; X12 824 Application Advice; X12 820 Payment Order Remittance Advice; X12 810 Invoice; X12 870 Order Status Report; X12 753 Request For Routing Instructions; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.

### How should I choose the JCPenney EDI channel?

The directory lists 20 channels for JCPenney, including JCPenney Catalog, JCPenney (Accounting (All Business Types)) (824), JCPenney All Business Remittance Advice, JCPenney (eCom Catalog) (810). Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

### Which identifiers should the JCPenney mapping preserve?

For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 860 Purchase Order Change Request Buyer Initiated, use original purchase order, change revision and affected line. Use the partner guide to locate these values and check their allowed formats.

### Does a successful EDI receipt mean JCPenney 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 JCPenney EDI?

Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

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

[Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)
