---
schema_version: "1"
id: 4f92e1137a0467f7c8160dc5d91e91f1f0204af141a2db2cffcde59a27b4d60a
title: Best Practices for Import/Export in B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_best_practices_for_import_export.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_best_practices_for_import_export.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 224a0c4587d15bd8d20f12b50aa0aa57ed456b6b9e5a918fee4f4e7984791550
description: We recommend that you follow established best practices for import and export.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Best Practices for Import/Export in B2C Commerce

We recommend that you follow established best practices for import and export.

If possible, for non-catalog feeds, create import feeds containing only the differences between the current and previous feed. These feeds are referred to as delta feeds. Such feeds are smaller and quicker to import and are less vulnerable to network interruptions.

To create a delta catalog feed, you can't include fields that replace the global import mode with a field-specific import mode. For example, it isn't possible to create a delta feed for a bundled product, because the bundled-products field always uses a REPLACE semantic.

You can't roll back feeds. Therefore, it’s best practice to archive at least the last feed, so that you can reimport an older version if the new feed can't be validated. However, B2C Commerce doesn't automatically clean out archives, so you must clean out archived files. Contact customer support for a demonstration cartridge for cleaning out archived files.