Feed table schema reference
Every feed has a dedicated MySQL table in the Adobe Commerce database. All feed tables share the same column structure. The table below lists each feed with its CLI feed name, indexer ID, and feed table name.
Supported feeds
Actual list of feeds depends on the installed SaaS Data Export package.
Feed (
--feed)Purpose
Indexer ID
Feed Table
Export Mode
productsProduct catalog (attributes, categories, images, etc.)
catalog_data_exporter_productscde_products_feedImmediate
productAttributesAttribute definitions and metadata. Used to define search schema.
catalog_data_exporter_product_attributescde_product_attributes_feedImmediate
categoriesCategories data
catalog_data_exporter_categoriescde_categories_feedImmediate
pricesProduct prices with customer group prices and tier prices
catalog_data_exporter_product_pricescde_product_prices_feedImmediate
variantsConfigurable product variants
catalog_data_exporter_product_variantscde_product_variants_feedImmediate
scopesWebsiteWebsite with store view codes
scopes_website_data_exporterscopes_website_data_exporterLegacy
scopesCustomerGroupCustomer group definitions
scopes_customergroup_data_exporterscopes_customergroup_data_exporterLegacy
productOverridesCalculated product permissions
catalog_data_exporter_product_overridescde_product_overrides_feedImmediate
categoryPermissions (EE)Raw category permissions data
catalog_data_exporter_category_permissionscde_category_permissions_feedImmediate
ordersSales orders status
sales_order_data_exporter_v2sales_data_exporter_orders_v2Legacy
The Export Mode column indicates how each feed collects and submits data:
- Immediate-mode feeds — Collect data, skip unchanged items using content hashes (hash deduplication), and submit updates in the same indexer run.
- Legacy-mode feeds (
scopesWebsite,scopesCustomerGroup,orders) — Store assembled data in the feed table first and submit it via a separate cron job.
Schema
Column
Type
Description
idINT (PK)
Auto-increment primary key
source_entity_idINT
Entity ID from the Commerce source table (for example,
catalog_product_entity.entity_id)feed_idVARCHAR
Unique identifier for a feed item. Computed as a hash of the item’s identity fields (for example,
sku + storeViewCode), not an auto-increment value.feed_dataJSON
Feed payload for this item. Only minimal information as entity identifier and scope is populated. When
PERSIST_EXPORTED_FEED=1 is set, full payload is stored.feed_hashVARCHAR
Content hash used for change detection. Computed from the payload, excluding timestamps (
modifiedAt, updatedAt). If the hash matches the previous export, the item is not re-submitted.is_deletedTINYINT
Soft-delete marker. Set to
1 when the entity is deleted in Commerce.modified_atTIMESTAMP
Last time this feed item was modified
statusINT
Submission status code from the last export attempt. See Feed submission and HTTP error handling.
errorsTEXT
JSON-encoded error details returned by the SaaS service for this item
metadataJSON
Internal sync flags and lock metadata info used by the export framework
Common diagnostic queries
Use the following SQL queries to inspect feed table state directly. Replace cde_products_feed with the table for the feed you are investigating. See Supported feeds for the full list of table names.
Find all items that have not been successfully exported:
SELECT source_entity_id, status, errors, modified_at
FROM cde_products_feed
WHERE status != 200
ORDER BY modified_at DESC
LIMIT 50;
Check export status for a specific SKU across all scopes:
SELECT p.sku, f.status, f.modified_at, f.is_deleted, f.feed_data, f.errors
FROM catalog_product_entity p
LEFT JOIN cde_products_feed f ON f.source_entity_id = p.entity_id
WHERE p.sku = 'ADB295';
recommendation-more-help
commerce-help-data-export