Sell on JC Penney

Integrating with JCPenney through CommerceHub (EDI)

  1. CommerceHub will provide testing instructions as well as an FTP (or VAN) for testing and production.
  2. If you have never used custom company settings before, enable the client setting Enable Custom Company Settings.
  3. Navigate to Toolbox > Custom Settings (on the DEFAULT company), and create the following settings:
    1. JCPenneyReceiverID – ISA ID provided by CommerceHub
    2. JcPenney Customer ISA ID – typically the client’s phone number is used
    3. GS1_CompanyPrefix – used by SellerCloud plugin
    4. ISAControlNumber
    5. GSControlNumber
    6. STControlNumber
    • Note: ISAControlNumber, GSControlNumber, and STControlNumber can all start at 1. The tracking and inventory exports will increment this number accordingly.
  4. The plugin requires a custom column for orders to be created: IsShipToStore (boolean).
  5. A scheduled task must be set up for the following plugins:
    1. Inventory Export (846): Plugin is named “SH JCPenney ProductExport EDI 846.” The JCPenney SKU is required on the 846, and is pulled from the product custom column “JCPenney_SKU.”
    2. Order Import (850): Plugin is named “SH JCPenney EDI Order Import”:
      • Ship To Store orders will be marked as such in an order custom column “IsShipToStore.”
      • The plugin will pull the order files from the FTP (or VAN), create the orders in SellerCloud, and send back a 997 acknowledgment for each file sent. The 997 will be placed on the server defined in the scheduled task. For FTP, the Queued Job Note in the scheduled task must be set to “FTP” so the plugin will know to drop the file in the “outgoing” folder (versus VAN, where the file is dropped in the root directory).
      Important! 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.
    3. Tracking Export (856): Plugin is named “SH JCPenney EDI 856”
      • The SSCC code generated by the packing slip plugin will be sent to JCP on the tracking export for Ship To Store orders.
      • 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
  6. Packing Slip: Plugin is named “JCPenney Packing Slip” will be installed by SellerCloud Support and does not need a scheduled task.
  • The plugin will generate an SSCC code for each package in the order for Ship To Store orders. The SSCC barcode and ID will be printed on the invoice and saved in SellerCloud to be used by the tracking export plugin.
  • The plugin generates two pages: The first page is the packing slip, and the second page is generated with the SSCC ID Label that should be attached to the outside of the package.
  • The SSCC code starts with the GS1 Company Prefix, pulled from the custom company setting “GS1_CompanyPrefix” set on the default company.

Was this article helpful?

Related Articles