Integrating with JCPenney through CommerceHub (EDI):
- CommerceHub will provide testing instructions as well as an FTP (or VAN) for testing and production.
- If you have never used custom company settings before, enable the client setting Enable Custom Company Settings.
- Navigate to Toolbox > Custom Settings, and create the following settings:
- JCPenneyReceiverID – ISA ID provided by CommerceHub
- JcPenney Customer ISA ID – typically the client’s phone number is used
A scheduled task will need to be set up for each of the plugins:
- Note: ISAControlNumber, GSControlNumber, and STControlNumber can all start at 1. The tracking and inventory exports will increment this number accordingly.
- Inventory Export (846): Plugin is named “SH JCPenney ProductExport EDI 846”
Order Import (850): Plugin is named “SH JCPenney EDI Order Import”
- The JCPenny SKU is required on the 846, and is pulled from the product custom column “JCPenney_SKU”.
Tracking Export (856): Plugin is named “SH JCPenney EDI 856”
- The plugin will pull the order files from the FTP (or VAN), create the orders in SellerCloud, and then send back a 997 acknowledgement for each file sent. The 997 will be placed on the server defined in the scheduled task, in the /incoming/intchg directory (for FTP).
- Important Note: When using FTP with CommerceHub, all documents for all of your CommerceHub integrations are sent to the same directory on the FTP. Therefore, if you are using FTP instead of VAN, the setting to “Delete files after processing” on the task should be set to FALSE, so files from other integrations do not get deleted. To alert the plugin that the JCP order files need to be deleted once they are processed, the Queued Job Note on the Scheduled Task should be set to FTP.
- The plugin will mark orders as SourceNotifiedForShipping once they are sent to JCP, so this field should be used in the saved search to select orders to update tracking for.