---
schema_version: "1"
id: a9dc13e3d257b87b3699d985ea5674785f9844f26194fcf96a691a3aafe66e85
title: Data Input and Output
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_data_input_output_overview.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_data_input_output_overview.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 56acc6ee977499f7fa0f73375da7ed96cfd866740b8735f5edf396fedd4ece54
description: Import to and export from staging, development, and production instances and replicate between instances. If your storefront uses a third-party application, you’re responsible for managing feeds into the catalog. Create feeds from B2C Commerce for other backend systems, such as an order management system (OMS), enterprise resource planning system (ERP), product information management system (PIM), or warehouse management system (WMS).
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Data Input and Output

Import to and export from staging, development, and production instances and replicate between instances. If your storefront uses a third-party application, you’re responsible for managing feeds into the catalog. Create feeds from B2C Commerce for other backend systems, such as an order management system (OMS), enterprise resource planning system (ERP), product information management system (PIM), or warehouse management system (WMS).

![Diagram of B2C Commerce data input and output overview](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_data_io_slide_01.gif)

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col>
        <col>
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d133262e43">B2C Commerce Feature</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d133262e46">Description</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="B2C Commerce Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e43 ">Import and Export</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e46 ">
            <p>Feeds data from external systems into B2C Commerce, such as product,
              pricing, and inventory information. You also Import and Export to move data
              from one instance type to another. </p>
            <p>Create XML feed files that conform to B2C
              Commerce schemas to import data into B2C Commerce. </p>
            <p>We recommend using the scheduled job feature to automate data import and
              export. Developers, administrators, and merchants work together to determine
              the frequency and schedule of import feeds. Developers are responsible for
              implementing the cartridges. Admins are responsible for creating the XML
              files containing data from the systems of record for products, pricing, and
              other data. They’re also responsible for configuring the jobs required to
              run the import. </p>
            <p style="margin-bottom:0;">Data is validated during import. If the import experiences too many errors,
              it can fail. To recover from a failed import, you must successfully complete
              another import. </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="B2C Commerce Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e43 ">Data Replication and Code Replication</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e46 ">Securely moves data and code between instances. Replication is a one-way
            process from Staging to either a Development or Production instances. You can
            roll back from a replication to the previous version of the instance.</td>

        </tr>
        <tr class="">
          <td data-label="B2C Commerce Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e43 ">Code Upload</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e46 ">Used to upload code from a developer's local machine via UX Studio to a
            Sandbox or Staging instance. Developers are responsible for code
            upload.</td>

        </tr>
        <tr class="">
          <td data-label="B2C Commerce Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e43 ">Catalog Feeds</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d133262e46 ">
            <p style="margin-bottom:0;">Used to process .zip files. This feature is only for additional information
              that you add to the catalog that isn't part of the normal catalog import and
              export process. </p>
          </td>

        </tr>
      </tbody>
    </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note The Batch Processing feature isn't used for data input and output.